简体中文
EnglishClaude Code Cheatsheet: Key Commands, Workflows, and Configuration at a Glance
Updated
Claude Code is Anthropic's terminal-based coding agent, and a useful cheatsheet centers on four things: how you start and resume sessions, what you type inside a session, how you configure project memory and permissions, and how you extend it with MCP servers and agent skills. The official reference for all of this lives at platform.claude.com/docs, and the Claude Code 2.1 cheatsheet is curated on awesomeclaude.ai. Use this page as a working map of those areas; confirm exact flags and syntax against the official docs before scripting anything.
Starting and Managing Sessions
Claude Code runs from your terminal and works against your local repository. The general pattern is: you launch it from the project directory, describe a task in natural language, and it reads files, proposes edits, and runs commands with your approval.
| Task | How it works |
|---|---|
| Start a session | Launch Claude Code from your project root so it picks up the repo context |
| Resume prior work | Session resume lets you continue a previous conversation instead of re-explaining context |
| Monitor usage | The Claude Developer Console (console.anthropic.com) covers API keys, prompt testing, usage monitoring, and Claude Code sessions |
| Get the full reference | platform.claude.com/docs documents Claude Code alongside the Messages API, tool use, and prompt caching |
Because the docs are the authoritative source for exact command names and flags, treat any third-party cheatsheet as a starting index rather than a spec.
In-Session Commands and Shortcuts
Inside a session, the workflow is conversational: you ask for a change, Claude Code reads the relevant files, and you review what it proposes. The recurring actions a cheatsheet should help you with are:
- Reviewing diffs before accepting. Edits are presented for approval, so read the diff rather than approving blindly, especially in files you haven't opened.
- Approving or rejecting commands. When Claude Code wants to run a shell command, you decide whether it proceeds. This is your main safety checkpoint.
- Correcting course mid-task. If it heads in the wrong direction, redirect in plain language instead of restarting the session.
- Referencing specific files. Point it at the files or directories that matter so it doesn't spend turns searching.
For the exact slash commands and keyboard shortcuts available in your version, check the official Claude Code documentation, since these change between releases.
Configuration: Project Memory and Permissions
The configuration layer is what makes Claude Code repeatable across sessions and across a team. Two pieces matter most:
CLAUDE.md project memory. A CLAUDE.md file at the project root gives Claude Code standing context: build commands, conventions, architecture notes, and things to avoid. Write it the way you'd onboard a new contributor — concrete commands and rules beat vague descriptions.
Permissions and settings. Settings files control what Claude Code may do without asking, such as which commands are pre-approved. Tighten these for shared or sensitive repositories and loosen them only where you've reviewed the risk.
A practical setup order: create CLAUDE.md with your build/test commands and conventions, then define permissions for the commands you run constantly, then commit both so every session and teammate starts from the same baseline.
Extending Claude Code: MCP Servers and Agent Skills
Claude Code's capabilities extend through two mechanisms highlighted in the Awesome Claude directory:
- MCP servers (Model Context Protocol) connect Claude Code to external tools and data sources — the directory lists top MCP servers, and Anthropic's docs cover the MCP Connector.
- Agent skills package reusable instructions and workflows so Claude Code handles recurring task types consistently.
Anthropic's Claude Cookbook (github.com/anthropics/claude-cookbooks, ~53k stars) includes official notebooks and recipes for common patterns including RAG, tool use, Skills, and MCP — the most reliable place to see these extensions in working code. The Agent SDKs (claude-agent-sdk-python, ~8.3k stars, and claude-agent-sdk-typescript) are the path if you want to build agents on top of Claude programmatically rather than only using the CLI.
Where to Go Beyond the Cheatsheet
A cheatsheet goes stale; the sources below don't:
| Need | Source |
|---|---|
| Full Claude Code and API reference | platform.claude.com/docs |
| Model IDs, context windows, pricing | platform.claude.com/docs/en/about-claude/models/overview |
| Working recipes (RAG, tool use, Skills, MCP) | github.com/anthropics/claude-cookbooks |
| Deployable example apps | github.com/anthropics/claude-quickstarts |
| Curated tools, MCP servers, plugins | awesomeclaude.ai |
| Cloud-hosted access | Amazon Bedrock (note: Managed Agents and Anthropic server-side tools aren't available there — use the Claude API with tool use instead) |
If you're on Bedrock, plan around that limitation: the Messages-API endpoint serves Claude 5 models with an ID prefix and supports cross-region inference and guardrails, but agent-style server-side tooling needs the direct Claude API.
Bottom Line
Learn Claude Code in this order: get comfortable starting and resuming sessions, build the habit of reviewing diffs and approving commands deliberately, write a solid CLAUDE.md and permissions file, then extend with MCP servers and skills once the basics are routine. Keep platform.claude.com/docs open as the source of truth and use awesomeclaude.ai to discover what to add next.