@polymorphism-tech/morph-spec 4.12.0 → 4.14.0

package/framework/rules/frontend-standards.md

@@ -1,13 +1,13 @@
----
-paths:
-  - "**/*.razor"
-  - "**/*.css"
-  - "**/*.scss"
-stacks:
-  - blazor
----
-
-# Frontend Standards
-
-@.morph/framework/standards/frontend/blazor/design-checklist.md
-@.morph/framework/standards/frontend/design-system/naming.md
+---
+paths:
+  - "**/*.tsx"
+  - "**/*.css"
+  - "**/*.scss"
+stacks:
+  - nextjs
+---
+
+# Frontend Standards
+
+@.morph/framework/standards/frontend/design-system/naming.md
+@.morph/framework/standards/frontend/design-system/animations.md

package/framework/rules/hangfire-standards.md

@@ -0,0 +1,13 @@
+---
+paths:
+  - "**/Jobs/**"
+  - "**/Background/**"
+  - "**/Hangfire/**"
+  - "**/Recurring/**"
+stacks:
+  - dotnet
+---
+
+# Hangfire Background Jobs Standards
+
+@.morph/framework/standards/backend/integrations/hangfire/hangfire-jobs.md

package/framework/rules/infrastructure-standards.md

@@ -1,16 +1,27 @@
----
-paths:
-  - "**/*.bicep"
-  - "**/Dockerfile"
-  - "**/docker-compose*.yml"
-  - "**/pipelines/**"
-  - "**/.github/workflows/**"
-stacks:
-  - azure
-  - docker
----
-
-# Infrastructure Standards
-
-@.morph/framework/standards/infrastructure/azure/azure.md
-@.morph/framework/standards/infrastructure/docker/easypanel-deploy.md
+---
+paths:
+  - "**/Dockerfile*"
+  - "**/docker-compose*"
+  - "**/.github/**"
+  - "**/easypanel*"
+stacks:
+  - docker
+---
+
+# Infrastructure Standards
+
+@.morph/framework/standards/infrastructure/docker/easypanel-deploy.md
+
+## Infrastructure Templates
+
+| Template | Path | Purpose |
+|----------|------|---------|
+| .NET API Dockerfile | `.morph/framework/templates/infrastructure/docker/dockerfile-api.dockerfile` | Multi-stage .NET |
+| Next.js Dockerfile | `.morph/framework/templates/infrastructure/docker/dockerfile-web.dockerfile` | Multi-stage Next.js |
+| Docker Compose | `.morph/framework/templates/infrastructure/docker/docker-compose.template.yml` | Local dev env |
+| EasyPanel Config | `.morph/framework/templates/infrastructure/docker/easypanel.template.json` | Deployment config |
+| .NET Build CI | `.morph/framework/templates/infrastructure/github/workflows/dotnet-build.yml.hbs` | CI workflow |
+| Docker Push CI | `.morph/framework/templates/infrastructure/github/workflows/docker-build-push.yml.hbs` | Build & push |
+| Deploy EasyPanel | `.morph/framework/templates/infrastructure/github/workflows/deploy-easypanel.yml.hbs` | CD webhook |
+
+Read the template and adapt to your project structure.

package/framework/rules/morph-workflow.md

@@ -14,19 +14,19 @@ stacks:
 **NEVER skip to code without a specification.** Every feature must progress through phases:
 
 1. **Proposal** — User story + acceptance criteria (`0-proposal/proposal.md`)
-2. **Design** — Technical spec + C# contracts + decisions (`1-design/`)
+2. **Design** — Technical spec + C# contracts + decisions (`2-design/`)
 3. **Plan** — Detailed implementation plan (`3-plan/plan.md`)
 4. **Tasks** — Atomic task list (`4-tasks/tasks.md`)
 5. **Implement** — Code + recap (`5-implement/recap.md`)
 
-UI-heavy features also include **UI/UX** phase (`2-ui/`) between Design and Tasks.
+UI-heavy features also include **UI/UX** phase (`1-ui/`) between Design and Tasks.
 
 ---
 
 ## Phase Sequence
 
 ```
-proposal → setup → [uiux] → design → clarify → plan → tasks → implement → [sync]
+proposal → [uiux] → design → plan → tasks → implement → [sync]
 ```
 
 Use `morph-spec status {feature}` to see current phase and pending approval gates.
