@polymorphism-tech/morph-spec 4.3.7 → 4.6.0

package/framework/templates/docs/ui-mockups.md

@@ -0,0 +1,98 @@
+# UI Mockups & Wireframes: {{titleCase FEATURE_NAME}}
+
+| Field | Value |
+|-------|-------|
+| **Feature** | {{FEATURE_NAME}} |
+| **Created** | {{DATE}} |
+
+---
+
+## Screen Inventory
+
+| Screen ID | Name | Route | Priority |
+|-----------|------|-------|----------|
+| **S001** | {Screen Name} | /path | High |
+| **S002** | {Screen Name} | /path | Medium |
+
+---
+
+## S001: {Primary Screen}
+
+### Desktop Layout
+
+```
+┌─────────────────────────────────────┐
+│  Header                    [User ▼] │
+├─────────────────────────────────────┤
+│                                     │
+│  [Title]                            │
+│                                     │
+│  ┌──────────────────────────────┐  │
+│  │ Main Content Area            │  │
+│  │                              │  │
+│  │  [Card 1]    [Card 2]        │  │
+│  │                              │  │
+│  │  ┌────────────────────────┐  │  │
+│  │  │ Data Table             │  │  │
+│  │  │ ...                    │  │  │
+│  │  └────────────────────────┘  │  │
+│  └──────────────────────────────┘  │
+│                                     │
+└─────────────────────────────────────┘
+```
+
+### Mobile Layout
+
+```
+┌──────────────────────┐
+│ ☰  Title    [User ▼]│
+├──────────────────────┤
+│                      │
+│ [Card 1]             │
+│                      │
+│ [Card 2]             │
+│                      │
+│ [View All Items]     │
+│                      │
+└──────────────────────┘
+```
+
+---
+
+## States
+
+### Loading
+- Show skeleton placeholders
+- Spinner for primary content
+
+### Empty
+- Icon + message
+- Clear call-to-action button
+
+### Error
+- Warning icon
+- User-friendly message
+- Retry button
+
+### Success (After Action)
+- Toast notification
+- Auto-dismiss after 3s
+
+---
+
+## Interactions
+
+- **Hover**: Subtle elevation increase
+- **Click**: Scale down (0.98)
+- **Transitions**: Fade-in 200ms
+
+---
+
+## Accessibility
+- [ ] 44x44px minimum touch targets
+- [ ] Focus indicators visible
+- [ ] Proper heading hierarchy (H1 → H2 → H3)
+
+---
+
+*Generated with MORPH Framework*

package/framework/templates/docs/user-stories.md

@@ -0,0 +1,34 @@
+# User Stories: {{featureName}}
+
+> Generated: {{date}} | Feature: {{featureName}} | Status: Draft
+
+---
+
+## Story 1: [Actor] [Action]
+
+**Feature:** {{featureName}}
+**Priority:** High / Medium / Low
+
+### Optimal Path
+1. [Step 1]
+2. [Step 2]
+3. [Step 3 — success state]
+
+### Edge Cases
+- [Edge case] → [Expected behavior]
+- [Error condition] → [Expected error handling]
+
+### Acceptance Criteria
+- [ ] [Measurable criterion 1]
+- [ ] [Measurable criterion 2]
+- [ ] Edge: [edge case criterion]
+
+---
+
+## Story 2: [Actor] [Action]
+
+[Repeat structure above]
+
+---
+
+*Generated by MORPH-SPEC — complete before implementation begins*

package/framework/templates/examples/spec-examples.md

@@ -2,7 +2,7 @@
 
 > **Layer:** 3 | **Load:** on-demand | **Keywords:** spec, specification, template
 
-**Use the stack's `.morph/templates/spec.md` as the canonical template.**
+**Use the stack's `.morph/framework/templates/spec.md` as the canonical template.**
 
 This file contains extended examples for each spec section.
 

package/framework/templates/infrastructure/github/README.md

@@ -104,7 +104,7 @@ steps:
 
 **Workflows:**
 - Framework: `deploy-azure-app-service.yml.hbs`
-- Stack: `stacks/blazor-azure/.morph/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
+- Stack: `stacks/blazor-azure/.morph/framework/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
 
 ### NextJS-Supabase (EasyPanel/Docker)
 
