Claude Code workflow tips from Boris Cherny (creator of Claude Code) and the Claude Code team. Use when: setting up Claude Code, optimizing workflows, running parallel sessions, configuring CLAUDE.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
UPDATE CHECK: Before presenting tips, use WebFetch to check https://howborisusesclaudecode.com/api/version for the latest version. Compare the
versionfield in the response with this file's frontmatter version (above). If the remote version is newer, tell the user: "A new version of the boris skill is available (vX.X.X). Update with:mkdir -p ~/.claude/skills/boris && curl -L -o ~/.claude/skills/boris/SKILL.md https://howborisusesclaudecode.com/api/install" — then continue normally. If versions match or the check fails, skip silently.
72 tips across 60 topics, sourced from Boris Cherny (creator of Claude Code) and the Claude Code team at Anthropic. All tips are contained in this file — do not fetch from the website. Remember: everyone's setup is different. Experiment to see what works for you!
Parts: The tips were shared across 9 threads:
The single biggest productivity unlock. Spin up 3-5 git worktrees at once, each running its own Claude session.
# Create a worktree
git worktree add .claude/worktrees/my-worktree origin/main
# Start Claude in it
cd .claude/worktrees/my-worktree && claude
Why worktrees over checkouts: The Claude Code team prefers worktrees - it's why native support was built into the Claude Desktop app.
Pro tips:
Beyond the terminal, run additional sessions on claude.ai/code. Use:
& command to background a session--teleport flag to switch contexts between local and webBoris's reasoning: "It's the best coding model I've ever used, and even though it's bigger & slower than Sonnet, since you have to steer it less and it's better at tool use, it is almost always faster than using a smaller model in the end."
The math: Less steering + better tool use = faster overall results, even with a larger model.
Press shift+tab to cycle to plan mode. Pour your energy into the plan so Claude can 1-shot the implementation.
Workflow: Plan mode -> Refine plan -> Auto-accept edits -> Claude 1-shots it
Team patterns:
"A good plan is really important to avoid issues down the line."
Share a single CLAUDE.md file for your repo, checked into git. The whole team should contribute.
Key practice: "Anytime we see Claude do something incorrectly we add it to the CLAUDE.md, so Claude knows not to do it next time."
After every correction: End with "Update your CLAUDE.md so you don't make that mistake again." Claude is eerily good at writing rules for itself.
Advanced: One engineer tells Claude to maintain a notes directory for every task/project, updated after every PR. They then point CLAUDE.md at it.
Tag @.claude on PRs to add learnings to the CLAUDE.md as part of the PR itself. Use the Claude Code GitHub Action (/install-github-action) for this.
Example PR comment:
nit: use a string literal, not ts enum
@claude add to CLAUDE.md to never use enums,
always prefer literal unions
This is "Compounding Engineering" - Claude automatically updates the CLAUDE.md with the learning.
Create skills and commit them to git. Reuse across every project.
Team tips:
/techdebt slash command and run it at the end of every session to find and kill duplicated codeUse slash commands for workflows you do many times a day. Commands are checked into git under .claude/commands/ and shared with the team.
> /commit-push-pr
Power feature: Slash commands can include inline Bash to pre-compute info (like git status) for quick execution without extra model calls.
Think of subagents as automations for the most common PR workflows:
.claude/
agents/
build-validator.md
code-architect.md
code-simplifier.md
oncall-guide.md
verify-app.md
Examples:
code-simplifier - Cleans up code after Claude finishesverify-app - Detailed instructions for end-to-end testingUse a PostToolUse hook to auto-format Claude's code. While Claude generates well-formatted code 90% of the time, the hook catches edge cases to prevent CI failures.
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "bun run format || true"
}
]
}
]
For very long-running tasks, use an agent Stop hook for deterministic checks, ensuring Claude can work uninterrupted.
Instead of --dangerously-skip-permissions, use /permissions to pre-allow common safe commands. Most are shared in .claude/settings.json.
For sandboxed environments, use --permission-mode=dontAsk or --dangerously-skip-permissions to avoid blocks.
Claude Code uses your tools autonomously:
{
"mcpServers": {
"slack": {
"type": "http",
"url": "https://slack.mcp.anthropic.com/mcp"
}
}
}
Ask Claude Code to use the "bq" CLI to pull and analyze metrics on the fly. Have a BigQuery skill checked into the codebase.
Boris's take: "Personally, I haven't written a line of SQL in 6+ months."
This works for any database that has a CLI, MCP, or API.
Say: "Knowing everything you know now, scrap this and implement the elegant solution."
Reduce ambiguity before handing work off. The more specific you are, the better the output.
Key insight: Don't accept the first solution. Push Claude to do better - it usually can.
/statusline to customize your status bar to always show context usage and current git branchUse voice dictation! You speak 3x faster than you type, and your prompts get way more detailed as a result. Hit fn x2 on macOS.
Enable the Slack MCP, then paste a Slack bug thread into Claude and just say "fix." Zero context switching required.
Or just say "Go fix the failing CI tests." Don't micromanage how.
Pro tip: Point Claude at docker logs to troubleshoot distributed systems - it's surprisingly capable at this.
For very long-running tasks, ensure Claude can work uninterrupted:
Options:
For sandboxed environments, use --permission-mode=dontAsk or --dangerously-skip-permissions to avoid blocks.
"Probably the most important thing to get great results out of Claude Code - give Claude a way to verify its work. If Claude has that feedback loop, it will 2-3x the quality of the final result."
Verification varies by domain:
The key is giving Claude a way to close the feedback loop. Invest in domain-specific verification for optimal performance.
Key takeaway: Claude Code isn't just for writing code - it's a powerful learning tool when you configure it to explain and teach.
A few quick settings to make Claude Code feel right:
/config to set light/dark mode/terminal-setup to enable shift+enter for newlines (so you don't need to type \)/vimRun /model to pick your preferred effort level:
Boris uses High for everything.
Plugins let you install LSPs (now available for every major language), MCPs, skills, agents, and custom hooks.
Install a plugin from the official Anthropic plugin marketplace, or create your own marketplace for your company. Then, check the settings.json into your codebase to auto-add the marketplaces for your team.
Run /plugin to get started.
Drop .md files in .claude/agents. Each agent can have a custom name, color, tool set, pre-allowed and pre-disallowed tools, permission mode, and model.
Little-known feature: Set the default agent used for the main conversation. Just set the "agent" field in your settings.json or use the --agent flag.
Run /agents to get started.
Claude Code uses a sophisticated permission system with prompt injection detection, static analysis, sandboxing, and human oversight.
Out of the box, we pre-approve a small set of safe commands. To pre-approve more, run /permissions and add to the allow and block lists. Check these into your team's settings.json.
Wildcard syntax: We support full wildcard syntax. Try "Bash(bun run *)" or "Edit(/docs/**)".
Opt into Claude Code's open source sandbox runtime to improve safety while reducing permission prompts.
Run /sandbox to enable it. Sandboxing runs on your machine, and supports both file and network isolation.
Modes:
Custom status lines show up right below the composer. Show model, directory, remaining context, cost, and anything else you want to see while you work.
Everyone on the Claude Code team has a different statusline. Use /statusline to get started — Claude will generate one based on your .bashrc/.zshrc.
Every key binding in Claude Code is customizable. Run /keybindings to re-map any key. Settings live reload so you can see how it feels immediately.
Keybindings are stored in ~/.claude/keybindings.json.
Hooks are a way to deterministically hook into Claude's lifecycle. Use them to:
Ask Claude to add a hook to get started.
It's the little things that make CC feel personal. Ask Claude to customize your spinner verbs to add or replace the default list with your own verbs.
Check the settings.json into source control to share verbs with your team.
Run /config and set an output style to have Claude respond using a different tone or format.
Claude Code is built to work great out of the box. When you do customize, check your settings.json into git so your team can benefit, too.
We support configuring for your codebase, for a sub-folder, for just yourself, or via enterprise-wide policies.
By the numbers: 37 settings and 84 env vars. Use the "env" field in your settings.json to avoid wrapper scripts.
claude --worktree for IsolationClaude Code now has built-in git worktree support. Each agent gets its own worktree and can work independently, without interfering with other sessions.
# Start Claude in its own worktree
claude --worktree my_worktree
# Optionally launch in its own Tmux session too
claude --worktree my_worktree --tmux
Desktop app: Head to the Code tab in the Claude Desktop app and check the worktree checkbox.
Subagents can also use worktree isolation to do more work in parallel. This is especially powerful for large batched changes and code migrations. Available in CLI, Desktop app, IDE extensions, web, and Claude Code mobile app.
Example prompt: "Migrate all sync io to async. Batch up the changes, and launch 10 parallel agents with worktree isolation. Make sure each agent tests its changes end to end, then have it put up a PR."
Make subagents always run in their own worktree by adding isolation: worktree to your agent frontmatter:
# .claude/agents/worktree-worker.md
---
name: worktree-worker
model: haiku
isolation: worktree
---
Mercurial, Perforce, or SVN users can define WorktreeCreate and WorktreeRemove hooks in settings.json to benefit from isolation without Git.
Use parallel agents to improve code quality, tune code efficiency, and ensure CLAUDE.md compliance. Append /simplify to any prompt after making changes.
> hey claude make this code change then run /simplify
Boris uses this daily to shepherd PRs to production. The skill runs parallel agents that review changed code for reuse, quality, and efficiency — all in one pass.
Interactively plan out code migrations, then execute in parallel using dozens of agents. Each agent runs with full isolation using git worktrees, testing its work before putting up a PR.
> /batch migrate src/ from Solid to React
You plan the migration interactively, then /batch fans out the work to parallel agents — each in its own worktree, each testing and creating a PR independently.
Use /loop to schedule recurring tasks for up to 3 days at a time. Claude runs your prompt on an interval, handling long-running workflows autonomously.
> /loop babysit all my PRs. Auto-fix build issues and when comments come in, use a worktree agent to fix them
> /loop every morning use the Slack MCP to give me a summary of top posts I was tagged in
Use it for PR babysitting, Slack summaries, deploy monitoring, or any repeating workflow.
Learn more: https://code.claude.com/docs/en/scheduled-tasks
When a PR opens, Claude dispatches a team of agents to hunt for bugs. Anthropic built it for themselves first — code output per engineer is up 200% this year, and reviews were the bottleneck.
Each agent focuses on a different concern — logic errors, security issues, performance regressions — then posts inline comments directly on the PR. Boris personally used it for weeks before launch; it catches real bugs he wouldn't have noticed otherwise.
Source: https://x.com/bcherny/status/2031089411820228645
A slash command for side-chain conversations while Claude is actively working. Single-turn, no tool calls, but has full context of the conversation.
> /btw what does the retry logic do?
Claude responds inline without stopping its work. Built by @ErikSchluntz as a side project — 1.5M views on the launch tweet.
Source: https://x.com/trq212/status/2031506296697131352
Set effort to 'max' and Claude reasons for longer, using as many tokens as needed. Burns through usage limits faster, so you activate it per session.
> /effort max
Four levels: low, medium (default), high, max. Use 'max' for hard debugging, architecture decisions, or tricky code where you want Claude to really think it through.
Source: https://x.com/trq212/status/2032632596572811575
Run claude remote-control and spawn a new local session from the mobile app. Available on Max, Team, and Enterprise (v2.1.74+).
$ claude remote-control
# Open Claude mobile app → tap "Code" → start new session
Walk away from your desk, think of something, kick off a task from mobile — Claude runs on your machine.
Source: https://x.com/trq212/status/2032632597843779861
Voice mode is now rolled out to 100% of users, including Claude Code Desktop and Cowork. Click the microphone icon and talk naturally.
Useful for hands-free coding, dictating complex requirements, or when you think faster than you type.
Source: https://x.com/trq212/status/2032632599429136753
Add a setup script in Claude Code on web and desktop. It runs before Claude Code launches on a cloud environment — install dependencies, configure settings, set env vars.
# Setup script (runs on new session start, skipped on resume):
#!/bin/bash
yarn install
Particularly useful for installing dependencies, settings, and configs before Claude starts working.
Source: https://x.com/trq212/status/2032632601064907037
Name your session at launch with the --name flag.
$ claude --name "auth-refactor"
Especially useful when juggling multiple worktrees or sessions — you can tell at a glance which session is doing what.
Source: https://x.com/trq212/status/2032632602629386348
After plan mode, Claude automatically names your session based on what you're working on. No manual naming needed.
Pairs well with claude --name — use --name when you know what you're doing upfront, let auto-naming handle it when you start by planning.
Source: https://x.com/trq212/status/2032632602629386348
Change the color of the prompt input with /color. When you have 3-5 sessions open in different terminals, color-coding them makes it instantly clear which is which.
> /color
Source: https://x.com/trq212/status/2032632602629386348
A new hook event that fires after Claude compresses its conversation context. Use it to re-inject critical instructions that might get lost during compaction, log when compaction happens, or trigger automation.
"hooks": {
"PostCompact": [{
"matcher": "",
"hooks": [{ "type": "command", "command": "echo 'Context was compacted'" }]
}]
}
Source: https://x.com/trq212/status/2032632602629386348
Instead of approving every file write and bash command, or skipping permissions entirely, auto mode lets Claude make permission decisions on your behalf. Classifiers evaluate each action before it runs — safe operations get auto-approved, risky ones still get flagged.
# Enable auto mode
claude --enable-auto-mode
# Or cycle with shift+tab during a session:
# plan mode → auto mode → normal mode
Boris's take: "no 👏 more 👏 permission prompts 👏"
Source: https://x.com/bcherny/status/2036555259997462541
Use /schedule to create recurring cloud-based jobs for Claude, directly from the terminal. Unlike /loop (which runs locally for up to 3 days), scheduled jobs run in the cloud — they work even when your laptop is closed.
> /schedule a daily job that looks at all PRs shipped since yesterday
and update our docs based on the changes. Use the Slack MCP to
message #docs-update with the changes
The Anthropic team uses these internally to automatically resolve CI failures, push doc updates, and power automations that need to exist beyond a closed laptop.
Source: https://x.com/noahzweben/status/2036129220959805859
iMessage is now available as a Claude Code channel. Install the plugin and text Claude like you'd text a friend — from any Apple device.
/plugin install imessage@claude-plugins-official
Claude Code becomes a contact in your Messages app. Send it tasks, get responses as iMessages. Works from your iPhone, iPad, or Mac — no terminal needed. Pairs well with remote control sessions for kicking off work from anywhere.
Source: https://x.com/trq212/status/2036959638646866021
Claude Code has a built-in memory system. Run /memory to configure it.
Auto-memory: When enabled, Claude automatically saves preferences, corrections, and patterns between sessions. User memory goes to ~/.claude/CLAUDE.md, project memory to ./CLAUDE.md.
Auto-dream: As memory accumulates, it can get messy — outdated assumptions, overlapping notes, low-signal entries. Auto-dream runs a subagent that periodically reviews past sessions, keeps what matters, removes what doesn't, and merges insights into cleaner structured memory. Run /dream to trigger manually, or enable auto-dream in /memory settings.
The naming maps to how REM sleep consolidates short-term memory into long-term storage.
Claude Code has a mobile app. Download the Claude app for iOS/Android, then tap the Code tab on the left. Boris writes a lot of his code from the iOS app — it's a convenient way to make changes without opening a laptop.
Source: https://x.com/bcherny/status/2038454337811386436
Move sessions back and forth between mobile/web/desktop and terminal.
# Continue a cloud session on your machine
claude --teleport
# or /teleport from inside a session
# Control a local session from phone/web
/remote-control
Boris has "Enable Remote Control for all sessions" set in his /config.
Source: https://x.com/bcherny/status/2038454339933548804
Two of the most powerful features in Claude Code. Use these to schedule Claude to run automatically at a set interval, for up to a week at a time.
Boris's running loops:
/loop 5m /babysit — auto-address code review, auto-rebase, and shepherd PRs to production/loop 30m /slack-feedback — automatically put up PRs for Slack feedback every 30 mins/loop /post-merge-sweeper — put up PRs to address code review comments I missed/loop 1h /pr-pruner — close out stale and no longer necessary PRsPro tip: Experiment with turning workflows into skills + loops. It's powerful.
Source: https://x.com/bcherny/status/2038454341884154269
Use hooks to deterministically run logic as part of the agent lifecycle:
See https://code.claude.com/docs/en/hooks
Source: https://x.com/bcherny/status/2038454343519932844
Boris uses Dispatch every day to catch up on Slack and emails, manage files, and do things on his laptop when he's not at a computer. "When I'm not coding, I'm dispatching."
Dispatch is a secure remote control for the Claude Desktop app. It can use your MCPs, browser, and computer, with your permission.
Source: https://x.com/bcherny/status/2038454345419936040
The most important tip for using Claude Code: give Claude a way to verify its output. Once you do that, Claude will iterate until the result is great.
Think of it like any other engineer: if you ask someone to build a website but they aren't allowed to use a browser, will the result look good? Probably not. But if you give them a browser, they will write code and iterate until it looks good.
Boris uses the Chrome extension every time he works on web code. It tends to work more reliably than other similar MCPs. Download for Chrome/Edge at code.claude.com/docs/en/browser.
Source: https://x.com/bcherny/status/2038454347156398333
Use the Claude Desktop app to have Claude automatically start and test web servers. The Desktop app bundles in the ability for Claude to automatically run your web server and even test it in a built-in browser.
You can set up something similar in CLI or VSCode using the Chrome extension, or just use the Desktop app.
Source: https://x.com/bcherny/status/2038454348804714642
People often ask how to fork an existing session. Two ways:
# Option 1: From inside your session
/branch
# Option 2: From the CLI
claude --resume <session-id> --fork-session
Source: https://x.com/bcherny/status/2038454350214041740
Use /btw all the time to answer quick questions while the agent works. Single-turn, no tool calls, but has full context of the conversation. Claude responds inline without stopping its work.
> /btw how do i spell daushund?
dachshund — German for "badger dog" (dachs = badger, hund = dog).
Source: https://x.com/bcherny/status/2038454351849787485
Claude Code ships with deep support for git worktrees. Worktrees are essential for doing lots of parallel work in the same repository. Boris has dozens of Claudes running at all times.
# Start a new session in a worktree
claude -w
# Or check the "worktree" checkbox in the Claude Desktop app
For non-git VCS users, use the WorktreeCreate hook to add your own logic for worktree creation.
Source: https://x.com/bcherny/status/2038454353787519164
/batch interviews you, then has Claude fan out the work to as many worktree agents as it takes (dozens, hundreds, even thousands) to get it done. Use it for large code migrations and other kinds of parallelizable work.
Source: https://x.com/bcherny/status/2038454355469484142
By default, when you run claude -p (or the TypeScript or Python SDKs) it searches for local CLAUDE.md's, settings, and MCPs. But for non-interactive usage, most of the time you want to explicitly specify what to load via --system-prompt, --mcp-config, --settings, etc.
claude -p "summarize this codebase" \
--output-format=stream-json \
--verbose \
--bare
This was a design oversight when the SDK was first built. In a future version, the default will flip to --bare. For now, opt in with the flag.
Source: https://x.com/bcherny/status/2038454357088457168
When working across multiple repositories, start Claude in one repo and use --add-dir (or /add-dir) to let Claude see the other repo. This not only tells Claude about the repo, but also gives it permissions to work in it.
# At launch
claude --add-dir /path/to/other-repo
# During a session
> /add-dir /path/to/other-repo
Or, add "additionalDirectories" to your team's settings.json to always load in additional folders when starting Claude Code.
Source: https://x.com/bcherny/status/2038454359047156203
Custom agents are a powerful primitive that often gets overlooked. Define a new agent in .claude/agents, then run claude --agent=<your agent's name>.
# .claude/agents/ReadOnly.md
---
name: ReadOnly
description: Read-only agent restricted to the Read tool only
color: blue
tools: Read
---
You are a read-only agent that cannot edit files or run bash.
See https://code.claude.com/docs/en/sub-agents
Source: https://x.com/bcherny/status/2038454360418787764
Boris does most of his coding by speaking to Claude, rather than typing. To do the same:
Source: https://x.com/bcherny/status/2038454362226467112
| Tip | Key Action |
|---|---|
| Parallel work | Use git worktrees, 3-5 sessions |
| Model | Opus with thinking |
| Planning | Start in plan mode for complex tasks |
| CLAUDE.md | Update after every correction |
| Skills | /simplify, /batch, /btw, custom workflows |
| Subagents | Offload to keep context clean |
| Hooks | PostToolUse, SessionStart, PermissionRequest, Stop |
| Permissions | Pre-allow safe commands, wildcards |
| MCP | Integrate Slack, BigQuery, Sentry |
| Long-running | Use Stop hooks, background agents |
| Verification | Chrome extension, browser testing |
| Learning | Use Claude to explain and teach |
| Terminal | /config, /voice, /color, keybindings |
| Effort | /effort max for deeper thinking |
| Plugins & Agents | LSPs, MCPs, --agent, custom agents |
| Sandboxing | /sandbox for file & network isolation |
| Status line | /statusline for custom info display |
| Customize | Spinners, output styles, 37 settings, 84 env vars |
| Worktrees | claude -w, Desktop, subagent isolation, non-git VCS |
| Scheduled Tasks | /loop, /schedule, automated workflows |
| Code Review | Agent-powered PR reviews that catch real bugs |
| Remote Control | Teleport, mobile app, /remote-control |
| Session Management | --name, /branch, --fork-session, auto-naming |
| Setup Scripts | Automate cloud environment setup |
| PostCompact | Hook for context compression events |
| Auto Mode | Safer permission skipping with classifiers |
| iMessage | Text Claude from any Apple device |
| Auto-Memory & Dream | Persistent, self-cleaning memory system |
| Mobile App | Code from iOS/Android Claude app |
| Cowork Dispatch | Remote control for Claude Desktop |
| Desktop App | Auto start and test web servers |
| --bare | 10x faster SDK startup |
| --add-dir | Give Claude access to more folders |
Source: howborisusesclaudecode.com - Tips from Boris Cherny's January–March 2026 threads
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Quick-save the last assistant response as a verbatim note in the 2ndBrain Obsidian vault (~/2ndBrain/quick-notes/<year>/). Use when the user asks to quick-save/save the last response to 2ndBrain, or invokes $2ndbrain or /skill:2ndbrain.
日本語の概要は準備中です。原文の説明を表示しています。
Write commit messages under the agent-commits convention - a Conventional Commits fork with no chore catch-all, intent-only type tokens, facts in trailers, and legally-grounded AI provenance (Assisted-by, never Co-authored-by). Use when composing a commit in a repo whose commitlint.config.js extends agent-commits, when deciding between feat/fix/refactor/perf, or when recording AI participation.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate multi-agent work through durable artifacts in git instead of chat. Use this whenever a task involves sending a message to another agent, agent mailboxes or handoffs, claiming work from a shared queue, notifying another agent or crew (OpenClaw, Grok Bot, Claude Code, Codex, Gas Town/Gas City workers) that work is ready, or whenever the user mentions the artifact bus, message bus, agent mail, beads mail, doorbells, or pings between agents — even if they don't say "bus" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Use aven to find tasks, update status, and leave durable handoff context.
日本語の概要は準備中です。原文の説明を表示しています。
Codex workflow tips from Boris Cherny (creator of Codex) and the Codex team. Use when: setting up Codex, optimizing workflows, running parallel sessions, configuring AGENTS.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").
日本語の概要は準備中です。原文の説明を表示しています。