@polymorphism-tech/morph-spec 4.16.0 → 4.17.0

package/framework/agents.json

@@ -1,1085 +1,1175 @@
-{
-  "$schema": "./agent-schema.json",
-  "version": "4.0.0",
-  "total_agents": 22,
-  "tiers": {
-    "tier_1_orchestrators": 2,
-    "tier_2_leaders": 3,
-    "tier_3_specialists": 12,
-    "tier_4_validators": 5
-  },
-  "agents": {
-    "standards-architect": {
-      "color": "red",
-      "tier": 1,
-      "title": "Chief Architect",
-      "group": "domain-analysis",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "user",
-      "domains": [
-        "architecture",
-        "developer-experience"
-      ],
-      "keywords": [],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "Team Lead (Delegate Mode)",
-        "icon": "🎯",
-        "triggers": "cross-domain conflicts, full spec synthesis, architecture decisions, team coordination",
-        "spawn_prompt": "You are the Chief Architect and Team Lead for MORPH-SPEC. Coordinate Domain Leaders, resolve architectural conflicts, and synthesize results.\n\nWorkflow:\n1. Read `.morph/state.json` for active feature and phase\n2. Read `.morph/features/{feature}/spec.md` for scope\n3. Delegate to Domain Leaders — DO NOT implement code yourself\n4. Synthesize results and escalate unresolvable conflicts to the user\n\nRefer to the Domain Knowledge section below for naming rules, instant-fail checks, and VSA project structure."
-      }
-    },
-    "ai-system-architect": {
-      "color": "orange",
-      "tier": 1,
-      "title": "AI/Agent Architect",
-      "group": "domain-analysis",
-      "active_phases": [
-        "design",
-        "tasks"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "ai-orchestration",
-        "architecture"
-      ],
-      "keywords": [
-        "agent system",
-        "ai architecture",
-        "orchestration",
-        "multi-agent",
-        "agent workflow"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "AI Architect",
-        "icon": "🤖",
-        "triggers": "AI system design, agent workflows, MCP integration, orchestration patterns",
-        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and AI orchestration patterns.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for AI requirements\n2. Design architecture using patterns from Domain Knowledge section below\n3. Delegate implementation to ms-agent-expert and vector-search-expert\n\nDO NOT implement code yourself. Refer to the Domain Knowledge section below for the 20 agentic patterns, MAF orchestration, and RAG pipeline architecture."
-      }
-    },
-    "dotnet-senior": {
-      "color": "blue",
-      "tier": 2,
-      "title": "Backend Squad Leader",
-      "group": "backend",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "backend",
-        "backend-api",
-        "architecture"
-      ],
-      "keywords": [
-        "backend",
-        "api",
-        "dotnet",
-        ".net",
-        "csharp",
-        "c#",
-        "web api",
-        "minimal api",
-        "vertical slice",
-        "vertical-slice",
-        "vsa",
-        "minimal apis",
-        "ihandler",
-        "result pattern",
-        "feature slice",
-        "scrutor",
-        "vertical slice architecture",
-        "scaffold",
-        "feature-slice",
-        "vsa-scaffold",
-        "rest",
-        "openapi",
-        "swagger",
-        "versioning",
-        "rate limiting",
-        "endpoint"
-      ],
-      "validators": [
-        "architecture",
-        "packages"
-      ],
-      "standards": [
-        {
-          "id": "architecture-vertical-slice-vertical-slice",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-scrutor",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-result-pattern",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-fluent-validation-vsa",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-scalar-ui",
-          "scope": "implement",
-          "priority": "reference"
-        },
-        {
-          "id": "backend-dotnet-vsa-handler-patterns",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "stacks": [
-        "dotnet"
-      ],
-      "teammate": {
-        "role": "Backend Squad Leader",
-        "icon": "⚙️",
-        "triggers": ".NET/C# backend, VSA architecture, EF Core, API design, backend squad coordination",
-        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists and own VSA architecture, API design, and .NET/C# standards.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for backend requirements\n2. Produce VSA Blueprint: entity fields, operations (slices), routes, error types, validation rules\n3. Delegate to squad: ef-modeler, hangfire-orchestrator, ms-agent-expert, supabase-expert, vector-search-expert, asaas-financial, clerk-auth, resend-email\n\nRefer to the Domain Knowledge section below for IHandler, Result<T>, Scrutor, IApiEndpoint patterns and code templates."
-      }
-    },
-    "infra-architect": {
-      "color": "green",
-      "tier": 2,
-      "title": "Infrastructure Squad Leader",
-      "group": "infra",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "infrastructure",
-        "infrastructure-cicd",
-        "infrastructure-containers"
-      ],
-      "keywords": [
-        "infrastructure",
-        "infra",
-        "cloud",
-        "deployment",
-        "hosting",
-        "ci/cd",
-        "container",
-        "iac",
-        "pipeline",
-        "easypanel",
-        "docker",
-        "containerize",
-        "dockerfile",
-        "multi-stage",
-        "deploy",
-        "release",
-        "github actions"
-      ],
-      "validators": [],
-      "standards": [],
-      "stacks": [
-        "docker"
-      ],
-      "teammate": {
-        "role": "Infrastructure Squad Leader",
-        "icon": "🏗️",
-        "triggers": "Docker, CI/CD, GitHub Actions, EasyPanel deployment, containerization",
-        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate Docker, CI/CD, and EasyPanel deployment.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for infrastructure requirements\n2. Design containerization and deployment architecture\n3. Escalate to standards-architect on cross-domain conflicts\n\nRefer to the Domain Knowledge section below for Docker, GitHub Actions, and EasyPanel patterns."
-      }
-    },
-    "ui-designer": {
-      "color": "purple",
-      "tier": 2,
-      "title": "UI/UX Squad Leader",
-      "group": "frontend",
-      "active_phases": [
-        "uiux"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "frontend-design"
-      ],
-      "keywords": [
-        "wireframe",
-        "mockup",
-        "user flow",
-        "ux",
-        "design",
-        "interface design",
-        "user experience",
-        "page",
-        "dashboard",
-        "form",
-        "UI",
-        "settings",
-        "interface",
-        "screen",
-        "panel",
-        "portal",
-        "view"
-      ],
-      "validators": [
-        "design-system",
-        "contrast"
-      ],
-      "standards": [
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "UI/UX Squad Leader",
-        "icon": "🎨",
-        "triggers": "UI/UX design, wireframes, user flows, design system, shadcn/ui component selection",
-        "spawn_prompt": "You are the UI/UX Squad Leader. Create wireframes, design system, and user flows during the UI/UX phase.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for UI requirements\n3. Generate deliverables: design-system.md, mockups.md, components.md, flows.md\n4. Coordinate squad: nextjs-expert, css-specialist, seo-growth-hacker\n\nWork is UI/UX phase ONLY — no implementation code. Refer to the Domain Knowledge section below for design brief protocol, shadcn/ui reference, and accessibility rules."
-      }
-    },
-    "ef-modeler": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Data Persistence Specialist (Relational)",
-      "stacks": ["dotnet"],
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-data"
-      ],
-      "keywords": [
-        "entity",
-        "database",
-        "migration",
-        "ef core",
-        "entity framework",
-        "sql",
-        "dbcontext"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [],
-      "teammate": {
-        "role": "Data Persistence Specialist",
-        "icon": "🗄️",
-        "triggers": "Entity Framework, database entities, migrations, DbContext, SQL schema design",
-        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Design and implement entities, migrations, and database schema.\n\nWorkflow:\n1. Read spec.md and VSA Blueprint from dotnet-senior for entity definitions\n2. Implement entity models, EF configurations, and migrations\n\nCRITICAL: Use IDbContextFactory for background services and Hangfire jobs — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for entity patterns, configuration patterns, and migration checklist."
-      }
-    },
-    "hangfire-orchestrator": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Background Jobs Specialist",
-      "stacks": ["hangfire"],
-      "group": "backend",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-jobs"
-      ],
-      "keywords": [
-        "scheduled",
-        "job",
-        "background",
-        "cron",
-        "hangfire",
-        "recurring",
-        "fire and forget",
-        "delayed"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [],
-      "teammate": {
-        "role": "Background Jobs Specialist",
-        "icon": "⏰",
-        "triggers": "background jobs, scheduled tasks, cron jobs, webhooks, async job pipelines",
-        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget, delayed, recurring, and continuation jobs.\n\nWorkflow:\n1. Read spec.md for background processing requirements\n2. Implement jobs with proper scoped service patterns\n\nCRITICAL: Use IDbContextFactory or IRepositoryFactory for scoped DB operations — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for setup, job types, retry patterns, and dashboard configuration."
-      }
-    },
-    "ms-agent-expert": {
-      "color": "yellow",
-      "tier": 3,
-      "title": "Microsoft Agent Framework Expert",
-      "stacks": ["dotnet", "semantic-kernel", "ms-agents"],
-      "group": "ai",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "ai-system-architect",
-      "domains": [
-        "ai-agents"
-      ],
-      "keywords": [
-        "agent",
-        "ai",
-        "llm",
-        "rag",
-        "embedding",
-        "mcp",
-        "a2a",
-        "middleware",
-        "microsoft agent framework",
-        "ichatclient"
-      ],
-      "validators": [
-        "architecture",
-        "packages"
-      ],
-      "standards": [
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Microsoft Agent Framework Expert",
-        "icon": "🤖",
-        "triggers": "Microsoft Agent Framework, IChatClient, agent workflows, MCP tools, A2A protocol",
-        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement AI agent systems using IChatClient, AIFunctionFactory, and workflow patterns.\n\nWorkflow:\n1. Read spec.md for AI agent requirements\n2. Review architecture from ai-system-architect\n3. Implement using Microsoft.Extensions.AI patterns\n\nRefer to the Domain Knowledge section below for agent implementation, tool registration, MCP integration, and A2A protocol patterns."
-      }
-    },
-    "supabase-expert": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Supabase & PostgreSQL Specialist",
-      "stacks": ["supabase"],
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-supabase"
-      ],
-      "keywords": [
-        "supabase",
-        "postgresql",
-        "rls",
-        "realtime",
-        "pgvector",
-        "row level security",
-        "edge functions"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "Supabase & PostgreSQL Specialist",
-        "icon": "🐘",
-        "triggers": "Supabase, PostgreSQL, RLS policies, pgvector, Edge Functions, Realtime subscriptions",
-        "spawn_prompt": "You are the Supabase & PostgreSQL Specialist. Implement auth, RLS, Realtime, Edge Functions, and pgvector.\n\nWorkflow:\n1. Read spec.md for database and auth requirements\n2. Design RLS policies and schema\n3. ALWAYS use PgBouncer (port 6543) for application connections\n\nRefer to the Domain Knowledge section below for RLS patterns, migration workflow, pgvector setup, and Clerk JWT integration."
-      }
-    },
-    "vector-search-expert": {
-      "color": "yellow",
-      "tier": 3,
-      "title": "Vector Search & RAG Specialist",
-      "group": "ai",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "ai-system-architect",
-      "domains": [
-        "ai-vector"
-      ],
-      "keywords": [
-        "vector db",
-        "embeddings",
-        "semantic search",
-        "rag",
-        "pgvector",
-        "similarity search",
-        "retrieval augmented"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Vector Search & RAG Specialist",
-        "icon": "🔎",
-        "triggers": "vector embeddings, RAG pipelines, semantic search, pgvector, HNSW indexes",
-        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement embeddings, similarity search, and RAG pipelines.\n\nWorkflow:\n1. Read spec.md for search and retrieval requirements\n2. Review AI architecture from ai-system-architect\n3. Implement chunking, embedding, and retrieval components\n\nRefer to the Domain Knowledge section below for chunking strategies, pgvector setup, hybrid search, and RAG tool patterns."
-      }
-    },
-    "asaas-financial": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Payment Integration Specialist (Brazil)",
-      "stacks": ["asaas"],
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "integration-payment"
-      ],
-      "keywords": [
-        "asaas",
-        "payment",
-        "pix",
-        "boleto",
-        "credit card",
-        "subscription",
-        "pagamento"
-      ],
-      "validators": [
-        "architecture",
-        "contract-compliance"
-      ],
-      "standards": [],
-      "teammate": {
-        "role": "Payment Integration Specialist",
-        "icon": "💳",
-        "triggers": "PIX payments, Boleto, Asaas SDK, subscription billing, Brazilian payments",
-        "spawn_prompt": "You are the Payment Integration Specialist (Asaas/Brazil). Implement PIX, Boleto, Credit Card, and subscription billing.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Asaas SDK patterns, webhook handling, and payment flow examples."
-      }
-    },
-    "clerk-auth": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Auth SaaS Integration Specialist",
-      "stacks": ["clerk"],
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "integration-auth"
-      ],
-      "keywords": [
-        "clerk",
-        "clerk auth",
-        "add auth",
-        "implement auth",
-        "login",
-        "signup",
-        "oauth"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "Auth SaaS Integration Specialist",
-        "icon": "🔐",
-        "triggers": "Clerk authentication, login/signup flows, OAuth, session management",
-        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk). Implement authentication flows and session management with Next.js App Router.\n\nRefer to the Domain Knowledge section below for Clerk SDK patterns, middleware configuration, and webhook handling."
-      }
-    },
-    "resend-email": {
-      "color": "teal",
-      "tier": 3,
-      "title": "Email Integration Specialist",
-      "stacks": ["resend"],
-      "group": "backend",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "integration-email"
-      ],
-      "keywords": [
-        "resend",
-        "email",
-        "transactional email",
-        "email notification",
-        "send email",
-        "email template",
-        "smtp"
-      ],
-      "validators": [
-        "architecture",
-        "contract-compliance"
-      ],
-      "standards": [],
-      "teammate": {
-        "role": "Email Integration Specialist",
-        "icon": "📧",
-        "triggers": "transactional email, Resend SDK, email templates, notifications",
-        "spawn_prompt": "You are the Email Integration Specialist (Resend). Implement transactional email delivery.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Resend SDK patterns, React Email templates, and error handling."
-      }
-    },
-    "nextjs-expert": {
-      "color": "pink",
-      "tier": 3,
-      "title": "Next.js Development Specialist",
-      "stacks": ["nextjs"],
-      "group": "frontend",
-      "active_phases": [
-        "uiux",
-        "design",
-        "tasks",
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "frontend-nextjs",
-        "frontend-nextjs-ui"
-      ],
-      "keywords": [
-        "next.js",
-        "nextjs",
-        "react",
-        "tsx",
-        "shadcn",
-        "tailwind",
-        "tanstack",
-        "react-query",
-        "zod",
-        "react-hook-form",
-        "app router",
-        "server component",
-        "client component",
-        "vercel",
-        "neon",
-        "planetscale",
-        "framer-motion",
-        "animation",
-        "transition",
-        "scaffold",
-        "feature-page",
-        "motion design",
-        "shadcn theme",
-        "tailwind tokens",
-        "tailwind config",
-        "design system",
-        "icon system",
-        "lucide",
-        "animated",
-        "micro-interaction",
-        "hover effect",
-        "scroll animation",
-        "page transition",
-        "variants",
-        "AnimatePresence"
-      ],
-      "validators": [
-        "nextjs-component",
-        "design-system"
-      ],
-      "standards": [
-        {
-          "id": "frontend-nextjs-naming-conventions",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-project-structure",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-app-router",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-components",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-data-fetching",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-forms",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-state-management",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-testing",
-          "scope": "implement",
-          "priority": "reference"
-        },
-        {
-          "id": "frontend-nextjs-nextjs-patterns",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-motion-patterns",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Next.js Development Specialist",
-        "icon": "⚛️",
-        "triggers": "Next.js, React, shadcn/ui, TanStack Query, Framer Motion, App Router",
-        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ apps with shadcn/ui, TanStack Query, and Framer Motion.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for frontend requirements\n3. Implement with App Router patterns (Server Components default, \"use client\" only when needed)\n\nALWAYS: useReducedMotion() for WCAG compliance. Never edit shadcn/ui primitives.\n\nRefer to the Domain Knowledge section below for App Router patterns, data fetching, animation, and component reference."
-      }
-    },
-    "css-specialist": {
-      "color": "pink",
-      "tier": 3,
-      "title": "CSS & Design System Specialist",
-      "group": "frontend",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "frontend-css"
-      ],
-      "keywords": [
-        "css",
-        "design system",
-        "styling",
-        "theme",
-        "design tokens",
-        "palette"
-      ],
-      "validators": [
-        "css",
-        "contrast",
-        "design-system"
-      ],
-      "standards": [
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "CSS & Design System Specialist",
-        "icon": "🎨",
-        "triggers": "CSS design tokens, Tailwind, color palette, WCAG accessibility, design system compliance",
-        "spawn_prompt": "You are the CSS & Design System Specialist. Validate and enforce design token compliance across all styling.\n\nMANDATORY FIRST STEP: Read `.morph/context/design-system.md` — any missing tokens must be added there before making fixes.\n\nRefer to the Domain Knowledge section below for token categories, naming conventions, and WCAG accessibility rules."
-      }
-    },
-    "seo-growth-hacker": {
-      "color": "pink",
-      "tier": 3,
-      "title": "SEO & Growth Specialist",
-      "group": "frontend",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "seo"
-      ],
-      "keywords": [
-        "seo",
-        "landing page",
-        "meta tags",
-        "core web vitals",
-        "schema markup",
-        "organic traffic",
-        "content marketing"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "SEO & Growth Specialist",
-        "icon": "📈",
-        "triggers": "SEO, meta tags, schema markup, Core Web Vitals, Lighthouse, structured data",
-        "spawn_prompt": "You are the SEO & Growth Specialist. Implement technical SEO, structured data, and Core Web Vitals optimization for Next.js.\n\nWorkflow:\n1. Read spec.md for SEO requirements and target keywords\n2. Audit existing pages and implement optimizations\n3. Target: 90+ Performance, 100 Accessibility, 100 Best Practices, 100 SEO on Lighthouse\n\nRefer to the Domain Knowledge section below for meta tag patterns, JSON-LD schemas, and Next.js optimization."
-      }
-    },
-    "morph-spec-architect": {
-      "color": "cyan",
-      "tier": 3,
-      "title": "Morph-Spec Architect",
-      "group": "domain-analysis",
-      "active_phases": [
-        "design",
-        "tasks"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "cli",
-        "framework-design",
-        "nodejs",
-        "architecture"
-      ],
-      "keywords": [
-        "morph-spec",
-        "framework feature",
-        "new command",
-        "cli architecture",
-        "plugin",
-        "hook design"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "specialist",
-        "icon": "🔧",
-        "triggers": "morph-spec framework, new CLI commands, hook design, plugin architecture",
-        "spawn_prompt": "You are the Morph-Spec Architect. You design new features for the morph-spec-framework CLI tool itself.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for the new framework feature requirements\n2. Review `bin/morph-spec.js` for existing command registrations\n3. Identify reusable modules in `src/commands/`, `src/core/`, `src/lib/`, `src/utils/`\n\nFocus areas:\n- CLI command design: Commander.js command definition, option parsing, help text\n- State impact: does the new feature require new state.json fields? (src/core/state/state-manager.js)\n- Output schema: does it produce new output types? (src/core/paths/output-schema.js)\n- Hook integration: does it need new hook events or hook scripts?\n- Test strategy: which test files in test/ need to be created/updated\n- ESM patterns: import/export, no CommonJS, Node.js 18+ APIs\n\nArchitecture rules:\n- Commands are thin wrappers — business logic goes in src/core/ or src/lib/\n- Follow existing normalizeOutputType(), derivePhase() patterns\n- Run `npm run generate` after modifying output-schema.js\n- All tests use node:test (no Jest/Mocha), run sequentially with --test-concurrency=1"
-      }
-    },
-    "security-expert": {
-      "color": "gray",
-      "tier": 4,
-      "title": "Security Validator",
-      "group": "testing",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "security"
-      ],
-      "keywords": [
-        "sql injection",
-        "xss",
-        "secrets",
-        "security scan",
-        "vulnerability",
-        "csrf",
-        "insecure deserialization"
-      ],
-      "validators": [
-        "security"
-      ],
-      "standards": [],
-      "teammate": {
-        "icon": "🛡️",
-        "role": "Security Validator (read-only)",
-        "triggers": "security scan, SQL injection, XSS, hardcoded secrets, CSRF validation",
-        "spawn_prompt": "You are the Security Validator (READ-ONLY). Scan for security vulnerabilities across all source files.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .cs, .tsx, .ts, .js files in the project\n2. Check for: SQL injection (string concat in queries), hardcoded secrets, XSS, insecure deserialization, CSRF\n\nScan checklist:\n- SQL injection: string concatenation inside SQL/EF raw queries ($\"...{var}...\" patterns)\n- Hardcoded secrets: API keys, passwords, connection strings in source (not in appsettings/env)\n- XSS: unsanitized HTML rendering (dangerouslySetInnerHTML without sanitization)\n- Insecure deserialization: BinaryFormatter usage\n- CSRF: POST forms/endpoints missing anti-forgery tokens\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
-      },
-      "hook_behavior": {
-        "validates": [
-          "SQL injection (string concatenation in queries)",
-          "Hardcoded secrets (API keys, passwords, connection strings)",
-          "XSS (unsanitized HTML rendering)",
-          "Insecure deserialization (BinaryFormatter)",
-          "CSRF (missing anti-forgery tokens)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "architecture-expert": {
-      "color": "gray",
-      "tier": 4,
-      "title": "Architecture Validator",
-      "group": "domain-analysis",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "architecture"
-      ],
-      "keywords": [
-        "architecture",
-        "clean code",
-        "solid",
-        "dependency injection"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [],
-      "teammate": {
-        "icon": "🏗️",
-        "role": "Architecture Validator (read-only)",
-        "triggers": "architecture validation, VSA slice violations, async anti-patterns, DI registration order",
-        "spawn_prompt": "You are the Architecture Validator (READ-ONLY). Scan for architectural violations in .NET VSA projects.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .cs files and Program.cs\n2. Check for: DbContext injection, async anti-patterns, DI registration order, VSA violations\n\nScan checklist:\n- DbContext injection: direct DbContext injection in background services (use IDbContextFactory)\n- Async anti-patterns: .Result, .Wait(), .GetAwaiter().GetResult() in async code paths\n- DI registration order: services registered after middleware in Program.cs (services before app.Use*/Map*)\n- VSA slice violations: cross-feature imports (Feature A referencing Feature B internals), shared code not in Shared project\n- Handler pattern: Handlers must return Result<T>, use CancellationToken, be sealed\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
-      },
-      "hook_behavior": {
-        "validates": [
-          "DbContext injection (IDbContextFactory required)",
-          "Async/await patterns (no .Result or .Wait)",
-          "DI registration order (services before middleware)",
-          "VSA slice isolation (no cross-feature imports)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "packages-validator": {
-      "color": "gray",
-      "tier": 4,
-      "title": "Packages Validator",
-      "group": "testing",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "packages"
-      ],
-      "keywords": [
-        "nuget",
-        "packages",
-        "dependencies",
-        "version conflict"
-      ],
-      "validators": [
-        "packages"
-      ],
-      "standards": [],
-      "teammate": {
-        "icon": "📦",
-        "role": "Packages Validator (read-only)",
-        "triggers": "NuGet packages, version conflicts, package vulnerabilities, .NET 10 compatibility",
-        "spawn_prompt": "You are the Packages Validator (READ-ONLY). Scan for NuGet and npm package issues.\n\nWhen invoked:\n1. Use Grep and Glob to scan all *.csproj files and package.json files\n2. Check for: version conflicts, incompatible packages, security vulnerabilities\n\nScan checklist:\n- NuGet version conflicts: same PackageReference appearing with different versions across .csproj files\n- .NET 10 compatibility: verify major package versions target .NET 10 (TargetFramework net10.0)\n- Security vulnerabilities: outdated packages (Newtonsoft.Json < 13.0.1, System.Text.Json < 8.0.5, etc.)\n- npm duplicates: duplicate dependencies across package.json, outdated major versions\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
-      },
-      "hook_behavior": {
-        "validates": [
-          "NuGet version conflicts (same package, different versions)",
-          "Incompatible .NET 10 packages",
-          "Security vulnerabilities (outdated packages)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "design-system-validator": {
-      "color": "gray",
-      "tier": 4,
-      "title": "Design System Validator",
-      "group": "frontend",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "design-system"
-      ],
-      "keywords": [
-        "design system",
-        "css",
-        "color palette",
-        "spacing",
-        "motion tokens",
-        "glassmorphism",
-        "design trends",
-        "advanced effects"
-      ],
-      "validators": [
-        "design-system"
-      ],
-      "standards": [
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🎨",
-        "role": "Design System Validator (read-only)",
-        "triggers": "CSS token compliance, hardcoded colors, spacing violations, motion tokens",
-        "spawn_prompt": "You are the Design System Validator (READ-ONLY). Scan CSS and component files for design token compliance.\n\nWhen invoked:\n1. Read `.morph/context/design-system.md` for project-specific design tokens\n2. Use Grep and Glob to scan all .css, .scss, .tsx, .ts files under src/\n\nScan checklist:\n- Colors: hardcoded hex/rgb instead of var(--color-primary/accent/surface-*/text-*)\n- Spacing: hardcoded px/rem instead of var(--space-*)\n- Typography: hardcoded font-size/family instead of var(--font-display/body/text-*)\n- Motion: hardcoded transition durations instead of var(--duration-*/easing-*)\n- Shadows: hardcoded box-shadow instead of var(--shadow-*/shadow-colored-*/shadow-layered-*)\n- Advanced effects: glassmorphism must use var(--glass-*), aurora var(--aurora-*), perspective var(--perspective-*)\n- Naming: verify kebab-case for custom CSS class names\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"warning\" }]\n}\n\nDo NOT modify any files."
-      },
-      "hook_behavior": {
-        "validates": [
-          "CSS color palette compliance (primary, accent, surface, text, neutral, semantic)",
-          "Spacing values (use var(--space-*))",
-          "Typography scale (use var(--font-display), var(--font-body), var(--text-*))",
-          "Motion tokens (use var(--duration-*), var(--easing-*))",
-          "Shadow tokens (use var(--shadow-*), var(--shadow-colored-*), var(--shadow-layered-*))",
-          "Advanced effects (glassmorphism: var(--glass-*), aurora: var(--aurora-*), perspective: var(--perspective-*))",
-          "Component naming (kebab-case for CSS)"
-        ],
-        "severity": "warning",
-        "blocks_on_fail": false
-      }
-    },
-    "nextjs-component-validator": {
-      "color": "gray",
-      "tier": 4,
-      "title": "Next.js Component Validator",
-      "group": "frontend",
-      "active_phases": [
-        "implement"
-      ],
-      "domains": [
-        "frontend-nextjs"
-      ],
-      "keywords": [
-        "nextjs",
-        "tsx",
-        "use client",
-        "server component",
-        "app router"
-      ],
-      "validators": [
-        "nextjs-component"
-      ],
-      "stacks": [
-        "nextjs"
-      ],
-      "teammate": {
-        "icon": "⚛️",
-        "role": "Next.js Component Validator (read-only)",
-        "triggers": "use client directive, React hooks validation, server component checks",
-        "spawn_prompt": "You are the Next.js Component Validator (READ-ONLY). Scan TypeScript/TSX files for App Router compliance.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .tsx/.ts files under src/\n2. Check for: incorrect \"use client\" usage, file naming violations, import pattern issues\n\nScan checklist:\n- \"use client\" required: must be present when React hooks (useState, useEffect, useRef, etc.) are used\n- \"use client\" absent: must NOT be present for pure Server Components (no hooks, no event handlers)\n- File naming: component files must use kebab-case (e.g., user-profile.tsx, not UserProfile.tsx)\n- Import patterns: client components must not import server-only modules (next/headers, cookies(), etc.)\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"message\": string, \"suggestion\": string, \"severity\": \"warning\" }]\n}\n\nDo NOT modify any files."
-      },
-      "hook_behavior": {
-        "severity": "warning",
-        "blocks_on_fail": false,
-        "validates": [
-          "use-client directive",
-          "hook usage",
-          "file naming"
-        ]
-      }
-    }
-  },
-  "squads": {
-    "backend_squad": {
-      "leader": "dotnet-senior",
-      "members": [
-        "ef-modeler",
-        "hangfire-orchestrator",
-        "ms-agent-expert",
-        "supabase-expert",
-        "vector-search-expert",
-        "asaas-financial",
-        "clerk-auth",
-        "resend-email"
-      ],
-      "domains": [
-        "backend",
-        "backend-data",
-        "backend-api",
-        "backend-jobs",
-        "ai-agents",
-        "backend-supabase",
-        "ai-vector",
-        "integration-payment",
-        "integration-auth",
-        "integration-email"
-      ]
-    },
-    "frontend_squad": {
-      "leader": "ui-designer",
-      "members": [
-        "nextjs-expert",
-        "css-specialist",
-        "seo-growth-hacker"
-      ],
-      "domains": [
-        "frontend-design",
-        "frontend-nextjs",
-        "frontend-nextjs-ui",
-        "frontend-css",
-        "seo"
-      ],
-      "active_phases": {
-        "design": [
-          "ui-designer"
-        ],
-        "implement": [
-          "nextjs-expert",
-          "css-specialist",
-          "seo-growth-hacker"
-        ]
-      }
-    },
-    "infrastructure_squad": {
-      "leader": "infra-architect",
-      "members": [],
-      "domains": [
-        "infrastructure",
-        "infrastructure-cicd",
-        "infrastructure-containers"
-      ]
-    },
-    "quality_squad": {
-      "leader": "standards-architect",
-      "members": [],
-      "domains": [
-        "quality-testing",
-        "quality-review"
-      ],
-      "note": "No permanent leader — standards-architect coordinates directly"
-    }
-  },
-  "relationship_types": {
-    "reports_to": "Hierarchical manager relationship",
-    "coordinates": "Manages/leads these agents",
-    "escalates_to": "Where to escalate unresolved issues",
-    "collaborates_with": "Peer agents for cross-domain work",
-    "runs_in": "Execution context (hooks, not teammates)",
-    "team_role": "Role in Agent Teams (lead, domain_leader, specialist, validator, escalation_specialist, post_implementation, planning_only)"
-  }
-}
+{
+  "version": "4.0.0",
+  "total_agents": 23,
+  "tiers": {
+    "tier_1_orchestrators": 2,
+    "tier_2_leaders": 3,
+    "tier_3_specialists": 13,
+    "tier_4_validators": 5
+  },
+  "agents": {
+    "standards-architect": {
+      "color": "red",
+      "tier": 1,
+      "title": "Chief Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "user",
+      "domains": [
+        "architecture",
+        "developer-experience"
+      ],
+      "keywords": [],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "Team Lead (Delegate Mode)",
+        "icon": "🎯",
+        "triggers": "cross-domain conflicts, full spec synthesis, architecture decisions, team coordination",
+        "spawn_prompt": "You are the Chief Architect and Team Lead for MORPH-SPEC. Coordinate Domain Leaders, resolve architectural conflicts, and synthesize results.\n\nWorkflow:\n1. Read `.morph/state.json` for active feature and phase\n2. Read `.morph/features/{feature}/spec.md` for scope\n3. Delegate to Domain Leaders — DO NOT implement code yourself\n4. Synthesize results and escalate unresolvable conflicts to the user\n\nRefer to the Domain Knowledge section below for naming rules, instant-fail checks, and VSA project structure."
+      }
+    },
+    "ai-system-architect": {
+      "color": "orange",
+      "tier": 1,
+      "title": "AI/Agent Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "tasks"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "ai-orchestration",
+        "architecture"
+      ],
+      "keywords": [
+        "agent system",
+        "ai architecture",
+        "orchestration",
+        "multi-agent",
+        "agent workflow"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-production",
+          "scope": "implement",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "AI Architect",
+        "icon": "🤖",
+        "triggers": "AI system design, agent workflows, MCP integration, orchestration patterns",
+        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and AI orchestration patterns.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for AI requirements\n2. Design architecture using patterns from Domain Knowledge section below\n3. Delegate implementation to ms-agent-expert and vector-search-expert\n\nDO NOT implement code yourself. Refer to the Domain Knowledge section below for the 20 agentic patterns, MAF orchestration, and RAG pipeline architecture."
+      }
+    },
+    "dotnet-senior": {
+      "color": "blue",
+      "tier": 2,
+      "title": "Backend Squad Leader",
+      "group": "backend",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "backend",
+        "backend-api",
+        "architecture"
+      ],
+      "keywords": [
+        "backend",
+        "api",
+        "dotnet",
+        ".net",
+        "csharp",
+        "c#",
+        "web api",
+        "minimal api",
+        "vertical slice",
+        "vertical-slice",
+        "vsa",
+        "minimal apis",
+        "ihandler",
+        "result pattern",
+        "feature slice",
+        "scrutor",
+        "vertical slice architecture",
+        "scaffold",
+        "feature-slice",
+        "vsa-scaffold",
+        "rest",
+        "openapi",
+        "swagger",
+        "versioning",
+        "rate limiting",
+        "endpoint"
+      ],
+      "validators": [
+        "architecture",
+        "packages"
+      ],
+      "standards": [
+        {
+          "id": "architecture-vertical-slice-vertical-slice",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-scrutor",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-result-pattern",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-fluent-validation-vsa",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "backend-dotnet-scalar-ui",
+          "scope": "implement",
+          "priority": "reference"
+        },
+        {
+          "id": "backend-dotnet-vsa-handler-patterns",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "stacks": [
+        "dotnet"
+      ],
+      "teammate": {
+        "role": "Backend Squad Leader",
+        "icon": "⚙️",
+        "triggers": ".NET/C# backend, VSA architecture, EF Core, API design, backend squad coordination",
+        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists and own VSA architecture, API design, and .NET/C# standards.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for backend requirements\n2. Produce VSA Blueprint: entity fields, operations (slices), routes, error types, validation rules\n3. Delegate to squad: ef-modeler, hangfire-orchestrator, ms-agent-expert, neon-expert, vector-search-expert, asaas-financial, clerk-auth, resend-email\n\nRefer to the Domain Knowledge section below for IHandler, Result<T>, Scrutor, IApiEndpoint patterns and code templates."
+      }
+    },
+    "infra-architect": {
+      "color": "green",
+      "tier": 2,
+      "title": "Infrastructure Squad Leader",
+      "group": "infra",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "infrastructure",
+        "infrastructure-cicd",
+        "infrastructure-containers"
+      ],
+      "keywords": [
+        "infrastructure",
+        "infra",
+        "cloud",
+        "deployment",
+        "hosting",
+        "ci/cd",
+        "container",
+        "iac",
+        "pipeline",
+        "easypanel",
+        "docker",
+        "containerize",
+        "dockerfile",
+        "multi-stage",
+        "deploy",
+        "release",
+        "github actions"
+      ],
+      "validators": [],
+      "standards": [],
+      "stacks": [
+        "docker"
+      ],
+      "teammate": {
+        "role": "Infrastructure Squad Leader",
+        "icon": "🏗️",
+        "triggers": "Docker, CI/CD, GitHub Actions, EasyPanel deployment, containerization",
+        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate Docker, CI/CD, and EasyPanel deployment.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for infrastructure requirements\n2. Design containerization and deployment architecture\n3. Escalate to standards-architect on cross-domain conflicts\n\nRefer to the Domain Knowledge section below for Docker, GitHub Actions, and EasyPanel patterns."
+      }
+    },
+    "ui-designer": {
+      "color": "purple",
+      "tier": 2,
+      "title": "UI/UX Squad Leader",
+      "group": "frontend",
+      "active_phases": [
+        "uiux"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "frontend-design"
+      ],
+      "keywords": [
+        "wireframe",
+        "mockup",
+        "user flow",
+        "ux",
+        "design",
+        "interface design",
+        "user experience",
+        "page",
+        "dashboard",
+        "form",
+        "UI",
+        "settings",
+        "interface",
+        "screen",
+        "panel",
+        "portal",
+        "view"
+      ],
+      "validators": [
+        "design-system",
+        "contrast"
+      ],
+      "standards": [
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "UI/UX Squad Leader",
+        "icon": "🎨",
+        "triggers": "UI/UX design, wireframes, user flows, design system, shadcn/ui component selection",
+        "spawn_prompt": "You are the UI/UX Squad Leader. Create wireframes, design system, and user flows during the UI/UX phase.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for UI requirements\n3. Generate deliverables: design-system.md, mockups.md, components.md, flows.md\n4. Coordinate squad: nextjs-expert, css-specialist, seo-growth-hacker\n\nWork is UI/UX phase ONLY — no implementation code. Refer to the Domain Knowledge section below for design brief protocol, shadcn/ui reference, and accessibility rules."
+      }
+    },
+    "ef-modeler": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Data Persistence Specialist (Relational)",
+      "stacks": ["dotnet"],
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-data"
+      ],
+      "keywords": [
+        "entity",
+        "database",
+        "migration",
+        "ef core",
+        "entity framework",
+        "sql",
+        "dbcontext"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [],
+      "teammate": {
+        "role": "Data Persistence Specialist",
+        "icon": "🗄️",
+        "triggers": "Entity Framework, database entities, migrations, DbContext, SQL schema design",
+        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Design and implement entities, migrations, and database schema.\n\nWorkflow:\n1. Read spec.md and VSA Blueprint from dotnet-senior for entity definitions\n2. Implement entity models, EF configurations, and migrations\n\nCRITICAL: Use IDbContextFactory for background services and Hangfire jobs — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for entity patterns, configuration patterns, and migration checklist."
+      }
+    },
+    "hangfire-orchestrator": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Background Jobs Specialist",
+      "stacks": ["hangfire"],
+      "group": "backend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-jobs"
+      ],
+      "keywords": [
+        "scheduled",
+        "job",
+        "background",
+        "cron",
+        "hangfire",
+        "recurring",
+        "fire and forget",
+        "delayed"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [],
+      "teammate": {
+        "role": "Background Jobs Specialist",
+        "icon": "⏰",
+        "triggers": "background jobs, scheduled tasks, cron jobs, webhooks, async job pipelines",
+        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget, delayed, recurring, and continuation jobs.\n\nWorkflow:\n1. Read spec.md for background processing requirements\n2. Implement jobs with proper scoped service patterns\n\nCRITICAL: Use IDbContextFactory or IRepositoryFactory for scoped DB operations — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for setup, job types, retry patterns, and dashboard configuration."
+      }
+    },
+    "ms-agent-expert": {
+      "color": "yellow",
+      "tier": 3,
+      "title": "Microsoft Agent Framework Expert",
+      "stacks": ["dotnet", "semantic-kernel", "ms-agents"],
+      "group": "ai",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-agents"
+      ],
+      "keywords": [
+        "agent",
+        "ai",
+        "llm",
+        "rag",
+        "embedding",
+        "mcp",
+        "a2a",
+        "middleware",
+        "microsoft agent framework",
+        "ichatclient"
+      ],
+      "validators": [
+        "architecture",
+        "packages"
+      ],
+      "standards": [
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-production",
+          "scope": "implement",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Microsoft Agent Framework Expert",
+        "icon": "🤖",
+        "triggers": "Microsoft Agent Framework, IChatClient, agent workflows, MCP tools, A2A protocol",
+        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement AI agent systems using IChatClient, AIFunctionFactory, and workflow patterns.\n\nWorkflow:\n1. Read spec.md for AI agent requirements\n2. Review architecture from ai-system-architect\n3. Implement using Microsoft.Extensions.AI patterns\n\nRefer to the Domain Knowledge section below for agent implementation, tool registration, MCP integration, and A2A protocol patterns."
+      }
+    },
+    "neon-expert": {
+      "color": "green",
+      "tier": 3,
+      "title": "Neon PostgreSQL & AI Data Specialist",
+      "stacks": ["neon"],
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "tasks",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "backend-database",
+        "ai-vector"
+      ],
+      "keywords": [
+        "neon",
+        "serverless postgres",
+        "database",
+        "postgresql",
+        "pgvector",
+        "pgrag",
+        "vector search",
+        "embeddings",
+        "semantic kernel",
+        "connection string",
+        "branching",
+        "scale-to-zero",
+        "ef core database",
+        "migration"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "neon-setup",
+          "scope": "neon"
+        },
+        {
+          "id": "neon-pgvector",
+          "scope": "neon"
+        },
+        {
+          "id": "neon-pgrag",
+          "scope": "neon"
+        },
+        {
+          "id": "neon-semantic-kernel",
+          "scope": "neon"
+        }
+      ],
+      "teammate": {
+        "role": "Neon PostgreSQL & AI Data Specialist",
+        "icon": "\uD83D\uDC18",
+        "triggers": "database setup, pgvector, pgrag, vector search, embeddings, Neon branching, RAG pipeline, Semantic Kernel vector store, neonctl",
+        "spawn_prompt": "You are the Neon PostgreSQL & AI Data Specialist. Implement database schemas, RLS policies, pgvector embeddings, pgrag RAG pipelines, and manage Neon branches.\n\nWorkflow:\n1. Read spec.md for database, vector search, and RAG requirements\n2. Review architecture from dotnet-senior for entity and schema design\n3. ALWAYS use the pooled connection (-pooler endpoint) for application code — direct connections only for EF Core migrations\n4. Implement RLS policies using auth.user_id() (Neon Authorize) with Clerk JWT\n5. Set up pgvector with HNSW indexes and tune maintenance_work_mem before index creation\n6. For RAG pipelines, use pgrag extensions (rag, rag_bge_small_en_v15, rag_jina_reranker_v1_tiny_en) for chunking, embedding, search, and reranking entirely in SQL\n7. Create database branches for PR previews (--schema-only) and run schema-diff before merging\n8. Configure connection retry logic for scale-to-zero cold starts\n\nCRITICAL: Two connection strings — pooled for application, direct for migrations. Never use direct connections in application code.\n\nRefer to the Domain Knowledge section below for connection pooling, RLS patterns, pgvector setup, pgrag pipeline, branching strategy, and scale-to-zero configuration."
+      }
+    },
+    "vector-search-expert": {
+      "color": "yellow",
+      "tier": 3,
+      "title": "Vector Search & RAG Specialist",
+      "group": "ai",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "ai-system-architect",
+      "domains": [
+        "ai-vector"
+      ],
+      "keywords": [
+        "vector db",
+        "embeddings",
+        "semantic search",
+        "rag",
+        "pgvector",
+        "similarity search",
+        "retrieval augmented"
+      ],
+      "validators": [],
+      "standards": [
+        {
+          "id": "ai-agents-setup",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "ai-agents-workflows",
+          "scope": "design",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Vector Search & RAG Specialist",
+        "icon": "🔎",
+        "triggers": "vector embeddings, RAG pipelines, semantic search, pgvector, HNSW indexes",
+        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement embeddings, similarity search, and RAG pipelines.\n\nWorkflow:\n1. Read spec.md for search and retrieval requirements\n2. Review AI architecture from ai-system-architect\n3. Implement chunking, embedding, and retrieval components\n\nRefer to the Domain Knowledge section below for chunking strategies, pgvector setup, hybrid search, and RAG tool patterns."
+      }
+    },
+    "asaas-financial": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Payment Integration Specialist (Brazil)",
+      "stacks": ["asaas"],
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-payment"
+      ],
+      "keywords": [
+        "asaas",
+        "payment",
+        "pix",
+        "boleto",
+        "credit card",
+        "subscription",
+        "pagamento"
+      ],
+      "validators": [
+        "architecture",
+        "contract-compliance"
+      ],
+      "standards": [],
+      "teammate": {
+        "role": "Payment Integration Specialist",
+        "icon": "💳",
+        "triggers": "PIX payments, Boleto, Asaas SDK, subscription billing, Brazilian payments",
+        "spawn_prompt": "You are the Payment Integration Specialist (Asaas/Brazil). Implement PIX, Boleto, Credit Card, and subscription billing.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Asaas SDK patterns, webhook handling, and payment flow examples."
+      }
+    },
+    "clerk-auth": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Auth SaaS Integration Specialist",
+      "stacks": ["clerk"],
+      "group": "backend",
+      "active_phases": [
+        "design",
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-auth"
+      ],
+      "keywords": [
+        "clerk",
+        "clerk auth",
+        "add auth",
+        "implement auth",
+        "login",
+        "signup",
+        "oauth"
+      ],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "Auth SaaS Integration Specialist",
+        "icon": "🔐",
+        "triggers": "Clerk authentication, login/signup flows, OAuth, session management",
+        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk). Implement authentication flows and session management with Next.js App Router.\n\nRefer to the Domain Knowledge section below for Clerk SDK patterns, middleware configuration, and webhook handling."
+      }
+    },
+    "resend-email": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Email Integration Specialist",
+      "stacks": ["resend"],
+      "group": "backend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "dotnet-senior",
+      "domains": [
+        "integration-email"
+      ],
+      "keywords": [
+        "resend",
+        "email",
+        "transactional email",
+        "email notification",
+        "send email",
+        "email template",
+        "smtp"
+      ],
+      "validators": [
+        "architecture",
+        "contract-compliance"
+      ],
+      "standards": [],
+      "teammate": {
+        "role": "Email Integration Specialist",
+        "icon": "📧",
+        "triggers": "transactional email, Resend SDK, email templates, notifications",
+        "spawn_prompt": "You are the Email Integration Specialist (Resend). Implement transactional email delivery.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Resend SDK patterns, React Email templates, and error handling."
+      }
+    },
+    "nextjs-expert": {
+      "color": "pink",
+      "tier": 3,
+      "title": "Next.js Development Specialist",
+      "stacks": ["nextjs"],
+      "group": "frontend",
+      "active_phases": [
+        "uiux",
+        "design",
+        "tasks",
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-nextjs",
+        "frontend-nextjs-ui"
+      ],
+      "keywords": [
+        "next.js",
+        "nextjs",
+        "react",
+        "tsx",
+        "shadcn",
+        "tailwind",
+        "tanstack",
+        "react-query",
+        "zod",
+        "react-hook-form",
+        "app router",
+        "server component",
+        "client component",
+        "vercel",
+        "neon",
+        "planetscale",
+        "framer-motion",
+        "animation",
+        "transition",
+        "scaffold",
+        "feature-page",
+        "motion design",
+        "shadcn theme",
+        "tailwind tokens",
+        "tailwind config",
+        "design system",
+        "icon system",
+        "lucide",
+        "animated",
+        "micro-interaction",
+        "hover effect",
+        "scroll animation",
+        "page transition",
+        "variants",
+        "AnimatePresence"
+      ],
+      "validators": [
+        "nextjs-component",
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-nextjs-naming-conventions",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-project-structure",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-app-router",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-components",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-data-fetching",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-forms",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-state-management",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-testing",
+          "scope": "implement",
+          "priority": "reference"
+        },
+        {
+          "id": "frontend-nextjs-nextjs-patterns",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-nextjs-motion-patterns",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "Next.js Development Specialist",
+        "icon": "⚛️",
+        "triggers": "Next.js, React, shadcn/ui, TanStack Query, Framer Motion, App Router",
+        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ apps with shadcn/ui, TanStack Query, and Framer Motion.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for frontend requirements\n3. Implement with App Router patterns (Server Components default, \"use client\" only when needed)\n\nALWAYS: useReducedMotion() for WCAG compliance. Never edit shadcn/ui primitives.\n\nRefer to the Domain Knowledge section below for App Router patterns, data fetching, animation, and component reference."
+      }
+    },
+    "css-specialist": {
+      "color": "pink",
+      "tier": 3,
+      "title": "CSS & Design System Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-css"
+      ],
+      "keywords": [
+        "css",
+        "design system",
+        "styling",
+        "theme",
+        "design tokens",
+        "palette"
+      ],
+      "validators": [
+        "css",
+        "contrast",
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "role": "CSS & Design System Specialist",
+        "icon": "🎨",
+        "triggers": "CSS design tokens, Tailwind, color palette, WCAG accessibility, design system compliance",
+        "spawn_prompt": "You are the CSS & Design System Specialist. Validate and enforce design token compliance across all styling.\n\nMANDATORY FIRST STEP: Read `.morph/context/design-system.md` — any missing tokens must be added there before making fixes.\n\nRefer to the Domain Knowledge section below for token categories, naming conventions, and WCAG accessibility rules."
+      }
+    },
+    "gsap-animator": {
+      "color": "green",
+      "tier": 3,
+      "title": "GSAP Animation Specialist",
+      "stacks": ["nextjs"],
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "frontend-gsap"
+      ],
+      "keywords": [
+        "gsap",
+        "greensock",
+        "scrolltrigger",
+        "scroll trigger",
+        "svg morph",
+        "morphsvg",
+        "drawsvg",
+        "splittext",
+        "text animation",
+        "flip animation",
+        "motion path",
+        "gsap timeline",
+        "pinning",
+        "scrubbing",
+        "parallax",
+        "complex animation",
+        "svg animation",
+        "useGSAP",
+        "draggable",
+        "observer"
+      ],
+      "validators": [
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-gsap-core",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-gsap-scrolltrigger",
+          "scope": "implement",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-gsap-plugins",
+          "scope": "implement",
+          "priority": "reference"
+        }
+      ],
+      "teammate": {
+        "role": "GSAP Animation Specialist",
+        "icon": "🎬",
+        "triggers": "GSAP animations, ScrollTrigger, SVG morphing, complex timelines, scroll-driven animations, SplitText, Flip layout transitions",
+        "spawn_prompt": "You are the GSAP Animation Specialist. Implement complex animations using GSAP with ScrollTrigger, timelines, and premium plugins in Next.js.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for animation requirements\n3. Always use useGSAP() hook from @gsap/react for React integration\n4. Check prefers-reduced-motion before any animation\n5. Never mix GSAP and Framer Motion on the same DOM element\n6. Register plugins ONCE at app init, not inside components\n\nRefer to the Domain Knowledge section below for GSAP core APIs, ScrollTrigger patterns, plugin usage, and performance optimization."
+      }
+    },
+    "seo-growth-hacker": {
+      "color": "pink",
+      "tier": 3,
+      "title": "SEO & Growth Specialist",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "seo"
+      ],
+      "keywords": [
+        "seo",
+        "landing page",
+        "meta tags",
+        "core web vitals",
+        "schema markup",
+        "organic traffic",
+        "content marketing"
+      ],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "SEO & Growth Specialist",
+        "icon": "📈",
+        "triggers": "SEO, meta tags, schema markup, Core Web Vitals, Lighthouse, structured data",
+        "spawn_prompt": "You are the SEO & Growth Specialist. Implement technical SEO, structured data, and Core Web Vitals optimization for Next.js.\n\nWorkflow:\n1. Read spec.md for SEO requirements and target keywords\n2. Audit existing pages and implement optimizations\n3. Target: 90+ Performance, 100 Accessibility, 100 Best Practices, 100 SEO on Lighthouse\n\nRefer to the Domain Knowledge section below for meta tag patterns, JSON-LD schemas, and Next.js optimization."
+      }
+    },
+    "morph-spec-architect": {
+      "color": "cyan",
+      "tier": 3,
+      "title": "Morph-Spec Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "tasks"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "cli",
+        "framework-design",
+        "nodejs",
+        "architecture"
+      ],
+      "keywords": [
+        "morph-spec",
+        "framework feature",
+        "new command",
+        "cli architecture",
+        "plugin",
+        "hook design"
+      ],
+      "validators": [],
+      "standards": [],
+      "teammate": {
+        "role": "specialist",
+        "icon": "🔧",
+        "triggers": "morph-spec framework, new CLI commands, hook design, plugin architecture",
+        "spawn_prompt": "You are the Morph-Spec Architect. You design new features for the morph-spec-framework CLI tool itself.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for the new framework feature requirements\n2. Review `bin/morph-spec.js` for existing command registrations\n3. Identify reusable modules in `src/commands/`, `src/core/`, `src/lib/`, `src/utils/`\n\nFocus areas:\n- CLI command design: Commander.js command definition, option parsing, help text\n- State impact: does the new feature require new state.json fields? (src/core/state/state-manager.js)\n- Output schema: does it produce new output types? (src/core/paths/output-schema.js)\n- Hook integration: does it need new hook events or hook scripts?\n- Test strategy: which test files in test/ need to be created/updated\n- ESM patterns: import/export, no CommonJS, Node.js 18+ APIs\n\nArchitecture rules:\n- Commands are thin wrappers — business logic goes in src/core/ or src/lib/\n- Follow existing normalizeOutputType(), derivePhase() patterns\n- Run `npm run generate` after modifying output-schema.js\n- All tests use node:test (no Jest/Mocha), run sequentially with --test-concurrency=1"
+      }
+    },
+    "security-expert": {
+      "color": "gray",
+      "tier": 4,
+      "title": "Security Validator",
+      "group": "testing",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "security"
+      ],
+      "keywords": [
+        "sql injection",
+        "xss",
+        "secrets",
+        "security scan",
+        "vulnerability",
+        "csrf",
+        "insecure deserialization"
+      ],
+      "validators": [
+        "security"
+      ],
+      "standards": [],
+      "teammate": {
+        "icon": "🛡️",
+        "role": "Security Validator (read-only)",
+        "triggers": "security scan, SQL injection, XSS, hardcoded secrets, CSRF validation",
+        "spawn_prompt": "You are the Security Validator (READ-ONLY). Scan for security vulnerabilities across all source files.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .cs, .tsx, .ts, .js files in the project\n2. Check for: SQL injection (string concat in queries), hardcoded secrets, XSS, insecure deserialization, CSRF\n\nScan checklist:\n- SQL injection: string concatenation inside SQL/EF raw queries ($\"...{var}...\" patterns)\n- Hardcoded secrets: API keys, passwords, connection strings in source (not in appsettings/env)\n- XSS: unsanitized HTML rendering (dangerouslySetInnerHTML without sanitization)\n- Insecure deserialization: BinaryFormatter usage\n- CSRF: POST forms/endpoints missing anti-forgery tokens\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
+      },
+      "hook_behavior": {
+        "validates": [
+          "SQL injection (string concatenation in queries)",
+          "Hardcoded secrets (API keys, passwords, connection strings)",
+          "XSS (unsanitized HTML rendering)",
+          "Insecure deserialization (BinaryFormatter)",
+          "CSRF (missing anti-forgery tokens)"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "architecture-expert": {
+      "color": "gray",
+      "tier": 4,
+      "title": "Architecture Validator",
+      "group": "domain-analysis",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "architecture"
+      ],
+      "keywords": [
+        "architecture",
+        "clean code",
+        "solid",
+        "dependency injection"
+      ],
+      "validators": [
+        "architecture"
+      ],
+      "standards": [],
+      "teammate": {
+        "icon": "🏗️",
+        "role": "Architecture Validator (read-only)",
+        "triggers": "architecture validation, VSA slice violations, async anti-patterns, DI registration order",
+        "spawn_prompt": "You are the Architecture Validator (READ-ONLY). Scan for architectural violations in .NET VSA projects.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .cs files and Program.cs\n2. Check for: DbContext injection, async anti-patterns, DI registration order, VSA violations\n\nScan checklist:\n- DbContext injection: direct DbContext injection in background services (use IDbContextFactory)\n- Async anti-patterns: .Result, .Wait(), .GetAwaiter().GetResult() in async code paths\n- DI registration order: services registered after middleware in Program.cs (services before app.Use*/Map*)\n- VSA slice violations: cross-feature imports (Feature A referencing Feature B internals), shared code not in Shared project\n- Handler pattern: Handlers must return Result<T>, use CancellationToken, be sealed\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
+      },
+      "hook_behavior": {
+        "validates": [
+          "DbContext injection (IDbContextFactory required)",
+          "Async/await patterns (no .Result or .Wait)",
+          "DI registration order (services before middleware)",
+          "VSA slice isolation (no cross-feature imports)"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "packages-validator": {
+      "color": "gray",
+      "tier": 4,
+      "title": "Packages Validator",
+      "group": "testing",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "standards-architect",
+      "domains": [
+        "packages"
+      ],
+      "keywords": [
+        "nuget",
+        "packages",
+        "dependencies",
+        "version conflict"
+      ],
+      "validators": [
+        "packages"
+      ],
+      "standards": [],
+      "teammate": {
+        "icon": "📦",
+        "role": "Packages Validator (read-only)",
+        "triggers": "NuGet packages, version conflicts, package vulnerabilities, .NET 10 compatibility",
+        "spawn_prompt": "You are the Packages Validator (READ-ONLY). Scan for NuGet and npm package issues.\n\nWhen invoked:\n1. Use Grep and Glob to scan all *.csproj files and package.json files\n2. Check for: version conflicts, incompatible packages, security vulnerabilities\n\nScan checklist:\n- NuGet version conflicts: same PackageReference appearing with different versions across .csproj files\n- .NET 10 compatibility: verify major package versions target .NET 10 (TargetFramework net10.0)\n- Security vulnerabilities: outdated packages (Newtonsoft.Json < 13.0.1, System.Text.Json < 8.0.5, etc.)\n- npm duplicates: duplicate dependencies across package.json, outdated major versions\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
+      },
+      "hook_behavior": {
+        "validates": [
+          "NuGet version conflicts (same package, different versions)",
+          "Incompatible .NET 10 packages",
+          "Security vulnerabilities (outdated packages)"
+        ],
+        "severity": "error",
+        "blocks_on_fail": true
+      }
+    },
+    "design-system-validator": {
+      "color": "gray",
+      "tier": 4,
+      "title": "Design System Validator",
+      "group": "frontend",
+      "active_phases": [
+        "*"
+      ],
+      "reports_to": "ui-designer",
+      "domains": [
+        "design-system"
+      ],
+      "keywords": [
+        "design system",
+        "css",
+        "color palette",
+        "spacing",
+        "motion tokens",
+        "glassmorphism",
+        "design trends",
+        "advanced effects"
+      ],
+      "validators": [
+        "design-system"
+      ],
+      "standards": [
+        {
+          "id": "frontend-design-system-naming",
+          "scope": "all",
+          "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-animations",
+          "scope": "all",
+          "priority": "required"
+        }
+      ],
+      "teammate": {
+        "icon": "🎨",
+        "role": "Design System Validator (read-only)",
+        "triggers": "CSS token compliance, hardcoded colors, spacing violations, motion tokens",
+        "spawn_prompt": "You are the Design System Validator (READ-ONLY). Scan CSS and component files for design token compliance.\n\nWhen invoked:\n1. Read `.morph/context/design-system.md` for project-specific design tokens\n2. Use Grep and Glob to scan all .css, .scss, .tsx, .ts files under src/\n\nScan checklist:\n- Colors: hardcoded hex/rgb instead of var(--color-primary/accent/surface-*/text-*)\n- Spacing: hardcoded px/rem instead of var(--space-*)\n- Typography: hardcoded font-size/family instead of var(--font-display/body/text-*)\n- Motion: hardcoded transition durations instead of var(--duration-*/easing-*)\n- Shadows: hardcoded box-shadow instead of var(--shadow-*/shadow-colored-*/shadow-layered-*)\n- Advanced effects: glassmorphism must use var(--glass-*), aurora var(--aurora-*), perspective var(--perspective-*)\n- Naming: verify kebab-case for custom CSS class names\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"warning\" }]\n}\n\nDo NOT modify any files."
+      },
+      "hook_behavior": {
+        "validates": [
+          "CSS color palette compliance (primary, accent, surface, text, neutral, semantic)",
+          "Spacing values (use var(--space-*))",
+          "Typography scale (use var(--font-display), var(--font-body), var(--text-*))",
+          "Motion tokens (use var(--duration-*), var(--easing-*))",
+          "Shadow tokens (use var(--shadow-*), var(--shadow-colored-*), var(--shadow-layered-*))",
+          "Advanced effects (glassmorphism: var(--glass-*), aurora: var(--aurora-*), perspective: var(--perspective-*))",
+          "Component naming (kebab-case for CSS)"
+        ],
+        "severity": "warning",
+        "blocks_on_fail": false
+      }
+    },
+    "nextjs-component-validator": {
+      "color": "gray",
+      "tier": 4,
+      "title": "Next.js Component Validator",
+      "group": "frontend",
+      "active_phases": [
+        "implement"
+      ],
+      "domains": [
+        "frontend-nextjs"
+      ],
+      "keywords": [
+        "nextjs",
+        "tsx",
+        "use client",
+        "server component",
+        "app router"
+      ],
+      "validators": [
+        "nextjs-component"
+      ],
+      "stacks": [
+        "nextjs"
+      ],
+      "teammate": {
+        "icon": "⚛️",
+        "role": "Next.js Component Validator (read-only)",
+        "triggers": "use client directive, React hooks validation, server component checks",
+        "spawn_prompt": "You are the Next.js Component Validator (READ-ONLY). Scan TypeScript/TSX files for App Router compliance.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .tsx/.ts files under src/\n2. Check for: incorrect \"use client\" usage, file naming violations, import pattern issues\n\nScan checklist:\n- \"use client\" required: must be present when React hooks (useState, useEffect, useRef, etc.) are used\n- \"use client\" absent: must NOT be present for pure Server Components (no hooks, no event handlers)\n- File naming: component files must use kebab-case (e.g., user-profile.tsx, not UserProfile.tsx)\n- Import patterns: client components must not import server-only modules (next/headers, cookies(), etc.)\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"message\": string, \"suggestion\": string, \"severity\": \"warning\" }]\n}\n\nDo NOT modify any files."
+      },
+      "hook_behavior": {
+        "severity": "warning",
+        "blocks_on_fail": false,
+        "validates": [
+          "use-client directive",
+          "hook usage",
+          "file naming"
+        ]
+      }
+    }
+  },
+  "squads": {
+    "backend_squad": {
+      "leader": "dotnet-senior",
+      "members": [
+        "ef-modeler",
+        "hangfire-orchestrator",
+        "ms-agent-expert",
+        "neon-expert",
+        "vector-search-expert",
+        "asaas-financial",
+        "clerk-auth",
+        "resend-email"
+      ],
+      "domains": [
+        "backend",
+        "backend-data",
+        "backend-api",
+        "backend-jobs",
+        "ai-agents",
+        "backend-database",
+        "ai-vector",
+        "integration-payment",
+        "integration-auth",
+        "integration-email"
+      ]
+    },
+    "frontend_squad": {
+      "leader": "ui-designer",
+      "members": [
+        "nextjs-expert",
+        "css-specialist",
+        "gsap-animator",
+        "seo-growth-hacker"
+      ],
+      "domains": [
+        "frontend-design",
+        "frontend-nextjs",
+        "frontend-nextjs-ui",
+        "frontend-css",
+        "frontend-gsap",
+        "seo"
+      ],
+      "active_phases": {
+        "design": [
+          "ui-designer"
+        ],
+        "implement": [
+          "nextjs-expert",
+          "css-specialist",
+          "gsap-animator",
+          "seo-growth-hacker"
+        ]
+      }
+    },
+    "infrastructure_squad": {
+      "leader": "infra-architect",
+      "members": [],
+      "domains": [
+        "infrastructure",
+        "infrastructure-cicd",
+        "infrastructure-containers"
+      ]
+    },
+    "quality_squad": {
+      "leader": "standards-architect",
+      "members": [],
+      "domains": [
+        "quality-testing",
+        "quality-review"
+      ],
+      "note": "No permanent leader — standards-architect coordinates directly"
+    }
+  },
+  "relationship_types": {
+    "reports_to": "Hierarchical manager relationship",
+    "coordinates": "Manages/leads these agents",
+    "escalates_to": "Where to escalate unresolved issues",
+    "collaborates_with": "Peer agents for cross-domain work",
+    "runs_in": "Execution context (hooks, not teammates)",
+    "team_role": "Role in Agent Teams (lead, domain_leader, specialist, validator, escalation_specialist, post_implementation, planning_only)"
+  }
+}