A Claude Code Cheat Sheet That Actually Grows With You

You've installed Claude Code, typed a prompt or two, and now you're staring at a blinking cursor wondering what else it can do. The tool has a lot of surface area — commands, flags, session management, subagents — and the official docs don't always make it obvious where to start. That's the gap this cheat sheet tries to fill.

What It Does

The Claude Code Cheat Sheet is a structured reference guide for Anthropic's Claude Code CLI, organized into six progressive levels that run from basic commands up through power-user and "master" territory. Rather than dumping every command into one flat list, it walks you through installation, authentication, navigation, file operations, and session management in roughly the order you'd actually need them.

The README covers the practical stuff first: how to install on macOS, Linux, WSL, Windows PowerShell, and Windows CMD, plus package manager options via Homebrew and WinGet. It notes that the npm install path is now a deprecated fallback. From there it moves into authentication commands (claude auth login, auth status, auth logout), first-run basics, and update commands like claude update and claude install for pinning a specific version. There's also a dedicated page for subagents — specialized AI agents for specific development tasks — linked separately from the main sheet.

Why It's Cool

• It's organized by skill level, not by category. Most cheat sheets sort commands alphabetically or by feature area, which is fine for lookup but useless for learning. This one uses color-coded levels (basic through master), so you can work through it linearly or jump to where you are. That's a small design decision with a real payoff.

• The quick-start section is genuinely quick. Install command, auth, launch — three lines and you're running, on every major platform. No hunting through a prerequisites section to find the one command you actually needed.

• It respects that context is a limited resource. The navigation section includes /compact for summarizing history to free context and /context for visualizing usage. Those are the commands people don't discover until they hit a wall, and having them in the "basic" tier means you'll find them early.

• Print mode gets proper coverage. The -p flag, piping content in via cat logs.txt | claude -p "explain", and continuing a conversation with -c are all documented with examples. This is the mode that turns Claude Code from an interactive toy into something you can script against, and it's easy to miss.

• Session management is spelled out. Continuing the most recent session, resuming by ID or name, naming a session at startup with -n, renaming mid-session with /rename — these are the features that make long-running projects bearable, and the README treats them as first-class rather than an afterthought.

One honest caveat: the README is marked as beta and is truncated in places, so you may find the occasional gap. But the structure means gaps are easy to spot and presumably easy to fill.

How to Try It

There's nothing to install beyond Claude Code itself. Start by setting up the CLI for your platform:

macOS, Linux, or WSL:

curl -fsSL https://claude.ai/install.sh | bash
claude auth login
claude

Windows PowerShell:

irm https://claude.ai/install.ps1 | iex
claude auth login
claude

Or use a package manager — brew install --cask claude-code on macOS, winget install Anthropic.ClaudeCode on Windows.

Verify things worked:

claude --version
claude auth status

Then start from the root of the project you want Claude to work on and work your way through Level 1. Once the basics feel natural, the intermediate and advanced levels are right there in the same document. The subagents page is worth reading on its own if you're doing repetitive task-specific work.

The full sheet lives at github.com/njengah/claude-code-cheat-sheet.

Final Thoughts

This is a reference for people who've decided to use Claude Code and want to get fluent in it faster than trial and error allows. It won't teach you what to build or how to prompt well — that's on you — but it will save you from discovering /compact three weeks after you needed it. If you're new to the tool, read it top to bottom once. If you're already deep in it, skim the upper levels; there's probably a flag or two in there you haven't touched.

Follow @githubprojects for more developer tools and open source projects.