My Claude Devteam

Claude Code Dev Team

English · 繁體中文
An entire engineering team for Claude Code
— 12 specialized agents, 15 automation hooks, and the P7/P9/P10 methodology that keeps them disciplined.

Most people use Claude Code as a single coder. This config turns it into a full engineering org: planner, fullstack-engineer, refactor-specialist, migration-engineer, frontend-designer, critic, vuln-verifier, debugger, db-expert, onboarder, tool-expert, web-researcher — each agent owns a role, each has its own tool permissions, and a strict delegation rulebook decides who touches what.

Backed by corporate-culture-inspired discipline (closure, fact-driven, exhaustiveness) and battle-tested hooks that catch debugger statements, hardcoded secrets, cost overruns, and MCP outages before they hit main.
The Team
Each agent is a markdown file under agents/ with its own system prompt, tool permissions, and model selection. Customize them. Fork them. Replace the ones you don't need.
The Workflow



Security-sensitive work takes a detour: critic flags → vuln-verifier writes PoC → fix or file PR.
The Methodology

Three Red Lines

Every agent enforces these. No exceptions. No "close enough".

- 🔒 Closure Discipline — Every task has a clear Definition of Done. "This is probably enough" is not an ending.
- 📎 Fact-Driven — Every judgment must cite actual code with paths and line numbers. "I guess" / "probably" / "should be" are violations.
- ✅ Exhaustiveness — Checklists cannot be skipped. Clean items must be explicitly marked "checked, no problems" — never silently ignored.

P7/P9/P10 Mode Switching

Not role-play. Operating modes that Claude switches between based on task scope:
PUA Mode (High-Pressure Triggers)

The team shifts into exhaustive mode when:

- Same…