Claude Code

Primary AI development tool. Power user workflow: task-driven delegation with structured plans and verification.

Quick Reference

Additional Cheatsheets

• CC Cheat Sheet

Action	Command/Shortcut
Initialize project memory	/init
Clear context	/clear
Compact conversation	/compact
Enter Plan Mode	Shift+Tab twice
Switch model	Alt+P (Windows)
Add memory on the fly	Type # then instruction
Check usage	/usage
Check status line	/statusline
Run insights	/insights
Name session	/session name
Resume session	/session resume name

---

Key Workflows

• Plan Mode First: always separate planning from coding for non-trivial work
• Checkpoints + /rewind: fearless experimentation with quick rollbacks
• Context Hygiene: /clear and /compact to maintain clarity
• Named Sessions: /session name for easy resume
• Human-Guided Git: manual control over history, let Claude focus on edits
• Short Sessions: ~40 messages or one feature per session as soft limit

---

Setup

Installation

• Use npm version of Claude Code (enables Claude Trace)
• Claude Trace: https://github.com/badlogic/lemmy/tree/main/apps/claude-trace

Max Reasoning Config

In ~/.claude/settings.json:

{
  "env": {
    "CLAUDE_CODE_MAX_OUTPUT_TOKENS": "64000",
    "MAX_THINKING_TOKENS": "31999"
  }
}

Config References

• Global CLAUDE.md: ~/.claude/CLAUDE.md
• Monorepo CLAUDE.md: d:\FSS\Websites\monorepo\CLAUDE.md
• Setup docs: d:\FSS\Websites\monorepo\docs\CLAUDE_CODE_SETUP.md
• MCP config: d:\FSS\Websites\monorepo\docs\MCP_CONFIGURATION.md

Memory System

Four Scopes (highest to lowest priority)

