The techniques, configurations, and workflow patterns that separate power users from casual users.
Most developers use 10% of Claude Code's capabilities. This deck covers the tactics that turn Claude Code into a true development partner.
Most people don't know this: Claude Code automatically reads a CLAUDE.md file from your repository root at the start of every session. This becomes part of Claude's system context.
The file is read before your first prompt. Pre-configure Claude's behavior, coding style, and project knowledge without wasting tokens explaining it every time.
Pro tip: Keep CLAUDE.md under 500 lines. Link to detailed docs instead of inlining.
Purpose: Persistent memory between sessions
Claude reads this at session start, instantly resuming context from yesterday.
Purpose: Task tracking Claude can update
"Update TODO.md when done" — Claude maintains your task list automatically.
Purpose: Framework-specific patterns
"All API routes return { data, error }. Use zod for validation."
The pattern: Reference these in CLAUDE.md: See SCRATCHPAD.md for current context. Claude reads them when relevant, keeping your main config lean.
/compact
Context
/clear
Reset
/model
Switch
/cost
Monitor
/review triggers a code review of staged changes against your CONVENTIONS.md.
Pipe input directly to Claude:
Shift + Enter for newlines, or wrap with """ for multi-line mode.
Power pattern: Use glob patterns for bulk operations: "add JSDoc to all files in src/utils/*.ts"
/remember:
~/.claude/memory.json for all future sessions.
Claude reads your commit history to match your commit message style.
The "as if" pattern: Prime Claude with expertise.
Key insight: Start broad, then drill down. "Fix all TypeScript errors" → "Now fix the ones in src/utils" → "Explain line 42"
/compact. Claude retains key decisions but frees up space."look at src/api/users.ts" instead of pasting. Claude reads files on-demand..claudeignore (like .gitignore) to exclude files.
Without .claudeignore, Claude might read massive generated files, wasting context. A good .claudeignore can 2-3x your effective context window.
Context budget: Keep CLAUDE.md under 500 lines, SCRATCHPAD.md under 200. Reserve 80% for the actual conversation.
Add to CLAUDE.md:
Tell Claude your Next.js version. Behavior differs between 13/14/15.
Add to CLAUDE.md:
Include your pyproject.toml path for dependency awareness.
Add to CLAUDE.md:
Reference tsconfig.json so Claude respects compiler settings.
Create docs/llm-guide.md with examples of good code. Reference it in CLAUDE.md. Claude pattern-matches against real examples, not abstract rules.
Include your test command in CLAUDE.md. Then "implement this and add tests" — Claude writes tests that actually run.
Create CLAUDE.md, SCRATCHPAD.md, TODO.md, and .claudeignore. 30 minutes that pays dividends forever.
Know --resume, /compact, /model, and /cost by heart. Use --print-system-prompt to debug.
Be specific about files and scope. State constraints. Ask Claude to plan before complex tasks. End with verification.
Run /compact between tasks. Keep config files lean. Use .claudeignore. Reference files instead of pasting.
Start broad, drill down. Use /remember for preferences. Update SCRATCHPAD.md at session end. Build knowledge over time.
Treat Claude Code as a junior developer with perfect memory and infinite patience. Give it context, give it constraints, verify its work, iterate. The tool amplifies your expertise — it doesn't replace it.