architect
01Agent
Use when Phase 3 design spec is needed before implementation begins.
TDD-first AI dev pipeline for Claude Code, Cursor, Codex, Gemini CLI & Antigravity. /dev /fix /quick + token-saving hooks. npx aicrew install
Agent
Use when Phase 3 design spec is needed before implementation begins.
Agent
Use when API routes, service layer, or backend business logic is being changed.
Agent
Use when 3 alternative approaches with trade-offs are needed before committing to one.
Agent
Use when a bug needs root-cause tracing from symptom to confirmed code location.
Agent
Default output style for all aicrew skills and commands. Not opt-in.
Agent
Use when infra files (migrations, Dockerfile, deps, env config) changed.
Agent
Default: apply on every session. Not opt-in via /lean on.
Agent
Speculative-context scout: cheap graph-first discovery that emits a fixed SCOUT: schema for a capable main agent to verify and act on.
Agent
Use when database schema, model files, or migration files are being changed.
Agent
Use when frontend files (.tsx, .vue, components, routes) are being changed.
Agent
Four principles for disciplined, goal-driven coding — derived from forrestchang/andrej-karpathy-skills (MIT). Adapted and extended for the aicrew pipeline.
Agent
Use when performance is an acceptance criterion or a flow is measurably slower.
Agent
Use when a security review of changed files is needed.
Agent
Goal: survive usage timeouts and multi-tool parallel work by keeping durable, compact state files outside the chat.
Agent
Use when implementing code with strict RED→GREEN→REFACTOR enforcement.
Agent
Default: caveman/lean output style. See /Agents/agents/caveman.md.
Agent
Use in Phase 5 to audit test pyramid balance, coverage gaps, and test quality.