@@ -64,7 +64,6 @@ Use `morph-spec state mark-output <feature> <type>` with one of these exact type
 | `contracts` | design | — |
 | `contractsVsa` | design | `contracts-vsa` |
 | `decisions` | design | — |
-| `clarifications` | clarify | — |
 | `plan` | plan | — |
 | `tasks` | tasks | — |
 | `uiDesignSystem` | uiux | `ui-design-system` |
@@ -82,10 +81,10 @@ All outputs go in `.morph/features/{feature}/`:
 | Phase | Path |
 |-------|------|
 | Proposal | `0-proposal/proposal.md` |
-| Spec | `1-design/spec.md` |
-| Contracts | `1-design/contracts.cs` |
-| Decisions | `1-design/decisions.md` |
-| UI Design | `2-ui/design-system.md`, `mockups.md`, `components.md`, `flows.md` |
+| UI Design | `1-ui/design-system.md`, `mockups.md`, `components.md`, `flows.md` |
+| Spec | `2-design/spec.md` |
+| Contracts | `2-design/contracts.cs` |
+| Decisions | `2-design/decisions.md` |
 | Plan | `3-plan/plan.md` |
 | Tasks | `4-tasks/tasks.md` |
 | Recap | `5-implement/recap.md` |
@@ -104,11 +103,10 @@ Run a checkpoint every 3 completed tasks:
 
 ## Approval Gates
 
-**Design Gate:** Before moving from Design → Plan, spec must be approved.
-**Plan Gate:** Before moving from Plan → Tasks, plan must be approved.
-**Implementation Gate:** Before starting implementation, task list must be approved.
-
-Check approval status: `morph-spec approval-status {feature}`
+Before completing any phase, verify pending approval gates:
+- `morph-spec approval-status <feature>` — check which gates are pending
+- `morph-spec approve <feature> <gate>` — approve a gate (design, plan, tasks, uiux)
+- Gates must be approved before advancing to the next phase
 
 ---
 
@@ -133,6 +131,68 @@ Do not modify test files to make a failing test pass when the implementation is
 
 ---
 
+## Context Maintenance
+
+After making structural changes (new packages, dependencies, project config changes), update the project context:
+- Edit `.morph/context/README.md` — update Tech Stack, Architecture, Key Integrations sections
+- Update `.morph/config/config.json` — update stack, architecture, integrations, paths
+- Structural changes include: package.json, .csproj, next.config.*, tsconfig.json, docker-compose.yml
+
+---
+
+## Spec-Driven Task Execution (implement phase)
+
+BEFORE implementing ANY task during the implement phase:
+
+1. **Read tasks.md** → identify the FR references for the current task (e.g., `[FR001, FR003]`)
+2. **Read spec.md** → the sections for those specific FRs
+3. **Read contracts.cs/.ts** → the DTOs/interfaces referenced by those FRs
+4. Only then begin implementation
+
+This is **NON-NEGOTIABLE**. The spec is the source of truth. Code that doesn't match the spec is a bug.
+
+Every task in `tasks.md` MUST have FR cross-references in this format:
+```
+### T001: Create user endpoint [FR001, FR003]
+- **Spec refs:** FR001 (user CRUD), FR003 (input validation)
+- **Contracts:** CreateUserRequest, CreateUserResponse, UserErrors
+- **Files:** Features/UserFeature/Create/Handler.cs, Validator.cs, Endpoint.cs
+```
+
+---
+
+## Mandatory Skills per Phase
+
+During implementation, these skills MUST be invoked at the specified triggers:
+
+### Implement Phase
+| Trigger | Skill | When |
+|---------|-------|------|
+| Before each task | `superpowers:test-driven-development` | Invoke BEFORE writing any code for a task |
+| Before task done | `morph-verification-before-completion` | Invoke BEFORE running `morph-spec task done` |
+| On bug/unexpected | `superpowers:systematic-debugging` | Invoke IF a bug or unexpected behavior is encountered |
+| After all tasks | `morph-post-implementation` | Invoke AFTER all tasks completed |
+| Before PR | `morph-checklist` | Invoke BEFORE creating pull request |
+
+### Tasks Phase
+| Trigger | Skill | When |
+|---------|-------|------|
+| On parallel tasks | `superpowers:dispatching-parallel-agents` | When parallel task groups are identified |
+| Before completion | `morph-verification-before-completion` | Before completing the tasks phase |
+
+These are MANDATORY. Use the `Skill()` tool. Do NOT skip.
+
+---
+
+## Scope Escalation
+
+If during implementation a task reveals significantly more complexity than estimated:
+- **Low impact:** `morph-spec task expand <feature> <task-id> --into "T00Xa: Sub" "T00Xb: Sub"`
+- **Medium/High impact:** `/morph-scope-escalation <feature>`
+- **Never** implement extra functionality within a task without registering it as a subtask
+
+---
+
 ## Context Window Tip
 
 When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.