@@ -130,7 +130,7 @@ steps:
 
 **Workflows:**
 - Framework: `docker-build-push.yml.hbs`, `deploy-easypanel.yml.hbs`
-- Stack: `stacks/nextjs-supabase/.morph/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
+- Stack: `stacks/nextjs-supabase/.morph/framework/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
 
 ---
 
@@ -290,7 +290,7 @@ morph-spec template render github-workflows \
 ### What Gets Committed
 
 ✅ **Commit:** Rendered `.yml` files in `.github/workflows/` and `.github/actions/`
-❌ **Don't Commit:** Template sources (`.yml.hbs` files) - these stay in `.morph/templates/`
+❌ **Don't Commit:** Template sources (`.yml.hbs` files) - these stay in `.morph/framework/templates/`
 
 **Example:**
 ```
@@ -305,7 +305,7 @@ morph-spec template render github-workflows \
         └── action.yml        # Rendered from template
 
 # NOT committed (template sources):
-.morph/templates/infrastructure/github/
+.morph/framework/templates/infrastructure/github/
 ├── workflows/
 │   ├── ci-build.yml.hbs      # Template source
 │   └── ...
@@ -318,11 +318,11 @@ morph-spec template render github-workflows \
 Templates follow the 3-tier resolution hierarchy:
 
 1. **Project-local** (highest priority)
-   - `.morph/templates/infrastructure/github/workflows/ci-build.yml.hbs`
+   - `.morph/framework/templates/infrastructure/github/workflows/ci-build.yml.hbs`
    - Use for project-specific customizations
 
 2. **Stack default** (medium priority)
-   - `stacks/blazor-azure/.morph/templates/infrastructure/github/workflows/ci-build.yml.hbs`
+   - `stacks/blazor-azure/.morph/framework/templates/infrastructure/github/workflows/ci-build.yml.hbs`
    - Stack-specific workflows (production, staging, CI)
 
 3. **Framework fallback** (lowest priority)
@@ -333,7 +333,7 @@ Templates follow the 3-tier resolution hierarchy:
 
 Stack workflow `cd-prod.yml.hbs` **calls** framework workflow `dotnet-build.yml.hbs`:
 ```yaml
-# Stack: stacks/blazor-azure/.morph/templates/.../cd-prod.yml.hbs
+# Stack: stacks/blazor-azure/.morph/framework/templates/.../cd-prod.yml.hbs
 jobs:
   build:
     uses: ./.github/workflows/dotnet-build.yml  # Framework template (rendered)
