Sam Yamashita sotayamashita

Warning

This was created around 2025-05-20, so the information may be out of date. Please refer to the official documentation first. Claude Code IDE integrations (Official Docs)

Installing Claude Code Extension in Cursor IDE

Since the official documentation method doesn't work for Cursor IDE, here's a working solution.

Note: This workaround likely works for other Visual Studio Code forks (including popular forks like Cursor and Windsurf) that support VSIX extensions but aren't automatically detected by Claude Code.

Prerequisites

"node_modules/@anthropic-ai/claude-code": {
      "version": "1.0.3",

329814-  if (
329815-    /\bthink harder\b/.test(B) ||
329816-    /\bthink intensely\b/.test(B) ||
329817- /\bthink longer\b/.test(B) ||

➜ xcrun simctl list devices --json | jq '.devices.'"com.apple.CoreSimulator.SimRuntime.iOS-14-4"[].name

iOS 14.4

"iPhone 8"
"iPhone 8 Plus"
"iPhone 11"
"iPhone 11 Pro"
"iPhone 11 Pro Max"
"iPhone SE (2nd generation)"

前提

$ pyenv versions
  system (2.7.16)
  2.7.0
* 3.7.0 (set by /path/to/.pyenv/version)

Python 2.7.16 が呼ばれることを期待

Sidekiq::RetrySet.new.clear
Sidekiq::ScheduledSet.new.clear
Sidekiq::Stats.new.reset
Sidekiq::DeadSet.new.clear
Sidekiq.redis { |conn| conn.flushdb }

https://stackoverflow.com/questions/24886371/how-to-clear-all-the-jobs-from-sidekiq

	{
	"mcpServers": {
	"deepwiki": {
	"command": "<TODO: Replace with output from `which -a npx` (use the Volta path)>",
	"args": [
	"-y",
	"mcp-remote",
	"https://mcp.deepwiki.com/sse"
	]
	}

	#!/usr/bin/env bash
	#
	# Monitors changes to macOS plist files by capturing the state before and after
	# modifications. Creates a diff of the changes and saves them to a timestamped
	# directory on the Desktop.
	#
	# This script is useful for:
	# - Debugging preference changes for dotfiles
	# - Documenting system modifications
	# - Identifying what settings are modified by GUI changes

	Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
	- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
	- Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
	- Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
	- Conclusion, classifications, or results should ALWAYS appear last.
	- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
	- What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p

	/**
	* https://github.com/sotayamashita/auto-skip-x
	*/
	const observer = new MutationObserver((mutationList, observer) => {
	const skipIntroButton = document.querySelector("button.watch-video--skip-content-button");
	if (skipIntroButton) {
	skipIntroButton.click();
	}
	});