@polymorphism-tech/morph-spec 4.10.8 → 4.10.10

package/framework/skills/level-1-workflows/morph-phase-implement/.morph/logs/activity.json

@@ -0,0 +1,38 @@
+{
+  "sessionId": "",
+  "feature": "",
+  "phase": "",
+  "hooks": [
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:06:20"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:07"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:15"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:15"
+    },
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:12:40"
+    }
+  ],
+  "skills": []
+}

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.10.8"
+cliVersion: "4.10.10"
 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 4 (Plan). Generates a detailed implementation plan
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.8"
+cliVersion: "4.10.10"
 ---
 
 # MORPH Plan — Phase 4

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1 (Setup). Reads project context, detects tech sta
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.8"
+cliVersion: "4.10.10"
 ---
 
 # MORPH Setup — Phase 1

package/framework/skills/level-1-workflows/morph-phase-tasks/.morph/logs/activity.json

@@ -0,0 +1,14 @@
+{
+  "sessionId": "",
+  "feature": "",
+  "phase": "",
+  "hooks": [
+    {
+      "name": "set-terminal-title",
+      "event": "UserPromptSubmit",
+      "result": "failed",
+      "ts": "16:38:44"
+    }
+  ],
+  "skills": []
+}

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.10.8"
+cliVersion: "4.10.10"
 ---
 
 # MORPH Tasks — Phase 4

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

@@ -4,7 +4,7 @@ description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md,
 argument-hint: "[feature-name]"
 user-invocable: false
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
-cliVersion: "4.10.8"
+cliVersion: "4.10.10"
 ---
 
 # MORPH UI/UX Design - Phase 1.5
@@ -70,31 +70,64 @@ Check the `"phase"` field in the output:
 
 ---
 
-### Step 0.5: Check Design System Exists
+### Step 0.5: Check Design System
 
-**CRITICAL:** Before starting UI/UX phase, check if a design system exists:
+**This step is MANDATORY and must always run before Step 1.**
+
+#### Step 0.5.1 — Scan frontend for CSS tokens (ALWAYS)
+
+Search for existing CSS custom properties in the project's frontend directories.
+
+Glob these patterns (exclude `node_modules/`, `.next/`, `dist/`, `build/`):
+```
+wwwroot/**/*.css
+wwwroot/**/*.scss
+styles/**/*.css
+src/styles/**/*.css
+src/**/*.css
+src/**/*.scss
+src/**/*.module.css
+public/**/*.css
+```
+
+For each CSS/SCSS file found, Grep for `:root {` blocks containing `--` custom properties.
+
+Classify found tokens:
+- **Colors**: lines with `--color-*`, or any `--*` containing `#hex` / `rgb(...)`
+- **Fonts**: `--font-*` or `font-family:` declarations
+- **Spacing**: `--space-*`, `--gap-*`, `--size-*` with rem/px values
+
+Track: `cssTokensFound` (bool), token counts by category, source file list.
+
+#### Step 0.5.2 — Check if design-system.md exists
 
 ```
 Read: .morph/context/design-system.md
 ```
 
-If the file doesn't exist (design system not found):
+Track: `dsExists` (bool).
+
+#### Step 0.5.3 — Decision tree (4 cases)
+
+| Case | Condition | Action |
+|------|-----------|--------|
+| **A** | `dsExists` AND `cssTokensFound` | Cross-check DS vs scanned tokens. If >2 colors diverge, flag misalignment and ask user if they want to update DS with `AskUserQuestion`. Proceed to Step 1. |
+| **B** | `dsExists` AND NOT `cssTokensFound` | Print: `✓ Design system found (no CSS tokens to cross-check)`. Proceed to Step 1. |
+| **C** | NOT `dsExists` AND `cssTokensFound` | Auto-generate `.morph/context/design-system.md` from scanned tokens (see Case C detail below). Proceed to Step 1. |
+| **D** | NOT `dsExists` AND NOT `cssTokensFound` | Greenfield project. Ask user for aesthetic direction + brand color using `AskUserQuestion` (same options as morph-init). Scaffold from template. Proceed to Step 1. |
 
-1. **Option A - Automatic scaffold:**
-   - The system will automatically create a design system when advancing to implementation
-   - You can generate manually now: `npx morph-spec generate design-system`
+**Case C — auto-generate from scanned tokens:**
 
-2. **Option B - Create manually:**
-   - Create `.morph/context/design-system.md` (project-level, shared)
-   - Or `.morph/features/$ARGUMENTS/2-ui/design-system.md` (feature-specific)
+Create `.morph/context/design-system.md` with these sections populated from scan results:
+- `## Color Tokens` → `:root { }` block with all found color variables (preserve exact variable names)
+- `## Typography` → found font-family values (map by variable name heuristic: `--font-display` vs `--font-body`)
+- `## Spacing Tokens` → found spacing variables
+- `## Aesthetic Direction` → `#TODO` (requires user judgment, fill in manually)
+- `## Changelog` → `- [today's date] [morph-phase-uiux] Auto-generated from CSS scan ([N] tokens from [files])`
 
-3. **Option C - Scan existing CSS:**
-   - If the project already has CSS with variables: `npx morph-spec generate design-system --scan`
+Print: `✓ Design system generated from [N] tokens — .morph/context/design-system.md`
 
-**IMPORTANT:**
-- Design system is **mandatory** for UI features
-- Automatic gate will block implementation (Phase 5) if design system doesn't exist
-- Better to create now to ensure visual consistency
+> **Design system is mandatory** for UI features. The implementation gate (Phase 5) will block if no design system exists.
 
 ### Step 1: Detect If Phase Is Needed
 

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.10.8"
+cliVersion: "4.10.10"
 ---
 
 # Scope Escalation Workflow