@polymorphism-tech/morph-spec 4.12.0 → 4.14.0

package/framework/agents.json

@@ -1,2278 +1,1084 @@
-{
-  "$schema": "./agent-schema.json",
-  "version": "4.0.0",
-  "total_agents": 46,
-  "tiers": {
-    "tier_1_orchestrators": 3,
-    "tier_2_leaders": 4,
-    "tier_3_specialists": 31,
-    "tier_4_validators": 7
-  },
-  "agents": {
-    "standards-architect": {
-      "tier": 1,
-      "title": "Chief Architect",
-      "group": "domain-analysis",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "user",
-      "domains": [
-        "architecture",
-        "developer-experience"
-      ],
-      "keywords": [],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-program-cs-checklist",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Team Lead (Delegate Mode)",
-        "icon": "🎯",
-        "spawn_prompt": "You are the Chief Architect and Team Lead in delegate mode. Coordinate Domain Leaders, resolve conflicts, synthesize results. DO NOT implement code yourself. Escalate conflicts to user when teammates disagree on architecture/tech choices."
-      }
-    },
-    "ai-system-architect": {
-      "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": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-blazor-ui",
-          "scope": "implement",
-          "priority": "reference"
-        }
-      ],
-      "teammate": {
-        "role": "AI Architect",
-        "icon": "🤖",
-        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and orchestration patterns."
-      }
-    },
-    "popm-advisor": {
-      "tier": 1,
-      "title": "Product/Project Advisor",
-      "group": "domain-analysis",
-      "active_phases": [
-        "proposal",
-        "setup",
-        "design"
-      ],
-      "reports_to": "user",
-      "domains": [
-        "requirements",
-        "business-value"
-      ],
-      "keywords": [
-        "unclear",
-        "requirements",
-        "priority",
-        "roi",
-        "business value",
-        "user story"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": null
-    },
-    "dotnet-senior": {
-      "tier": 2,
-      "title": "Backend Squad Leader",
-      "group": "backend",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "backend"
-      ],
-      "keywords": [
-        "backend",
-        "api",
-        "dotnet",
-        ".net",
-        "csharp",
-        "c#",
-        "web api",
-        "minimal api"
-      ],
-      "validators": [
-        "architecture",
-        "packages"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-core",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-program-cs-checklist",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "stacks": [
-        "dotnet",
-        "blazor"
-      ],
-      "teammate": {
-        "role": "Backend Squad Leader",
-        "icon": "⚙️",
-        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists (ef-modeler, event-architect, api-designer, etc.). Assign tasks, review designs, enforce backend standards. Escalate cross-domain conflicts to standards-architect."
-      }
-    },
-    "infra-architect": {
-      "tier": 2,
-      "title": "Infrastructure Squad Leader",
-      "group": "infra",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "infrastructure"
-      ],
-      "keywords": [
-        "infrastructure",
-        "infra",
-        "cloud",
-        "deployment",
-        "hosting",
-        "ci/cd",
-        "container",
-        "iac",
-        "pipeline",
-        "vercel",
-        "neon",
-        "planetscale",
-        "serverless database",
-        "serverless postgres"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-vercel-database",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "stacks": [
-        "azure",
-        "docker"
-      ],
-      "teammate": {
-        "role": "Infrastructure Squad Leader",
-        "icon": "🏗️",
-        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate infra specialists regardless of cloud provider (azure-architect, devops-engineer, container-specialist, observability-expert). Focus on IaC, CI/CD, containerization, cost optimization. Delegate to azure-architect for Azure-specific work. IMPORTANT: When deployment target is Vercel, ALWAYS enforce serverless database (Neon, Supabase/PgBouncer, PlanetScale) — never TCP connection pools. Escalate to standards-architect on conflicts."
-      }
-    },
-    "azure-architect": {
-      "tier": 3,
-      "title": "Azure Infrastructure Specialist",
-      "group": "infra",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "infra-architect",
-      "domains": [
-        "infrastructure"
-      ],
-      "keywords": [
-        "azure",
-        "bicep",
-        "arm template",
-        "azure resources",
-        "container apps",
-        "azure sql",
-        "key vault",
-        "app insights"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-azure-azure",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Infrastructure Squad Leader",
-        "icon": "☁️",
-        "spawn_prompt": "You are the Azure Infrastructure Specialist (tier-3). Focus exclusively on Azure resources, Bicep IaC templates, Azure cost optimization, and zero-portal policy. Report to infra-architect."
-      }
-    },
-    "ui-designer": {
-      "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-blazor-fluent-ui",
-          "scope": "uiux",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-naming",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-design-system-animations",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "UI/UX Squad Leader (FASE 1.5)",
-        "icon": "🎨",
-        "spawn_prompt": "You are the UI/UX Squad Leader for FASE 1.5. Create wireframes, mockups, user flows. Define design system (colors, typography, spacing). Work is AGNOSTIC (no implementation code). Apply modern design trends (glassmorphism, gradients, soft shadows, micro-interactions). Guide Fluent UI vs MudBlazor selection. Enforce WCAG AA accessibility (4.5:1 contrast, focus visible, ARIA)."
-      }
-    },
-    "ef-modeler": {
-      "tier": 3,
-      "title": "Data Persistence Specialist (Relational)",
-      "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",
-        "blazor-concurrency"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-database-ef-core",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-dotnet-core",
-          "scope": "implement",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Data Persistence Specialist",
-        "icon": "🗄️",
-        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Focus on Models/, Migrations/, DbContext. Follow blazor-efcore.md standards. Use IDbContextFactory for background ops. Message blazor-builder when entities ready for UI binding."
-      }
-    },
-    "event-architect": {
-      "tier": 3,
-      "title": "Event-Driven Architecture Specialist",
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-events"
-      ],
-      "keywords": [
-        "event",
-        "service bus",
-        "rabbitmq",
-        "cqrs",
-        "event sourcing",
-        "messaging",
-        "pub/sub",
-        "domain events",
-        "saga",
-        "real-time",
-        "realtime",
-        "websocket",
-        "live updates"
-      ],
-      "validators": [
-        "architecture",
-        "event-driven"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Event-Driven Architecture Specialist",
-        "icon": "📨",
-        "spawn_prompt": "You are the Event-Driven Architecture Specialist. Implement Azure Service Bus queues/topics, CQRS patterns, Event Sourcing, Domain Events. Design idempotent handlers, dead letter queues, saga patterns."
-      }
-    },
-    "api-designer": {
-      "tier": 3,
-      "title": "API Design Specialist",
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-api"
-      ],
-      "keywords": [
-        "rest",
-        "graphql",
-        "grpc",
-        "api",
-        "openapi",
-        "swagger",
-        "versioning",
-        "rate limiting",
-        "hot chocolate",
-        "endpoint"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "API Design Specialist",
-        "icon": "🔌",
-        "spawn_prompt": "You are the API Design Specialist. Design REST APIs (resource naming, HTTP verbs, status codes), GraphQL schemas with Hot Chocolate, gRPC .proto files. Add OpenAPI/Swagger annotations. Implement API versioning, rate limiting. Review with frontend specialists."
-      }
-    },
-    "nosql-cache-expert": {
-      "tier": 3,
-      "title": "NoSQL & Cache Specialist",
-      "group": "backend",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "dotnet-senior",
-      "domains": [
-        "backend-nosql"
-      ],
-      "keywords": [
-        "cosmos",
-        "cosmosdb",
-        "redis",
-        "cache",
-        "blob storage",
-        "nosql",
-        "document db",
-        "key-value",
-        "azure storage"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "NoSQL & Cache Specialist",
-        "icon": "💾",
-        "spawn_prompt": "You are the NoSQL & Cache Specialist. Implement Azure Cosmos DB (SQL API, partition keys, RUs), Redis Cache (cache-aside, read-through, write-behind), Blob Storage (hot/cool/archive tiers). Design cache invalidation strategies."
-      }
-    },
-    "domain-architect": {
-      "tier": 2,
-      "title": "Domain Modeling Leader",
-      "group": "domain-analysis",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "backend-ddd"
-      ],
-      "keywords": [
-        "ddd",
-        "domain driven design",
-        "aggregate",
-        "aggregate root",
-        "entity",
-        "value object",
-        "domain event",
-        "bounded context",
-        "ubiquitous language",
-        "domain modeling",
-        "aggregateroot",
-        "domainevents",
-        "integration event"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-complexity-levels",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-aggregates",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-entities",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-value-objects",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-bounded-contexts",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-ddd-ubiquitous-language",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Domain Modeling Leader",
-        "icon": "📐",
-        "spawn_prompt": "You are the Domain Modeling Leader for MORPH-SPEC. Your primary responsibility is detecting the correct domain complexity level and producing the Aggregate Blueprint before any contracts are generated.\n\nALWAYS start with the 5-question complexity detection:\n1. Does the main entity have state transitions? (Draft → Confirmed → Shipped) → Yes = Level 2+\n2. Are there business invariants? (\"can only cancel if Active\") → Yes = Level 2+\n3. Are there derived calculations? (Total, Balance, Discount) → Yes = Level 2+\n4. Do other modules need to react to changes? (Domain Events with consumers) → Yes = Level 2+\n5. Did the user explicitly declare a Bounded Context? Or are there 3+ domains with conflicting models? → Yes = Level 3\nIf none of the above: Level 1 (CRUD)\n\nFor Level 1: Use contracts-level1.cs template. No AggregateRoot, no Domain Events.\nFor Level 2: Use contracts-level2.cs template. Design AggregateRoot with factory methods, invariants, Value Objects, Domain Events.\nFor Level 3: Use contracts-level3.cs template. Add BOUNDED_CONTEXT namespace, Integration Events, cross-BC ID references only.\n\nDocument in spec.md under ## Domain Complexity and ## Aggregate Blueprint (Level 2+).\nCoordinate ef-modeler for persistence design and event-architect for Domain Event patterns.\nRef: framework/standards/architecture/ddd/complexity-levels.md"
-      }
-    },
-    "hangfire-orchestrator": {
-      "tier": 3,
-      "title": "Background Jobs Specialist",
-      "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",
-        "blazor-concurrency"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Background Jobs Specialist",
-        "icon": "⏰",
-        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget jobs, delayed jobs, recurring jobs (cron), continuations (chaining). Configure retry policies, queue management. Use IDbContextFactory/IRepositoryFactory for scoped operations in background jobs (NOT direct DbContext injection). Also handles webhook integration, event-driven job pipelines, and async processing of external service callbacks."
-      }
-    },
-    "ms-agent-expert": {
-      "tier": 3,
-      "title": "Microsoft Agent Framework Expert",
-      "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": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-production",
-          "scope": "implement",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-blazor-ui",
-          "scope": "implement",
-          "priority": "reference"
-        }
-      ],
-      "teammate": {
-        "role": "Microsoft Agent Framework Expert",
-        "icon": "🤖",
-        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement ChatClientAgent, AIFunctionFactory, agent workflows (sequential, handoff, group chat). Integrate MCP tools (McpClientFactory, ListToolsAsync, Cast<AITool>). Host agents via A2A protocol (MapA2A, agent cards). Add middleware pipeline, observability (WithOpenTelemetry)."
-      }
-    },
-    "supabase-expert": {
-      "tier": 3,
-      "title": "Supabase & PostgreSQL Specialist",
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Supabase & PostgreSQL Specialist",
-        "icon": "🐘",
-        "spawn_prompt": "You are the Supabase & PostgreSQL Specialist. Implement Supabase Auth (magic links, OAuth, JWT), Row Level Security (RLS policies), Realtime subscriptions, Edge Functions (Deno/TypeScript). Use pgvector for embeddings/similarity search. Design efficient schemas with proper indexing."
-      }
-    },
-    "vector-search-expert": {
-      "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": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-setup",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Vector Search & RAG Specialist",
-        "icon": "🔎",
-        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement vector embeddings (OpenAI, Azure AI), similarity search (pgvector, Azure AI Search), RAG pipelines (chunking, embedding, retrieval). Design hybrid search (vector + full-text). Optimize embedding dimensions and index types (HNSW, IVFFlat)."
-      }
-    },
-    "context-optimizer": {
-      "tier": 3,
-      "title": "Context & Token Optimization Specialist",
-      "group": "ai",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "ai-system-architect",
-      "domains": [
-        "ai-context"
-      ],
-      "keywords": [
-        "context window",
-        "token optimization",
-        "chunking",
-        "context compression",
-        "summarization",
-        "token budget"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "ai-agents-workflows",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Context & Token Optimization Specialist",
-        "icon": "🧠",
-        "spawn_prompt": "You are the Context & Token Optimization Specialist. Optimize context windows (sliding window, summarization, selective inclusion), implement token counting and budget management, design chunking strategies (semantic, fixed-size, recursive). Reduce costs through prompt caching, context compression."
-      }
-    },
-    "prompt-engineer": {
-      "tier": 3,
-      "title": "Prompt Engineer",
-      "group": "ai",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "ai-system-architect",
-      "domains": [
-        "ai-prompts"
-      ],
-      "keywords": [
-        "prompt",
-        "prompting",
-        "system prompt",
-        "few-shot",
-        "chain-of-thought",
-        "llm prompt",
-        "agent prompt"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Prompt Engineer",
-        "icon": "✍️",
-        "spawn_prompt": "You are the Prompt Engineer (tier-3). Design system prompts, few-shot examples, chain-of-thought patterns, and optimize LLM interactions. Always show the full prompt text — never just describe it. Apply techniques: constitutional AI, recursive prompting, tree of thoughts, self-consistency."
-      }
-    },
-    "asaas-financial": {
-      "tier": 3,
-      "title": "Payment Integration Specialist (Brazil)",
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Payment Integration Specialist",
-        "icon": "💳",
-        "spawn_prompt": "You are the Payment Integration Specialist (Asaas SDK for Brazil). Implement PIX payments, Boleto generation, Credit Card processing, Subscription management. Follow contract-compliance validator patterns for SDK usage."
-      }
-    },
-    "clerk-auth": {
-      "tier": 3,
-      "title": "Auth SaaS Integration Specialist",
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Auth SaaS Integration Specialist",
-        "icon": "🔐",
-        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk SDK). Implement Clerk authentication flows (login, signup, OAuth), session management, user profile. Integrate with Blazor or Next.js frontend."
-      }
-    },
-    "resend-email": {
-      "tier": 3,
-      "title": "Email Integration Specialist",
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Email Integration Specialist",
-        "icon": "📧",
-        "spawn_prompt": "You are the Email Integration Specialist (Resend SDK). Implement transactional emails, email templates, notification sending. Follow contract-compliance validator for SDK usage patterns."
-      }
-    },
-    "blazor-builder": {
-      "tier": 3,
-      "title": "Blazor Development Specialist",
-      "group": "frontend",
-      "active_phases": [
-        "uiux",
-        "tasks",
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "frontend-blazor"
-      ],
-      "keywords": [
-        "blazor",
-        "razor",
-        "server-side",
-        "component",
-        "fluent ui",
-        "mudblazor",
-        "signalr",
-        "page",
-        "view",
-        "form"
-      ],
-      "validators": [
-        "architecture",
-        "blazor",
-        "blazor-concurrency",
-        "blazor-state",
-        "css",
-        "design-system"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-lifecycle",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-state",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-pitfalls",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "backend-database-ef-core",
-          "scope": "implement",
-          "priority": "reference"
-        },
-        {
-          "id": "frontend-blazor-fluent-ui",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Blazor Development Specialist",
-        "icon": "⚡",
-        "spawn_prompt": "You are the Blazor Development Specialist. Build Blazor Server components (Fluent UI or MudBlazor). Follow component-per-file pattern, use @inject for DI, implement loading states and error boundaries. Integrate SignalR for real-time features. Message ef-modeler for data, css-specialist for design system validation."
-      }
-    },
-    "nextjs-expert": {
-      "tier": 3,
-      "title": "Next.js Development Specialist",
-      "group": "frontend",
-      "active_phases": [
-        "uiux",
-        "tasks",
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "frontend-nextjs"
-      ],
-      "keywords": [
-        "next.js",
-        "nextjs",
-        "react",
-        "tsx",
-        "shadcn",
-        "tailwind",
-        "tanstack",
-        "react-query",
-        "zod",
-        "react-hook-form",
-        "app router",
-        "server component",
-        "client component",
-        "vercel",
-        "neon",
-        "planetscale"
-      ],
-      "validators": [
-        "nextjs-component"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "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": "infrastructure-vercel-database",
-          "scope": "design",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Next.js Development Specialist",
-        "icon": "⚛️",
-        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ applications with shadcn/ui components, TanStack Query for data fetching, Server Actions for mutations. Implement Route Handlers for API routes. Message api-designer for backend endpoints, css-specialist for design system. IMPORTANT: When deployment target is Vercel, database must be serverless (Neon, Supabase/PgBouncer port 6543, PlanetScale) — never a plain TCP connection pool."
-      }
-    },
-    "nextjs-ui-specialist": {
-      "tier": 3,
-      "title": "Next.js UI Specialist",
-      "group": "frontend",
-      "active_phases": [
-        "design",
-        "tasks",
-        "implement"
-      ],
-      "reports_to": "ui-designer",
-      "domains": [
-        "frontend-nextjs-ui"
-      ],
-      "keywords": [
-        "framer-motion",
-        "animation",
-        "transition",
-        "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": [
-        "design-system",
-        "nextjs-component"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-components",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-nextjs-patterns",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-nextjs-motion-patterns",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Next.js UI Specialist",
-        "icon": "✨",
-        "spawn_prompt": "You are the Next.js UI Specialist (Tier 3). Focus exclusively on the visual layer: Framer Motion animations (variants, AnimatePresence, useInView, gestures), shadcn/ui theming via CSS vars without editing primitives, Tailwind token bridging from design-system.md, and Lucide icon consistency. ALWAYS read .morph/context/design-system.md first and use only defined tokens. ALWAYS implement useReducedMotion() for WCAG compliance. Do NOT handle data-fetching, routing, or API routes — that's nextjs-expert's domain."
-      }
-    },
-    "css-specialist": {
-      "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": "🎨",
-        "spawn_prompt": "You are the CSS & Design System Specialist (FASE 5 only). MANDATORY FIRST STEP: Read .morph/context/design-system.md. Validate all CSS follows the design system — colors (var(--color-*)), spacing (var(--space-*)), typography (var(--font-*, --text-*)), motion (var(--duration-*, --easing-*)), shadows (var(--shadow-*)), and advanced effects (var(--glass-*, --aurora-*, --perspective-*)). No off-palette hardcoded colors, no inline styles with raw values. Enforce naming conventions (BEM for custom classes). Verify WCAG AA contrast (4.5:1 text, 3:1 UI). Ref: framework/standards/frontend/design-system/design-trends.md for modern technique catalog. Run design-system, css, contrast validators. Any missing tokens must be added to design-system.md before proceeding."
-      }
-    },
-    "seo-growth-hacker": {
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "SEO & Growth Specialist",
-        "icon": "📈",
-        "spawn_prompt": "You are the SEO & Growth Specialist (tier-3). Audit technical SEO (Core Web Vitals, meta tags, schema markup JSON-LD), optimize content for search engines, implement structured data (Product, Article, FAQ, HowTo, Organization). Focus on Next.js/Blazor page optimization, Lighthouse scores, and organic traffic growth."
-      }
-    },
-    "bicep-architect": {
-      "tier": 3,
-      "title": "Infrastructure as Code Specialist",
-      "group": "infra",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "azure-architect",
-      "domains": [
-        "infrastructure-iac"
-      ],
-      "keywords": [
-        "bicep",
-        "iac",
-        "infra",
-        "provision",
-        "arm template",
-        "infrastructure as code"
-      ],
-      "validators": [
-        "architecture"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "infrastructure-azure-azure",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Infrastructure as Code Specialist",
-        "icon": "📜",
-        "spawn_prompt": "You are the Infrastructure as Code Specialist (Bicep). Write main.bicep, modules/*.bicep, parameters.{env}.json. Never create Azure resources manually. Also handles Azure Container Apps deployment: env var mapping (config:path → DOUBLE__UNDERSCORE), what-if validation before deploy, Blazor Server sticky sessions, rollback via revision activation, and cost validation."
-      }
-    },
-    "devops-engineer": {
-      "tier": 3,
-      "title": "CI/CD Specialist",
-      "group": "infra",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "infra-architect",
-      "domains": [
-        "infrastructure-cicd"
-      ],
-      "keywords": [
-        "pipeline",
-        "ci/cd",
-        "deploy",
-        "release",
-        "github actions",
-        "azure pipelines",
-        "deployment"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "CI/CD Specialist",
-        "icon": "🚀",
-        "spawn_prompt": "You are the CI/CD Specialist. Build Azure Pipelines or GitHub Actions workflows. Implement Blue-Green, Canary, Rolling deployment strategies. Integrate with bicep-architect for IaC deployment, container-specialist for image builds."
-      }
-    },
-    "container-specialist": {
-      "tier": 3,
-      "title": "Containerization Specialist",
-      "group": "infra",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "infra-architect",
-      "domains": [
-        "infrastructure-containers"
-      ],
-      "keywords": [
-        "docker",
-        "container",
-        "containerize",
-        "dockerfile",
-        "multi-stage",
-        "container apps"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Containerization Specialist",
-        "icon": "🐳",
-        "spawn_prompt": "You are the Containerization Specialist. Write Dockerfiles (multi-stage builds), .dockerignore. Deploy to Azure Container Apps (scale-to-zero, KEDA scaling). Optimize image size, configure health checks."
-      }
-    },
-    "observability-expert": {
-      "tier": 3,
-      "title": "Observability Specialist",
-      "group": "infra",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "infra-architect",
-      "domains": [
-        "infrastructure-observability"
-      ],
-      "keywords": [
-        "monitoring",
-        "logging",
-        "tracing",
-        "metrics",
-        "app insights",
-        "serilog",
-        "opentelemetry",
-        "dashboards",
-        "alerts"
-      ],
-      "validators": [
-        "observability"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Observability Specialist",
-        "icon": "📊",
-        "spawn_prompt": "You are the Observability Specialist. Setup Application Insights (connection strings, sampling), configure Serilog (sinks, enrichers), instrument OpenTelemetry (.NET SDK). Create custom metrics, dashboards, alert rules. Write Log Analytics queries (KQL)."
-      }
-    },
-    "azure-identity": {
-      "tier": 3,
-      "title": "Microsoft Identity Specialist",
-      "group": "infra",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "reports_to": "infra-architect",
-      "domains": [
-        "infrastructure-identity"
-      ],
-      "keywords": [
-        "identity",
-        "entra",
-        "microsoft auth",
-        "azure ad",
-        "b2c",
-        "passkeys",
-        "webauthn",
-        "managed identity"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Microsoft Identity Specialist",
-        "icon": "🔑",
-        "spawn_prompt": "You are the Microsoft Identity Specialist. Implement Azure AD B2C, Entra External ID, Managed Identity for Azure resources. Add WebAuthn/Passkeys support (FIDO2 registration/authentication flows)."
-      }
-    },
-    "testing-specialist": {
-      "tier": 3,
-      "title": "Testing Specialist",
-      "group": "testing",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "quality-testing"
-      ],
-      "keywords": [
-        "test",
-        "testing",
-        "unit",
-        "integration",
-        "e2e",
-        "xunit",
-        "moq",
-        "testcontainers",
-        "bunit"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Testing Specialist",
-        "icon": "🧪",
-        "spawn_prompt": "You are the Testing Specialist. Write unit tests (xUnit, Moq/NSubstitute, FluentAssertions), integration tests (TestContainers, Respawn for DB reset), Blazor component tests (bUnit), HTTP mocking (WireMock). Follow Arrange-Act-Assert (AAA) pattern."
-      }
-    },
-    "code-analyzer": {
-      "tier": 3,
-      "title": "Code Quality Analyst",
-      "group": "testing",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "quality-review"
-      ],
-      "keywords": [
-        "analyze",
-        "review",
-        "refactor",
-        "clean code",
-        "smell",
-        "duplicate",
-        "solid",
-        "architecture review"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Code Quality Analyst",
-        "icon": "🔍",
-        "spawn_prompt": "You are the Code Quality Analyst. Review code for architecture violations, clean code principles (naming, complexity, duplication), SOLID principles. Identify code smells, suggest refactorings. Run architecture and packages validators."
-      }
-    },
-    "troubleshooting-expert": {
-      "tier": 3,
-      "title": "Troubleshooting & Debug Expert",
-      "group": "support",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "quality-debug"
-      ],
-      "keywords": [
-        "debug",
-        "troubleshoot",
-        "root cause",
-        "analyze error",
-        "investigate",
-        "diagnose"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Troubleshooting Expert (Escalation)",
-        "icon": "🔧",
-        "spawn_prompt": "You are the Troubleshooting Expert (spawned after 3 failed attempts). Analyze root cause of failures: validation errors, compilation errors, runtime exceptions. Review attempt logs from recovery-tracker. Propose alternative approaches. Message standards-architect with findings."
-      }
-    },
-    "load-testing-expert": {
-      "tier": 3,
-      "title": "Load Testing & Performance Specialist",
-      "group": "testing",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "quality-performance"
-      ],
-      "keywords": [
-        "load test",
-        "performance test",
-        "k6",
-        "jmeter",
-        "stress test",
-        "capacity planning",
-        "bottleneck",
-        "scalability",
-        "concurrent users"
-      ],
-      "validators": [
-        "performance"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Load Testing Specialist",
-        "icon": "📈",
-        "spawn_prompt": "You are the Load Testing Specialist. Write k6 scripts (stress test, spike test, soak test), JMeter test plans. Analyze bottlenecks (DB, CPU, memory). Recommend capacity planning (how many users system supports)."
-      }
-    },
-    "documentation-specialist": {
-      "tier": 3,
-      "title": "Documentation Specialist",
-      "group": "docs",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "developer-experience-docs"
-      ],
-      "keywords": [
-        "readme",
-        "documentation",
-        "api docs",
-        "contributing",
-        "deployment guide",
-        "onboarding"
-      ],
-      "validators": [],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "Documentation Specialist (Post-FASE 5)",
-        "icon": "📝",
-        "spawn_prompt": "You are the Documentation Specialist (runs after FASE 5). Generate README.md (how to run project), CONTRIBUTING.md (contributor guide), API documentation (Swagger annotations, markdown docs), deployment guides (infra setup). Update existing docs with new features."
-      }
-    },
-    "vsa-architect": {
-      "tier": 3,
-      "title": "Vertical Slice Architecture Specialist",
-      "group": "domain-analysis",
-      "active_phases": [
-        "design",
-        "implement"
-      ],
-      "domains": [
-        "architecture",
-        "backend"
-      ],
-      "keywords": [
-        "vertical slice",
-        "vertical-slice",
-        "vsa",
-        "minimal api",
-        "minimal apis",
-        "ihandler",
-        "result pattern",
-        "feature slice",
-        "scrutor",
-        "vertical slice architecture"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "architecture-vertical-slice-vertical-slice",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "role": "VSA Architecture Specialist",
-        "icon": "🍕",
-        "spawn_prompt": "Você é o VSA Specialist. Analise a proposta e produza um VSA Blueprint:\n1. ENTITY FIELDS: todos os campos com tipos C# corretos (sem AggregateRoot, sem Value Objects)\n2. OPERATIONS: slices necessários (Create, GetAll, GetById, Update, Delete + operações customizadas)\n3. ROUTES: HTTP method + rota por operação (ex: POST /api/products, GET /api/products/{id:guid})\n4. ERROR TYPES: Error factory methods para {Entity}Errors (apenas NotFound e casos específicos)\n5. VALIDATION RULES: regras FluentValidation por campo por operação\n\nNão use AggregateRoot, DomainEvent, CQRS formal, MediatR, Application Service layer.\nCada operação é um slice autônomo: Request + Response + Handler + Validator + Endpoint.\nRef: framework/standards/architecture/vertical-slice/vertical-slice.md"
-      }
-    },
-    "morph-spec-architect": {
-      "tier": 3,
-      "title": "Morph-Spec Architect",
-      "group": "domain-analysis",
-      "active_phases": [
-        "design",
-        "tasks"
-      ],
-      "reports_to": "feature-lead",
-      "domains": [
-        "cli",
-        "framework-design",
-        "nodejs",
-        "architecture"
-      ],
-      "keywords": [
-        "morph-spec",
-        "framework feature",
-        "new command",
-        "cli architecture",
-        "plugin",
-        "hook design"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "specialist",
-        "icon": "🔧",
-        "spawn_prompt": "You are the Morph-Spec Architect. You deeply understand the morph-spec-framework codebase: its 4-tier agent hierarchy, state machine (with filesystem-based phase derivation), Commander.js CLI surface (~25 commands registered in bin/morph-spec.js), hooks system, skills system, and the .morph/ directory layout. Your job is to design new features that fit naturally into the existing architecture. Before proposing implementation, always: (1) identify which existing modules can be reused, (2) determine where the new command should live in src/commands/, (3) define the state impact (does it need new state fields?), (4) list which tests need to be written. Follow ESM module patterns throughout."
-      }
-    },
-    "nodejs-cli-expert": {
-      "tier": 3,
-      "title": "Node.js CLI Expert",
-      "group": "testing",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "feature-lead",
-      "domains": [
-        "nodejs",
-        "cli",
-        "javascript",
-        "esm",
-        "testing"
-      ],
-      "keywords": [
-        "nodejs",
-        "javascript",
-        "esm",
-        "commander",
-        "node --test",
-        "cli command",
-        "morph-spec implementation"
-      ],
-      "validators": [],
-      "standards": [],
-      "teammate": {
-        "role": "specialist",
-        "icon": "🟢",
-        "spawn_prompt": "You are the Node.js CLI Expert for the morph-spec-framework. You implement features in Node.js ESM following the project's conventions: (1) All imports use ESM syntax with .js extensions on relative paths; (2) Commands are registered in bin/morph-spec.js after being defined in src/commands/<domain>/<command>.js; (3) Tests use native node:test runner with mock.fn() for mocking — no external test libraries; (4) Error handling: hooks are fail-open (catch+exit 0), CLI commands exit(1) on fatal errors; (5) Never use require() or module.exports. When implementing a feature, always write the tests alongside the implementation. The test command is: node --test --test-concurrency=1"
-      }
-    },
-    "security-expert": {
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🛡️",
-        "role": "Security Validator (read-only)",
-        "spawn_prompt": "You are the Security Validator (Tier 4, READ-ONLY). Scan ALL source files (.cs, .razor, .tsx, .ts, .js) in the project for security vulnerabilities:\n\n1. SQL injection — string concatenation in queries (look for $\"...{var}...\" inside SQL/EF raw queries)\n2. Hardcoded secrets — API keys, passwords, connection strings in source code (not in appsettings)\n3. XSS — @Html.Raw usage in Razor/Blazor without sanitization\n4. Insecure deserialization — BinaryFormatter usage\n5. CSRF — POST forms/endpoints missing anti-forgery tokens ([ValidateAntiForgeryToken] or @Html.AntiForgeryToken)\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "SQL injection (string concatenation in queries)",
-          "Hardcoded secrets (API keys, passwords, connection strings)",
-          "XSS (@Html.Raw usage in Razor/Blazor)",
-          "Insecure deserialization (BinaryFormatter)",
-          "CSRF (missing anti-forgery tokens)"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "architecture-expert": {
-      "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": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "core-architecture",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "🏗️",
-        "role": "Architecture Validator (read-only)",
-        "spawn_prompt": "You are the Architecture Validator (Tier 4, READ-ONLY). Scan the project for architectural violations:\n\n1. DbContext injection — look for direct DbContext injection instead of IDbContextFactory in Blazor components (.razor, .razor.cs)\n2. Async/await anti-patterns — search for .Result, .Wait(), .GetAwaiter().GetResult() in async code\n3. DI registration order — in Program.cs, verify services are registered before middleware (app.Use*/Map*)\n4. Blazor render mode — verify InteractiveServer/InteractiveWebAssembly components don't use incompatible patterns\n5. Layer violations — Domain/Application projects must not reference Infrastructure or Web projects\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "DbContext injection (IDbContextFactory required)",
-          "Async/await patterns (no .Result or .Wait)",
-          "DI registration order (services before middleware)",
-          "Blazor render mode compatibility"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "packages-validator": {
-      "tier": 4,
-      "title": "Packages Validator",
-      "group": "testing",
-      "active_phases": [
-        "*"
-      ],
-      "reports_to": "standards-architect",
-      "domains": [
-        "packages"
-      ],
-      "keywords": [
-        "nuget",
-        "packages",
-        "dependencies",
-        "version conflict"
-      ],
-      "validators": [
-        "packages"
-      ],
-      "standards": [
-        {
-          "id": "core-coding",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "teammate": {
-        "icon": "📦",
-        "role": "Packages Validator (read-only)",
-        "spawn_prompt": "You are the Packages Validator (Tier 4, READ-ONLY). Scan all project files for package issues:\n\n1. NuGet version conflicts — search *.csproj files for the same PackageReference appearing with different versions across projects\n2. Incompatible .NET 10 packages — check that major package versions are compatible with the target framework\n3. Security vulnerabilities — look for known outdated packages (Newtonsoft.Json < 13.0.1, System.Text.Json < 8.0.5, etc.)\n4. For npm projects: check package.json for duplicate dependencies, outdated major versions\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "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": {
-      "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)",
-        "spawn_prompt": "You are the Design System Validator (Tier 4, READ-ONLY). Scan CSS/SCSS and component files for design system compliance:\n\n1. Color palette — look for hardcoded hex/rgb colors instead of CSS variables (var(--color-primary), var(--color-accent), var(--color-surface-*), var(--color-text-*), etc.)\n2. Spacing — look for hardcoded px/rem values instead of spacing variables (var(--space-*))\n3. Typography — look for hardcoded font-size/font-family instead of typography variables (var(--font-display), var(--font-body), var(--text-*))\n4. Motion — look for hardcoded transition/animation durations instead of motion tokens (var(--duration-*), var(--easing-*))\n5. Shadows — look for hardcoded box-shadow instead of shadow tokens (var(--shadow-*), var(--shadow-colored-*), var(--shadow-layered-*))\n6. Advanced effects — verify glassmorphism uses tokens (var(--glass-*)), aurora uses tokens (var(--aurora-*)), perspective uses tokens (var(--perspective-*))\n7. Component naming — verify PascalCase for Blazor components (.razor) and kebab-case for CSS classes\n8. Check .morph/context/design-system.md for project-specific design tokens\n9. Ref: framework/standards/frontend/design-system/design-trends.md for modern technique catalog\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"warning\" }] }"
-      },
-      "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 (PascalCase for Blazor, kebab-case for CSS)"
-        ],
-        "severity": "warning",
-        "blocks_on_fail": false
-      }
-    },
-    "blazor-concurrency-validator": {
-      "tier": 4,
-      "title": "Blazor Concurrency Validator",
-      "group": "frontend",
-      "active_phases": [
-        "implement"
-      ],
-      "reports_to": "blazor-builder",
-      "domains": [
-        "blazor-concurrency"
-      ],
-      "keywords": [
-        "blazor",
-        "dbcontext",
-        "lifecycle",
-        "async",
-        "concurrency"
-      ],
-      "validators": [
-        "blazor-concurrency"
-      ],
-      "standards": [
-        {
-          "id": "frontend-blazor-lifecycle",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-pitfalls",
-          "scope": "all",
-          "priority": "required"
-        },
-        {
-          "id": "frontend-blazor-state",
-          "scope": "all",
-          "priority": "required"
-        }
-      ],
-      "stacks": [
-        "blazor"
-      ],
-      "teammate": {
-        "icon": "⚡",
-        "role": "Blazor Concurrency Validator (read-only)",
-        "spawn_prompt": "You are the Blazor Concurrency Validator (Tier 4, READ-ONLY). Scan all Blazor component files (.razor, .razor.cs) for concurrency and lifecycle violations:\n\n1. DbContext lifecycle — look for injected DbContext (not IDbContextFactory), disposed context usage, scope issues\n2. Async void — search for 'async void' methods (must be 'async Task' except event handlers)\n3. JSInterop in OnInitialized — look for IJSRuntime calls in OnInitialized/OnInitializedAsync (must be in OnAfterRender/OnAfterRenderAsync)\n4. State mutation — look for property changes without calling StateHasChanged() or InvokeAsync(StateHasChanged)\n5. Thread safety — look for shared mutable state without synchronization in Blazor Server components\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "DbContext lifecycle violations (dispose, scope issues)",
-          "Async void methods (use async Task instead)",
-          "JSInterop in OnInitialized (move to OnAfterRender)",
-          "State mutation without StateHasChanged"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "morph-spec-validator": {
-      "tier": 4,
-      "title": "Morph-Spec Validator",
-      "group": "testing",
-      "active_phases": [
-        "implement",
-        "validate"
-      ],
-      "reports_to": "qa-lead",
-      "domains": [
-        "nodejs",
-        "cli",
-        "testing",
-        "validation"
-      ],
-      "keywords": [
-        "validate morph-spec",
-        "node.js validation",
-        "cli test"
-      ],
-      "validators": [
-        "morph-spec-standards"
-      ],
-      "standards": [],
-      "teammate": {
-        "icon": "🔬",
-        "role": "Morph-Spec Validator (read-only)",
-        "tools": "Read, Glob, Grep, Bash",
-        "maxTurns": 12,
-        "spawn_prompt": "You are the Morph-Spec Validator (Tier 4, READ-ONLY). Scan the morph-spec framework codebase for standards compliance:\n\n1. ESM imports — all relative imports must use .js extensions (e.g., './foo.js' not './foo')\n2. Command registration — new commands in src/commands/ must be imported and registered in bin/morph-spec.js\n3. Test coverage — each module in src/ should have a corresponding test file in tests/\n4. No CommonJS — search for require() or module.exports (must use import/export)\n5. Hook fail-open — all hooks in framework/hooks/ must have try/catch with exit(0) fallback\n6. Run 'npm test' to verify all tests pass\n\nUse Grep, Glob, and Bash to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }] }"
-      },
-      "hook_behavior": {
-        "validates": [
-          "ESM imports use .js extensions on relative paths",
-          "New commands are registered in bin/morph-spec.js",
-          "Tests exist for new modules (one test file per module)",
-          "npm test passes with no failures",
-          "No require() or module.exports used",
-          "Error handling follows fail-open pattern for hooks"
-        ],
-        "severity": "error",
-        "blocks_on_fail": true
-      }
-    },
-    "nextjs-component-validator": {
-      "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)",
-        "spawn_prompt": "You are the Next.js Component Validator (Tier 4, READ-ONLY). Scan all .tsx/.ts files under src/ and validate:\n\n1. \"use client\" directive — must be present when React hooks (useState, useEffect, etc.) are used\n2. Server Components — \"use client\" must be absent for pure Server Components (no hooks, no event handlers)\n3. File naming — component files must use kebab-case naming convention\n4. Import patterns — client components should not import server-only modules\n\nUse Grep and Glob to scan. Do NOT modify any files.\n\nOutput a JSON object: { \"passed\": boolean, \"issues\": [{ \"file\": string, \"message\": string, \"suggestion\": string, \"severity\": \"warning\" }] }"
-      },
-      "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",
-        "event-architect",
-        "api-designer",
-        "nosql-cache-expert",
-        "hangfire-orchestrator",
-        "ms-agent-expert",
-        "supabase-expert",
-        "vector-search-expert",
-        "context-optimizer",
-        "prompt-engineer",
-        "asaas-financial",
-        "clerk-auth",
-        "resend-email"
-      ],
-      "domains": [
-        "backend",
-        "backend-data",
-        "backend-events",
-        "backend-api",
-        "backend-nosql",
-        "backend-ddd",
-        "backend-jobs",
-        "ai-agents",
-        "backend-supabase",
-        "ai-vector",
-        "ai-context",
-        "integration-payment",
-        "integration-auth",
-        "integration-email"
-      ]
-    },
-    "frontend_squad": {
-      "leader": "ui-designer",
-      "members": [
-        "blazor-builder",
-        "nextjs-expert",
-        "css-specialist",
-        "seo-growth-hacker"
-      ],
-      "domains": [
-        "frontend-design",
-        "frontend-blazor",
-        "frontend-nextjs",
-        "frontend-css",
-        "seo"
-      ],
-      "active_phases": {
-        "design": [
-          "ui-designer"
-        ],
-        "implement": [
-          "blazor-builder",
-          "nextjs-expert",
-          "css-specialist",
-          "seo-growth-hacker"
-        ]
-      }
-    },
-    "infrastructure_squad": {
-      "leader": "infra-architect",
-      "members": [
-        "bicep-architect",
-        "devops-engineer",
-        "container-specialist",
-        "observability-expert",
-        "azure-identity"
-      ],
-      "domains": [
-        "infrastructure",
-        "infrastructure-iac",
-        "infrastructure-cicd",
-        "infrastructure-containers",
-        "infrastructure-observability",
-        "infrastructure-identity"
-      ]
-    },
-    "quality_squad": {
-      "leader": "standards-architect",
-      "members": [
-        "testing-specialist",
-        "code-analyzer",
-        "troubleshooting-expert",
-        "load-testing-expert",
-        "documentation-specialist"
-      ],
-      "domains": [
-        "quality-testing",
-        "quality-review",
-        "quality-debug",
-        "quality-performance",
-        "developer-experience-docs"
-      ],
-      "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)"
-  }
-}
+{
+  "$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. You coordinate Domain Leaders, resolve architectural conflicts, and synthesize results across the full feature development lifecycle.\n\nWhen invoked:\n1. Read `.morph/state.json` for the active feature and current phase\n2. Review `.morph/features/{feature}/spec.md` for overall feature scope\n3. Identify which Domain Leaders need to be coordinated for this phase\n4. Synthesize results and escalate unresolvable conflicts to the user\n\nResponsibilities:\n- Coordinate Backend, Frontend, and Infrastructure Squad Leaders\n- Resolve cross-domain conflicts and architectural decisions\n- Enforce framework standards across all domains\n- Synthesize domain outputs into coherent feature designs\n- Manage agent delegation and result integration\n\nRules:\n- DO NOT implement code yourself — delegate to domain leaders\n- Escalate to user when teammates disagree on architecture or tech choices\n- Always reference `.morph/framework/standards/` for enforcement decisions"
+      }
+    },
+    "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 for MORPH-SPEC. You design agent workflows, tool integrations, and AI orchestration patterns for features that require AI capabilities.\n\nWhen invoked:\n1. Read `.morph/state.json` for the active feature and current phase\n2. Review AI-related FR sections in `.morph/features/{feature}/spec.md`\n3. Design agent workflow and tool integration architecture\n4. Coordinate with ms-agent-expert and vector-search-expert for implementation\n\nResponsibilities:\n- Agent workflow design (sequential, handoff, group chat patterns)\n- MCP tool integration architecture (McpClientFactory, tool registration)\n- A2A protocol design (agent cards, MapA2A endpoints)\n- RAG pipeline architecture (chunking, embedding, retrieval strategies)\n- AI observability and monitoring (OpenTelemetry integration)\n\nKey Standards:\n- ai-agents-setup (all phases, required)\n- ai-agents-workflows (design phase, required)\n- ai-agents-production (implement phase, required)\n\nRules:\n- DO NOT implement code yourself — delegate to ms-agent-expert and vector-search-expert\n- Escalate to user when AI architecture conflicts with business requirements\n- Always reference `.morph/framework/standards/` for enforcement decisions"
+      }
+    },
+    "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",
+        "graphql",
+        "grpc",
+        "openapi",
+        "swagger",
+        "versioning",
+        "rate limiting",
+        "hot chocolate",
+        "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. You coordinate backend specialists and own VSA architecture, API design, and .NET/C# standards enforcement.\n\nWhen invoked:\n1. Read `.morph/state.json` for active feature context\n2. Read `.morph/features/{feature}/spec.md` FR sections relevant to backend domain\n3. Assign domain-specific tasks to backend specialists as needed\n4. Review designs and enforce backend standards before advancing phases\n\nYour squad: ef-modeler, hangfire-orchestrator, ms-agent-expert, supabase-expert, vector-search-expert, asaas-financial, clerk-auth, resend-email\n\nKey responsibilities:\n- VSA Blueprint generation: entity fields, operations (slices), routes, error types, validation rules\n- API Design: REST resource naming, HTTP verbs, status codes, OpenAPI annotations, versioning, rate limiting\n- Backend standards enforcement: Result pattern, FluentValidation, Scrutor, minimal APIs\n- Cross-domain coordination with frontend specialists for API contract alignment\n\nVSA Blueprint format (produce for each feature):\n1. ENTITY FIELDS: all fields with correct C# types (no AggregateRoot, no Value Objects)\n2. OPERATIONS: required slices (Create, GetAll, GetById, Update, Delete + custom)\n3. ROUTES: HTTP method + route per operation (e.g., POST /api/products, GET /api/products/{id:guid})\n4. ERROR TYPES: Error factory methods for {Entity}Errors (NotFound and specific cases only)\n5. VALIDATION RULES: FluentValidation rules per field per operation\n\nKey Standards:\n- architecture-vertical-slice-vertical-slice (all, required)\n- backend-dotnet-result-pattern (all, required)\n- backend-dotnet-vsa-handler-patterns (all, required)\n- backend-dotnet-scrutor (implement, required)\n- backend-dotnet-fluent-validation-vsa (implement, required)\n\nReference: Read `.morph/framework/templates/code/dotnet/feature/` for VSA code patterns. Follow templates exactly."
+      }
+    },
+    "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",
+        "vercel",
+        "neon",
+        "planetscale",
+        "serverless database",
+        "serverless postgres",
+        "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, cloud deployment, containerization",
+        "spawn_prompt": "You are the Infrastructure Squad Leader. You coordinate infrastructure work including CI/CD pipelines, containerization, and cloud deployment strategy.\n\nWhen invoked:\n1. Read `.morph/state.json` for active feature context\n2. Read `.morph/features/{feature}/spec.md` infrastructure-related FR sections\n3. Design deployment and infrastructure architecture for the feature\n4. Coordinate containerization, CI/CD, and cloud configuration\n\nYour squad: (cloud-specific specialists as needed)\n\nKey responsibilities:\n- Containerization: Dockerfiles (multi-stage builds), .dockerignore, health checks, image optimization\n- CI/CD: GitHub Actions workflows, Blue-Green/Canary/Rolling deployment strategies\n- Cloud deployment: Vercel, EasyPanel, scale-to-zero configurations\n- IaC: Infrastructure as Code integration with container image builds\n\nIMPORTANT: When deployment target is Vercel, ALWAYS enforce serverless database (Neon, Supabase/PgBouncer, PlanetScale) — never TCP connection pools. Escalate to standards-architect on cross-domain conflicts.\n\nReference: Read `.morph/framework/templates/infrastructure/` for Docker/CI templates."
+      }
+    },
+    "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 (FASE 2)",
+        "icon": "🎨",
+        "triggers": "UI/UX design, wireframes, user flows, design system, shadcn/ui component selection",
+        "spawn_prompt": "You are the UI/UX Squad Leader. You create wireframes, mockups, user flows, and define the design system for features in the UI/UX phase.\n\nWhen invoked:\n1. Read `.morph/state.json` for active feature context\n2. Read `.morph/features/{feature}/spec.md` UI-related FR sections\n3. Create wireframes and user flows for each screen/interaction\n4. Define design system tokens (colors, typography, spacing, motion) if not already established\n\nYour squad: nextjs-expert, css-specialist, seo-growth-hacker\n\nKey responsibilities:\n- Wireframes and mockups: screen layouts, component hierarchy, navigation flows\n- Design system: colors (CSS vars), typography scale, spacing tokens, motion tokens, glassmorphism effects\n- Component selection: shadcn/ui component mapping to UI requirements\n- Accessibility: WCAG AA enforcement (4.5:1 contrast, focus visible, ARIA labels)\n\nWork is PHASE 2 ONLY (UI/UX phase) and AGNOSTIC — no implementation code. Apply modern design trends: glassmorphism, gradients, soft shadows, micro-interactions.\n\nKey Standards:\n- frontend-design-system-naming (all, required)\n- frontend-design-system-animations (all, required)"
+      }
+    },
+    "ef-modeler": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Data Persistence Specialist (Relational)",
+      "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). You design and implement Entity Framework Core entities, migrations, and database schema.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for entity and data requirements\n2. Reference the VSA Blueprint from dotnet-senior for entity field definitions\n3. Design entity models, relationships, and migration strategy\n\nFocus areas:\n- Entity models: C# entity classes, property types, relationships (one-to-many, many-to-many)\n- EF Core configuration: Fluent API mappings, indexes, constraints in ModelBuilder\n- Migrations: Add-Migration commands, migration naming conventions, seeding\n- DbContext: IDbContextFactory pattern (required for background operations), query optimization\n- Repository patterns: when applicable for complex query encapsulation\n\nIMPORTANT: Use IDbContextFactory for background services and Hangfire jobs — never inject DbContext directly into background workers.\n\nMessage nextjs-expert when entities are ready for UI data binding."
+      }
+    },
+    "hangfire-orchestrator": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Background Jobs Specialist",
+      "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). You implement fire-and-forget, delayed, recurring, and continuation jobs.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for async/background processing requirements\n2. Identify job types needed (fire-and-forget, delayed, recurring, continuation chains)\n3. Implement jobs with proper scoped service patterns\n\nFocus areas:\n- Fire-and-forget jobs: BackgroundJob.Enqueue, immediate execution\n- Delayed jobs: BackgroundJob.Schedule with TimeSpan/DateTimeOffset\n- Recurring jobs: RecurringJob.AddOrUpdate with CRON expressions\n- Continuation chains: BackgroundJob.ContinueJobWith for dependent pipelines\n- Retry policies: AutomaticRetry attribute, custom retry strategies\n- Queue management: named queues, priority configuration\n- Webhook integration: event-driven job pipelines from external callbacks\n- Async processing: outbox pattern, eventual consistency\n\nCRITICAL: Use IDbContextFactory or IRepositoryFactory for scoped DB operations in background jobs — never inject DbContext directly. Use IServiceScopeFactory.CreateScope() for scoped services."
+      }
+    },
+    "ms-agent-expert": {
+      "color": "yellow",
+      "tier": 3,
+      "title": "Microsoft Agent Framework Expert",
+      "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. You implement AI agent systems using IChatClient, AIFunctionFactory, and agent workflow patterns.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for AI agent requirements\n2. Review AI architecture design from ai-system-architect\n3. Implement agent workflows using Microsoft.Extensions.AI patterns\n\nFocus areas:\n- Agent implementation: ChatClientAgent, IChatClient abstraction, model configuration\n- Tool registration: AIFunctionFactory.Create, [AIFunction] attribute, tool descriptions\n- Workflow patterns: sequential agents, handoff orchestration, group chat\n- MCP integration: McpClientFactory, ListToolsAsync, Cast<AITool>(), MCP server configuration\n- A2A protocol: MapA2A endpoint registration, agent card definition, peer agent discovery\n- Middleware pipeline: logging, observability, rate limiting, retry\n- Observability: WithOpenTelemetry(), activity tracing, token usage tracking\n\nKey Standards:\n- ai-agents-setup (all, required)\n- ai-agents-workflows (design, required)\n- ai-agents-production (implement, required)"
+      }
+    },
+    "supabase-expert": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Supabase & PostgreSQL Specialist",
+      "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. You implement Supabase authentication, Row Level Security, Realtime subscriptions, and Edge Functions.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for authentication and database requirements\n2. Design RLS policies and authentication flows\n3. Implement Supabase integration points\n\nFocus areas:\n- Authentication: Supabase Auth (magic links, OAuth providers, JWT validation, session management)\n- Row Level Security: RLS policy design, user-scoped queries, service role bypass patterns\n- Realtime: Realtime subscriptions for live data, channel management, presence\n- Edge Functions: Deno/TypeScript edge functions, webhook handlers, serverless compute\n- pgvector: Embedding storage, similarity search queries, IVFFlat/HNSW index configuration\n- Schema design: efficient table structures, proper indexing, foreign key constraints"
+      }
+    },
+    "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. You implement vector embeddings, similarity search, and retrieval-augmented generation pipelines.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for search and AI retrieval requirements\n2. Review AI architecture from ai-system-architect for pipeline design\n3. Implement embedding and retrieval components\n\nFocus areas:\n- Embeddings: OpenAI text-embedding models, batch embedding, dimension selection\n- Vector storage: pgvector integration, HNSW vs IVFFlat index selection, cosine/L2 distance\n- RAG pipelines: document chunking strategies, embedding generation, similarity retrieval, reranking\n- Hybrid search: combining vector similarity with full-text search (tsvector + pgvector)\n- Query optimization: index tuning, probes configuration, approximate vs exact search trade-offs\n\nKey Standards:\n- ai-agents-setup (all, required)\n- ai-agents-workflows (design, required)"
+      }
+    },
+    "asaas-financial": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Payment Integration Specialist (Brazil)",
+      "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). You implement Brazilian payment methods using the Asaas SDK.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for payment and billing requirements\n2. Design payment flows (PIX, Boleto, Credit Card) per business rules\n3. Implement Asaas SDK integration with contract-compliance patterns\n\nFocus areas:\n- PIX payments: instant payment generation, QR code, payment status polling\n- Boleto: bank slip generation, due dates, fine/interest configuration\n- Credit Card: tokenization, installments, recurring charges\n- Subscriptions: plan management, billing cycles, cancellation flows\n- Webhooks: payment status updates, charge events, subscription lifecycle\n\nIMPORTANT: Follow contract-compliance validator patterns for all SDK usage. Never hardcode Asaas API keys — use configuration/secrets management."
+      }
+    },
+    "clerk-auth": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Auth SaaS Integration Specialist",
+      "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). You implement Clerk authentication flows and session management.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for authentication requirements\n2. Design auth flows (login, signup, OAuth, MFA) per user stories\n3. Implement Clerk SDK integration with Next.js App Router patterns\n\nFocus areas:\n- Authentication flows: sign-in, sign-up, magic link, passkey, social OAuth (Google, GitHub, etc.)\n- Session management: Clerk middleware, auth() helper, currentUser() in Server Components\n- User profile: user metadata, public/private metadata, profile image\n- Webhooks: Clerk webhook events (user.created, session.created) for backend sync\n- Next.js integration: middleware.ts configuration, ClerkProvider wrapper, route protection"
+      }
+    },
+    "resend-email": {
+      "color": "teal",
+      "tier": 3,
+      "title": "Email Integration Specialist",
+      "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). You implement transactional email delivery using the Resend SDK.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for email notification requirements\n2. Design email templates and trigger conditions\n3. Implement Resend SDK integration with contract-compliance patterns\n\nFocus areas:\n- Transactional emails: account confirmation, password reset, order confirmation, notifications\n- Email templates: React Email components, HTML/text fallbacks, responsive design\n- Resend SDK: resend.emails.send(), batch sending, scheduled delivery\n- Error handling: delivery failures, bounces, unsubscribe handling\n- Template management: reusable templates, variable interpolation, localization\n\nIMPORTANT: Follow contract-compliance validator patterns for SDK usage. Never hardcode Resend API keys."
+      }
+    },
+    "nextjs-expert": {
+      "color": "pink",
+      "tier": 3,
+      "title": "Next.js Development Specialist",
+      "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. You build Next.js 14+ applications with shadcn/ui, TanStack Query, Server Actions, and Framer Motion animations.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for frontend FR requirements\n2. Read `.morph/context/design-system.md` for design tokens and component selections\n3. Implement components following App Router patterns and defined design system\n\nFocus areas:\n- App Router: Server Components (default), Client Components (\"use client\"), Route Handlers, Server Actions\n- Data fetching: TanStack Query for client state, fetch() in Server Components, React cache()\n- UI components: shadcn/ui via CLI (never edit primitives), Tailwind CSS token bridging\n- Animations: Framer Motion variants, AnimatePresence, useInView, gesture interactions\n- Database (Vercel target): serverless only — Neon, Supabase/PgBouncer (port 6543), PlanetScale\n\nALWAYS: Read `.morph/context/design-system.md` first and use only defined tokens. Implement useReducedMotion() for WCAG compliance. Never use raw TCP connection pools on Vercel.\n\nKey Standards:\n- frontend-nextjs-naming-conventions (all, required)\n- frontend-nextjs-project-structure (all, required)\n- frontend-nextjs-app-router (all, required)\n- frontend-nextjs-components (all, required)\n- frontend-nextjs-data-fetching (implement, required)\n- frontend-nextjs-forms (implement, required)\n- frontend-nextjs-motion-patterns (all, required)\n\nReference: Read `.morph/framework/templates/frontend/nextjs/` for Next.js code patterns."
+      }
+    },
+    "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. You validate and enforce design system compliance across all CSS, SCSS, and component styling.\n\nWhen invoked:\n1. Read `.morph/context/design-system.md` FIRST — this is mandatory before any work\n2. Scan CSS/component files for design system violations\n3. Add missing design tokens to design-system.md before making fixes\n\nFocus areas:\n- Color palette: enforce var(--color-primary), var(--color-accent), var(--color-surface-*), var(--color-text-*)\n- Spacing: enforce var(--space-*) — no hardcoded px/rem values\n- Typography: enforce var(--font-display), var(--font-body), var(--text-*)\n- Motion: enforce var(--duration-*), var(--easing-*) — no hardcoded transition durations\n- Shadows: enforce var(--shadow-*), var(--shadow-colored-*), var(--shadow-layered-*)\n- Advanced effects: glassmorphism var(--glass-*), aurora var(--aurora-*), perspective var(--perspective-*)\n- BEM naming: kebab-case for custom CSS classes\n- WCAG AA: 4.5:1 contrast for text, 3:1 for UI elements\n\nMANDATORY FIRST STEP: Read .morph/context/design-system.md. Any missing tokens must be added there before proceeding with fixes.\n\nKey Standards:\n- frontend-design-system-naming (all, required)\n- frontend-design-system-animations (all, required)"
+      }
+    },
+    "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. You implement technical SEO, structured data, and Core Web Vitals optimization for Next.js applications.\n\nWhen invoked:\n1. Read `.morph/features/{feature}/spec.md` for SEO requirements and target keywords\n2. Audit existing pages for technical SEO issues\n3. Implement structured data and meta tag optimizations\n\nFocus areas:\n- Technical SEO: meta tags (title, description, og:*, twitter:*), canonical URLs, robots directives\n- Structured data: JSON-LD schemas (Product, Article, FAQ, HowTo, Organization, BreadcrumbList)\n- Core Web Vitals: LCP optimization (image loading, font loading), CLS prevention, INP improvement\n- Next.js optimization: generateMetadata(), next/image, font optimization, route-level metadata\n- Lighthouse scores: targeting 90+ Performance, 100 Accessibility, 100 Best Practices, 100 SEO\n- Content strategy: keyword-rich headings, semantic HTML structure, internal linking"
+      }
+    },
+    "morph-spec-architect": {
+      "color": "cyan",
+      "tier": 3,
+      "title": "Morph-Spec Architect",
+      "group": "domain-analysis",
+      "active_phases": [
+        "design",
+        "tasks"
+      ],
+      "reports_to": "feature-lead",
+      "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, layer violations, async anti-patterns, DI registration order",
+        "spawn_prompt": "You are the Architecture Validator (READ-ONLY). Scan for architectural violations in .NET 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, layer 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- Layer violations: Domain/Application projects referencing Infrastructure or Web projects\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)",
+          "Layer violations"
+        ],
+        "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)"
+  }
+}