The Ultimate Claude Code Cheatsheet One Pager
Michael Aechtler
AI keynote speaker based in Stuttgart; on stage since 2005. He builds with AI agents and tools every day, not slide-only talks. Co-founder of the CREATORS ScaleUp Campus.
WebsiteA Claude Code cheat sheet is a one-page reference for slash commands, session workflows, MCP, skills, and agentic TDD. This printable Claude Code one pager keeps the commands you reach for every day next to your terminal.
Updated July 2026. Install steps live in the Claude Code setup guide. Workflow advice lives in Claude Code best practices. Official product docs: Claude Code overview.
Claude Code commands quick reference
Search engines and AI answers need HTML text, not only a poster image. Use this quick reference, then unlock the full printable cheatsheet below.
Project setup
- CLAUDE.md — project commands, conventions, and constraints for every session.
- /init — generate a starter CLAUDE.md for the repo.
- /memory — edit memory files and manage auto-memory.
- /permissions — set allow, ask, and deny tool rules.
- /doctor — diagnose install, config, and health issues.
- /mcp — connect, enable, disable, and auth MCP servers.
- /add-dir — grant file access to another working directory.
During a task
- /plan — enter plan mode before a large change.
- /model — switch model and default effort level.
- /effort — set reasoning effort from low through max.
- /context — see what is filling the context window.
- /compact — summarize history to free context space.
- /btw — ask a side question without adding history.
- /diff — review uncommitted and per-turn diffs.
Parallel work and review
- /tasks, /background, /batch, /fork, /branch, /agents — manage parallel and background work.
- /code-review, /review, /security-review — review diffs and PRs before you ship.
- /clear, /resume, /rewind — reset, resume, or roll back a session.
- /skills, /hooks, /plugin — extend Claude Code with skills, hooks, and plugins.
Core practices on the poster
- Be specific: name files, expected behavior, and acceptance checks.
- Take small verified steps: one logical change, then run checks and review the diff.
- Use version control so Claude can inspect history and roll back.
- Plan before big edits; tighten permissions for destructive commands.
- RED / GREEN TDD: write a failing test, make it pass, then refactor.
For install and first-run config, read the Claude Code setup guide. For day-to-day workflows, read Claude Code best practices and Anthropic's official best practices.
Unlock the newsletter gate to download the printable Claude Code one pager image.

Who is this for
Founders, developers, and AI engineers who use Claude Code daily and want a single command reference they can print, pin, or share with a team. Keep this page for cheat sheet and slash-command lookups; use the setup and best-practices guides when you need full walkthroughs.
Frequently asked questions
- What is a Claude Code cheat sheet?
- A Claude Code cheat sheet is a one-page reference for slash commands, session controls, MCP, skills, and agentic TDD patterns you use while coding in the terminal.
- Which Claude Code commands should I learn first?
- Start with /init, /plan, /permissions, /mcp, /context, /compact, /diff, and /code-review. Those cover project setup, planning, permissions, context management, and shipping.
- Is this Claude Code one pager printable?
- Yes. Unlock the newsletter gate on this page to view and download the printable poster image.
- Where do I find Claude Code setup steps?
- Use the dedicated Claude Code setup guide for install, auth, CLAUDE.md, permissions, and first-project configuration.
- Where do I find Claude Code best practices?
- Use the dedicated Claude Code best practices guide for verification loops, plan mode, context management, hooks, and review workflows.
- Does this page replace Anthropic's docs?
- No. This page is a compact command reference. For full product docs, use code.claude.com/docs and the setup and best-practices articles linked from this post.