package/framework/rules/nextjs-standards.md

@@ -17,3 +17,4 @@ stacks:
 @.morph/framework/standards/frontend/nextjs/state-management.md
 @.morph/framework/standards/frontend/nextjs/testing.md
 @.morph/framework/standards/frontend/nextjs/nextjs-patterns.md
+@.morph/framework/standards/frontend/nextjs/motion-patterns.md

package/framework/rules/nextjs-templates.md

@@ -0,0 +1,40 @@
+---
+paths:
+  - "**/*.tsx"
+  - "**/*.ts"
+stacks:
+  - nextjs
+---
+
+# Next.js Code Templates
+
+When implementing Next.js features, use these templates as reference patterns.
+Read the template file to see the exact pattern, then generate code following it.
+
+## Scaffold (preferred for new features)
+
+**Always use scaffold for new feature pages — never create feature files manually.**
+
+```bash
+morph-spec scaffold nextjs <feature> [--dry-run]
+```
+
+Examples:
+```bash
+morph-spec scaffold nextjs book
+morph-spec scaffold nextjs user-profile
+```
+
+Generates 4 files: page (Server Component), list component, form component, TanStack Query hook.
+
+**Only use `template render` for individual files when modifying an existing feature.**
+
+| Template | Path | Purpose |
+|----------|------|---------|
+| Server Page | `.morph/framework/templates/frontend/nextjs/page.tsx.hbs` | App Router server component |
+| Client Component | `.morph/framework/templates/frontend/nextjs/client-component.tsx.hbs` | `'use client'` component |
+| Feature Form | `.morph/framework/templates/frontend/nextjs/feature-form.tsx.hbs` | react-hook-form + Zod + shadcn |
+| Custom Hook | `.morph/framework/templates/frontend/nextjs/use-feature.ts.hbs` | TanStack Query hook |
+| Env Config | `.morph/framework/templates/frontend/nextjs/env.mjs.hbs` | T3 Env validation |
+| TypeScript Config | `.morph/framework/templates/frontend/nextjs/tsconfig.json.hbs` | Path aliases |
+| Dockerfile | `.morph/framework/templates/frontend/nextjs/Dockerfile.nextjs.hbs` | Multi-stage build |

package/framework/rules/resend-standards.md

@@ -0,0 +1,12 @@
+---
+paths:
+  - "**/Email/**"
+  - "**/Notification*/**"
+  - "**/Resend/**"
+stacks:
+  - dotnet
+---
+
+# Resend Email Standards
+
+@.morph/framework/standards/backend/integrations/resend/resend-email.md

package/framework/rules/supabase-standards.md

@@ -0,0 +1,29 @@
+---
+paths:
+  - "**/*.sql"
+  - "**/supabase/**"
+  - "**/migrations/**"
+stacks:
+  - supabase
+---
+
+# Supabase & PostgreSQL Standards
+
+@.morph/framework/standards/infrastructure/supabase/supabase-auth.md
+@.morph/framework/standards/infrastructure/supabase/supabase-rls.md
+@.morph/framework/standards/infrastructure/supabase/supabase-storage.md
+@.morph/framework/standards/infrastructure/supabase/supabase-pgvector.md
+@.morph/framework/standards/infrastructure/supabase/mcp-setup.md
+@.morph/framework/standards/infrastructure/supabase/supabase-custom-jwt.md
+@.morph/framework/standards/backend/database/postgresql/database.md
+
+## SQL & Migration Templates
+
+| Template | Path | Purpose |
+|----------|------|---------|
+| Migration (full) | `.morph/framework/templates/code/sql/supabase-migration.template.sql` | RLS + indexes |
+| Migration (simple) | `.morph/framework/templates/code/sql/supabase-migration.sql` | Basic migration |
+| RLS Policy | `.morph/framework/templates/code/sql/rls-policy.sql` | Row Level Security |
+| TS Types | `.morph/framework/templates/code/typescript/contracts.ts` | Supabase DB types |
+
+Read the template to see the exact pattern for migrations, RLS policies, and type generation.

