Unlock Claude Code’s Hidden Power: 15 Must‑Know Commands to Supercharge Your Development

Claude Code ships with more than 50 commands, yet most developers only use three to five, leaving a huge productivity gap. The article first explains the tool’s underlying three‑layer architecture—CLI startup flags, slash commands entered during a session, and keyboard shortcuts that act as neural reflexes—so readers understand why each command matters.

Three‑Level Command Model

CLI commands (startup configuration) : injected when launching Claude, setting the initial speed of the session.

Slash commands (session core) : typed after a leading / to invoke specific actions.

Shortcut keys (neural reflex) : avoid typing full words, enabling instant mode switches.

Part 1 – Core Daily Commands (Top 10)

/init

– creates a CLAUDE.md file that acts as the project’s long‑term memory. Example content:

# CLAUDE.md

## Authentication
- Use JWT tokens, not sessions
- Store in httpOnly cookies

## Testing
- Write tests for all API endpoints
- Use Jest, not Mocha

## Error Handling
- Return structured errors: { error: string, code: number }

/compact

– when context usage is high, summarizes the core decisions in seconds; recommended at 70‑80% usage. /clear – wipes the session history, useful when switching to a completely different task. /model – switches between Claude models (Sonnet, Opus, Haiku). Example:

/model sonnet   # Switch to Sonnet 4.6 (everyday workhorse)
/model opus      # Switch to Opus 4.6 (architectural killer)
/model haiku     # Switch to Haiku 4.5 (speed specialist)

/cost

– shows real‑time token consumption. Sample output:

Session cost: $2.47
Input tokens: 48,392
Output tokens: 12,847
Model: claude‑sonnet‑4‑20250514

/context

– displays current context usage (e.g., Context usage: 67% (134,400 / 200,000 tokens)), warning you when Claude starts “forgetting”. /diff – reveals line‑by‑line changes, turning Claude into a code‑review assistant. Usage examples:

/diff               # Show all changes
/diff src/auth.ts   # Show changes for a specific file

/help

– provides an up‑to‑date command reference directly in the session. /memory – edits the persistent CLAUDE.md without leaving the chat; lines prefixed with # are appended automatically. /resume – reloads a previous conversation, e.g., “Find the chat from December 2025”.

Part 2 – Advanced “Killer” Commands

/btw

– inserts a side question without breaking the current task; after answering, Claude returns to the original flow. /fast – enables API‑level speed optimizations (e.g., Opus 4.6 runs dramatically faster). /plan – puts Claude into a read‑only planning mode, showing a proposal before any changes are made, preventing ~90 % of accidents. /todos – creates a persistent to‑do list that survives session restarts. /simplify – replaces the deprecated /review command; it runs three parallel agents to evaluate code for security, performance, and style.

Part 3 – CLI Startup Flags (Power‑User Secrets)

claude --print "..."

– one‑shot query that exits immediately, ideal for scripting. claude -c – continues the last session in the current directory. --agents – pre‑defines sub‑agents at launch, e.g.: <code>claude --agents '{ "test-writer": { "role": "Write comprehensive Jest tests", "model": "claude-sonnet-4" } }' </code> --dangerously-skip-permissions – skips all approval checks; only safe inside trusted containers (Docker/CI).

Part 4 – Keyboard Shortcuts (Efficiency Boosters)

Shift + Tab

– cycles between normal, auto‑accept, and planning modes. Esc Esc – opens a rollback menu to revert code or conversation. ! + command – runs a Bash command directly in the session, e.g., ! git status. @ + path – auto‑completes file paths. Ctrl + T – toggles the task list view.

Part 5 – Hidden “Forbidden” Tricks

/vim

– enables Vim keybindings inside the prompt (h/j/k/l for navigation). /remote-control – lets you control Claude on your desktop from a mobile device. /usage-report – generates a monthly analysis of time and token consumption.

Part 6 – Full‑Day Automated Refactor Workflow

Enter planning mode: claude → Shift+Tab.

Describe the refactor: “Migrate Auth from session‑based to JWT with bcrypt password hashing.”

Monitor context: run /context; when usage hits 70 %, execute /compact retain auth patterns and migration strategy.

Review changes with /diff, then run /simplify for final quality checks.

Stage and commit via Bash shortcuts: ! git add . → ! git commit -m "feat: jwt migration".

Export the whole operation as a knowledge asset with /export.

By mastering just one new command each week, a developer can quickly surpass peers and turn Claude Code into a personal AI‑powered development cockpit.