@polymorphism-tech/morph-spec 4.14.0 → 4.16.0

package/framework/agents.json

@@ -29,7 +29,7 @@
         "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"
+        "spawn_prompt": "You are the Chief Architect and Team Lead for MORPH-SPEC. Coordinate Domain Leaders, resolve architectural conflicts, and synthesize results.\n\nWorkflow:\n1. Read `.morph/state.json` for active feature and phase\n2. Read `.morph/features/{feature}/spec.md` for scope\n3. Delegate to Domain Leaders — DO NOT implement code yourself\n4. Synthesize results and escalate unresolvable conflicts to the user\n\nRefer to the Domain Knowledge section below for naming rules, instant-fail checks, and VSA project structure."
       }
     },
     "ai-system-architect": {
@@ -75,7 +75,7 @@
         "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"
+        "spawn_prompt": "You are the AI/Agent System Architect. Design agent workflows, tool integrations, and AI orchestration patterns.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for AI requirements\n2. Design architecture using patterns from Domain Knowledge section below\n3. Delegate implementation to ms-agent-expert and vector-search-expert\n\nDO NOT implement code yourself. Refer to the Domain Knowledge section below for the 20 agentic patterns, MAF orchestration, and RAG pipeline architecture."
       }
     },
     "dotnet-senior": {
@@ -114,13 +114,10 @@
         "feature-slice",
         "vsa-scaffold",
         "rest",
-        "graphql",
-        "grpc",
         "openapi",
         "swagger",
         "versioning",
         "rate limiting",
-        "hot chocolate",
         "endpoint"
       ],
       "validators": [
@@ -166,7 +163,7 @@
         "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."
+        "spawn_prompt": "You are the Backend Squad Leader. Coordinate backend specialists and own VSA architecture, API design, and .NET/C# standards.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for backend requirements\n2. Produce VSA Blueprint: entity fields, operations (slices), routes, error types, validation rules\n3. Delegate to squad: ef-modeler, hangfire-orchestrator, ms-agent-expert, supabase-expert, vector-search-expert, asaas-financial, clerk-auth, resend-email\n\nRefer to the Domain Knowledge section below for IHandler, Result<T>, Scrutor, IApiEndpoint patterns and code templates."
       }
     },
     "infra-architect": {
@@ -193,11 +190,7 @@
         "container",
         "iac",
         "pipeline",
-        "vercel",
-        "neon",
-        "planetscale",
-        "serverless database",
-        "serverless postgres",
+        "easypanel",
         "docker",
         "containerize",
         "dockerfile",
@@ -214,8 +207,8 @@
       "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."
+        "triggers": "Docker, CI/CD, GitHub Actions, EasyPanel deployment, containerization",
+        "spawn_prompt": "You are the Infrastructure Squad Leader. Coordinate Docker, CI/CD, and EasyPanel deployment.\n\nWorkflow:\n1. Read `.morph/state.json` and spec.md for infrastructure requirements\n2. Design containerization and deployment architecture\n3. Escalate to standards-architect on cross-domain conflicts\n\nRefer to the Domain Knowledge section below for Docker, GitHub Actions, and EasyPanel patterns."
       }
     },
     "ui-designer": {
@@ -266,16 +259,17 @@
         }
       ],
       "teammate": {
-        "role": "UI/UX Squad Leader (FASE 2)",
+        "role": "UI/UX Squad Leader",
         "icon": "🎨",
         "triggers": "UI/UX design, wireframes, user flows, design system, shadcn/ui component selection",
-        "spawn_prompt": "You are the UI/UX Squad Leader. 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)"
+        "spawn_prompt": "You are the UI/UX Squad Leader. Create wireframes, design system, and user flows during the UI/UX phase.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for UI requirements\n3. Generate deliverables: design-system.md, mockups.md, components.md, flows.md\n4. Coordinate squad: nextjs-expert, css-specialist, seo-growth-hacker\n\nWork is UI/UX phase ONLY — no implementation code. Refer to the Domain Knowledge section below for design brief protocol, shadcn/ui reference, and accessibility rules."
       }
     },
     "ef-modeler": {
       "color": "teal",
       "tier": 3,
       "title": "Data Persistence Specialist (Relational)",
+      "stacks": ["dotnet"],
       "group": "backend",
       "active_phases": [
         "design",
@@ -302,13 +296,14 @@
         "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."
+        "spawn_prompt": "You are the Data Persistence Specialist (EF Core). Design and implement entities, migrations, and database schema.\n\nWorkflow:\n1. Read spec.md and VSA Blueprint from dotnet-senior for entity definitions\n2. Implement entity models, EF configurations, and migrations\n\nCRITICAL: Use IDbContextFactory for background services and Hangfire jobs — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for entity patterns, configuration patterns, and migration checklist."
       }
     },
     "hangfire-orchestrator": {
       "color": "teal",
       "tier": 3,
       "title": "Background Jobs Specialist",
+      "stacks": ["hangfire"],
       "group": "backend",
       "active_phases": [
         "implement"
@@ -335,13 +330,14 @@
         "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."
+        "spawn_prompt": "You are the Background Jobs Specialist (Hangfire). Implement fire-and-forget, delayed, recurring, and continuation jobs.\n\nWorkflow:\n1. Read spec.md for background processing requirements\n2. Implement jobs with proper scoped service patterns\n\nCRITICAL: Use IDbContextFactory or IRepositoryFactory for scoped DB operations — never inject DbContext directly.\n\nRefer to the Domain Knowledge section below for setup, job types, retry patterns, and dashboard configuration."
       }
     },
     "ms-agent-expert": {
       "color": "yellow",
       "tier": 3,
       "title": "Microsoft Agent Framework Expert",
+      "stacks": ["dotnet", "semantic-kernel", "ms-agents"],
       "group": "ai",
       "active_phases": [
         "design",
@@ -388,13 +384,14 @@
         "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)"
+        "spawn_prompt": "You are the Microsoft Agent Framework Expert. Implement AI agent systems using IChatClient, AIFunctionFactory, and workflow patterns.\n\nWorkflow:\n1. Read spec.md for AI agent requirements\n2. Review architecture from ai-system-architect\n3. Implement using Microsoft.Extensions.AI patterns\n\nRefer to the Domain Knowledge section below for agent implementation, tool registration, MCP integration, and A2A protocol patterns."
       }
     },
     "supabase-expert": {
       "color": "teal",
       "tier": 3,
       "title": "Supabase & PostgreSQL Specialist",
+      "stacks": ["supabase"],
       "group": "backend",
       "active_phases": [
         "design",
@@ -419,7 +416,7 @@
         "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"
+        "spawn_prompt": "You are the Supabase & PostgreSQL Specialist. Implement auth, RLS, Realtime, Edge Functions, and pgvector.\n\nWorkflow:\n1. Read spec.md for database and auth requirements\n2. Design RLS policies and schema\n3. ALWAYS use PgBouncer (port 6543) for application connections\n\nRefer to the Domain Knowledge section below for RLS patterns, migration workflow, pgvector setup, and Clerk JWT integration."
       }
     },
     "vector-search-expert": {
@@ -461,13 +458,14 @@
         "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)"
+        "spawn_prompt": "You are the Vector Search & RAG Specialist. Implement embeddings, similarity search, and RAG pipelines.\n\nWorkflow:\n1. Read spec.md for search and retrieval requirements\n2. Review AI architecture from ai-system-architect\n3. Implement chunking, embedding, and retrieval components\n\nRefer to the Domain Knowledge section below for chunking strategies, pgvector setup, hybrid search, and RAG tool patterns."
       }
     },
     "asaas-financial": {
       "color": "teal",
       "tier": 3,
       "title": "Payment Integration Specialist (Brazil)",
+      "stacks": ["asaas"],
       "group": "backend",
       "active_phases": [
         "design",
@@ -495,13 +493,14 @@
         "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."
+        "spawn_prompt": "You are the Payment Integration Specialist (Asaas/Brazil). Implement PIX, Boleto, Credit Card, and subscription billing.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Asaas SDK patterns, webhook handling, and payment flow examples."
       }
     },
     "clerk-auth": {
       "color": "teal",
       "tier": 3,
       "title": "Auth SaaS Integration Specialist",
+      "stacks": ["clerk"],
       "group": "backend",
       "active_phases": [
         "design",
@@ -526,13 +525,14 @@
         "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"
+        "spawn_prompt": "You are the Auth SaaS Integration Specialist (Clerk). Implement authentication flows and session management with Next.js App Router.\n\nRefer to the Domain Knowledge section below for Clerk SDK patterns, middleware configuration, and webhook handling."
       }
     },
     "resend-email": {
       "color": "teal",
       "tier": 3,
       "title": "Email Integration Specialist",
+      "stacks": ["resend"],
       "group": "backend",
       "active_phases": [
         "implement"
@@ -559,13 +559,14 @@
         "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."
+        "spawn_prompt": "You are the Email Integration Specialist (Resend). Implement transactional email delivery.\n\nNever hardcode API keys. Follow contract-compliance patterns.\n\nRefer to the Domain Knowledge section below for Resend SDK patterns, React Email templates, and error handling."
       }
     },
     "nextjs-expert": {
       "color": "pink",
       "tier": 3,
       "title": "Next.js Development Specialist",
+      "stacks": ["nextjs"],
       "group": "frontend",
       "active_phases": [
         "uiux",
@@ -675,7 +676,7 @@
         "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."
+        "spawn_prompt": "You are the Next.js Development Specialist. Build Next.js 14+ apps with shadcn/ui, TanStack Query, and Framer Motion.\n\nWorkflow:\n1. Read `.morph/context/design-system.md` FIRST — use only defined tokens\n2. Read spec.md for frontend requirements\n3. Implement with App Router patterns (Server Components default, \"use client\" only when needed)\n\nALWAYS: useReducedMotion() for WCAG compliance. Never edit shadcn/ui primitives.\n\nRefer to the Domain Knowledge section below for App Router patterns, data fetching, animation, and component reference."
       }
     },
     "css-specialist": {
@@ -719,7 +720,7 @@
         "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)"
+        "spawn_prompt": "You are the CSS & Design System Specialist. Validate and enforce design token compliance across all styling.\n\nMANDATORY FIRST STEP: Read `.morph/context/design-system.md` — any missing tokens must be added there before making fixes.\n\nRefer to the Domain Knowledge section below for token categories, naming conventions, and WCAG accessibility rules."
       }
     },
     "seo-growth-hacker": {
@@ -749,7 +750,7 @@
         "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"
+        "spawn_prompt": "You are the SEO & Growth Specialist. Implement technical SEO, structured data, and Core Web Vitals optimization for Next.js.\n\nWorkflow:\n1. Read spec.md for SEO requirements and target keywords\n2. Audit existing pages and implement optimizations\n3. Target: 90+ Performance, 100 Accessibility, 100 Best Practices, 100 SEO on Lighthouse\n\nRefer to the Domain Knowledge section below for meta tag patterns, JSON-LD schemas, and Next.js optimization."
       }
     },
     "morph-spec-architect": {
@@ -761,7 +762,7 @@
         "design",
         "tasks"
       ],
