@polymorphism-tech/morph-spec 4.21.0 → 4.22.0

package/README.md

@@ -3,7 +3,7 @@
 > Spec-driven development framework for multi-stack projects. Turns feature requests into implementation-ready code through structured, AI-orchestrated phases.
 
 **Package:** `@polymorphism-tech/morph-spec`
-**Version:** 4.21.0  
+**Version:** 4.22.0  
 **Requires:** Node.js 18+, Claude Code
 
 ---
@@ -364,4 +364,4 @@ Code generated by morph-spec (contracts, templates, implementation output) belon
 
 ---
 
-*morph-spec v4.21.0 by [Polymorphism Tech](https://polymorphism.tech)*
+*morph-spec v4.22.0 by [Polymorphism Tech](https://polymorphism.tech)*

package/claude-plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "morph-spec",
-  "version": "4.21.0",
+  "version": "4.22.0",
   "displayName": "MORPH-SPEC Framework",
   "description": "Spec-driven development with 38 agents and 8-phase workflow for .NET/Blazor/Next.js/Azure",
   "publisher": "polymorphism-tech",

package/docs/CHEATSHEET.md

@@ -196,4 +196,4 @@ These files are never edited directly. Use CLI commands or `morph-spec update` i
 
 ---
 
-*morph-spec v4.21.0 by Polymorphism Tech*
+*morph-spec v4.22.0 by Polymorphism Tech*

package/docs/QUICKSTART.md

@@ -197,4 +197,4 @@ morph-spec doctor
 
 ---
 
-*morph-spec v4.21.0 by Polymorphism Tech*
+*morph-spec v4.22.0 by Polymorphism Tech*

package/framework/agents.json

@@ -255,6 +255,11 @@
           "id": "frontend-design-system-animations",
           "scope": "all",
           "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-ai-image-generation",
+          "scope": "uiux",
+          "priority": "recommended"
         }
       ],
       "teammate": {
@@ -703,6 +708,11 @@
           "id": "frontend-nextjs-motion-patterns",
           "scope": "all",
           "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-ai-image-generation",
+          "scope": "implement",
+          "priority": "recommended"
         }
       ],
       "teammate": {
@@ -747,6 +757,11 @@
           "id": "frontend-design-system-animations",
           "scope": "all",
           "priority": "required"
+        },
+        {
+          "id": "frontend-design-system-ai-image-generation",
+          "scope": "implement",
+          "priority": "recommended"
         }
       ],
       "teammate": {

package/framework/hooks/shared/phase-utils.js

@@ -35,6 +35,7 @@ export const OUTPUT_PHASE_MAP = {
   uiMockups: 'uiux',
   uiComponents: 'uiux',
   uiFlows: 'uiux',
+  stitchHtml: 'uiux',
   decisions: 'design',
   recap: 'implement',
 };
@@ -53,6 +54,7 @@ export const FILENAME_TO_OUTPUT = {
   'mockups.md': 'uiMockups',
   'components.md': 'uiComponents',
   'flows.md': 'uiFlows',
+  'stitch-screen-map.json': 'stitchHtml',
   'decisions.md': 'decisions',
   'recap.md': 'recap',
 };
@@ -70,6 +72,7 @@ export const PROTECTED_SPEC_FILES = {
   'mockups.md': 'uiux',
   'components.md': 'uiux',
   'flows.md': 'uiux',
+  'stitch-screen-map.json': 'uiux',
 };
 
 /**

package/framework/phases.json

@@ -34,7 +34,7 @@
         "Produce wireframes and user flows"
       ],
       "requiredOutputs": ["uiDesignSystem"],
-      "optionalOutputs": ["uiMockups", "uiComponents", "uiFlows"],
+      "optionalOutputs": ["uiMockups", "uiComponents", "uiFlows", "stitchHtml"],
       "recommendedMCPs": ["playwright", "context7", "stitch"],
       "pausePoints": [
         { "id": "uiux", "label": "Approve UI/UX Design" }

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

@@ -198,13 +198,46 @@
         "skills": ["stitch-design", "stitch-loop", "design-md", "prompt-enhance", "react-components", "shadcn-ui"],
         "description": "Official Stitch agent skills for Claude Code — design generation, multi-page loops, design.md export"
       }
+    },
+    "gemini-image": {
+      "phases": ["uiux", "implement"],
+      "tools": ["generate_image", "edit_image", "continue_editing", "list_images", "get_image_info", "get_configuration_status"],
+      "detection": "mcpServers includes gemini-image-mcp",
+      "fallback": "Manual image creation, stock photos, or placeholder divs",
+      "usage": "AI image generation for project assets (heroes, illustrations, brand images) using Gemini models",
+      "healthCheck": {
+        "toolPattern": "gemini-image",
+        "testCall": "Call get_configuration_status to verify API key and server health",
+        "testParams": {},
+        "successIndicator": "Returns status with valid API key configured",
+        "failureHint": "Gemini Image MCP not responding. Ensure GEMINI_API_KEY is set in MCP server configuration. Install: npx gemini-image-mcp@latest"
+      },
+      "install": {
+        "autoInstall": false,
+        "transport": "stdio",
+        "config": {
+          "command": "cmd",
+          "args": ["/c", "npx", "-y", "gemini-image-mcp@latest"]
+        },
+        "credentials": [
+          {
+            "name": "Gemini API Key",
+            "envVar": "GEMINI_API_KEY",
+            "source": "Google AI Studio (https://aistudio.google.com/apikey)"
+          }
+        ],
+        "prerequisites": ["Google AI Studio API key"],
+        "stackRelevance": ["nextjs", "next"],
+        "warnings": ["Requires GEMINI_API_KEY environment variable. Image generation costs apply per Google AI pricing."],
+        "setupGuide": "1. Get API key from https://aistudio.google.com/apikey\n2. Run: claude mcp add gemini-image-mcp -- npx gemini-image-mcp@latest\n3. Set GEMINI_API_KEY in MCP env config"
+      }
     }
   },
   "phaseMatrix": {
     "proposal": ["context7"],
-    "uiux": ["playwright", "context7", "stitch"],
+    "uiux": ["playwright", "context7", "stitch", "gemini-image"],
     "design": ["context7", "github"],
     "tasks": ["context7", "github"],
-    "implement": ["context7", "playwright", "github", "vercel"]
+    "implement": ["context7", "playwright", "github", "vercel", "gemini-image"]
   }
 }

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

@@ -10,7 +10,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion,
   mcp__playwright__browser_navigate, mcp__playwright__browser_resize,
   mcp__playwright__browser_take_screenshot, mcp__playwright__browser_snapshot,
   mcp__playwright__browser_evaluate, mcp__playwright__browser_console_messages
-cliVersion: "4.21.0"
+cliVersion: "4.22.0"
 stacks:
   - nextjs
 ---

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

@@ -0,0 +1,290 @@
+---
+name: morph-gemini-image
+description: |
+  Expert at generating and editing images via the Gemini Image MCP (gemini-image-mcp).
+  Constructs high-quality prompts for Gemini image models using narrative natural language.
+  Use when implementing UI components that need generated images, or when assets.md
+  specifies image requirements. Also use for standalone image generation requests.
+  Triggers: /morph-gemini-image, "generate image", "create image", "edit image",
+  "make a logo", "generate assets", image generation for components.
+argument-hint: "[optional: image description or assets.md IMG-ID]"
+user-invocable: true
+allowed-tools: Read, Write, Glob, Grep, AskUserQuestion
+cliVersion: "4.22.0"
+---
+
+# Gemini Image — Prompt Specialist
+
+You are an expert at communicating with the Gemini 2.5 Flash Image model (Nano Banana) through the `gemini-image-mcp` MCP server. Your job is to transform the user's intent into the best possible prompt and then execute it.
+
+## The Golden Rules
+
+**1. Describe scenes narratively, never list keywords.** The Gemini image model has deep language comprehension — coherent paragraphs consistently outperform disconnected keyword lists. Think of it as briefing a photographer or illustrator, not filling in search tags.
+
+**2. Generation demands depth; editing demands restraint.** These are opposite strategies:
+- **Generation**: Go deep. Multi-layered compositions, rich textures, dramatic lighting contrasts, visual storytelling. Simple prompts produce flat, generic images. Push for complexity — foreground interest, mid-ground subject, background atmosphere. Think in layers.
+- **Editing**: Go minimal. Short, direct instructions targeting exactly what changes. The more you describe in an edit prompt, the more the model "re-imagines" the image and the more artificial it looks. 1-2 sentences max for edits.
+
+## Important: JSON Does NOT Work
+
+The Gemini image models do NOT support JSON/structured output mode for image generation. Sending JSON-formatted prompts provides no benefit and can confuse the model. Always use natural language.
+
+## Available MCP Tools
+
+| Tool | When to use |
+|------|-------------|
+| `generate_image` | Create new images from text description |
+| `edit_image` | Modify an existing image (needs `imagePath`) |
+| `continue_editing` | Iterate on the last generated/edited image |
+| `list_images` | Browse image history |
+| `get_image_info` | Get metadata about a specific image |
+| `get_configuration_status` | Check API key and server health |
+
+## How to Build Prompts
+
+### Step 1: Identify the Category
+
+Determine what kind of image the user wants. Each category has a different prompt template that produces optimal results:
+
+**Photorealistic** — Real-world scenes, portraits, product photos, landscapes
+**Illustration** — Stickers, icons, cartoon, kawaii, branded designs
+**Text Rendering** — Logos, infographics, menus, diagrams with legible text
+**Product Mockup** — E-commerce, studio product shots
+**Minimalist / Negative Space** — Clean compositions for overlays or branding
+**Sequential Art** — Comics, storyboards, panels
+
+### Step 2: Construct the Prompt
+
+Build the prompt by layering these elements (order matters — put the most important things first).
+
+The key to images that feel deep and impactful rather than flat and generic is **visual layering** — describe what's happening in the foreground, mid-ground, and background separately. A flat description ("neon city at night") produces a flat image. A layered description creates depth that pulls the viewer in.
+
+1. **Subject** — Who/what is the main focus? Be hyper-specific.
+   - Bad: "a warrior in armor"
+   - Good: "a tall elven warrior in ornate silver plate armor with falcon-wing pauldrons and a high collar etched with leaf patterns"
+
+2. **Action / Pose** — What is the subject doing? Expression? Gesture?
+
+3. **Environment / Setting** — Where is this happening? Describe in **layers**:
+   - **Foreground**: What's closest to camera? (objects, textures, particles, rain drops)
+   - **Mid-ground**: Where is the subject? What surrounds them?
+   - **Background**: What's far away? (sky, distant buildings, horizon, atmospheric haze)
+   - This layered approach creates depth of field and visual richness that flat descriptions miss.
+
+4. **Lighting** — This dramatically affects mood and is the single biggest quality lever. Use photography terms and describe **multiple light sources** for complexity:
+   - "golden hour key light from the left, with cool blue fill from ambient sky on the right, and warm rim light from behind catching hair edges"
+   - "harsh overhead spotlight casting dramatic shadows, with neon signs reflecting colored light off wet surfaces"
+   - "soft diffused window light as primary, with practical warm bulbs adding depth in the background"
+   - Single-source flat lighting = flat image. Multiple sources with different colors/directions = cinematic depth.
+
+5. **Style / Medium** — How should it look?
+   - Photography: mention camera, lens, film stock ("85mm portrait lens, shallow depth of field, Kodak Portra 400 film grain")
+   - Illustration: name the style ("kawaii", "cel-shaded", "watercolor", "ink wash", "art nouveau")
+   - Reference artists when useful: "in the style of Studio Ghibli", "Van Gogh's Starry Night brushwork"
+
+6. **Color Palette** — Specify dominant colors and **contrast relationships**
+   - "warm amber highlights against deep teal shadows"
+   - "desaturated cool tones with a single pop of crimson red on the subject"
+   - Color contrast draws the eye and creates visual hierarchy.
+
+7. **Composition** — Camera angle, framing, negative space
+   - "low angle looking up", "bird's eye view", "close-up macro", "rule of thirds with subject on left"
+   - Describe **depth cues**: objects overlapping, foreground blur, atmospheric perspective (distant objects fading into haze)
+
+8. **Texture and Detail** — What makes it tactile and real?
+   - "rain droplets on glass", "worn leather with visible stitching", "dust particles floating in light beams", "condensation on cold metal"
+   - These micro-details transform flat images into immersive scenes.
+
+9. **Aspect Ratio** — Choose based on purpose:
+   - `1:1` — Social media posts, avatars, icons
+   - `16:9` — Presentations, YouTube thumbnails, desktop wallpapers
+   - `9:16` — Stories, reels, mobile wallpapers
+   - `3:2` — Landscape photography, blog headers
+   - `2:3` — Portrait photography, book covers
+   - `4:3` — Standard display, documents
+   - `3:4` — Pinterest, portrait posters
+
+### Step 3: Apply Category-Specific Templates
+
+#### Photorealistic
+```
+A [shot type] of [subject with specific details], [action/pose],
+set in [environment with atmosphere], illuminated by [lighting description],
+captured with [camera/lens], [mood/feeling], [aspect ratio orientation].
+```
+Example: "A close-up portrait of an elderly ceramicist inspecting a hand-glazed tea bowl in his sun-drenched workshop, golden hour light streaming through dusty windows, 85mm portrait lens with soft bokeh, serene and contemplative atmosphere, vertical orientation."
+
+#### Illustration / Sticker
+```
+[Art style] [subject with personality traits], [key visual details],
+[line style] outlines, [shading approach], [color palette],
+[background specification].
+```
+Example: "Kawaii-style red panda sticker wearing a tiny bamboo hat and holding a matcha cup, bold clean outlines, cel-shading with soft highlights, vibrant warm colors with pink accents, white background."
+
+#### Text Rendering (Logos, Infographics)
+```
+[Image type] for [brand/concept context], featuring the text "[exact text]"
+in [font style description], [visual elements around text],
+[overall color scheme and style], [format].
+```
+Example: "Minimalist coffee shop logo for a premium artisan brand, featuring the text 'The Daily Grind' in clean geometric sans-serif, with a stylized coffee bean icon integrated into the letter 'D', black and white with a single copper accent, square format."
+
+**Important: Text rendering often contains spelling errors.** The model frequently misspells words, swaps letters, or drops characters — especially in longer words. After generating any image with text, always verify the spelling by viewing the result. If text is wrong, use `continue_editing` with a prompt like: "Fix the text spelling — it should read '[correct text]' exactly. Keep everything else the same." You may need 2-3 iterations to get text perfect.
+
+#### Product Mockup
+```
+High-resolution studio photograph of [product with materials],
+on [surface/background], [lighting setup], [camera angle] for [purpose],
+sharp focus on [detail], [realism level], [aspect ratio].
+```
+Example: "High-resolution studio photograph of a minimalist black ceramic mug with a matte finish on a polished concrete surface, three-point softbox lighting with a subtle warm key light, 45-degree elevated angle for e-commerce listing, sharp focus on the steam rising from dark coffee, photorealistic, square format."
+
+#### Minimalist / Negative Space
+```
+[Single subject] positioned [placement], [vast background description],
+generous negative space [purpose], [subtle lighting direction], [aspect ratio].
+```
+Example: "A single red maple leaf positioned in the bottom-right third, vast off-white linen-textured background, generous negative space ideal for text overlay, soft diffused light from top-left casting a gentle shadow, square format."
+
+## How to Handle Image Editing
+
+**The cardinal rule of editing: LESS IS MORE.** Verbose edit prompts cause the model to "re-imagine" the entire image, producing an artificial, over-processed look. Keep edit prompts short, direct, and focused on exactly what changes. Let the model figure out how to integrate the change naturally — it's very good at this when you don't over-constrain it.
+
+### Adding / Removing Elements
+One sentence describing the change. Don't describe how to integrate it — the model handles that.
+```
+"Add a knitted wizard hat to the cat."
+```
+
+### Background Replacement
+State the new background simply. Don't over-describe — the model matches lighting automatically.
+```
+"Replace the background with a tropical beach at sunset."
+```
+Avoid: "Replace the background with a beautiful tropical beach with golden sand, palm trees swaying, turquoise waves, warm orange and pink sunset colors reflecting on the water, ensuring the subject's lighting matches the warm sunset glow..." — this level of detail makes the result look MORE artificial, not less.
+
+### Inpainting (Targeted Changes)
+Name what changes and state what stays in one line.
+```
+"Change the blue sofa to a brown leather chesterfield. Keep everything else."
+```
+
+### Style Transfer
+Name the target style. Keep it simple.
+```
+"Transform this into Van Gogh's Starry Night style."
+```
+
+### Multi-Image Composition
+Use `referenceImages` parameter to supply source images.
+```
+"Put the woman from the second image in the blue dress from the first image."
+```
+
+### Iterative Refinement
+Use `continue_editing` for small adjustments. One change at a time:
+- "Make the lighting warmer"
+- "More contrast in the shadows"
+- "Zoom out a bit"
+- "More serious expression"
+
+## Critical Best Practices
+
+1. **Be hyper-specific** — Generic descriptions produce generic images. Replace "fantasy armor" with "ornate elven plate armor, etched with silver leaf patterns, high collar, falcon-wing pauldrons."
+
+2. **Frame positively** — The model handles positive instructions better than negations. Say "empty deserted street with no traffic, completely still" instead of "street without cars." Describe what IS there, not what isn't.
+
+3. **Use photography language** — Camera terms give precise control: "85mm portrait lens", "wide-angle", "macro", "Dutch angle", "low-angle looking up", "bird's eye view."
+
+4. **Specify lighting explicitly** — Lighting is the single biggest quality lever. Always include it. "Golden hour", "overcast diffused", "dramatic Rembrandt", "neon rim-lit", "three-point studio."
+
+5. **Include context and intent** — "Logo for a high-end minimalist skincare brand" produces better results than just "make a logo." The model uses context to make style decisions.
+
+6. **One concept per generation** — Complex multi-scene compositions work less reliably. Break them into separate generations and compose with editing tools.
+
+7. **Character consistency** — If features drift after multiple edits, restart the conversation with a detailed character description upfront.
+
+8. **Aspect ratio matters** — Choose deliberately based on final use. The model preserves input image ratio during editing. Be explicit if you need a specific ratio.
+
+## Workflow
+
+When the user asks for an image:
+
+1. **Understand intent** — What is this image for? What style/mood? What will it be used for?
+2. **Ask clarifying questions if needed** — Use AskUserQuestion for ambiguous requests. Ask about style, mood, aspect ratio, specific elements.
+3. **Build the prompt** — Apply the templates above. Be detailed and narrative.
+4. **Choose the right tool** — `generate_image` for new, `edit_image` for modifying existing, `continue_editing` for iterating.
+5. **Set `outputPath`** — If the user specifies where to save, use absolute paths. Otherwise let the MCP use its default directory.
+6. **Execute and review** — After generation, read the image file to show the user the result.
+7. **Iterate** — If the user wants changes, use `continue_editing` with targeted adjustment prompts.
+
+## Design System Integration
+
+When generating images for a morph-spec project:
+
+1. **Read design tokens first:**
+   ```
+   Read: .morph/context/design-system.md
+   ```
+   Extract: background color (`--color-background`), primary (`--color-primary`), accent (`--color-accent`), font pair, aesthetic direction.
+
+2. **Inject tokens into prompts:**
+   Replace generic color references with actual project values:
+   - "dark background" → "dark charcoal background ({--color-background value})"
+   - "accent colors" → "{--color-primary value} and {--color-accent value} accents"
+   - "premium aesthetic" → "{aesthetic direction from design-system.md}"
+
+3. **If `globals.css` exists**, read it for additional token values:
+   ```
+   Grep: "--color-" in src/app/globals.css (or similar)
+   ```
+
+## Assets.md Integration
+
+When invoked from the implement phase with an assets.md reference:
+
+1. **Read the assets spec:**
+   ```
+   Read: .morph/features/{feature}/1-ui/assets.md
+   ```
+
+2. **For each IMG-NNN entry assigned to the current task:**
+   - Use the `Prompt` field as the base prompt
+   - Use the `Aspect Ratio` field for the aspectRatio parameter
+   - Use the `Output Path` field for the outputPath parameter
+   - Apply design system token injection (section above)
+
+3. **Generate and verify:**
+   ```
+   mcp__gemini-image-mcp__generate_image({
+     prompt: "{enhanced prompt with design tokens}",
+     aspectRatio: "{from assets.md}",
+     outputPath: "{from assets.md}"
+   })
+   ```
+   Read the generated image to verify quality. If it needs refinement, use `continue_editing`.
+
+## Output Path Conventions
+
+- **morph-spec projects:** `public/images/{feature}/{purpose}.png`
+- **Custom path:** Use `outputPath` parameter with absolute path
+- **Default:** saves to `generated-images/` in the MCP project root
+- Supported formats: PNG (most common), JPG, WEBP, GIF, BMP
+
+## Model Options
+
+The default model is `gemini-2.5-flash-image`. Alternative models can be specified via the `model` parameter:
+- `gemini-2.5-flash-image` — Default, fastest, great quality
+- `gemini-3.1-flash-image-preview` — Newer, supports up to 14 reference images
+- `gemini-3-pro-image-preview` — Higher quality, slower
+
+## Common Pitfalls to Avoid
+
+- **Keyword spam** — "beautiful, stunning, amazing, 4k, ultra HD, masterpiece" adds noise, not quality
+- **JSON prompts** — The model does not support structured output; natural language only
+- **Negative prompts with "no/don't"** — Frame what you want, not what you don't want
+- **Vague lighting** — "good lighting" means nothing; specify the type
+- **Missing context** — Always explain what the image is for (social media, website, print, etc.)
+- **Too many subjects** — Keep compositions focused; split complex scenes into steps
+- **Forgetting aspect ratio** — Always set it deliberately based on the intended use

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

@@ -64,6 +64,25 @@ Fix all CRITICALs before continuing. To review the full checklist:
 - .NET: `/morph-code-review`
 - Next.js: `/morph-code-review-nextjs`
 
+### Asset Completeness Check (if assets.md exists):
+
+If `.morph/features/{feature}/1-ui/assets.md` exists:
+
+1. **Read assets.md** and list all IMG-NNN entries with their `Output Path` values.
+2. **Check each output path exists:**
+   ```bash
+   test -f {outputPath} && echo "✓ {IMG-ID}" || echo "✗ {IMG-ID} MISSING: {outputPath}"
+   ```
+3. **Check for broken Image references:**
+   ```bash
+   grep -rn 'src="/images/' src/ --include="*.tsx" --include="*.jsx" | while read line; do
+     path=$(echo "$line" | grep -oP 'src="(/images/[^"]+)"' | sed 's/src="//;s/"//');
+     test -f "public$path" || echo "⚠️  Broken ref: $line → public$path not found";
+   done
+   ```
+
+**⚠️  ADVISORY** — missing assets produce warnings, not blocks. Some images may be intentionally deferred or optional.
+
 ---
 
 ## Step 3 — Test Suite

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.21.0"
+cliVersion: "4.22.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.21.0"
+cliVersion: "4.22.0"
 ---
 
 # MORPH Design — Phase 2
@@ -429,15 +429,15 @@ morph-spec state set $ARGUMENTS costs.estimated {X.XX}
 
 ---
 
-<!-- morph-outputs:design -->
-| Output | Caminho |
-|--------|---------|
-| `schemaAnalysis` | `.morph/features/{feature}/2-design/schema-analysis.md` |
-| `spec` | `.morph/features/{feature}/2-design/spec.md` |
-| `contracts` | `.morph/features/{feature}/2-design/contracts.cs` |
-| `contractsTs` | `.morph/features/{feature}/2-design/contracts.ts` |
-| `contractsVsa` | `.morph/features/{feature}/2-design/contracts-vsa.cs` |
-| `decisions` | `.morph/features/{feature}/2-design/decisions.md` |
+<!-- morph-outputs:design -->
+| Output | Caminho |
+|--------|---------|
+| `schemaAnalysis` | `.morph/features/{feature}/2-design/schema-analysis.md` |
+| `spec` | `.morph/features/{feature}/2-design/spec.md` |
+| `contracts` | `.morph/features/{feature}/2-design/contracts.cs` |
+| `contractsTs` | `.morph/features/{feature}/2-design/contracts.ts` |
+| `contractsVsa` | `.morph/features/{feature}/2-design/contracts-vsa.cs` |
+| `decisions` | `.morph/features/{feature}/2-design/decisions.md` |
 <!-- /morph-outputs -->
 
 ## Relevant Standards