What is the .claude folder? (For beginners)
The .claude folder is Claude Code's brain — a hidden directory Anthropic's tool creates in your project.
It holds your AI team's "office":
- agents/ — AI teammates like @chief (full, lite, full versions)
- hooks/ — Lifecycle hooks (SessionStart.js, PreToolUse.js etc.)
- skills/ — Best practice patterns
- commands/ — Slash command implementations
- settings.json — Registers hooks with Claude Code
- session-state.json — Session memory
- codebase-map.json — Tracks file changes
- CLAUDE.md — Project entry point
Memory persists via thoughts/ folder (ledgers, handoffs, plans).
Sources:
So What's This Then? (For .claude users)
This upgrades your .claude folder into a **self-healing, memory-aware, production-grade autonomous engineering organization** with 25 specialized agents.
Key upgrades:
- @chief — unbreakable master orchestrator
- Confidence-based routing (≥70% auto, 40–69% queue, <40% block)
- File-based memory persistence (thoughts/ledgers, handoffs, plans)
- Token optimization (96.7% reduction via lite agents + escalation)
- Lifecycle hooks for validation & tracking
- OpenSpec enforcement & drift protection
- 25 agents: Planner, Verifier, ReflectionAgent, DatabaseAgent, UIAgent, etc.
- Slash commands: /bootstrap, /review-queue, /swarm-planner, /spawn-subagent
- Mandatory Orchestration SOP.md (unbreakable rulebook)
- No database — lightweight JSON + files only
Preserves existing .claude if present; upgrades safely. Production-ready as of 2026-ultimate.
Deploy This First — Legendary Deployment
Before running:
- Be in your project root folder
- Have internet (for initial clone if using one-liner)
Recommended one-liner (Linux/macOS/WSL2):
cd ~/your-project && \
git clone https://github.com/RegardV/LegendaryTeam_For_Claude .legendary-tmp && \
cp -r .legendary-tmp/.claude . && \
cp .legendary-tmp/CLAUDE.md .legendary-tmp/"Orchestration SOP.md" . && \
rm -rf .legendary-tmp && \
bash LegendaryTeamDeploy.sh
After deployment:
- Start Claude Code:
claude
- Run:
/bootstrap
- Respond: "discovery complete — proceed" then "specs approved"
- Paste full content of
Orchestration SOP.md into the session
@chief will confirm: "S.O.P. LOCKED IN — ALL AGENTS NOW FOLLOW THIS EXACT FLOW FOREVER"
For returning sessions: @chief resume session
Quick Start
Command the Team
Manage & Commands
Quick Start — Deployment & Bootstrap
Run the deployment script (LegendaryTeamDeploy.sh or .ps1), then in Claude Code:
/bootstrap- Reply to prompts: "discovery complete — proceed", "specs approved"
- Paste
Orchestration SOP.md content
Team is active. Use @chief for orchestration.
Command the Team — @chief Prompts
New/Empty Project
@chief
This is a brand-new or empty project.
Execute the full legendary bootstrap.
I will provide specs when requested.
Begin now.
Existing Project
@chief
This is an existing project.
Execute full legendary bootstrap with discovery protection.
Recompile specs vs actual code.
Rebuild team for current stack.
Begin now.
Resume Session
@chief resume session
Typical Requests
@chief add dark mode with user preference persistence
@chief fix the auth bug in login flow
@chief implement rate limiting on API routes
Advanced Analysis
@chief please ensure the OpenSpec and SessionState is in line with the current codebase. then report the techstack then report what the code shows we can do if there is a front end and a back end and a database. Look for all and do a comprehensive indepth scan to look for disconnects, duplicates, Drift, wrong implementations, Scan the code with the codecartographer and write a comprehensive report on the findings.
Manage Your Team — Slash Commands & Tools
Core Slash Commands
/bootstrap → full system startup & initialization
/review-queue → show tasks pending human review
/team-status → display active agents & progress
/approve-task [id] → approve a queued task
/swarm-planner [task] → generate dependency-aware plan
/parallel-task → execute in waves
/spawn-subagent → dynamic agent creation
/emergency-stop → halt all operations
Deployment Scripts
Linux / WSL2 / macOS
Windows
Linux / WSL2 / macOS
# Create and run LegendaryTeamDeploy.sh
# (Paste full script content from repo into this file)
chmod +x LegendaryTeamDeploy.sh
./LegendaryTeamDeploy.sh
Or use the one-liner clone method above.
Windows (PowerShell)
# Create LegendaryTeamDeploy.ps1
# (Paste full script content from repo)
powershell -ExecutionPolicy Bypass -File LegendaryTeamDeploy.ps1