-      "reports_to": "feature-lead",
+      "reports_to": "standards-architect",
       "domains": [
         "cli",
         "framework-design",
@@ -853,15 +854,15 @@
       "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."
+        "triggers": "architecture validation, VSA slice violations, async anti-patterns, DI registration order",
+        "spawn_prompt": "You are the Architecture Validator (READ-ONLY). Scan for architectural violations in .NET VSA projects.\n\nWhen invoked:\n1. Use Grep and Glob to scan all .cs files and Program.cs\n2. Check for: DbContext injection, async anti-patterns, DI registration order, VSA violations\n\nScan checklist:\n- DbContext injection: direct DbContext injection in background services (use IDbContextFactory)\n- Async anti-patterns: .Result, .Wait(), .GetAwaiter().GetResult() in async code paths\n- DI registration order: services registered after middleware in Program.cs (services before app.Use*/Map*)\n- VSA slice violations: cross-feature imports (Feature A referencing Feature B internals), shared code not in Shared project\n- Handler pattern: Handlers must return Result<T>, use CancellationToken, be sealed\n\nOutput JSON:\n{\n  \"passed\": boolean,\n  \"issues\": [{ \"file\": string, \"line\": number, \"message\": string, \"severity\": \"error\" }]\n}\n\nDo NOT modify any files."
       },
       "hook_behavior": {
         "validates": [
           "DbContext injection (IDbContextFactory required)",
           "Async/await patterns (no .Result or .Wait)",
           "DI registration order (services before middleware)",
-          "Layer violations"
+          "VSA slice isolation (no cross-feature imports)"
         ],
         "severity": "error",
         "blocks_on_fail": true

package/framework/skills/level-0-meta/morph-init/SKILL.md

@@ -364,6 +364,23 @@ To create a new VSA project:
 
 ---
 
+## Step 6.5 — Reinstall Stack-Filtered Assets
+
+Now that config.json has the correct `project.stack` and `project.integrations`,
+re-install stack-aware assets (rules, skills, agents) with the correct stack tags:
+
+```bash
+morph-spec setup-infra --reinstall
+```
+
+This re-runs only the stack-aware installation steps (rules, skills, tier 1-4 agents,
+domain agents) using projectTags derived from the updated config.json.
+Infrastructure steps (directory creation, framework copy, hooks) are skipped.
+
+Output confirms: `✓ setup-infra (reinstall): complete.`
+
+---
+
 ## Step 7 — Configure MCPs
 
 For each detected integration with an available MCP:
@@ -494,6 +511,8 @@ For Node.js CLI projects, update config:
 
 Before printing the summary, check `~/.claude/settings.local.json` for `env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`. If set to `"1"`, mark Agent Teams as enabled; otherwise show the warning.
 
+**Important:** Report the `morph-spec doctor` output verbatim. Do NOT fabricate or reinterpret warnings about missing agents — the doctor check is authoritative. If doctor reports no issues, do not add your own warnings.
+
 ```
 ✓ Plugins:       superpowers ✓   context7 ✓   playwright ✓
 ✓ Infrastructure: .morph/ structure, hooks, agents, rules, skills

package/framework/skills/level-1-workflows/morph-phase-codebase-analysis/SKILL.md

@@ -3,7 +3,7 @@ name: morph-phase-codebase-analysis
 description: MORPH-SPEC Design sub-phase that analyzes existing codebase and database schema, producing schema-analysis.md with real column names, types, relationships, and field mismatches. Use at the start of Design phase before generating contracts.cs to prevent incorrect field names or types.
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # MORPH Codebase Analysis - Design Sub-phase

package/framework/skills/level-1-workflows/morph-phase-design/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 2 (Design). Schema-first interactive design: reads
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # MORPH Design — Phase 2

package/framework/skills/level-1-workflows/morph-phase-implement/SKILL.md

@@ -5,7 +5,7 @@ argument-hint: "[feature-name]"
 context: fork
 agent: general-purpose
 user-invocable: false
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
 ---
 

package/framework/skills/level-1-workflows/morph-phase-plan/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 3 (Plan). Generates a detailed implementation plan
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # MORPH Plan — Phase 3

package/framework/skills/level-1-workflows/morph-phase-tasks/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 4 (Tasks). Breaks approved spec into bottom-up ord
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # MORPH Tasks — Phase 4

package/framework/skills/level-1-workflows/morph-phase-uiux/SKILL.md

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 2 (UI/UX). Creates design-system.md, mockups.md, c
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # MORPH UI/UX Design - Phase 2

package/framework/skills/level-1-workflows/morph-scope-escalation/SKILL.md

@@ -4,7 +4,7 @@ description: Guided workflow for mid-implementation scope escalation — analyze
 user-invocable: true
 argument-hint: "[feature-name]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.14.0"
+cliVersion: "4.16.0"
 ---
 
 # Scope Escalation Workflow

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "4.14.0",
+  "version": "4.16.0",
   "description": "MORPH-SPEC: AI-First development framework with validation pipeline and multi-stack support",
   "keywords": [
     "claude-code",

package/src/commands/project/setup-infra-cmd.js

@@ -4,7 +4,7 @@ import { logger } from '../../utils/logger.js';
 export async function setupInfraCommand(options) {
   const targetPath = options.path || process.cwd();
   try {
-    await setupInfra(targetPath);
+    await setupInfra(targetPath, { reinstall: options.reinstall ?? false });
   } catch (err) {
     logger.error(`setup-infra failed: ${err.message}`);
     process.exit(1);

package/src/scripts/setup-infra.js

@@ -79,19 +79,75 @@ export function installRulesForStack(rulesSrc, rulesDest, projectTags) {
   }
 }
 
+/**
+ * Re-install only stack-aware assets (rules, skills, agents) using current config.json.
+ * Skips infrastructure steps (dirs, framework copy, hooks).
+ *
+ * @param {string} targetPath - Absolute path to the target project directory
+ * @param {Function} log - Logging function
+ * @returns {{ agentCounts: object, domainCounts: object, projectTags: string[] }}
+ */
+async function installStackAwareAssets(targetPath, log) {
+  const configPath = join(targetPath, '.morph', 'config', 'config.json');
+  let projectTags = [];
+  if (await pathExists(configPath)) {
+    try {
+      const config = JSON.parse(readFileSync(configPath, 'utf-8'));
+      projectTags = getProjectTags(config);
+    } catch { /* ignore malformed config */ }
+  }
+
+  log('Installing stack-filtered rules...');
+  const claudeDest = join(targetPath, '.claude');
+  const rulesSrc = join(FRAMEWORK_DIR, 'rules');
+  const rulesDest = join(claudeDest, 'rules');
+  if (await pathExists(rulesSrc)) {
+    await ensureDir(rulesDest);
+    installRulesForStack(rulesSrc, rulesDest, projectTags);
+  }
+
+  log('Installing skills...');
+  await installSkills(targetPath, { projectTags });
+
+  log('Installing agents...');
+  const agentCounts = await installAgents(targetPath, FRAMEWORK_DIR, { projectTags });
+
+  log('Installing domain agents...');
+  const domainCounts = await installDomainAgents(targetPath, FRAMEWORK_DIR, { projectTags });
+
+  return { agentCounts, domainCounts, projectTags };
+}
+
 /**
  * Installs MORPH-SPEC infrastructure into the target project directory.
  * Headless — no prompts, no spinner (suppressed when MORPH_QUIET=1), no stack detection.
  *
  * @param {string} targetPath - Absolute path to the target project directory
+ * @param {object} options
+ * @param {Function} options._exec - exec function (for testing)
+ * @param {boolean} options.reinstall - If true, only re-install stack-aware assets (rules, skills, agents)
  */
-export async function setupInfra(targetPath, { _exec = execSync } = {}) {
+export async function setupInfra(targetPath, { _exec = execSync, reinstall = false } = {}) {
   const quiet = process.env.MORPH_QUIET === '1';
 
   function log(msg) {
     if (!quiet) process.stdout.write(msg + '\n');
   }
 
+  // --- Reinstall mode: only re-install stack-aware assets ---
+  if (reinstall) {
+    log('setup-infra (reinstall): re-installing stack-aware assets...');
+    const { agentCounts, domainCounts } = await installStackAwareAssets(targetPath, log);
+    log('setup-infra (reinstall): complete.');
+    return {
+      agents: {
+        tier1: agentCounts?.tier1 ?? 0,
+        tier2: agentCounts?.tier2 ?? 0,
+        specialists: domainCounts?.specialists ?? 0,
+      },
+    };
+  }
+
   // --- 0. Install required Claude Code plugins ---
   await installRequiredPlugins(log, _exec);
 
@@ -188,35 +244,9 @@ export async function setupInfra(targetPath, { _exec = execSync } = {}) {
     await copyDirectory(commandsSrc, commandsDest);
   }
 
-  // --- Compute project tags for stack-aware installation ---
-  let projectTags = [];
-  if (await pathExists(configPath)) {
-    try {
-      const config = JSON.parse(readFileSync(configPath, 'utf-8'));
-      projectTags = getProjectTags(config);
-    } catch { /* ignore malformed config */ }
-  }
-
-  // --- 10. Copy framework/rules → .claude/rules (filtered by stack) ---
-  log('Step 10: Installing path-scoped rules...');
-  const rulesSrc = join(FRAMEWORK_DIR, 'rules');
-  const rulesDest = join(claudeDest, 'rules');
-  if (await pathExists(rulesSrc)) {
-    await ensureDir(rulesDest);
-    installRulesForStack(rulesSrc, rulesDest, projectTags);
-  }
-
-  // --- 11. installSkills (filtered by stack) ---
-  log('Step 11: Installing skills...');
-  await installSkills(targetPath, { projectTags });
-
-  // --- 12. installAgents ---
-  log('Step 12: Installing agents...');
-  const agentCounts = await installAgents(targetPath, FRAMEWORK_DIR, { projectTags });
-
-  // --- 13. installDomainAgents (filtered by stack) ---
-  log('Step 13: Installing domain agents...');
-  const domainCounts = await installDomainAgents(targetPath, FRAMEWORK_DIR, { projectTags });
+  // --- 10-13. Install stack-aware assets (rules, skills, agents) ---
+  log('Steps 10-13: Installing stack-aware assets...');
+  const { agentCounts, domainCounts } = await installStackAwareAssets(targetPath, log);
 
   // --- 14. Copy framework/CLAUDE.md → .claude/CLAUDE.md (morph-owned, gitignored) ---
   log('Step 14: Installing .claude/CLAUDE.md...');

package/src/utils/agents-installer.js

@@ -262,19 +262,23 @@ function buildBody(agent) {
  * Handles both inline values and YAML block scalars (>).
  *
  * @param {string} rawContent - Raw file content
- * @returns {{ name: string|null, description: string|null, allowedTools: string, body: string }}
+ * @returns {{ name: string|null, description: string|null, allowedTools: string, color: string|null, effort: string|null, permissionMode: string|null, background: boolean, stacks: string[], body: string }}
  */
 export function parseSkillFile(rawContent) {
   // Normalize CRLF to LF for consistent parsing on Windows
   const content = rawContent.replace(/\r\n/g, '\n');
   const match = content.match(/^---\n([\s\S]*?)\n---\n?([\s\S]*)$/);
-  if (!match) return { name: null, description: null, allowedTools: 'Read, Write, Edit, Bash, Glob, Grep', body: rawContent };
+  if (!match) return { name: null, description: null, allowedTools: 'Read, Write, Edit, Bash, Glob, Grep', color: null, effort: null, permissionMode: null, background: false, body: rawContent };
 
   const fm = match[1];
   const body = match[2];
 
   const name = (fm.match(/^name:\s*(.+)$/m) ?? [])[1]?.trim() ?? null;
   const allowedTools = (fm.match(/^allowed-tools:\s*(.+)$/m) ?? [])[1]?.trim() ?? 'Read, Write, Edit, Bash, Glob, Grep';
+  const color = (fm.match(/^color:\s*(.+)$/m) ?? [])[1]?.trim() ?? null;
+  const effort = (fm.match(/^effort:\s*(.+)$/m) ?? [])[1]?.trim() ?? null;
+  const permissionMode = (fm.match(/^permissionMode:\s*(.+)$/m) ?? [])[1]?.trim() ?? null;
+  const background = (fm.match(/^background:\s*(.+)$/m) ?? [])[1]?.trim() === 'true';
 
   let description = null;
   const blockMatch = fm.match(/^description:\s*>\s*\n((?:[ \t]+.*\n?)*)/m);
@@ -286,7 +290,7 @@ export function parseSkillFile(rawContent) {
   }
 
   const stacks = parseStacks(rawContent);
-  return { name, description, allowedTools, stacks, body };
+  return { name, description, allowedTools, color, effort, permissionMode, background, stacks, body };
 }
 
 /**
@@ -311,6 +315,8 @@ export function collectSkillFiles(dir) {
 /**
  * Installs domain agent files as native Claude Code subagents
  * in .claude/agents/ with memory:project, model:sonnet, maxTurns:20.
+ * Supports optional CC-native fields (color, effort, permissionMode, background)
+ * declared in each domain file's YAML frontmatter.
  *
  * @param {string} projectDir - Target project directory
  * @param {string} frameworkDir - Path to morph-spec framework/ directory
@@ -326,20 +332,24 @@ export async function installDomainAgents(projectDir, frameworkDir = 'framework'
   const installed = new Set();
   for (const filePath of collectSkillFiles(domainsDir)) {
     const raw = readFileSync(filePath, 'utf-8');
-    const { name, description, allowedTools, stacks, body } = parseSkillFile(raw);
+    const { name, description, allowedTools, color, effort, permissionMode, background, stacks, body } = parseSkillFile(raw);
     if (!name) continue;
     if (!shouldInstall(stacks, projectTags)) continue;
 
     const desc = description ?? `MORPH-SPEC domain agent: ${name}`;
-    const frontmatter = [
+    const lines = [
       `name: ${name}`,
       `description: ${desc}`,
       `model: sonnet`,
       `tools: ${allowedTools}`,
       `maxTurns: 20`,
-      `memory: project`,
-      '',
-    ].join('\n');
+    ];
+    if (color) lines.push(`color: ${color}`);
+    if (effort) lines.push(`effort: ${effort}`);
+    if (permissionMode && permissionMode !== 'default') lines.push(`permissionMode: ${permissionMode}`);
+    if (background) lines.push(`background: true`);
+    lines.push(`memory: project`, '');
+    const frontmatter = lines.join('\n');
 
     // If agents.json already generated morph-{name}.md, append domain content there
     const agentsJsonFile = `morph-${name}.md`;