@polymorphism-tech/morph-spec 4.11.1 → 4.13.0

package/framework/templates/meta-prompts/parallel-workers/parallel-worker.md

@@ -28,9 +28,9 @@ Files you OWN (safe to create/modify):
 {{DELIVERABLES}}
 
 Files you can READ (shared, do not modify):
-- `.morph/features/{{FEATURE_NAME}}/1-design/spec.md`
+- `.morph/features/{{FEATURE_NAME}}/2-design/spec.md`
 - `framework/standards/` (all)
-- `.morph/features/{{FEATURE_NAME}}/1-design/contracts.*`
+- `.morph/features/{{FEATURE_NAME}}/2-design/contracts.*`
 
 ## Spec Summary
 {{SPEC_SUMMARY}}

package/framework/templates/meta-prompts/squad-leaders/backend-squad.md

@@ -14,8 +14,7 @@ You are the **Backend Squad Leader** (dotnet-senior) in the MORPH-SPEC agent hie
 
 You coordinate the following backend specialists:
 - **ef-modeler** — Entity Framework Core, database schema, migrations
-- **api-designer** — REST endpoints, DTOs, OpenAPI contracts
-- **event-architect** — Domain events, background jobs (Hangfire), CQRS
+- **hangfire-orchestrator** — Background jobs, scheduled tasks, async processing
 
 {{#if ADDITIONAL_LEADERS}}
 Additional domain leaders for this feature:

package/framework/templates/meta-prompts/squad-leaders/frontend-squad.md

@@ -1,126 +1,83 @@
-# Frontend Squad Leader — {{AGENT_ID}}
-
-You are the **Frontend Squad Leader** in the MORPH-SPEC agent hierarchy.
-
-## Your Identity
-- Agent: {{AGENT_ID}}
-- Role: Frontend Squad Leader (Tier 2)
-- Domain: {{DOMAIN}} (UI / Components / UX)
-
-## Your Mission
-{{MISSION}}
-
-## Your Domain Leaders
-
-{{#if IS_BLAZOR}}
-You coordinate the following Blazor specialists:
-- **component-designer** — Razor components, Blazor lifecycle, state management
-- **ui-styler** — CSS, design system compliance, Fluent UI / MudBlazor
-- **blazor-forms** — Forms, validation, EditContext, FluentValidation integration
-{{/if}}
-
-{{#if IS_NEXTJS}}
-You coordinate the following Next.js specialists:
-- **react-architect** — Next.js 15 App Router, Server/Client components, RSC patterns
-- **ui-styler** — Tailwind CSS, design tokens, shadcn/ui components
-- **form-specialist** — React Hook Form, Zod validation, server actions
-{{/if}}
-
-{{#if ADDITIONAL_LEADERS}}
-Additional domain leaders for this feature:
-{{ADDITIONAL_LEADERS}}
-{{/if}}
-
-## Spec Summary
-{{SPEC_SUMMARY}}
-
-## Frontend Standards to Follow
-
-{{#if IS_BLAZOR}}
-### Blazor (.NET 10)
-- Components use `@rendermode InteractiveServer` (not static SSR by default)
-- Use `IDbContextFactory` if components need DB access (via injected services)
-- `@implements IAsyncDisposable` when component holds disposable resources
-- `OnInitializedAsync` for data loading (not `OnParametersSetAsync` unless watching params)
-- `StateHasChanged()` only after async operations that update UI
-- `IJSRuntime` for JS interop — wrap in try/catch for prerender safety
-
-### Component Architecture (Blazor)
-- Pages in `Pages/` with `@page` directive
-- Reusable components in `Components/Shared/`
-- Feature components in `Components/{Feature}/`
-- Services injected via `[Inject]` or `@inject`
-
-### Design System (Blazor)
-- Use Fluent UI Blazor or MudBlazor components (per project config)
-- Follow CSS design tokens from `wwwroot/css/design-tokens.css`
-- Typography: `var(--font-size-base)`, `var(--font-weight-medium)`, etc.
-- Colors: ONLY use CSS variables — no hex codes directly
-- Spacing: multiples of 4px (4, 8, 12, 16, 24, 32, 48, 64)
-{{/if}}
-
-{{#if IS_NEXTJS}}
-### Next.js 15 (App Router)
-- Default to Server Components — use `'use client'` only when needed
-- Server Actions for mutations (not separate API routes for simple CRUD)
-- Data fetching in Server Components with `fetch()` or ORM calls
-- `Suspense` boundaries for async data with `loading.tsx` fallbacks
-- `error.tsx` for error boundaries per route segment
-
-### Component Architecture (Next.js)
-- Pages in `app/` directory (App Router)
-- Shared components in `components/` (Server Components by default)
-- Client-side interactive components in `components/client/`
-- Types in `types/` or co-located with components
-
-### Design System (Next.js)
-- Tailwind CSS utility classes — prefer over custom CSS
-- Design tokens in `tailwind.config.ts` (colors, spacing, typography)
-- shadcn/ui components as base — customize via `components/ui/`
-- Responsive: mobile-first with `sm:`, `md:`, `lg:` breakpoints
-{{/if}}
-
-## Your Tasks
-{{TASKS}}
-
-## Deliverables Expected
-{{DELIVERABLES}}
-
-Frontend deliverables typically include:
-{{#if IS_BLAZOR}}
-- `Pages/` — Blazor page components with `@page` routes
-- `Components/{Feature}/` — Feature-specific components
-- `Components/Shared/` — Reusable UI components
-- CSS files (if custom styles needed)
-{{/if}}
-{{#if IS_NEXTJS}}
-- `app/{routes}/` — Next.js page and layout files
-- `components/{Feature}/` — Feature-specific components
-- `components/ui/` — Base UI components (shadcn overrides)
-- TypeScript type definitions
-{{/if}}
-
-## Constraints
-{{CONSTRAINTS}}
-
-- Follow design system strictly — no ad-hoc colors or spacing
-- Components must be accessible (ARIA attributes where needed)
-- Loading states required for all async operations
-- Error states required for all data-fetching components
-
-## How to Work
-1. Start with page layout and routing structure
-2. Build reusable sub-components before composing pages
-3. Wire up API calls/services last (after UI is structured)
-4. Test each component with loading + error + empty states
-5. After every 3 tasks, run: `morph-spec task done {{FEATURE_NAME}} <task-id>`
-6. If design system validator blocks you, check `framework/standards/css-design-system.md`
-
-## Report Back When Done
-Provide a summary of:
-- Files created/modified (with paths)
-- Pages/routes implemented
-- Components created (with brief description)
-- Design system compliance status
-- Any accessibility concerns
-- Checkpoint pass/fail status
+# Frontend Squad Leader — {{AGENT_ID}}
+
+You are the **Frontend Squad Leader** in the MORPH-SPEC agent hierarchy.
+
+## Your Identity
+- Agent: {{AGENT_ID}}
+- Role: Frontend Squad Leader (Tier 2)
+- Domain: {{DOMAIN}} (UI / Components / UX)
+
+## Your Mission
+{{MISSION}}
+
+## Your Domain Leaders
+
+You coordinate the following Next.js specialists:
+- **react-architect** — Next.js 15 App Router, Server/Client components, RSC patterns
+- **ui-styler** — Tailwind CSS, design tokens, shadcn/ui components
+- **form-specialist** — React Hook Form, Zod validation, server actions
+
+{{#if ADDITIONAL_LEADERS}}
+Additional domain leaders for this feature:
+{{ADDITIONAL_LEADERS}}
+{{/if}}
+
+## Spec Summary
+{{SPEC_SUMMARY}}
+
+## Frontend Standards to Follow
+
+### Next.js 15 (App Router)
+- Default to Server Components — use `'use client'` only when needed
+- Server Actions for mutations (not separate API routes for simple CRUD)
+- Data fetching in Server Components with `fetch()` or ORM calls
+- `Suspense` boundaries for async data with `loading.tsx` fallbacks
+- `error.tsx` for error boundaries per route segment
+
+### Component Architecture (Next.js)
+- Pages in `app/` directory (App Router)
+- Shared components in `components/` (Server Components by default)
+- Client-side interactive components in `components/client/`
+- Types in `types/` or co-located with components
+
+### Design System (Next.js)
+- Tailwind CSS utility classes — prefer over custom CSS
+- Design tokens in `tailwind.config.ts` (colors, spacing, typography)
+- shadcn/ui components as base — customize via `components/ui/`
+- Responsive: mobile-first with `sm:`, `md:`, `lg:` breakpoints
+
+## Your Tasks
+{{TASKS}}
+
+## Deliverables Expected
+{{DELIVERABLES}}
+
+Frontend deliverables typically include:
+- `app/{routes}/` — Next.js page and layout files
+- `components/{Feature}/` — Feature-specific components
+- `components/ui/` — Base UI components (shadcn overrides)
+- TypeScript type definitions
+
+## Constraints
+{{CONSTRAINTS}}
+
+- Follow design system strictly — no ad-hoc colors or spacing
+- Components must be accessible (ARIA attributes where needed)
+- Loading states required for all async operations
+- Error states required for all data-fetching components
+
+## How to Work
+1. Start with page layout and routing structure
+2. Build reusable sub-components before composing pages
+3. Wire up API calls/services last (after UI is structured)
+4. Test each component with loading + error + empty states
+5. After every 3 tasks, run: `morph-spec task done {{FEATURE_NAME}} <task-id>`
+
+## Report Back When Done
+Provide a summary of:
+- Files created/modified (with paths)
+- Pages/routes implemented
+- Components created (with brief description)
+- Design system compliance status
+- Any accessibility concerns
+- Checkpoint pass/fail status

package/framework/templates/meta-prompts/validators/pre-commit-validator.md

@@ -24,8 +24,8 @@ Types: feat, fix, docs, style, refactor, test, chore, perf, ci, build
 
 Valid examples:
 - `feat(auth): add JWT refresh token rotation`
-- `fix(blazor): resolve DbContext lifecycle in reports component`
-- `chore(deps): update MudBlazor to 6.12.0`
+- `fix(api): resolve handler lifecycle in reports endpoint`
+- `chore(deps): update TanStack Query to 5.x`
 
 ### 2. Secret Scan
 Check staged files for accidental secrets:

package/framework/templates/project/validate.js

@@ -5,7 +5,7 @@
  * Thin validator entry-point called by morph-spec validate-completion hook:
  *   node bin/validate.js <validator> [--json]
  *
- * Supported validators: architecture, blazor, blazor-concurrency, nextjs-component,
+ * Supported validators: architecture, nextjs-component,
  *   packages, design-system, ui-contrast, css
  *
  * Exits 0 on pass, 1 on validation errors.
@@ -64,9 +64,7 @@ const backendDir  = existsSync(join(cwd, 'src/backend'))  ? 'src/backend'  : 'ba
 // ── Validator dispatch ────────────────────────────────────────────────────────
 
 switch (validator) {
-  case 'architecture':
-  case 'blazor':
-  case 'blazor-concurrency': {
+  case 'architecture': {
     if (hasBackend && hasSln) {
       const slnFile = hasSln ? (
         existsSync(join(cwd, 'src/backend/backend.sln')) ? 'backend.sln' : 'Backend.sln'

package/framework/templates/ui/design-system.css

@@ -1,7 +1,7 @@
 /**
  * Design System - {Project Name}
  *
- * CSS Variables generated from ui-design-system.md
+ * CSS Variables generated from design-system.md
  * Use estas variáveis em todo o projeto para manter consistência visual.
  *
  * Template MORPH-SPEC by Polymorphism Tech

package/framework/workflows/README.md

@@ -169,10 +169,10 @@ Different types of changes require different levels of planning and documentatio
 
 **Outputs:**
 - proposal.md
-- ui-design-system.md
-- ui-mockups.md
-- ui-components.md
-- ui-flows.md
+- design-system.md
+- mockups.md
+- components.md
+- flows.md
 - spec.md
 - contracts.cs
 - tasks.json
@@ -575,7 +575,7 @@ Create `framework/workflows/configs/my-workflow.json`:
   "keywords": ["custom-keyword", "my-use-case"],
   "phases": {
     "run": ["proposal", "design", "implement"],
-    "skip": ["setup", "clarify", "tasks"]
+    "skip": ["uiux", "plan", "tasks"]
   },
   "pausePoints": [
     { "phase": "design", "question": "Approve custom design?" }
@@ -686,7 +686,7 @@ morph-spec feature create login-typo --request "fix typo in login button"
 morph-spec phase advance login-typo
 
 # Output:
-⏩ Skipping: setup, uiux, design, clarify, tasks, sync
+⏩ Skipping: uiux, design, plan, sync
 ➡️  Next phase: implement
 ```
 
@@ -878,7 +878,7 @@ Create `framework/workflows/configs/blazor-standard.json`:
   "keywords": ["pagination", "filter"],
   "phases": {
     "run": ["proposal", "uiux", "design", "tasks", "implement"],
-    "skip": ["setup", "clarify", "sync"]
+    "skip": ["sync"]
   },
   "priority": 2
 }
@@ -993,7 +993,7 @@ projectPath?: string       // Optional: Project path (default: '.')
 import { getWorkflowConfig } from './src/lib/workflow-detector.js';
 
 const config = getWorkflowConfig('standard');
-console.log(config.phases.skip);  // ["setup", "uiux", "clarify", "sync"]
+console.log(config.phases.skip);  // []
 ```
 
 ### listWorkflows(projectPath?)

package/framework/workflows/configs/fast-track.json

@@ -0,0 +1,51 @@
+{
+  "id": "fast-track",
+  "name": "Fast-Track (Low Complexity)",
+  "description": "Simple features - CRUD, isolated endpoints, UI components, bug fixes",
+  "criteria": {
+    "maxFiles": 3,
+    "maxLines": 50,
+    "maxComponents": 1,
+    "noInfrastructure": true
+  },
+  "keywords": [
+    "crud",
+    "endpoint",
+    "button",
+    "fix",
+    "typo",
+    "add field",
+    "simple",
+    "component",
+    "quick",
+    "small",
+    "ajuste",
+    "correção",
+    "campo",
+    "rename",
+    "toggle",
+    "flag",
+    "label",
+    "icon",
+    "badge",
+    "tooltip"
+  ],
+  "phases": {
+    "run": ["proposal", "tasks", "implement"],
+    "skip": ["uiux", "design", "plan", "sync"],
+    "skipIfCondition": {},
+    "combined": {}
+  },
+  "pausePoints": [
+    {
+      "phase": "tasks",
+      "question": "Approve task breakdown?"
+    }
+  ],
+  "outputs": {
+    "required": ["proposal.md", "tasks.md"],
+    "optional": ["recap.md"],
+    "skip": ["spec.md", "contracts.cs", "contracts.ts", "plan.md", "design-system.md", "schema-analysis.md"]
+  },
+  "priority": 1
+}

package/framework/workflows/configs/full.json

@@ -0,0 +1,68 @@
+{
+  "id": "full",
+  "name": "Full (High Complexity)",
+  "description": "Complex features - multi-domain, new entities, integrations, infrastructure",
+  "criteria": {
+    "minFiles": 10,
+    "minLines": 500,
+    "minComponents": 2
+  },
+  "keywords": [
+    "system",
+    "integration",
+    "architecture",
+    "migrate",
+    "infrastructure",
+    "platform",
+    "multi",
+    "subsystem",
+    "security",
+    "auth",
+    "deploy",
+    "pipeline",
+    "redesign",
+    "rewrite",
+    "overhaul",
+    "migração",
+    "plataforma",
+    "arquitetura",
+    "integração"
+  ],
+  "phases": {
+    "run": ["proposal", "uiux", "design", "plan", "tasks", "implement", "sync"],
+    "skip": [],
+    "skipIfCondition": {
+      "uiux": "!hasUIAgents"
+    },
+    "combined": {}
+  },
+  "pausePoints": [
+    {
+      "phase": "proposal",
+      "question": "Approve feature proposal?"
+    },
+    {
+      "phase": "uiux",
+      "question": "Approve UI/UX designs?",
+      "condition": "hasUIAgents"
+    },
+    {
+      "phase": "design",
+      "question": "Approve technical specification?"
+    },
+    {
+      "phase": "plan",
+      "question": "Approve implementation plan?"
+    },
+    {
+      "phase": "tasks",
+      "question": "Approve task breakdown?"
+    }
+  ],
+  "outputs": {
+    "required": ["proposal.md", "spec.md", "plan.md", "tasks.md", "recap.md"],
+    "optional": ["contracts.cs", "contracts.ts", "schema-analysis.md", "decisions.md"],
+    "skip": []
+  },
+  "priority": 3
+}

package/framework/workflows/configs/standard.json

@@ -29,8 +29,8 @@
     "busca"
   ],
   "phases": {
-    "run": ["proposal", "design", "tasks", "implement"],
-    "skip": ["setup", "clarify", "sync"],
+    "run": ["proposal", "design", "plan", "tasks", "implement", "sync"],
+    "skip": [],
     "skipIfCondition": {
       "uiux": "!hasUIAgents"
     },
@@ -45,6 +45,10 @@
       "phase": "design",
       "question": "Approve spec (concise, 1-2 pages)?"
     },
+    {
+      "phase": "plan",
+      "question": "Approve implementation plan?"
+    },
     {
       "phase": "tasks",
       "question": "Approve task breakdown?",
@@ -52,7 +56,7 @@
     }
   ],
   "outputs": {
-    "required": ["proposal.md", "spec.md", "recap.md"],
+    "required": ["proposal.md", "spec.md", "plan.md", "recap.md"],
     "optional": ["decisions.md"],
     "skip": ["contracts.cs"]
   },

package/framework/workflows/docs/STORY-DRIVEN-DEVELOPMENT.md

@@ -33,7 +33,7 @@ morph-spec story shard scheduled-reports
 # ├── index.md
 # ├── entity-design.md
 # ├── service-layer.md
-# └── ui-components.md
+# └── components.md
 
 # 1.2 - Criar primeira story
 morph-spec story create scheduled-reports SR-001 \

package/framework/workflows/docs/enforcement-pipeline.md

@@ -12,10 +12,10 @@ The enforcement pipeline consists of **6 integrated phases** that work together
 
 | Phase | Component | When | What |
 |-------|-----------|------|------|
-| **1** | Data-Driven Validators | FASE 5 (task done) | Maps agents → validators via agents.json |
+| **1** | Data-Driven Validators | FASE 7 (task done) | Maps agents → validators via agents.json |
 | **2** | Standards Context Injector | Agent detection | Auto-loads 55k+ chars of standards per agent |
-| **3** | Design System Enforcement | FASE 5 gate | Blocks UI features without design system |
-| **4** | Spec-Time Validation | FASE 2 gate | Validates contracts.cs before implementation |
+| **3** | Design System Enforcement | FASE 7 gate | Blocks UI features without design system |
+| **4** | Spec-Time Validation | FASE 3 gate | Validates contracts.cs before implementation |
 | **5** | Standards Optimization | N/A | Optimized standards (23% token reduction) |
 | **6** | Comprehensive Testing | All phases | 242 tests, 100% pass rate |
 
@@ -37,8 +37,8 @@ Before: Hardcoded AGENT_VALIDATOR_MAP in validation-runner.js made it impossible
 ```json
 {
   "agents": {
-    "blazor-builder": {
-      "validators": ["architecture", "blazor", "blazor-concurrency", "blazor-state", "css", "design-system"]
+    "nextjs-expert": {
+      "validators": ["architecture", "nextjs", "css", "design-system"]
     },
     "standards-architect": {
       "validators": ["architecture", "packages"]
@@ -80,7 +80,7 @@ morph-spec task done my-feature T001
 
 Before: Specialists had to manually read standards files, often missing relevant patterns.
 
-**After:** All relevant standards automatically loaded into agent context (55k+ chars for blazor-builder).
+**After:** All relevant standards automatically loaded into agent context (55k+ chars for nextjs-expert).
 
 ### Implementation
 
@@ -103,22 +103,21 @@ export function loadStandardsForAgent(agentId, projectPath) {
 **Agent → Standards Mapping:**
 | Agent | Standards Loaded |
 |-------|------------------|
-| `blazor-builder` | blazor-lifecycle, blazor-state, blazor-efcore, blazor-pitfalls, html-to-blazor, fluent-ui-blazor, css-*, coding, architecture |
+| `nextjs-expert` | nextjs-*, css-*, coding, architecture |
 | `ai-system-architect` | agent-framework-*, architecture, coding |
 | `infra-architect` | azure, architecture, dotnet10-compatibility, infrastructure (tier-2 Infrastructure Squad Leader) |
-| `azure-architect` | azure, architecture, dotnet10-compatibility (tier-3 specialist) |
 | `ms-agent-expert` | agent-framework-*, coding, architecture |
 
 ### Usage
 
 ```bash
 # Standards auto-injected when running detect-agents with --json
-morph-spec detect-agents --json "create blazor dashboard"
+morph-spec detect-agents --json "create user dashboard"
 
 # Output includes standardsSummary for each agent:
 {
   "standardsSummary": {
-    "blazor-builder": {
+    "nextjs-expert": {
       "fullContent": "... 55304 characters ...",
       "sections": [...]
     }
@@ -146,7 +145,7 @@ Before: UI features implemented with hardcoded colors, inconsistent styling, no
 
 **1. design-system-detector.js**
 - Checks 4 levels (priority order):
-  1. Feature-level: `.morph/features/{feature}/ui-design-system.md`
+  1. Feature-level: `.morph/features/{feature}/design-system.md`
   2. Project-level: `.morph/context/design-system.md`
   3. Generated CSS: `wwwroot/css/design-system.css`
   4. Existing CSS variables: scans `.css` files for `--app-*` tokens
@@ -184,7 +183,7 @@ morph-spec phase advance my-ui-feature
 #
 # Create a design system with one of these options:
 #   1. Project-level: .morph/context/design-system.md
-#   2. Feature-level: .morph/features/my-ui-feature/ui-design-system.md
+#   2. Feature-level: .morph/features/my-ui-feature/design-system.md
 #   3. Auto-generate: morph-spec generate design-system
 
 # Auto-scaffold design system
@@ -206,7 +205,7 @@ morph-spec generate design-system my-ui-feature      # Feature-level
 
 Before: C# coding violations only discovered during code review or runtime.
 
-**After:** contracts.cs validated at FASE 2 (design phase) before any implementation.
+**After:** contracts.cs validated at FASE 3 (design phase) before any implementation.
 
 ### Validation Rules
 
@@ -277,7 +276,7 @@ Before: C# coding violations only discovered during code review or runtime.
 
 ```javascript
 // advance-phase.js
-if (currentPhase === 'design' && (nextPhase === 'clarify' || nextPhase === 'tasks')) {
+if (currentPhase === 'design' && nextPhase === 'plan') {
   const specValidation = await validateSpec('.', feature);
   if (specValidation.errors > 0) {
     // Block advancement + show violations
@@ -419,7 +418,7 @@ Before: Standards files verbose (1761 lines total), wasting tokens on redundant
 3. ✅ Decision Wiring (decisions.md → constraints → validators)
 4. ✅ Design System Gate (blocks UI features without design system)
 5. ✅ Spec Validator (detects 9 C# violations in test)
-6. ✅ Standards Injector (55k+ chars loaded for blazor-builder)
+6. ✅ Standards Injector (55k+ chars loaded for nextjs-expert)
 
 ---
 
@@ -433,14 +432,14 @@ Before: Standards files verbose (1761 lines total), wasting tokens on redundant
 2. detect-agents --json → agents registered in state.json
    ↓ (standards-context-injector loads 55k+ chars per agent)
    ↓
-3. FASE 2: Design → spec.md + contracts.cs created
+3. FASE 3: Design → spec.md + contracts.cs created
    ↓
 4. Spec validator runs → blocks if C# violations found
    ↓ (decisions.md ADRs parsed → constraints extracted)
    ↓
-5. FASE 4: Tasks → advance-phase checks prerequisites
+5. FASE 6: Tasks → advance-phase checks prerequisites
    ↓
-6. FASE 5: Implement → design system gate blocks if UI agents + no design system
+6. FASE 7: Implement → design system gate blocks if UI agents + no design system
    ↓
 7. Each `task done` → validation-runner orchestrates validators
    ↓ (validators use: agents.json mapping + decision constraints + standards content)
@@ -535,7 +534,7 @@ morph-spec state add-agent {feature} {agent-id}
 
 **Check:**
 1. Detection order: feature > project > generated > existing CSS
-2. File location: `.morph/context/design-system.md` or `.morph/features/{feature}/ui-design-system.md`
+2. File location: `.morph/context/design-system.md` or `.morph/features/{feature}/design-system.md`
 3. Format: Must have `# Design System` or `## Colors` sections
 
 **Fix:**