package/framework/skills/README.md

@@ -16,7 +16,7 @@ Each skill is a directory: `{name}/SKILL.md` + optional `scripts/`, `references/
 | `brainstorming` | Collaborative ideation → spec via dialogue |
 | `verification-before-completion` | Gate check before marking any work done |
 | `code-review` | .NET/C# review checklist (naming, arch, async, DI, DTOs) |
-| `morph-replicate` | Convert HTML prototypes to Blazor components |
+
 
 ### level-0-meta extras
 
@@ -36,19 +36,17 @@ Invoked internally by `/morph-proposal` and `/morph-apply`. Not user-invocable.
 | Skill | Phase | Description |
 |-------|-------|-------------|
 | `phase-codebase-analysis` | 0 | Analyse existing codebase before design |
-| `phase-setup` | 1 | Project scaffolding and initial setup |
-| `phase-design` | 2 | Technical spec + contracts + decisions |
-| `phase-uiux` | 3 | UI/UX design system + mockups + components |
-| `phase-clarify` | 4 | Clarification questions → edge cases → spec update |
-| `phase-tasks` | 5 | Break spec into ordered task list (tasks.md) |
-| `phase-implement` | 6 | Implement tasks with TDD + checkpoints + recap |
+| `phase-design` | 2 | Technical spec + contracts + decisions + clarification |
+| `phase-uiux` | 1 | UI/UX design system + mockups + components |
+| `phase-plan` | 3 | Implementation plan with exact paths and TDD |
+| `phase-tasks` | 4 | Break spec into ordered task list (tasks.md) |
+| `phase-implement` | 5 | Implement tasks with TDD + checkpoints + recap |
 
 ### level-1-workflows extras
 
 | Skill | File | Purpose |
 |-------|------|---------|
 | `phase-design` | `references/spec-example.md` | Filled-in spec.md example |
-| `phase-clarify` | `references/clarifications-example.md` | Filled-in clarifications Q&A |
 | `phase-tasks` | `references/tasks-example.md` | Filled-in tasks.md with T### format |
 | `phase-tasks` | `scripts/validate-tasks.mjs` | Validate tasks.md structure and IDs |
 | `phase-implement` | `references/recap-example.md` | Filled-in recap.md example |

package/framework/skills/level-0-meta/mcp-registry.json

@@ -56,35 +56,8 @@
         "setupGuide": null
       }
     },
-    "supabase": {
-      "phases": ["design", "implement"],
-      "tools": ["list_tables", "get_table_schema", "get_relationships", "query"],
-      "detection": "mcpServers includes supabase",
-      "fallback": "Grep query files + Read type definitions for schema inference",
-      "usage": "Schema analysis, migrations, RLS policies, data operations",
-      "healthCheck": {
-        "toolPattern": "supabase",
-        "testCall": "Call list_tables with no parameters",
-        "testParams": {},
-        "successIndicator": "Returns a list of tables (even if empty)",
-        "failureHint": "Supabase MCP not responding. If using remote mode, re-authenticate via /mcp in Claude Code. If using local mode, verify SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY in .claude/settings.local.json."
-      },
-      "install": {
-        "autoInstall": false,
-        "transport": "http",
-        "config": {
-          "type": "http",
-          "url": "https://mcp.supabase.com/mcp"
-        },
-        "credentials": [],
-        "prerequisites": [],
-        "stackRelevance": ["nextjs-supabase", "supabase", "nextjs"],
-        "warnings": ["Uses OAuth — you will be prompted to authenticate via browser when first connecting.", "NEVER connect to PRODUCTION databases. Use local/dev environment only."],
-        "setupGuide": "Run: claude mcp add --transport http supabase https://mcp.supabase.com/mcp"
-      }
-    },
     "github": {
-      "phases": ["setup", "tasks", "implement"],
+      "phases": ["tasks", "implement"],
       "tools": ["get_repo", "search_code", "create_issue", "create_pull_request", "search_issues"],
       "detection": "mcpServers includes github",
       "fallback": "Bash `gh` CLI commands",
@@ -153,90 +126,39 @@
         "setupGuide": "Run: claude mcp add --transport http vercel https://mcp.vercel.com"
       }
     },
-    "docker": {
-      "phases": ["implement"],
-      "tools": ["build", "run", "compose"],
-      "detection": "mcpServers includes docker",
-      "fallback": "Bash `docker` CLI commands",
-      "usage": "Container management, build and run containers",
+    "asaas": {
+      "phases": ["design", "implement"],
+      "tools": ["enumerate_endpoints", "get_endpoint_schema", "generate_code_example", "execute_api_call", "search_docs"],
+      "detection": "mcpServers includes asaas",
+      "fallback": "WebFetch https://docs.asaas.com for API documentation",
+      "usage": "Asaas payment API docs, endpoint schemas, code examples, direct API calls",
       "healthCheck": {
-        "toolPattern": "docker",
-        "testCall": "Call any read-only Docker tool to verify Docker daemon connectivity",
-        "testParams": {},
-        "successIndicator": "Tool responds without connection errors (Docker daemon is reachable)",
-        "failureHint": "Docker MCP not responding. Ensure Docker Desktop is running and the Docker daemon is accessible. Run 'docker info' to verify."
+        "toolPattern": "asaas",
+        "testCall": "Search Asaas docs for 'payments' to verify connectivity",
+        "testParams": { "query": "payments" },
+        "successIndicator": "Returns documentation results about payment endpoints",
+        "failureHint": "Asaas MCP not responding. Verify the MCP is configured with url: https://docs.asaas.com/mcp"
       },
       "install": {
         "autoInstall": false,
-        "transport": "stdio",
+        "transport": "http",
         "config": {
-          "command": "cmd",
-          "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-docker"]
+          "type": "http",
+          "url": "https://docs.asaas.com/mcp"
         },
         "credentials": [],
-        "prerequisites": [
-          {
-            "name": "Docker",
-            "checkCommand": "docker --version",
-            "installUrl": "https://docs.docker.com/get-docker/"
-          }
-        ],
-        "stackRelevance": ["dotnet", "blazor", "nextjs", "nodejs"],
-        "warnings": [],
-        "setupGuide": null
-      }
-    },
-    "azure": {
-      "phases": ["implement"],
-      "tools": ["deploy", "resource_management"],
-      "detection": "mcpServers includes azure",
-      "fallback": "Bash `az` CLI commands",
-      "usage": "Cloud resource management, deployment",
-      "healthCheck": {
-        "toolPattern": "azure",
-        "testCall": "Call any read-only Azure tool to verify credentials and connectivity",
-        "testParams": {},
-        "successIndicator": "Tool responds without authentication or subscription errors",
-        "failureHint": "Azure MCP not responding. Verify AZURE_SUBSCRIPTION_ID in .claude/settings.local.json and ensure 'az login' has been run. Check that Azure CLI is installed with 'az --version'."
-      },
-      "install": {
-        "autoInstall": false,
-        "transport": "stdio",
-        "config": {
-          "command": "cmd",
-          "args": ["/c", "npx", "-y", "@azure/mcp-server"],
-          "env": {
-            "AZURE_SUBSCRIPTION_ID": ""
-          }
-        },
-        "credentials": [
-          {
-            "name": "Azure Subscription ID",
-            "envVar": "AZURE_SUBSCRIPTION_ID",
-            "secret": false,
-            "helpUrl": "https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade"
-          }
-        ],
-        "prerequisites": [
-          {
-            "name": "Azure CLI",
-            "checkCommand": "az --version",
-            "installUrl": "https://learn.microsoft.com/en-us/cli/azure/install-azure-cli"
-          }
-        ],
-        "stackRelevance": ["blazor", "dotnet", "azure"],
-        "warnings": [],
-        "setupGuide": null
+        "prerequisites": [],
+        "stackRelevance": ["asaas"],
+        "warnings": ["API call execution requires your Asaas access_token. Doc search works without authentication."],
+        "setupGuide": "Run: claude mcp add --transport http asaas https://docs.asaas.com/mcp"
       }
     }
   },
   "phaseMatrix": {
     "proposal": ["context7"],
-    "setup": ["github"],
     "uiux": ["playwright", "context7"],
-    "design": ["supabase", "context7", "github"],
-    "clarify": ["context7", "github"],
+    "design": ["context7", "github"],
     "tasks": ["context7", "github"],
-    "implement": ["supabase", "context7", "playwright", "github", "vercel", "docker", "azure"]
+    "implement": ["context7", "playwright", "github", "vercel"]
   }
 }