1. Enterprise: C:\Program Files\ClaudeCode\CLAUDE.md — org-wide policy
2. Project: ./CLAUDE.md or ./.claude/CLAUDE.md — team-shared
3. Project rules: ./.claude/rules/*.md — modular, topic-specific
4. User: ~/.claude/CLAUDE.md — personal preferences across all projects
5. Project local: ./CLAUDE.local.md — personal project-specific (auto-gitignored)

Auto Memory

• CC maintains MEMORY.md per project: \\wsl$\Ubuntu-24.04\home\ta\.claude\projects\...\memory\MEMORY.md
• Automatically read at start of every conversation

CLAUDE.md Best Practices

• Keep under 100 lines (context efficiency)
• Use as roadmap to docs, not the docs itself — use @path/to/file imports
• Always use absolute paths in references
• Add subdirectory CLAUDE.md for module-specific rules
• Include: verification requirements, planning instructions, deployment architecture
• Schedule monthly audits: delete stale, add missing
• Hot reload only works for skills; CLAUDE.md changes require session restart

Import Syntax

See @README for project overview and @package.json for npm commands.
@docs/git-instructions.md
@~/.claude/my-project-instructions.md

Remote Control

Access a running local CC session from phone, tablet, or any browser. Session stays on your machine — remote device is just another keyboard into the same conversation.

Requirements

• Plan: Pro, Max, Team, or Enterprise (not PAYG API)
• CC v2.1.51+ (claude --version)
• Auth via claude.ai account (not Console API key — run /login if needed)
• Team/Enterprise: admin must enable in org admin settings

Starting a Remote Session

Method	Command	Use when
Server mode	claude remote-control	Dedicated remote-only session; terminal shows status, no local input
Interactive + remote	claude --remote-control or claude --rc	Most common — local terminal + remote both active
Mid-session	/remote-control or /rc	Already in a session, want to keep going from another device

Name your session: claude --remote-control "Auth refactor" or /remote-control Auth refactor

Connecting Another Device

1. QR code — press spacebar to toggle (server mode); auto-shown in interactive mode. Scan from Claude mobile app.
2. Session URL — appears in terminal at startup; open in any browser at claude.ai/code
3. Session list — open claude.ai/code or Claude app → tap Code → find session (green dot = online)

Push Notifications

Get notified when long tasks finish or decisions are needed.

1. Install Claude mobile app (iOS/Android)
2. Sign in with same claude.ai account
3. Accept OS notification permission
4. In CC: /config → enable Push when Claude decides

Requires CC v2.1.110+. If no notifications: check /config shows a mobile registered; check iOS Focus/notification settings.

Auto-Enable for Every Session

/config → Enable Remote Control for all sessions → true

Each concurrent CC process gets its own remote session with its own URL.

my_OpenClaw Integration

Tap Start Claude Remote in Telegram → starts a Remote Control session in the KB vault → connect from Claude mobile app. See \\wsl$\Ubuntu-24.04\home\ta\utils\ai\my_OpenClaw\README.md.

Config changes require a service restart — my_OpenClaw reads config.yaml once at startup. Telegram keyboard buttons reflect the running config, not the file on disk. After editing config.yaml:

systemctl --user restart my-openclaw.service

Then send any message to the bot — the updated keyboard appears with the reply. The service auto-restarts on failure and on WSL launch, so one restart is all that’s needed.

Common Pitfalls

• New directory: run claude once first to accept workspace trust, then start Remote Control
• API key login: won’t work — /login to switch to claude.ai account auth
• Older CC version: claude update to upgrade
• VS Code: type /rc in the prompt box; connection status banner appears above prompt

---

Advanced Strategies

Thinking Levels

Level	Use For
think	Quick fixes, moderate complexity
think hard	Design decisions, optimization
think harder	Architectural decisions
ultrathink	Debugging hell, race conditions

Model Selection

• Haiku 4.5: sprinter — simple tasks, implementation (much cheaper)
• Sonnet 4.5: steady builder — standard development
• Opus 4.5: careful reviewer — complex refactors, architecture

Subagents

• Parallelize development: spawn specialized agents for backend, frontend, tests
• Each works in isolated context window
• Parent agent coordinates and runs integration tests

Hooks

Shell commands that auto-run at lifecycle events:

• PreToolUse: auto-format before tool runs
• PostToolUse: trigger tests after code changes
• Stop: finalize tasks, send notifications
• Exit code 2: block Claude from editing protected files
• Scoping hierarchy: global -> project -> skill -> sub-agent
• Async hooks: run in background, ~3x faster workflows

Skills and Commands (Merged)

• Simple commands: single .md in .claude/commands/
• Complex skills: directory in .claude/skills/skill-name/ with SKILL.md, scripts, templates
• Skills auto-reload on SKILL.md changes
• Invoke with /skill-name
• See 02_Skills for full skills ecosystem

Plugins

• Combine /commands with MCP servers
• Marketplace available for community plugins
• CCPlugins: 24 predefined commands extending CC CLI

CC /insights Report Summary (2026-02-05)

3,336 messages across 439 sessions over 31 days

What’s Working

• Task-driven workflow with structured backlists
• Confirm-then-implement planning discipline
• Multi-language infrastructure orchestration (Python, TS, YAML, JSON)
• 276 commits (9/day shipping cadence)

Key Friction Points

1. Claude claims “done” without verifying — deployment bugs missed
2. Wrong approach on config/deployment — lacks persistent context
3. No CLAUDE.md guardrails — no rules about deployment architecture, testing

Priority Actions from Insights

1. Add verification rules to CLAUDE.md: “Never claim done without testing”
2. Set up hooks for post-edit deployment validation
3. Create /taskfix skill encoding the full fix-verify workflow
4. Use headless mode for automated task-list fixes
5. Implement verify-before-done protocol
6. Per-item verification (fix -> test -> next) instead of batch

Suggested CLAUDE.md Additions

## Workflow Rules
- After implementing changes, verify by running deployment/build scripts and checking output. Never claim "done" without testing.
- When working from task list, do final grep pass for remaining old/replaced values.

## Deployment and Config
- For config changes (YAML, JSON, shell), diff final file contents after editing. Check for: domain names, provider names, URLs, environment-specific values.

Resources

• Claude Code Docs
• Everything Claude Code
• Awesome Claude Code
• Anthropic Best Practices
• ClaudeLog - The no.1 Claude Code community resource
• Free Course: Claude Code in Action
• CC Cheatsheet
• The Only CLAUDE.md Guide
• Boris Cherny’s 22 Tips
• 47 CC WSL Tricks
• 30 CC Subagent Templates
• Deep Learning AI Course
• Who to Follow