The 5 levels of Claude Code (and how to know when you've hit the ceiling on each one)

Who Should Read

Developers already using or evaluating Claude Code. Especially useful if your project is growing and you're noticing the AI coding assistant becoming less consistent.

Core Mechanics

• Level 1 (Raw Prompting) works fine for small, one-off tasks, but the moment a project outgrows a single conversation context, the agent starts forgetting existing conventions and introducing random patterns.
• Level 2 (CLAUDE.md) defines tech stack, file structure, naming conventions, etc. in a markdown file at project root. However, at 145 lines compliance visibly dropped. Cutting to 77 lines immediately improved it — keeping it short and focused is critical.
• Level 3 (Skills) are markdown protocol files containing step-by-step workflows for specific task types. They're loaded only when needed, so unused skills cost zero tokens. Eliminates the need to re-explain component build processes every session.
• Level 4 (Hooks) are lifecycle scripts that auto-run at specific session events. For example, a PostToolUse hook that typechecks only the modified file after each edit prevents dumping 200+ project-wide errors into the agent's context. Instead of telling the agent to validate, you build validation infrastructure.
• Level 5 (Orchestration) involves running parallel agents in isolated worktrees, maintaining state across sessions with persistent campaign files, and adding a coordination layer to prevent same-file conflicts. The author reported running 198 agents across 32 fleet sessions with a 3.1% merge conflict rate.
• Don't try to skip levels. The author explicitly shared that jumping to Level 5 without Level 4 hooks was a disaster. Each level's infrastructure enables the next, so you should naturally progress when you feel friction and limitations at your current level.

Evidence

• Running CLAUDE.md at 145 lines led to noticeably worse rule compliance. Cutting to 77 lines brought immediate improvement. Anthropic recommends 200 lines, but in practice agents start silently ignoring rules well below that threshold, prioritizing top rules only.
• At Level 5 orchestration, 198 parallel agents were run across 32 fleet sessions with a 3.1% merge conflict rate. The author described this as enabling one developer to work at organization-level scale.
• With Level 4 PostToolUse hooks, typechecking runs only on the edited file after each modification, avoiding the inefficiency of dumping 200+ project-wide errors into the agent context from a full project check.
• The author directly shared their failed attempt to jump straight to Level 5, confirming that multi-agent operation without hook-based auto-validation infrastructure (Level 4) causes quality control to collapse.

How to Apply

• If your agent keeps forgetting conventions, create a CLAUDE.md under 80 lines at your project root. As content grows, lower rules get ignored — keep only the most critical rules and move the rest to Skills files.
• If you repeatedly explain the same task types (e.g., React component creation, API endpoint procedures), create Skills markdown files for them and have the agent reference them when needed. They cost zero tokens when unused, so creating many is free.
• If your TypeScript/Python project has too many type errors polluting agent context, set up PostToolUse hooks to typecheck only the edited file right after modification. Much more efficient than dumping a full project check at the agent.

Terminology

Related Resources

• Original Reddit Post
• Citadel - Open Source Claude Code Orchestration System (GitHub)