@@ -394,7 +394,7 @@ actionlint .github/workflows/*.yml
 
 ### Example 1: CI Build (Blazor-Azure)
 
-**Stack Template:** `stacks/blazor-azure/.morph/templates/infrastructure/github/workflows/ci-build.yml.hbs`
+**Stack Template:** `stacks/blazor-azure/.morph/framework/templates/infrastructure/github/workflows/ci-build.yml.hbs`
 
 ```yaml
 name: CI Build
@@ -424,7 +424,7 @@ jobs:
 
 ### Example 2: Production Deployment (NextJS-Supabase)
 
-**Stack Template:** `stacks/nextjs-supabase/.morph/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
+**Stack Template:** `stacks/nextjs-supabase/.morph/framework/templates/infrastructure/github/workflows/cd-prod.yml.hbs`
 
 ```yaml
 name: Deploy to Production
@@ -459,13 +459,13 @@ jobs:
 
 1. **Create override template:**
    ```bash
-   mkdir -p stacks/blazor-azure/.morph/templates/infrastructure/github/workflows
+   mkdir -p stacks/blazor-azure/.morph/framework/templates/infrastructure/github/workflows
    ```
 
 2. **Copy framework template:**
    ```bash
    cp framework/templates/infrastructure/github/workflows/deploy-azure-app-service.yml.hbs \
-      stacks/blazor-azure/.morph/templates/infrastructure/github/workflows/
+      stacks/blazor-azure/.morph/framework/templates/infrastructure/github/workflows/
    ```
 
 3. **Customize:**

package/framework/templates/infrastructure/github/workflows/deploy-azure-app-service.yml.hbs

@@ -35,8 +35,8 @@ jobs:
         uses: azure/arm-deploy@v1
         with:
           resourceGroupName: ${{{{ inputs.resource-group }}}}
-          template: .morph/templates/infra/main.bicep
-          parameters: .morph/templates/infra/parameters.${{{{ inputs.environment }}}}.json
+          template: .morph/framework/templates/infra/main.bicep
+          parameters: .morph/framework/templates/infra/parameters.${{{{ inputs.environment }}}}.json
 
       - name: Setup .NET
         uses: actions/setup-dotnet@v4

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/project/outputs/{{FEATURE_NAME}}/spec.md`
+- `.morph/features/{{FEATURE_NAME}}/1-design/spec.md`
 - `framework/standards/` (all)
-- `.morph/project/outputs/{{FEATURE_NAME}}/contracts.*`
+- `.morph/features/{{FEATURE_NAME}}/1-design/contracts.*`
 
 ## Spec Summary
 {{SPEC_SUMMARY}}

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

@@ -40,7 +40,7 @@ Check staged files for accidental secrets:
 - Private key headers
 
 ### 3. Agent Spec Validation (if agents.json staged)
-If `.morph/config/agents.json` is in staged files:
+If `.morph/framework/agents.json` is in staged files:
 - Valid JSON structure
 - All required agent fields present (agentId, role, tier, domain)
 - No duplicate agentIds

package/framework/workflows/configs/express.json

@@ -0,0 +1,45 @@
+{
+  "id": "express",
+  "name": "Express (Backend Focus)",
+  "description": "Streamlined workflow for backend changes - skips UI/UX and Clarify phases",
+  "criteria": {
+    "maxFiles": 20,
+    "maxLines": 500,
+    "maxComponents": 0,
+    "noInfrastructure": false,
+    "noArchitecturalDecisions": false
+  },
+  "keywords": [
+    "api",
+    "endpoint",
+    "service",
+    "repository",
+    "migration",
+    "background job",
+    "integration",
+    "backend",
+    "data",
+    "queue",
+    "webhook"
+  ],
+  "phases": {
+    "run": ["proposal", "setup", "design", "tasks", "implement"],
+    "skip": ["uiux", "clarify", "sync"],
+    "combined": {}
+  },
+  "pausePoints": [
+    {
+      "phase": "design",
+      "question": "Approve spec and contracts before task breakdown?"
+    },
+    {
+      "phase": "tasks",
+      "question": "Approve task breakdown before implementation?"
+    }
+  ],
+  "outputs": {
+    "required": ["proposal", "spec", "contracts", "tasks"],
+    "optional": ["schema-analysis", "decisions", "recap"]
+  },
+  "priority": 3
+}

package/framework/workflows/configs/spec-only.json

@@ -0,0 +1,43 @@
+{
+  "id": "spec-only",
+  "name": "Spec Only (Documentation)",
+  "description": "Documentation-driven workflow - produces specs and plans without implementation",
+  "criteria": {
+    "maxFiles": 0,
+    "maxLines": 0,
+    "maxComponents": 0,
+    "noInfrastructure": false,
+    "noArchitecturalDecisions": false
+  },
+  "keywords": [
+    "spec",
+    "specification",
+    "document",
+    "plan",
+    "architecture",
+    "design",
+    "rfc",
+    "proposal",
+    "planning"
+  ],
+  "phases": {
+    "run": ["proposal", "setup", "uiux", "design", "clarify", "tasks"],
+    "skip": ["implement", "sync"],
+    "combined": {}
+  },
+  "pausePoints": [
+    {
+      "phase": "design",
+      "question": "Approve technical specification?"
+    },
+    {
+      "phase": "tasks",
+      "question": "Approve task breakdown? (Implementation will not be executed)"
+    }
+  ],
+  "outputs": {
+    "required": ["proposal", "spec", "contracts", "decisions", "tasks"],
+    "optional": ["schema-analysis", "clarifications", "ui-design-system", "ui-mockups"]
+  },
+  "priority": 5
+}

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

@@ -59,7 +59,7 @@ Before: Hardcoded AGENT_VALIDATOR_MAP in validation-runner.js made it impossible
 # Validators run automatically on task completion
 morph-spec task done my-feature T001
 
-# To customize: edit .morph/config/agents.json
+# To customize: edit .morph/framework/agents.json
 {
   "my-custom-agent": {
     "validators": ["architecture", "custom-validator"]
@@ -88,8 +88,8 @@ Before: Specialists had to manually read standards files, often missing relevant
 ```javascript
 export function loadStandardsForAgent(agentId, projectPath) {
   // Resolution order:
-  // 1. .morph/project/standards/{file}.md (project overrides)
-  // 2. .morph/standards/{file}.md (content standards)
+  // 1. .morph/context/{file}.md (project overrides)
+  // 2. .morph/framework/standards/{file}.md (content standards)
   // 3. framework/standards/{file}.md (framework standards)
 
   return {
@@ -146,7 +146,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`
-  2. Project-level: `.morph/project/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
 
@@ -182,7 +182,7 @@ morph-spec phase advance my-ui-feature
 # ✗ Cannot advance to implementation — UI agents are active but no design system found
 #
 # Create a design system with one of these options:
-#   1. Project-level: .morph/project/design-system.md
+#   1. Project-level: .morph/context/design-system.md
 #   2. Feature-level: .morph/features/my-ui-feature/ui-design-system.md
 #   3. Auto-generate: morph-spec generate design-system
 
@@ -512,7 +512,7 @@ morph-spec phase advance {feature} --skip-warnings
 
 **Check:**
 1. Is agent active? `morph-spec state get {feature}` → check activeAgents
-2. Is validator mapped? Check `.morph/config/agents.json` → agent's `validators` array
+2. Is validator mapped? Check `.morph/framework/agents.json` → agent's `validators` array
 3. Is agents.json readable? Run `morph-spec validate-agents-skills`
 
 **Fix:**
@@ -534,7 +534,7 @@ morph-spec state add-agent {feature} {agent-id}
 
 **Check:**
 1. Detection order: feature > project > generated > existing CSS
-2. File location: `.morph/project/design-system.md` or `.morph/features/{feature}/ui-design-system.md`
+2. File location: `.morph/context/design-system.md` or `.morph/features/{feature}/ui-design-system.md`
 3. Format: Must have `# Design System` or `## Colors` sections
 
 **Fix:**
@@ -542,7 +542,7 @@ morph-spec state add-agent {feature} {agent-id}
 # Create design system
 morph-spec generate design-system {feature}
 
-# Or manually create .morph/project/design-system.md with:
+# Or manually create .morph/context/design-system.md with:
 # # Design System
 # ## Colors
 # - primary: #007bff

package/framework/workflows/docs/full-morph.md

@@ -11,10 +11,10 @@
 
 ### FASE 0.5: CONTEXT (automática)
 1. Detectar framework MORPH (`@polymorphism-tech/morph-spec`)
-2. Detectar/criar estrutura `.morph/project/`
+2. Detectar/criar estrutura `.morph/`
 3. Análise automática: stack (glob patterns), arquitetura (pastas), configs, UI library
 4. Analisar histórico: decisions.md passados, preferências do usuário
-5. Gerar/atualizar `.morph/project/standards/inferred.md`
+5. Gerar/atualizar `.morph/context/inferred.md`
 6. Ativar agentes baseado em stack + keywords
 
 ### FASE 0: PROPOSAL
@@ -61,7 +61,7 @@
 
 ### FASE 6: SYNC (condicional - se complexidade média/alta)
 1. Revisar decisions.md, categorizar (coding, architecture, azure, integrations, ui-ux)
-2. Promover para `.morph/project/standards/{category}.md`
+2. Promover para `.morph/context/{category}.md`
 3. Gerar commit dedicado de sync
 - **⛔ PAUSA:** Aprovar promoção de decisões para standards
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "4.3.7",
+  "version": "4.6.0",
   "description": "MORPH-SPEC: AI-First development framework with validation pipeline and multi-stack support",
   "keywords": [
     "claude-code",
@@ -28,6 +28,7 @@
     "src/",
     ".morph/",
     "framework/",
+    "claude-plugin.json",
     "scripts/",
     "docs/",
     "README.md",
@@ -40,6 +41,7 @@
   },
   "scripts": {
     "start": "node bin/morph-spec.js",
+    "generate": "node scripts/generate-refs.js",
     "test": "node --test --test-concurrency=1",
     "test:coverage": "c8 --reporter=text --reporter=html --reporter=lcov node --test --test-concurrency=1",
     "test:coverage:summary": "c8 --reporter=text-summary node --test --test-concurrency=1",