Claude Code commands, checked against the docs
The slash commands worth knowing, grouped by the moment you need them. Each one is explained in plain words, with its aliases, and marked when it is really a bundled skill.
/help to see what you have. The 39 above are the ones most people reach for; 50 more are one click down. Source: official commands reference.Click a card to flip it: you get what the command does, how to use it, and two examples. The examples are illustrations, not quotes from the docs.
First session in a repo
Set the project up so Claude knows it and asks before doing risky things.
/initCreates a starter CLAUDE.md so Claude knows your project.
Details and examples ↻/initClick to flip back ↻What it does
Creates a starter CLAUDE.md, the file Claude reads at the start of every session to learn your project. With CLAUDE_CODE_NEW_INIT=1 it runs an interactive flow that also covers skills, hooks and personal memory files.
How to use it
Run it once in a new repo, then edit the file by hand so it holds what only you know: build commands, naming rules, things to avoid.
Examples
- In a fresh project:
/init, then open CLAUDE.md and delete anything that is wrong. - Switching from another tool:
/initalso looks for Codex or Gemini CLI setup in the repo.
/memoryEdit your CLAUDE.md files, turn auto memory on or off, and see what it has stored.
Details and examples ↻/memoryClick to flip back ↻What it does
Opens your CLAUDE.md files for editing, and lets you turn auto memory on or off and see the entries it has saved.
How to use it
Use it when Claude keeps forgetting a rule, or has remembered something wrong.
Examples
- Claude keeps using the wrong test command:
/memory, open the project CLAUDE.md and write the right one. - Curious what Claude saved by itself:
/memoryand look through the auto memory entries.
/mcp [reconnect|enable|disable]Manage MCP server connections and their sign-ins.
Details and examples ↻/mcpClick to flip back ↻What it does
Manages MCP server connections and their sign-ins. With no argument it opens an interactive list. With reconnect, enable or disable plus a server name (or all) it changes the connection directly.
How to use it
Use it when a tool server shows as disconnected, or when you want a server off for a while.
Examples
/mcpto see every server and whether it is connected.- A server dropped:
/mcp reconnect all.
/permissionsSet allow, ask and deny rules for each tool.
/permissionsClick to flip back ↻What it does
Shows and edits the allow, ask and deny rules for each tool. You can view rules by scope, add or remove them, manage working directories and review recent auto mode denials.
How to use it
Open it when Claude asks permission for the same safe thing again and again, or when you want to block something for good.
Examples
- Tired of the same prompt:
/permissionsand add an allow rule for that command. - Protect a folder: add a deny rule so Claude cannot touch it.
/add-dir <path>Give Claude file access to one more folder for this session.
Details and examples ↻/add-dirClick to flip back ↻What it does
Gives Claude file access to one more folder for the current session. Type a partial path to see suggestions and press Tab to accept one.
How to use it
Use it when the work spans two folders, for example an app and its shared library. Most .claude settings are not read from an added folder.
Examples
/add-dir ../shared-libraryso Claude can read and edit the library too.- Compare two projects:
/add-dir ~/projects/old-version.
/doctorSkillA setup checkup: finds installation, settings, extension and CLAUDE.md problems and proposes fixes after you confirm.
/doctorClick to flip back ↻What it does
A setup checkup. It looks for problems in your installation, settings, extensions and CLAUDE.md, and proposes fixes that Claude applies only after you confirm.
How to use it
Run it when something behaves oddly, or after an update. Read the proposals before you confirm.
Examples
- Commands stopped working after an update:
/doctor. - A skill does not show up:
/doctorand read what it found.
During a task
Steer how Claude works, and keep the conversation from filling up.
/plan [task]Enter plan mode. Add a task and Claude starts planning it right away.
Details and examples ↻/planClick to flip back ↻What it does
Enters plan mode straight from the prompt. Claude explores and proposes a plan before changing anything. Add a task and it starts planning that task at once.
How to use it
Use it for anything bigger than a small edit, so you can correct the approach before code changes.
Examples
/plan fix the auth bug(the docs use this very example)./planalone, then describe the task in your next message.
/goal [condition|clear]Claude keeps working across turns until your condition is met.
Details and examples ↻/goalClick to flip back ↻What it does
Sets a goal condition. Claude keeps working across turns until the condition is met or the goal clears for another reason. With no argument it shows the current goal, and clear removes it.
How to use it
Use it for work that takes many steps and has a clear finish line you can state in a sentence.
Examples
/goal all tests in the api folder pass/goal clearif you changed your mind.
/model [model]Switch model. The choice is saved as your default for new sessions.
Details and examples ↻/modelClick to flip back ↻What it does
Switches the AI model and saves it as the default for new sessions. For models that support it, the left and right arrows adjust effort. With no argument it opens a picker.
How to use it
Pick a smaller model for simple, repetitive work and a stronger one for hard problems.
Examples
/modeland choose from the list.- Quick tasks today: switch to a smaller model, then switch back for the hard part.
/effort [level|auto|status]Set how hard Claude thinks, from low up to max.
Details and examples ↻/effortClick to flip back ↻What it does
Sets how hard Claude thinks, from low up to max, or auto. status prints the current setting.
How to use it
Raise it for tricky bugs and design questions. Lower it for simple edits to save time and usage.
Examples
/effort statusto see where it is now./effort lowfor renaming a variable across a file.
/contextSee what is filling your context window, with suggestions to free space.
Details and examples ↻/contextClick to flip back ↻What it does
Shows what is filling your context window as a colored grid, with suggestions for tools that take a lot of space, memory bloat and capacity warnings.
How to use it
Run it when answers get worse in a long session, or before deciding between /compact and /clear.
Examples
- Long session, Claude forgets things:
/context, then/compact. - Check whether a big MCP server is eating space.
/compact [instructions]Summarize the conversation to free space. Say what to keep. Long idle conversations are also compacted automatically; you can turn that off in /config.
Details and examples ↻/compactClick to flip back ↻What it does
Frees up context by summarizing the conversation so far. You can pass instructions about what the summary must keep. Long idle conversations are also compacted automatically; you can turn that off in /config.
How to use it
Use it to keep working in the same conversation when the window is filling up. Use /clear when you want a clean start instead.
Examples
/compact keep the list of files we changed and the open bugs/compactalone when you just need room.
/btw [question]Ask a side question without adding it to the conversation.
Details and examples ↻/btwClick to flip back ↻What it does
Asks a side question about the current session without adding it to the conversation. With no question it shows your most recent side question.
How to use it
Use it for quick questions that should not clutter the main thread or send Claude off in a new direction.
Examples
- Mid-task:
/btw what does the retry flag do again? - Look back at your last side answer with
/btw.
Run work in parallel
Hand work to other sessions and keep your terminal free.
/batch <instruction>SkillSplits a large change into independent units, each in its own worktree, after you approve the plan. Needs a git repository.
Details and examples ↻/batchClick to flip back ↻What it does
Orchestrates a large change across a codebase in parallel. It researches the code, splits the work into 5 to 30 independent units and shows a plan. After you approve, each unit runs in its own worktree. Needs a git repository.
How to use it
Use it for repetitive, wide changes, such as migrating many files to a new API. Read the plan before approving.
Examples
/batch replace the old logging helper with the new one everywhere/batch add types to every function in the utils folder
/background [prompt]Detach this session to run in the background and free your terminal.
/backgroundClick to flip back ↻What it does
Detaches the current session to run as a background agent and frees your terminal. Pass a prompt to give one more instruction before detaching. Alias: /bg.
How to use it
Use it when a task will take a while and you want your terminal back. Watch it later with claude agents.
Examples
/background keep going and open a PR when the tests pass/bgto detach right now.
/fork [prompt]Copy the conversation into a new background session and keep working here.
Details and examples ↻/forkClick to flip back ↻What it does
Copies the current conversation into a new background session and lets you keep working here. With a prompt, the copy starts on it immediately.
How to use it
Use it to try a second approach in parallel without losing your place.
Examples
/fork try the same fix with a different library/forkand give the copy a task later from the agent view.
/subtask <task>Start a background subagent that inherits the conversation; its result comes back here.
Details and examples ↻/subtaskClick to flip back ↻What it does
Starts a background subagent that inherits the whole conversation and works on a task while you keep working. Its result comes back to this conversation when it is done.
How to use it
Use it for side jobs that need the context you have built up, such as writing tests for what was just changed.
Examples
/subtask write unit tests for the function we just changed/subtask check the docs folder for outdated examples
/tasksSee background work in this session, including finished subagents.
/tasksClick to flip back ↻What it does
Shows background work in this session, including subagents that have finished, and lets you manage it. Alias: /bashes.
How to use it
Run it to see what is still running before you close the session.
Examples
- After a
/subtask:/tasksto see if it has finished. /bashesdoes the same.
/loop [interval] [prompt]SkillRepeat a prompt while the session stays open. Leave out the interval and Claude paces itself.
/loopClick to flip back ↻What it does
Runs a prompt repeatedly while the session stays open. Leave out the interval and Claude paces itself between iterations. Alias: /proactive.
How to use it
Use it for watching or polling jobs: a build, a deploy, a review queue. It stops when you close the session.
Examples
/loop 5m check whether the deploy finished/loop babysit my open pull request(Claude picks the pace).
Before you ship
Check the change from different angles before it leaves your machine.
/diffReview every change in your working tree.
Details and examples ↻/diffClick to flip back ↻What it does
Opens a review of every change in your working tree, including the edits Claude has made so far.
How to use it
Use it before you commit, to read what actually changed rather than trusting a summary.
Examples
- After a long task:
/diffand go file by file. - Spot an edit you did not expect and ask Claude to undo it.
/code-review [level] [--fix] [--comment] [target]SkillReview the diff, a PR, a branch or a path for correctness bugs. --fix applies the findings; --comment posts them; ultra runs a deep cloud review. In a GitHub PR, comment @claude review stop to pause the automatic review.
/code-reviewClick to flip back ↻What it does
Reviews the current diff, or a PR number, branch or path you pass, for correctness bugs. Depending on your model and effort level it may also cover cleanup opportunities. --fix applies findings, --comment posts them, and ultra runs a deep cloud review.
How to use it
Run it before you open a PR. In a GitHub PR, commenting @claude review stop pauses the automatic review. Alias: /review.
Examples
/code-reviewon your current changes./code-review --comment 123to post findings on pull request 123.
/security-reviewCheck the changes on your branch for vulnerabilities. Needs an origin remote.
Details and examples ↻/security-reviewClick to flip back ↻What it does
Analyzes the changes on your current branch for security problems such as injection, auth issues and data exposure. It compares your branch with origin's default branch, so it needs an origin remote.
How to use it
Run it on a branch that touches logins, input handling or anything that talks to the outside world.
Examples
- Before merging a new login flow:
/security-review. - After adding a file upload endpoint.
/simplify [target]SkillA cleanup review that applies fixes. It does not look for bugs; use /code-review for that.
Details and examples ↻/simplifyClick to flip back ↻What it does
A cleanup review that applies fixes. Four review agents run in parallel, covering reuse of existing helpers, simplification and more. It does not hunt for bugs; use /code-review for that.
How to use it
Use it after a feature works, to trim duplicated or overbuilt code.
Examples
/simplifyon the files you just changed./simplify src/billingto point it at one folder.
/verifySkillBuilds and runs your app to confirm a change really works, instead of trusting tests alone.
Details and examples ↻/verifyClick to flip back ↻What it does
Confirms a code change really works by building and running your app and observing the result, rather than trusting tests or type checks alone.
How to use it
Run it after a change that tests could miss, such as a UI or startup change. /run-skill-generator teaches it how to start your app.
Examples
- After a layout change:
/verify. - Before telling a teammate it is fixed.
Between sessions
Start fresh, come back later, or try another direction.
/clear [name]Start a new conversation with empty context. A name labels the old one in the picker.
/clearClick to flip back ↻What it does
Starts a new conversation with empty context. A name labels the previous conversation in the /resume picker. Aliases: /reset, /new.
How to use it
Use it between unrelated tasks. To keep the same conversation but free space, use /compact instead.
Examples
/clearwhen you move to a new bug./clear billing workso you can find the old chat later.
/resume [session]Reopen an earlier conversation by name or ID, or pick from a list.
/resumeClick to flip back ↻What it does
Reopens an earlier conversation by ID or name, or opens the session picker. Background sessions appear in the picker marked bg. Alias: /continue.
How to use it
Use it to pick up yesterday's work with its full context.
Examples
/resumeand choose from the list./resume billing workif you named it with /clear or /rename.
/rename [name]Name the session so you can find it later. Without a name, Claude suggests one.
Details and examples ↻/renameClick to flip back ↻What it does
Names the current session and shows the name on the prompt bar. Without a name Claude suggests one from the conversation.
How to use it
Name sessions you will want again, so the picker is not a wall of similar titles.
Examples
/rename checkout bug/renameand accept the suggested name.
/branch [name]Branch the conversation to try another direction. The original stays; return with /resume.
Details and examples ↻/branchClick to flip back ↻What it does
Creates a branch of the conversation at this point so you can try another direction. The original is kept; return to it with /resume.
How to use it
Use it before a risky idea, so you can go back to the version that worked.
Examples
/branch try-redisand test the Redis idea.- Go back with
/resumeand pick the original.
/rewindRoll code and conversation back to an earlier checkpoint.
/rewindClick to flip back ↻What it does
Rolls the conversation and/or your code back to an earlier checkpoint, or summarizes from a selected message. Aliases: /checkpoint, /undo.
How to use it
Use it when an approach went wrong and you want to undo both the chat and the edits.
Examples
/rewindand pick the point before the refactor./undodoes the same.
/export [filename]Save the whole conversation as a plain text file.
Details and examples ↻/exportClick to flip back ↻What it does
Saves the current conversation as plain text. With a filename it writes the file directly; without, it opens a dialog to copy or save.
How to use it
Use it to keep a record, or to share a session with someone who does not use Claude Code.
Examples
/export session-notes.txt/exportand choose copy to clipboard.
/copy [N]Copy Claude's last reply, or the Nth latest, or pick one code block.
Details and examples ↻/copyClick to flip back ↻What it does
Copies Claude's last reply to the clipboard. Pass a number N for the Nth-latest reply. When there are code blocks you get a picker to copy just one.
How to use it
Use it instead of selecting text by hand in the terminal.
Examples
/copyfor the last answer./copy 2for the second-to-last (this is the docs' own example).
/recapA one-line summary of where the session stands.
Details and examples ↻/recapClick to flip back ↻What it does
Generates a one-line summary of where the session stands, on demand.
How to use it
Use it when you come back to a session and cannot remember what you were doing.
Examples
- Back after lunch:
/recap. - Before handing a session to a teammate.
When something is wrong
Find out what it costs, what broke, and how to report it.
/usageSession cost, plan limits and activity stats.
/usageClick to flip back ↻What it does
Shows session cost, plan usage limits and activity stats. On Pro, Max, Team or Enterprise it includes a breakdown of what counts against your plan. Aliases: /cost, /stats.
How to use it
Check it before a big job or when you hit a limit and want to know why.
Examples
/usagemid-session to see what it has cost./costfor the same screen.
/debug [description]SkillTurns on debug logging and troubleshoots by reading the session log.
Details and examples ↻/debugClick to flip back ↻What it does
Turns on debug logging for the current session and troubleshoots by reading the session debug log. Logging is off by default unless you started with claude --debug.
How to use it
Use it when Claude Code itself misbehaves, for example a hook that does not fire.
Examples
/debug my hook never runs/debugand describe the odd behavior.
/feedback [report]Send a bug report or feedback, with a consent step before anything is sent.
/feedbackClick to flip back ↻What it does
Sends product feedback about Claude Code. It opens the same dialog as /bug, with a consent step before anything is sent.
How to use it
Use it to report a bug or an idea. Nothing is sent until you agree.
Examples
/feedback the diff view cuts off long lines/bugopens the same dialog.
Working with Skills
Commands that matter most if you build or maintain your own skills.
/skillsList available skills and cycle how visible each one is to Claude and the menu.
Details and examples ↻/skillsClick to flip back ↻What it does
Lists the available skills. Type to filter, press t to sort by token count, and Space or Enter to cycle a skill's visibility to Claude and the slash menu.
How to use it
Use it to see what is installed and to switch off skills you do not use.
Examples
/skillsand type a word to filter.- Sort by token count to find the heavy ones.
/reload-skillsRe-scan skill folders so changes made during the session take effect without a restart.
Details and examples ↻/reload-skillsClick to flip back ↻What it does
Re-scans skill and command folders so skills you added or edited on disk become available without restarting. It reports how many were added or removed.
How to use it
Run it right after saving a new SKILL.md while a session is open.
Examples
- Wrote a new skill file:
/reload-skills, then try it. - Edited a description and want it picked up.
/skill-doctorShows what each skill costs in context and how often it is used, so you can turn off the dead weight.
Details and examples ↻/skill-doctorClick to flip back ↻What it does
Shows what each skill costs in context and how often it is used, so you can find skills to turn off. Needs Claude Code v2.1.252 or later and may sit behind a feature flag.
How to use it
Use it when you have many skills and sessions feel crowded.
Examples
/skill-doctorand look at the least-used skills.- Turn off two skills you have not used for weeks.
/claude-api [subcommand]SkillLoads Claude API reference for your project. Subcommands include migrate, cost-optimize, build-eval and api-version (move your code to the newest Claude API version).
Details and examples ↻/claude-apiClick to flip back ↻What it does
Loads Claude API and Managed Agents reference material for your project. Subcommands include migrate, cost-optimize, build-eval and api-version (move your code to the newest Claude API version).
How to use it
Use it when you are writing or updating code that calls the Claude API.
Examples
/claude-api migrateto move code to a newer model./claude-api cost-optimizeto look for savings.
More commands: 50 more for setup, design, automation and teams
Setup and settings
Configure Claude Code and your terminal.
/config [key=value]Open settings, or set one directly, for example theme or model.
/configClick to flip back ↻What it does
Opens the Settings screen for theme, model, output style and other preferences. Pass key=value pairs to set a setting directly. Alias: /settings.
How to use it
Use the key=value form when you know exactly which setting you want.
Examples
/configto browse settings./config theme=darksets one directly (the key names are in the Settings screen).
/cd <path>Move this session to another working directory and keep the conversation.
Details and examples ↻/cdClick to flip back ↻What it does
Moves this session to another working directory and keeps the conversation. Type a partial path for suggestions.
How to use it
Use it when the work moves to another project but you want to keep the context.
Examples
/cd ../apiafter finishing the front end.- Type
/cd ~/proand press Tab to complete.
/import [codex|gemini|cursor]Bring instruction files, MCP servers, commands, subagents and skills over from Codex, Gemini CLI or Cursor.
Details and examples ↻/importClick to flip back ↻What it does
Brings configuration from OpenAI Codex, Google Gemini CLI or Cursor on your machine into Claude Code: instruction files, MCP servers, commands, subagents and skills.
How to use it
Use it when you switch tools and do not want to rebuild your setup by hand.
Examples
/import codex/import cursor
/install-github-appInstall the Claude GitHub app for a repository, with optional GitHub Actions setup.
Details and examples ↻/install-github-appClick to flip back ↻What it does
Installs the Claude GitHub App for a repository, with an optional step to set up GitHub Actions workflows and secrets. It walks you through picking the repo.
How to use it
Use it once per repository to get Claude into pull requests and CI.
Examples
- Set up a new project:
/install-github-appand follow the steps. - Skip the Actions step if you only want the app.
/terminal-setupSet up Shift+Enter for new lines in supported terminals.
Details and examples ↻/terminal-setupClick to flip back ↻What it does
Installs a Shift+Enter keybinding for new lines in VS Code, Cursor, Devin Desktop, Alacritty or Zed. In Apple Terminal it helps you enable Option+Enter instead.
How to use it
Run it if Shift+Enter sends your message instead of adding a line.
Examples
/terminal-setupin the editor's built-in terminal.- Check that Shift+Enter now adds a new line.
/hooksView your hook configurations.
Details and examples ↻/hooksClick to flip back ↻What it does
Shows your hook configurations. Hooks are commands that run automatically at set moments, such as before a tool runs.
How to use it
Use it to check which hooks are active and where they come from.
Examples
/hooksto see what runs automatically.- Look here first when something happens that you did not ask for.
/update-config [request]SkillDescribe a settings change in words and Claude edits the right settings file.
Details and examples ↻/update-configClick to flip back ↻What it does
Describe a settings change in words and Claude edits the matching settings.json file, for example allowing a command, setting an environment variable or adding a hook.
How to use it
Use it instead of editing JSON by hand.
Examples
/update-config allow npm test without asking/update-config set an environment variable called DEBUG to 1
/keybindingsOpen your keyboard shortcuts file.
Details and examples ↻/keybindingsClick to flip back ↻What it does
Opens your keyboard shortcuts file.
How to use it
Use it to remap keys you keep pressing by accident.
Examples
/keybindingsand edit the file.- Change a shortcut that clashes with your terminal.
/sandboxToggle sandbox mode, on supported platforms.
Details and examples ↻/sandboxClick to flip back ↻What it does
Toggles sandbox mode, which limits what commands can reach. Available on supported platforms only.
How to use it
Use it when you want extra protection while Claude runs commands.
Examples
/sandboxto switch it on.- Run it again to switch it off.
/fewer-permission-promptsSkillScan your past sessions for safe, repeated read-only calls and propose an allowlist.
Details and examples ↻/fewer-permission-promptsClick to flip back ↻What it does
Scans your past transcripts for common read-only Bash and MCP tool calls and adds a prioritized allowlist to the project's .claude/settings.json, to reduce permission prompts.
How to use it
Use it after a few weeks of work, when the same safe prompts keep appearing. Read the list it proposes.
Examples
/fewer-permission-promptsand review the allowlist.- Keep only the entries you are comfortable with.
/auto-mode-setupDraft auto-mode rules from your project and recent sessions, for you to review and save. Needs a Pro, Max or Team plan.
Details and examples ↻/auto-mode-setupClick to flip back ↻What it does
Drafts autoMode.environment entries from your project and recent sessions, then lets you review the draft and save it to your user settings. Needs a Pro, Max or Team plan.
How to use it
Use it to give auto mode a description of your environment so it makes better calls.
Examples
/auto-mode-setupand read the draft before saving.- Edit any line that does not match your setup.
Look and feel
Make the terminal easier on the eyes.
/themeChange the color theme, including auto light and dark, and custom themes.
Details and examples ↻/themeClick to flip back ↻What it does
Changes the color theme. Options include auto (matches your terminal's light or dark background), light and dark variants, colorblind-accessible themes and ANSI themes.
How to use it
Pick one that is readable in your terminal and easy on your eyes.
Examples
/themeand try a few.- Choose auto if your terminal switches with the time of day.
/color [color|default]Set the prompt bar color for this session.
Details and examples ↻/colorClick to flip back ↻What it does
Sets the prompt bar color for the current session: red, blue, green, yellow, purple, orange, pink or cyan. default resets it; no argument picks a random one.
How to use it
Use different colors to tell several open sessions apart.
Examples
/color bluein the front-end session./color defaultto reset.
/statuslineSet up the status line: describe what you want, or let Claude copy your shell prompt.
Details and examples ↻/statuslineClick to flip back ↻What it does
Configures Claude Code's status line. Describe what you want, or run it with no arguments to copy your shell prompt.
How to use it
Use it to keep model, folder or branch always visible.
Examples
/statusline show the git branch and the model/statuslinealone to copy your shell prompt.
/focusShow only your last prompt, a one-line tool summary and the final answer. Fullscreen rendering only.
Details and examples ↻/focusClick to flip back ↻What it does
Toggles the focus view, which shows only your last prompt, a one-line tool-call summary with edit diffstats and the final response. Fullscreen rendering only.
How to use it
Use it to cut the noise when you only care about the result.
Examples
/focusduring a long run.- Run it again to bring back the full view.
/output-style [style]List output styles or switch to one.
Details and examples ↻/output-styleClick to flip back ↻What it does
Lists output styles or switches to one. Needs Claude Code v2.1.269 or later.
How to use it
Use it to change how Claude words its answers, for example shorter or more explanatory.
Examples
/output-style concise(the docs use this example)./output-stylealone to see the list.
/helpShow help and the commands available to you.
Details and examples ↻/helpClick to flip back ↻What it does
Shows help and the commands available to you.
How to use it
If a command in this list is missing for you, run it to see what your version and plan include.
Examples
/helpto see everything on your setup.- Compare it with this page when a command seems to be missing.
/release-notesBrowse the changelog by version.
Details and examples ↻/release-notesClick to flip back ↻What it does
Opens the changelog in an interactive version picker. Pick a version to read its notes, or show all.
How to use it
Use it after an update to see what changed.
Examples
/release-notesand select the newest version.- Look for a command you saw on this page.
/powerupShort interactive lessons with demos of Claude Code features.
Details and examples ↻/powerupClick to flip back ↻What it does
Short interactive lessons with animated demos of Claude Code features.
How to use it
Use it when you want to learn a feature by trying it, not by reading docs.
Examples
/powerupand pick a lesson.- Do one lesson a day for a week.
Create
Make designs, slides and charts from the terminal.
/artifactsList artifacts you own or that are shared with you; attach one, open it or copy its link.
Details and examples ↻/artifactsClick to flip back ↻What it does
Lists the artifacts you own or that are shared with you, then lets you attach one to the session, open it in your browser or copy its link.
How to use it
Use it to find a page or document Claude made earlier.
Examples
/artifactsand pick the one from last week.- Copy a link to share it.
/design [brief]SkillDraft UI mockups, screen flows, landing pages or posters as editable artboards.
Details and examples ↻/designClick to flip back ↻What it does
Drafts UI mockups, screen flows, landing pages or posters as artboards on one canvas, published as a Claude Design artifact.
How to use it
Describe what you need; edit the result on the canvas afterwards.
Examples
/design a landing page for a bakery/design three options for a settings screen
/design-sync [hint]SkillConvert your repo's React design system and upload it to Claude Design.
Details and examples ↻/design-syncClick to flip back ↻What it does
Converts your repo's React design system and uploads it to Claude Design, so designs use your real components. You can name the design system.
How to use it
Use it once your design system is stable and you want mockups to match it.
Examples
/design-syncin your front-end repo.- Add a hint with the design system's name if you have several.
/slides [brief]SkillMake a presentation from a brief.
Details and examples ↻/slidesClick to flip back ↻What it does
Makes a new presentation as a Claude Slides artifact, filled in from your brief.
How to use it
Give it the audience and the point, not just the topic.
Examples
/slides a quarterly review of the platform team(the docs' own example)./slides five minutes on why we should adopt code review
/dataviz [request]SkillGuidance for charts and dashboards: chart type, color roles, accessibility.
Details and examples ↻/datavizClick to flip back ↻What it does
Design guidance for charts, graphs and dashboards. Claude picks the chart form for the data, assigns color by role and checks the palette for colorblind safety and contrast.
How to use it
Use it before you build a chart, to avoid rainbow colors and unreadable labels.
Examples
/dataviz monthly sales by region/dataviz a dashboard for support ticket trends
Context and models
Control how much Claude remembers and which model answers.
/autocompact [auto|tokens]Set how full the context window gets before Claude Code compacts it for you.
Details and examples ↻/autocompactClick to flip back ↻What it does
Sets the auto-compact window: how full the context window gets before Claude Code compacts automatically. Pass a size such as 500k, or auto to return to the default for your model.
How to use it
Use it if you want more control over when summarizing happens.
Examples
/autocompact 500k/autocompact autoto go back to the default.
/fast [on|off]Toggle fast mode.
Details and examples ↻/fastClick to flip back ↻What it does
Toggles fast mode on or off. If you run it while Claude is responding, it changes at once, though the running turn finishes at its original speed.
How to use it
Use it when you want quicker answers and accept the trade-offs described in the fast mode docs.
Examples
/fast on/fast offwhen you want the normal mode back.
/advisor [model|off]Let a second model give guidance at key moments during a task.
Details and examples ↻/advisorClick to flip back ↻What it does
Enables or disables the advisor tool, which consults a second model for guidance at key moments during a task. It accepts fable, opus, sonnet or a full model ID.
How to use it
Use it for hard tasks where a second opinion helps. Some choices need extra access.
Examples
/advisor opus/advisor off
Parallel and background work
Keep working while other sessions run.
/stopStop the background session you are attached to. The transcript is kept.
Details and examples ↻/stopClick to flip back ↻What it does
Stops the background session you are attached to, or the one you send it to as a peek reply. The transcript and any worktree are kept.
How to use it
Use it to end a job that is going the wrong way. To leave it running, detach instead.
Examples
- Attached to a background session:
/stop. - Check the transcript afterwards to see how far it got.
/workflowsWatch, pause, resume or save running workflows.
Details and examples ↻/workflowsClick to flip back ↻What it does
Opens the workflow progress view to watch, pause, resume or save running and completed workflows.
How to use it
Use it when a multi-step workflow is running and you want to see or steer it.
Examples
/workflowsto watch a run.- Pause it while you review what it has done.
/list-agentsList the subagents and sessions Claude can message. Only where cross-session messaging is on.
/list-agentsClick to flip back ↻What it does
Lists the subagents, agent team teammates and other Claude Code sessions Claude can message, with the name to use for each. Only where cross-session messaging is on. Alias: /peers.
How to use it
Use it to find the right name before sending a message to another session.
Examples
/list-agents/peersis the same.
/exitExit Claude Code. In an attached background session it detaches and the session keeps running.
/exitClick to flip back ↻What it does
Exits Claude Code. In an attached background session it detaches and the session keeps running. Alias: /quit.
How to use it
Use it to leave cleanly. A background session carries on without you.
Examples
/exit/quitdoes the same.
/runSkillLaunch and drive your app to see a change working, not only passing tests.
Details and examples ↻/runClick to flip back ↻What it does
Launches and drives your project's app to see a change working, not only passing tests.
How to use it
Use it to look at the real result after an edit. /run-skill-generator teaches it how to start your app.
Examples
/runafter a front-end change.- Run it before opening a PR.
/run-skill-generatorSkillRecord a per-project recipe so /run and /verify know how to build and start your app.
Details and examples ↻/run-skill-generatorClick to flip back ↻What it does
Teaches /run and /verify how to build, launch and drive your project's app from a clean environment, by writing a per-project skill.
How to use it
Do it once per project, so /run and /verify work without guessing.
Examples
/run-skill-generatorin a new repo.- Then try
/run.
Automate and research
Put work on a schedule or send it to the cloud.
/schedule [description]Create, update, list or run cloud scheduled tasks (formerly called routines).
/scheduleClick to flip back ↻What it does
Creates, updates, lists or runs cloud scheduled tasks (formerly called routines). Claude walks you through the setup in conversation, and you can ask about a task's recent runs. Alias: /routines.
How to use it
Use it for work that should happen on a timetable even when your laptop is closed.
Examples
/schedule every weekday morning, summarize new pull requests/scheduleand ask how last night's run went.
/deep-research <question>WorkflowFan out web searches, cross-check sources and return a cited report.
Details and examples ↻/deep-researchClick to flip back ↻What it does
A bundled workflow that fans out web searches on a question, fetches and cross-checks sources and synthesizes a cited report.
How to use it
Use it for questions that need many sources. Check the citations before you rely on it.
Examples
/deep-research how do teams version their internal skills/deep-research what changed in the latest MCP release
/autofix-pr [prompt]Start a cloud session that watches your branch's PR and pushes fixes when CI fails or reviewers comment. Needs the gh CLI.
Details and examples ↻/autofix-prClick to flip back ↻What it does
Starts a cloud session that watches your branch's PR and pushes fixes when CI fails or reviewers comment. It detects the open PR from your checked-out branch. Needs the gh CLI.
How to use it
Use it when you open a PR and want routine fixes handled while you do other work.
Examples
/autofix-pr/autofix-pr only fix lint errors
Extend Claude
Plugins, browser and IDE connections.
/plugin [subcommand]Manage plugins: list, install, enable or disable.
Details and examples ↻/pluginClick to flip back ↻What it does
Manages Claude Code plugins. With no argument it opens the plugin menu; with a subcommand such as list, install, enable or disable it acts directly.
How to use it
Use it to add or remove bundles of skills, commands and tools.
Examples
/plugin list/plugin marketplace add anthropics/skills(as on chapter 03).
/reload-plugins [--force]Apply plugin changes without restarting.
Details and examples ↻/reload-pluginsClick to flip back ↻What it does
Reloads all active plugins to apply pending changes without restarting. It reports counts per component and flags load errors.
How to use it
Run it after installing or changing a plugin.
Examples
/reload-plugins/reload-plugins --forceif something did not refresh.
/ideManage IDE integrations and show their status.
Details and examples ↻/ideClick to flip back ↻What it does
Manages IDE integrations and shows their status.
How to use it
Use it when Claude Code and your editor do not seem connected.
Examples
/ideto see the status.- Check it after opening the project in your editor.
/chromeConfigure Claude in Chrome settings.
Details and examples ↻/chromeClick to flip back ↻What it does
Configures Claude in Chrome settings.
How to use it
Use it to check or change how Claude Code connects to the browser extension.
Examples
/chrome- Run it before your first browser task.
/claude-in-chrome [task]SkillHave Claude do a task in your browser, such as testing a page or reading console logs.
Details and examples ↻/claude-in-chromeClick to flip back ↻What it does
Has Claude carry out a task in your browser through Claude in Chrome, such as testing a page, filling a form or reading console logs. Available when Chrome is connected.
How to use it
Describe the page and what to check.
Examples
/claude-in-chrome check the signup page for console errors/claude-in-chrome fill the contact form with test data
Work anywhere
Continue a session on another device.
/remote-controlMake this session available from claude.ai.
/remote-controlClick to flip back ↻What it does
Makes this session available for Remote Control from claude.ai. Needs a claude.ai subscription. Alias: /rc.
How to use it
Use it to keep an eye on a long session from your phone or another computer.
Examples
/remote-control/rcfor short.
/teleportPull a cloud session into this terminal.
/teleportClick to flip back ↻What it does
Pulls a cloud session into this terminal. It opens a picker, then fetches the branch and the conversation. Needs a claude.ai subscription. Alias: /tp.
How to use it
Use it to continue locally what you started in the cloud.
Examples
/teleportand pick the session./tpfor short.
/desktopContinue this session in the Claude Code desktop app. macOS and x64 Windows.
/desktopClick to flip back ↻What it does
Continues the current session in the Claude Code Desktop app. Needs macOS or x64 Windows and a Claude subscription. Alias: /app.
How to use it
Use it when you want the graphical app for the rest of the work.
Examples
/desktop/appfor short.
/voice [hold|tap|off]Toggle voice dictation. Needs a Claude.ai account.
Details and examples ↻/voiceClick to flip back ↻What it does
Toggles voice dictation, or enables it in a specific mode (hold, tap or off). Needs a Claude.ai account.
How to use it
Use it to talk instead of type for long prompts.
Examples
/voice holdto speak while a key is held./voice offto turn it off.
Team, usage and limits
See what you used and keep working when a limit hits.
/team-onboardingGenerate a getting-started guide for teammates from your last 30 days of usage.
Details and examples ↻/team-onboardingClick to flip back ↻What it does
Generates a team onboarding guide from your Claude Code usage over the last 30 days: your sessions, commands and MCP server usage. It produces a markdown guide a teammate can paste as a first message.
How to use it
Use it to turn what works for you into a head start for a new teammate. Read it before sharing, since it comes from your own history.
Examples
/team-onboarding- Trim anything private before you send it.
/usage-creditsSet up usage credits, or request them from your admin, when you hit a limit.
Details and examples ↻/usage-creditsClick to flip back ↻What it does
Sets up usage credits, or requests them from your admin, when you hit a limit. It opens your usage-credits billing settings in the browser, with a different flow on Team and Enterprise.
How to use it
Use it when a limit blocks you and waiting is not an option.
Examples
/usage-credits- On a Team plan, use it to ask your admin.
/rate-limit-optionsShow ways to keep working when a usage limit blocks a request.
Details and examples ↻/rate-limit-optionsClick to flip back ↻What it does
Shows ways to keep working when a claude.ai usage limit blocks a request: wait and continue automatically when the limit resets, add usage credits and more.
How to use it
Run it the moment a limit message appears.
Examples
/rate-limit-options- Choose to continue automatically after the reset.
/statusShow version, model, account and connectivity.
Details and examples ↻/statusClick to flip back ↻What it does
Opens Settings on the Status tab, showing version, model, account and connectivity.
How to use it
Use it to check which version and account you are on when reporting a problem.
Examples
/status- Check the version before reading the release notes.
/insightsGenerate an HTML report on how you use Claude Code and where things go wrong.
Details and examples ↻/insightsClick to flip back ↻What it does
Generates an HTML report analyzing your recent sessions on this machine: which projects you work in, how you use Claude Code, where things go wrong and features to try. Not available in cloud sessions.
How to use it
Use it now and then to see your own habits and find features you are missing.
Examples
/insights- Open the report and pick one suggested feature to try.
Removed: don't look for these
Older guides still mention them.
/ultraplanis gone. Use plan mode with/plan./vimis gone. Use/configand change the editor mode./pr-commentsis gone. Ask Claude directly to read the pull request comments.