Complete Claude Code reference: keyboard shortcuts, slash commands, hooks, MCP setup, CLAUDE.md tips & vibe coding workflows. Bookmark this. Updated March 2026.
Keyboard Shortcuts and Slash Commands
Claude Code is built for speed once the core controls live in muscle memory. Treat keyboard shortcuts as the layer that keeps you in the editor and terminal without hunting menus, and slash commands as the layer that turns repeated intent into a single typed action. Learn a small set first: open or focus the session, cancel a long-running turn, accept or reject proposed edits, and jump between the prompt and the file under review. Then add the slash commands you actually use—project context refresh, plan or review modes, diff inspection, and session reset—rather than memorizing every option on day one.
A practical habit is to keep a personal shortlist next to the official list. Group shortcuts by job (navigation, edit control, session hygiene) and slash commands by outcome (scaffold, explain, test, ship). When a command has flags or submodes, note only the variants that change results for your stack. Revisit the list after a few real sessions; the commands you reach for under deadline are the ones that belong at the top of any cheat sheet.
Hooks That Keep the Agent Honest
Hooks let you run fixed checks or scripts at defined points in the agent loop—before a tool runs, after a file write, or when a turn ends. Use them to enforce house rules without repeating yourself in every prompt: format or lint after edits, block writes outside allowed paths, require a test pass before a commit-related step, or log risky actions for later review. Prefer hooks that fail loud and early over silent post-processing that only surfaces problems after the session is over.
Design hooks like CI for a single developer session. Keep them fast, deterministic, and easy to disable when you are exploring. Document what each hook expects (cwd, env, exit codes) so the agent and your teammates share the same contract. If a hook fires often, treat that as a product signal: either the prompt is too loose, the allowlist is too tight, or the workflow needs a dedicated slash command instead of another guardrail.
MCP Setup and CLAUDE.md That Actually Help
MCP servers extend Claude Code with tools and data sources outside the default sandbox—issue trackers, docs search, internal APIs, design systems. Install only what the current project needs, scope credentials tightly, and verify each tool’s description matches how you want the agent to call it. A bloated MCP config slows reasoning and invites wrong tool choice; a lean set with clear names beats a kitchen-sink setup every time.
CLAUDE.md is the durable project brief the agent should load without being told. Put architecture boundaries, preferred commands, test entry points, naming rules, and “never do this” constraints there. Keep it short enough to stay accurate: outdated CLAUDE.md is worse than none. Pair it with path-local notes when monorepos differ by package. Update the file when a painful session reveals missing context—that is how the cheat sheet’s “tips” section earns its keep in production work.
- State the stack, package manager, and how to run tests in the first screen of CLAUDE.md.
- List allowed edit paths and forbidden areas (secrets, generated vendor trees, production configs).
- Name the MCP tools the team actually uses and what each is for in one line.
Vibe Coding Workflows Without Losing Control
Vibe coding works when you give Claude Code a clear outcome, tight scope, and a feedback loop—not when you dump an entire product into one prompt. Start with a short plan turn, accept or revise the plan, then implement in thin slices with review after each change. Use shortcuts to accept partial diffs, hooks to catch regressions, and slash commands to reset context when the thread drifts. The cheat sheet is most useful as a session checklist: setup context, constrain tools, implement, verify, commit.
Bookmark this reference for the moments when flow breaks—wrong directory, runaway edits, missing project rules—and recover with the right command instead of restarting from scratch. Updated March 2026, it is meant to stay open beside the terminal: shortcuts for speed, slash commands for intent, hooks for safety, MCP and CLAUDE.md for project truth, and a workflow that keeps “vibe” productive rather than chaotic.