# πŸ”„ Agent Flow Architecture > **AG Kit 2026.7.26** β€” Antigravity-native production workflow documentation --- ## Antigravity runtime boundary AG Kit defines project behavior in `.agents/`; Google Antigravity is the production runtime that discovers and executes it. ```text User request ↓ Antigravity workspace discovery β”œβ”€β”€ .agents/rules/ persistent constraints β”œβ”€β”€ .agents/skills/ progressive domain context β”œβ”€β”€ .agents/workflows/ slash-command procedures β”œβ”€β”€ .agents/agent/ specialist role definitions └── .agents/memory/ durable project context ↓ Routing and orchestration β”œβ”€β”€ direct specialist selection β”œβ”€β”€ /coordinate β†’ parallel read/research + synthesis └── /orchestrate β†’ plan β†’ user approval β†’ delegated implementation ↓ Tool boundary β”œβ”€β”€ Antigravity permissions and workspace trust └── .agents/hooks.json β†’ PreToolUse safety gate ↓ Execution, validation, evidence, and result delivery β”œβ”€β”€ /agents and /tasks are runtime state β”œβ”€β”€ toolkit validators and project tests are evidence └── memory is updated only for durable accepted information ``` ### Six production integration phases | Phase | Responsibility | Source of truth | | --- | --- | --- | | 1. Discovery | Load rules, skills, and workflows | `.agents/rules/`, `.agents/skills/`, `.agents/workflows/` | | 2. MCP | Validate workspace servers and explicitly sync reviewed config | `.agents/mcp_config.json` | | 3. Hooks | Gate high-confidence destructive command patterns | `.agents/hooks.json` and `.agents/hooks/validate-tool-call.mjs` | | 4. Orchestration | Coordinate specialist roles without creating a second scheduler | workflows, agent definitions, Antigravity `/agents` and `/tasks` | | 5. Plugin | Package reviewed components for optional local installation | `.agents/hooks/build-plugin.mjs` | | 6. Validation | Prove structure, compatibility, security, CLI, and web health | CI, Doctor, regression tests, and `PRODUCTION_CHECKLIST.md` | ### Runtime safety rules 1. Antigravity permission and workspace-trust controls remain enabled. 2. The AG Kit hook supplements those controls; it is not a sandbox. 3. Destructive behavior is tested with mocked payloads, never by executing a real destructive command. 4. MCP writes require explicit `--apply`; unresolved placeholders block the write. 5. The repository `.agents/` tree remains the source of truth even when a plugin bundle is installed. 6. Planning, deployment, destructive operations, and security-sensitive work retain human approval gates. ## πŸ” Version Resolution Layer Before an agent is invoked, AG Kit resolves the component contract recorded in `.agents/manifest.json`, verifies the selected skill version against the agent's SemVer range, and rejects stale registry/lock state during validation. Workflow metadata declares required agents, required skills, and expected artifacts, enabling deterministic orchestration without changing the existing Markdown-first runtime. ```text Request β†’ Workflow metadata β†’ Agent version β†’ Skill range β†’ Tool boundary β†’ Verification artifact ``` The generated dependency graph is available at `.agents/DEPENDENCY_GRAPH.md`. --- ## πŸ“Š Overview Flow Diagram ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ USER REQUEST β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ REQUEST CLASSIFICATION β”‚ β”‚ β€’ Analyze intent (build, debug, test, deploy, etc.) β”‚ β”‚ β€’ Identify domain (frontend, backend, mobile, etc.) β”‚ β”‚ β€’ Detect complexity (simple, medium, complex) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β–Ό β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ WORKFLOW COMMAND β”‚ β”‚ DIRECT AGENT β”‚ β”‚ (Slash Command) β”‚ β”‚ ASSIGNMENT β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β–Ό β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ /brainstorm β”‚ β”‚ Agent Selection β”‚ β”‚ /coordinate β”‚ β”‚ Based on Domain β”‚ β”‚ /create β”‚ β”‚ β”‚ β”‚ /debug β”‚ β”‚ β€’ frontend-* β”‚ β”‚ /deploy β”‚ β”‚ β€’ backend-* β”‚ β”‚ /enhance β”‚ β”‚ β€’ mobile-* β”‚ β”‚ /orchestrate β”‚ β”‚ β€’ database-* β”‚ β”‚ /plan β”‚ β”‚ β€’ devops-* β”‚ β”‚ /remember β”‚ β”‚ β€’ test-* β”‚ β”‚ /verify β”‚ β”‚ β€’ security-* β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ AGENT INITIALIZATION β”‚ β”‚ β€’ Load agent persona/role β”‚ β”‚ β€’ Load required skills β”‚ β”‚ β€’ Set behavioral mode β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ SKILL LOADING PROTOCOL β”‚ β”‚ β”‚ β”‚ 1. Read SKILL.md metadata β”‚ β”‚ 2. Load references/ (if needed) β”‚ β”‚ 3. Execute scripts/ (if needed) β”‚ β”‚ 4. Apply rules and patterns β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ TASK EXECUTION β”‚ β”‚ β”‚ β”‚ β€’ Analyze codebase β”‚ β”‚ β€’ Apply best practices β”‚ β”‚ β€’ Generate/modify code β”‚ β”‚ β€’ Run validations β”‚ β”‚ β€’ Execute tests β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ VALIDATION LAYER β”‚ β”‚ β”‚ β”‚ Quick Check (checklist.py): β”‚ β”‚ β€’ Security scan β”‚ β”‚ β€’ Code quality (lint/types) β”‚ β”‚ β€’ Schema validation β”‚ β”‚ β€’ Test suite β”‚ β”‚ β€’ UX audit β”‚ β”‚ β€’ SEO check β”‚ β”‚ β”‚ β”‚ Full Check (verify_all.py): β”‚ β”‚ β€’ All above + Lighthouse β”‚ β”‚ β€’ E2E tests (Playwright) β”‚ β”‚ β€’ Bundle analysis β”‚ β”‚ β€’ Mobile audit β”‚ β”‚ β€’ i18n check β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ RESULT DELIVERY β”‚ β”‚ β€’ Present changes to user β”‚ β”‚ β€’ Provide explanations β”‚ β”‚ β€’ Suggest next steps β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` --- ## 🎯 Detailed Agent Workflow ### 1️⃣ **Request Entry Points** ``` User Input Types: β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ A. Natural Language Request β”‚ β”‚ "Build a React dashboard with charts" β”‚ β”‚ β”‚ β”‚ B. Slash Command β”‚ β”‚ "/create feature: user authentication" β”‚ β”‚ β”‚ β”‚ C. Domain-Specific Request β”‚ β”‚ "Optimize database queries" β†’ database-architect β”‚ β”‚ "Fix security vulnerability" β†’ security-auditor β”‚ β”‚ "Deploy to AWS" β†’ devops-engineer β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` #### Socratic Gate Protocol Before implementation, verify: - **New Feature** β†’ ASK 3 strategic questions - **Bug Fix** β†’ Confirm understanding + ask impact - **Vague request** β†’ Ask Purpose, Users, Scope ### 2️⃣ **Agent Selection Matrix** #### Agent Routing Checklist (Mandatory) Before ANY code/design work: | Step | Check | If Unchecked | | ---- | ---------------------------- | ---------------------------------------- | | 1 | Identify correct agent | β†’ Analyze request domain | | 2 | Read agent's .md file | β†’ Open `.agents/agent/{agent}.md` | | 3 | Announce agent | β†’ `πŸ€– Applying knowledge of @[agent]...` | | 4 | Load skills from frontmatter | β†’ Check `skills:` field | ``` Request Domain β†’ Agent Mapping: β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Domain β”‚ Primary Agent β”‚ Skills Loaded β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ UI/UX Design β”‚ frontend-specialist β”‚ nextjs-react-expert β”‚ β”‚ β”‚ β”‚ frontend-architecture β”‚ β”‚ β”‚ β”‚ frontend-design β”‚ β”‚ β”‚ β”‚ tailwind-patterns β”‚ | β”‚ β”‚ web-design-guidelines β”‚ β”‚ β”‚ β”‚ lint-and-validate β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ API Development β”‚ backend-specialist β”‚ api-patterns β”‚ β”‚ β”‚ β”‚ nodejs-best-practices β”‚ β”‚ β”‚ β”‚ python-patterns β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Database Design β”‚ database-architect β”‚ database-design β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Mobile App β”‚ mobile-developer β”‚ mobile-design β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Game Development β”‚ game-developer β”‚ game-development β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ DevOps/Deployment β”‚ devops-engineer β”‚ deployment-procedures β”‚ β”‚ β”‚ β”‚ server-management β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Security Audit β”‚ security-auditor β”‚ vulnerability-scanner β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Penetration Testing β”‚ penetration-tester β”‚ red-team-tactics β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Testing β”‚ test-engineer β”‚ testing-patterns β”‚ β”‚ β”‚ β”‚ webapp-testing β”‚ β”‚ β”‚ β”‚ tdd-workflow β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Debugging β”‚ debugger β”‚ systematic-debugging β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Performance β”‚ performance- β”‚ performance-profiling β”‚ β”‚ β”‚ optimizer β”‚ β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ SEO β”‚ seo-specialist β”‚ seo-fundamentals β”‚ β”‚ β”‚ β”‚ geo-fundamentals β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Documentation β”‚ documentation- β”‚ documentation-templates β”‚ β”‚ β”‚ writer β”‚ β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Planning/Discovery β”‚ project-planner β”‚ brainstorming β”‚ β”‚ β”‚ β”‚ plan-writing β”‚ β”‚ β”‚ β”‚ architecture β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Multi-Agent Tasks β”‚ orchestrator β”‚ parallel-agents β”‚ β”‚ β”‚ β”‚ behavioral-modes β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` ### 3️⃣ **Skill Loading Protocol** ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ SKILL LOADING FLOW β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ Step 1: Match Request to Skill β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ User: "Build a REST API" β”‚ β”‚ ↓ β”‚ β”‚ Keyword Match: "API" β†’ api-patterns β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ↓ Step 2: Load Skill Metadata β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Read: .agents/skills/api-patterns/ β”‚ β”‚ └── SKILL.md (main instructions) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ↓ Step 3: Load References (if needed) β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Read: api-patterns/rest.md β”‚ β”‚ api-patterns/graphql.md β”‚ β”‚ api-patterns/auth.md β”‚ β”‚ api-patterns/documentation.md β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ↓ Step 4: Execute Scripts (if needed) β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Run: scripts/api_validator.py β”‚ β”‚ (validates API design) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ↓ Step 5: Apply Knowledge β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Agent now has: β”‚ β”‚ β€’ API design patterns β”‚ β”‚ β€’ Authentication strategies β”‚ β”‚ β€’ Documentation templates β”‚ β”‚ β€’ Validation scripts β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ### Related Skills Pattern Skills now link to each other: - `frontend-design` β†’ `web-design-guidelines` (after coding) - `web-design-guidelines` β†’ `frontend-design` (before coding) > **Note**: Scripts are NOT auto-executed. AI suggests running them, user approves. ``` ### 4️⃣ **Workflow Command Execution** ``` Slash Command Flow: /brainstorm ↓ 1. Load: brainstorming skill 2. Apply: Socratic questioning 3. Output: Structured discovery document /create ↓ 1. Detect: Project type (web/mobile/api/game) 2. Load: app-builder skill + domain-specific skills 3. Select: Template from app-builder/templates/ 4. Scaffold: Generate project structure 5. Validate: Run checklist.py /debug ↓ 1. Load: systematic-debugging skill 2. Analyze: Error logs, stack traces 3. Apply: Root cause analysis 4. Suggest: Fix with code examples 5. Test: Verify fix works /deploy ↓ 1. Load: deployment-procedures skill 2. Detect: Platform (Vercel, AWS, Docker, etc.) 3. Prepare: Build artifacts 4. Execute: Deployment scripts 5. Verify: Health checks 6. Output: Deployment URL /test ↓ 1. Load: testing-patterns + webapp-testing skills 2. Detect: Test framework (Jest, Vitest, Playwright) 3. Generate: Test cases 4. Execute: Run tests 5. Report: Coverage + results /orchestrate ↓ 1. Load: parallel-agents skill 2. Decompose: Task into subtasks 3. Assign: Each subtask to specialist agent 4. Coordinate: Parallel execution 5. Merge: Combine results 6. Validate: Run full verification /plan ↓ 1. Load: plan-writing + architecture skills 2. Analyze: Requirements 3. Break down: Tasks with estimates 4. Output: Structured plan with milestones ``` ### 5️⃣ **Multi-Agent Orchestration** ``` Complex Task β†’ /orchestrate β†’ Multiple Specialist Personas Example: "Build a full-stack e-commerce app" β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ ORCHESTRATOR AGENT β”‚ β”‚ Decomposes task into sequential workstreams β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”‚ β”‚ β–Ό β–Ό β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ FRONTEND β”‚ β”‚ BACKEND β”‚ β”‚ DATABASE β”‚ β”‚ SPECIALIST β”‚ β”‚ SPECIALIST β”‚ β”‚ ARCHITECT β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ Skills: β”‚ β”‚ Skills: β”‚ β”‚ Skills: β”‚ β”‚ β€’ react-* β”‚ β”‚ β€’ api-* β”‚ β”‚ β€’ database-* β”‚ β”‚ β€’ nextjs-* β”‚ β”‚ β€’ nodejs-* β”‚ β”‚ β€’ prisma-* β”‚ β”‚ β€’ tailwind-* β”‚ β”‚ β€’ nestjs-* β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ β”‚ Builds: β”‚ β”‚ Builds: β”‚ β”‚ Builds: β”‚ β”‚ β€’ UI/UX β”‚ β”‚ β€’ REST API β”‚ β”‚ β€’ Schema β”‚ β”‚ β€’ Components β”‚ β”‚ β€’ Auth β”‚ β”‚ β€’ Migrations β”‚ β”‚ β€’ Pages β”‚ β”‚ β€’ Business β”‚ β”‚ β€’ Indexes β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β”‚ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ CODE COHERENCE β”‚ β”‚ β€’ AI maintains consistency β”‚ β”‚ β€’ Sequential context switching β”‚ β”‚ β€’ Ensure API contracts match β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ VALIDATION (All Agents) β”‚ β”‚ β€’ test-engineer β†’ Tests β”‚ β”‚ β€’ security-auditor β†’ Security β”‚ β”‚ β€’ performance-optimizer β†’ Perf β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β–Ό β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ DEPLOYMENT β”‚ β”‚ β€’ devops-engineer β†’ Deploy β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` ### 6️⃣ **Validation & Quality Gates** ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ VALIDATION PIPELINE β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ During Development (Quick Checks): β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ python .agents/scripts/checklist.py . β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ βœ“ Security Scan (vulnerabilities) β”‚ β”‚ βœ“ Code Quality (ESLint, TypeScript) β”‚ β”‚ βœ“ Schema Validation (Prisma/DB) β”‚ β”‚ βœ“ Test Suite (Unit tests) β”‚ β”‚ βœ“ UX Audit (Accessibility) β”‚ β”‚ βœ“ SEO Check (Meta tags, performance) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ Time: ~30 seconds Pre-Deployment (Full Verification): β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ python .agents/scripts/verify_all.py . β”‚ β”‚ --url http://localhost:3000 β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ βœ“ All Quick Checks β”‚ β”‚ βœ“ Lighthouse Audit (Core Web Vitals) β”‚ β”‚ βœ“ Playwright E2E Tests β”‚ β”‚ βœ“ Bundle Analysis (Size, tree-shaking) β”‚ β”‚ βœ“ Mobile Audit (Responsive, touch targets) β”‚ β”‚ βœ“ i18n Check (Translations, locale) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ Time: ~3-5 minutes ``` --- ## 🧩 Skill-to-Script Mapping ``` Skills with Automated Scripts: β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Skill β”‚ Script β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ api-patterns β”‚ scripts/api_validator.py β”‚ β”‚ database-design β”‚ scripts/schema_validator.py β”‚ β”‚ frontend-design β”‚ scripts/accessibility_checker.py β”‚ β”‚ β”‚ scripts/ux_audit.py β”‚ β”‚ geo-fundamentals β”‚ scripts/geo_checker.py β”‚ β”‚ i18n-localization β”‚ scripts/i18n_checker.py β”‚ β”‚ lint-and-validate β”‚ scripts/lint_runner.py β”‚ β”‚ β”‚ scripts/type_coverage.py β”‚ β”‚ mobile-design β”‚ scripts/mobile_audit.py β”‚ β”‚ performance-profiling β”‚ scripts/lighthouse_runner.py β”‚ β”‚ β”‚ scripts/bundle_analyzer.py β”‚ β”‚ seo-fundamentals β”‚ scripts/seo_checker.py β”‚ β”‚ testing-patterns β”‚ scripts/test_runner.py β”‚ β”‚ vulnerability-scanner β”‚ scripts/security_scanner.py β”‚ β”‚ webapp-testing β”‚ scripts/e2e_runner.py β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` --- ## πŸ”„ Complete Request Lifecycle Example ``` User Request: "Build a Next.js dashboard with authentication" 1. REQUEST CLASSIFICATION β”œβ”€ Type: Build new feature β”œβ”€ Domain: Frontend + Backend β”œβ”€ Complexity: Medium-High └─ Suggested: /create or /orchestrate 2. WORKFLOW SELECTION └─ User chooses: /orchestrate (multi-agent approach) 3. ORCHESTRATOR DECOMPOSITION β”œβ”€ Frontend: Dashboard UI (React components) β”œβ”€ Backend: Auth API (JWT, session management) β”œβ”€ Database: User schema (Prisma) └─ Testing: E2E auth flow 4. AGENT ASSIGNMENT β”œβ”€ frontend-specialist β”‚ └─ Skills: nextjs-react-expert, tailwind-patterns, frontend-design β”œβ”€ backend-specialist β”‚ └─ Skills: api-patterns, nodejs-best-practices β”œβ”€ database-architect β”‚ └─ Skills: database-design └─ test-engineer └─ Skills: testing-patterns, webapp-testing 5. SEQUENTIAL MULTI-DOMAIN EXECUTION Note: AI processes each domain sequentially, switching context between specialist "personas." This is NOT true parallel execution but simulated multi-agent behavior. β”œβ”€ Frontend builds: β”‚ β”œβ”€ app/dashboard/page.tsx (Server Component) β”‚ β”œβ”€ components/DashboardLayout.tsx β”‚ β”œβ”€ components/LoginForm.tsx β”‚ └─ lib/auth-client.ts β”œβ”€ Backend builds: β”‚ β”œβ”€ app/api/auth/login/route.ts β”‚ β”œβ”€ app/api/auth/logout/route.ts β”‚ β”œβ”€ lib/jwt.ts β”‚ └─ middleware.ts β”œβ”€ Database builds: β”‚ β”œβ”€ prisma/schema.prisma (User, Session models) β”‚ └─ prisma/migrations/ └─ Testing builds: β”œβ”€ tests/auth.spec.ts (Playwright) └─ tests/dashboard.spec.ts 6. CODE INTEGRATION Reality Note: AI writes code as a continuous stream, maintaining consistency. There is no "merge" step - it's all generated coherently from the start. └─ AI maintains coherence across domains β”œβ”€ Resolves import paths β”œβ”€ Ensures type safety └─ Connects API routes to UI 7. VALIDATION β”œβ”€ checklist.py β”‚ βœ“ Security: No leaked secrets β”‚ βœ“ Lint: No ESLint errors β”‚ βœ“ Types: TypeScript passes β”‚ βœ“ Tests: Auth flow passes └─ verify_all.py βœ“ E2E: Login β†’ Dashboard β†’ Logout works βœ“ Accessibility: WCAG AA compliant βœ“ Performance: Lighthouse score > 90 8. RESULT DELIVERY └─ User receives: β”œβ”€ Complete codebase β”œβ”€ Documentation (how to run) β”œβ”€ Test reports └─ Deployment instructions ``` --- ## πŸ“ˆ Statistics & Metrics ``` β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ SYSTEM CAPABILITIES β”‚ β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€ β”‚ Total Agents: 20 β”‚ β”‚ Total Skills: 47 β”‚ β”‚ Total Workflows: 13 β”‚ β”‚ Master Scripts: 2 (checklist, verify_all) β”‚ β”‚ Skill-Level Scripts: 16 β”‚ β”‚ Coverage: ~95% web/mobile + orchestrationβ”‚ β”‚ β”‚ β”‚ Orchestration & Memory: β”‚ β”‚ β”œβ”€ Coordinator Mode (parallel orchestration) β”‚ β”‚ β”œβ”€ Persistent Memory System (MEMORY.md) β”‚ β”‚ β”œβ”€ Context Compression (auto-compact) β”‚ β”‚ β”œβ”€ Conditional Skill Loading (when_to_use) β”‚ β”‚ └─ Verification by Execution (/verify) β”‚ β”‚ β”‚ β”‚ Supported Frameworks: β”‚ β”‚ β”œβ”€ Frontend: React 19, Next.js 16, Vue, Nuxt 4, Astro 6 β”‚ β”‚ β”œβ”€ Backend: Node.js 24, FastAPI, Express 5, Rust β”‚ β”‚ β”œβ”€ Mobile: React Native, Flutter β”‚ β”‚ β”œβ”€ Database: Prisma, Drizzle, PostgreSQL β”‚ β”‚ β”œβ”€ Testing: Jest, Vitest, Playwright, Cypress β”‚ β”‚ └─ DevOps: Docker, Vercel, AWS, GitHub Actions β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ ``` --- ## πŸŽ“ Best Practices ### When to Use Each Workflow ``` /brainstorm βœ“ Unclear requirements βœ“ Need to explore options βœ“ Complex problem needs breaking down /create βœ“ New feature in existing project βœ“ Small-to-medium complexity βœ“ Single domain (frontend OR backend) /orchestrate βœ“ Full-stack features βœ“ Complex multi-step tasks βœ“ Need multiple specialist agents /debug βœ“ Bug reports βœ“ Unexpected behavior βœ“ Performance issues /test βœ“ Need test coverage βœ“ Before deployment βœ“ After major changes /deploy βœ“ Ready to ship βœ“ After all tests pass βœ“ Need production URL /plan βœ“ Large projects βœ“ Need time estimates βœ“ Team coordination needed ``` --- ## πŸ”— Quick Reference Links - **Architecture**: `.agents/ARCHITECTURE.md` - **Agents**: `.agents/agent/` - **Skills**: `.agents/skills/` - **Workflows**: `.agents/workflows/` - **Scripts**: `.agents/scripts/` --- **Last Updated**: 2026-05-31 **Version**: 2026.5.31