maestro-flow 0.3.48 → 0.4.1

package/.codex/skills/maestro-ui-craft/SKILL.md

@@ -1,341 +0,0 @@
----
-name: maestro-ui-craft
-description: Chain maestro-impeccable commands with intelligent routing and quality gate loops for automated UI production
-argument-hint: "<intent|target> [--chain build|improve|enhance|harden|live] [--enhance <cmd>] [--threshold <score>] [--max-loops <n>] [-y] [-c]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, request_user_input
----
-<purpose>
-Orchestrate maestro-impeccable skill commands via intelligent intent routing + quality gate auto-iteration.
-Chain: Build → Evaluate → Auto-Refine → Re-evaluate → Verify.
-
-Core innovation: critique/audit scores drive automatic command selection and iteration loops.
-maestro-impeccable has 23 commands across 6 categories -- this command chains them into automated pipelines
-with quality gates that loop until design quality meets the threshold.
-
-Prerequisite: maestro-impeccable skill available (auto-discovered by harness).
-
-Session: `.workflow/.maestro/ui-craft-{YYYYMMDD-HHmmss}/status.json`
-</purpose>
-
-<invariants>
-1. **Session before execution** -- status.json created before any chain step runs
-2. **All steps via Skill** -- every impeccable command dispatched through `$maestro-impeccable`
-3. **Gate scores drive loops** -- refine loop auto-selects commands from P0/P1 findings, never from hardcoded lists
-4. **Interactive gates respected** -- teach, shape, craft retain their user gates; never suppress
-</invariants>
-
-<context>
-$ARGUMENTS -- intent description or target path, with optional flags.
-
-**Keywords:** `continue`/`next` → resume previous session
-
-**Usage:**
-
-```bash
-$maestro-ui-craft "create a landing page"
-$maestro-ui-craft "improve the dashboard" --chain improve
-$maestro-ui-craft "add animations" --chain enhance --enhance animate
-$maestro-ui-craft "production ready" --chain harden
-$maestro-ui-craft -c                               # resume previous session
-$maestro-ui-craft -y "create pricing page --chain build"
-```
-
-**Flags:**
-- `--chain <type>` -- Force chain type: build, improve, enhance, harden, live
-- `--enhance <cmd>` -- Specific enhance command (animate|colorize|typeset|layout|delight|overdrive|bolder)
-- `--threshold <score>` -- Critique pass threshold (default: 26/40). Audit threshold auto-computed as threshold*0.5
-- `--max-loops <n>` -- Maximum quality gate iterations (default: 3)
-- `-c` / `--continue` -- Resume previous ui-craft session
-- `-y` -- Auto mode: auto-select at ambiguous routing, skip confirmations where maestro-impeccable allows
-</context>
-
-<chains>
-
-### Chain Definitions
-
-| Chain | Sequence | Gate Condition |
-|-------|----------|----------------|
-| **build** | teach? → shape → craft → **critique** → [refine loop] → audit → polish | critique >= threshold AND P0 == 0 |
-| **improve** | **critique** → [refine loop] → polish → audit | critique >= threshold AND P0 == 0 |
-| **enhance** | {cmd} → **critique** → polish (if needed) | critique >= threshold |
-| **harden** | harden → **audit** → polish | audit >= threshold*0.5 |
-| **live** | live | -- (interactive, no gate) |
-
-- `teach?` -- conditional: only if PRODUCT.md missing/placeholder
-- `[refine loop]` -- quality gate loop: extract suggested commands from critique → execute → re-critique
-
-### Intent → Chain Routing
-
-| Intent Pattern | Chain |
-|---------------|-------|
-| create, build, new, landing, feature, page | build |
-| improve, fix, iterate, better, optimize | improve |
-| animate, color, type, bold, delight, enhance | enhance |
-| production, harden, ship, edge case, i18n | harden |
-| live, browser, variant | live |
-
-Explicit `--chain` overrides routing. Ambiguous + no `-y` → `request_user_input`.
-
-</chains>
-
-<state_machine>
-
-<states>
-S_PARSE      -- parse args, intent classification, chain selection       PERSIST: --
-S_RESUME     -- scan existing ui-craft sessions, resume execution         PERSIST: --
-S_SETUP      -- load context, check PRODUCT.md                           PERSIST: --
-S_CREATE     -- create session + status.json                              PERSIST: session (full)
-S_CHAIN      -- execute chain steps in sequence                           PERSIST: step progress, executed commands
-S_GATE       -- quality gate: parse scores, decide                        PERSIST: scores, loop count
-S_REFINE     -- execute auto-selected refine commands                     PERSIST: refine commands, loop state
-S_REPORT     -- final report + trend                                      PERSIST: final scores, status
-</states>
-
-<transitions>
-
-S_PARSE:
-  → S_RESUME     WHEN: -c / --continue flag OR keyword "continue"/"next"
-  → S_SETUP      WHEN: chain selected (explicit or routed)
-  → S_PARSE      WHEN: ambiguous AND not -y          DO: request_user_input
-  → END          WHEN: no intent AND no target → E002
-
-S_RESUME:
-  → S_CHAIN      WHEN: session found                  DO: A_LOCATE_SESSION
-  → END          WHEN: no session found → E005
-
-S_SETUP:
-  → S_CREATE     DO: A_LOAD_CONTEXT
-
-S_CREATE:
-  → S_CHAIN      DO: A_CREATE_SESSION
-
-S_CHAIN:
-  → S_GATE       WHEN: current step is gate command (critique/audit)
-  → S_CHAIN      WHEN: step is normal command → execute → advance
-  → S_REPORT     WHEN: all steps complete
-
-S_GATE:
-  → S_CHAIN      WHEN: PASS (score >= threshold AND P0 == 0) → advance
-  → S_REFINE     WHEN: FAIL (score < threshold OR P0 > 0)
-  → S_CHAIN      WHEN: max loops exceeded → W002 → force advance
-
-S_REFINE:
-  → S_GATE       DO: execute auto-selected commands → re-run gate command
-                  GUARD: loop_count < max_loops
-
-S_REPORT:
-  → END          DO: A_FINAL_REPORT
-
-</transitions>
-
-<actions>
-
-### A_LOCATE_SESSION
-
-1. Scan `.workflow/.maestro/ui-craft-*/status.json`, filter `status == "running"`, sort DESC
-2. Take most recent; load into context as current session
-3. Resume from `current_step` position
-
-### A_LOAD_CONTEXT
-
-1. Trigger impeccable context loading: `$maestro-impeccable teach`
-   - Impeccable's own setup auto-discovers and loads PRODUCT.md / DESIGN.md from `.workflow/impeccable/`
-   - If PRODUCT.md missing/placeholder, impeccable teach handles the interview
-2. If teach was not in the chain but PRODUCT.md is missing:
-   - Prepend `teach` to chain start
-   - Announce: W001
-3. Context is now loaded for subsequent commands
-
-### A_CREATE_SESSION
-
-1. Read `.workflow/state.json` for project context (phase, milestone)
-2. Create `.workflow/.maestro/ui-craft-{YYYYMMDD-HHmmss}/status.json`:
-   ```json
-   { "session_id": "ui-craft-{ts}", "source": "ui-craft", "intent": "...",
-     "chain_type": "build|improve|enhance|harden|live", "target": "...",
-     "auto_mode": false, "threshold": 26, "max_loops": 3,
-     "steps": [{ "index": 0, "command": "shape", "status": "pending" }],
-     "gate_history": [], "loop_count": 0,
-     "current_step": 0, "status": "running",
-     "created_at": "ISO-8601", "updated_at": "ISO-8601" }
-   ```
-3. Write status.json before executing any step
-
-### A_FINAL_REPORT
-
-1. Read critique trend if available (impeccable's critique persists snapshots automatically)
-2. Update status.json with `status: "completed"` and final scores
-3. Present summary table with scores, iterations, commands executed
-
-</actions>
-
-</state_machine>
-
-<execution>
-
-## 1. Parse & Route
-
-1. If `-c` / `--continue` or keyword "continue"/"next" → S_RESUME
-2. If `--chain` present → use directly
-3. Otherwise → match $ARGUMENTS against intent patterns
-4. If `--enhance` present → chain = enhance, cmd = --enhance value
-5. For enhance chain without `--enhance` → infer from intent
-6. Ambiguous + no `-y` → `request_user_input`:
-   ```json
-   { "questions": [{ "id": "chain_select", "header": "Chain", "question": "Which workflow?", "options": [
-     { "label": "Build (Recommended)", "description": "New UI from scratch: shape → craft → critique → refine → audit" },
-     { "label": "Improve", "description": "Iterate existing: critique → refine → polish → audit" },
-     { "label": "Enhance", "description": "Targeted improvement: specific command → critique → polish" },
-     { "label": "Harden", "description": "Production-ready: harden → audit → polish" }
-   ]}] }
-   ```
-
-## 2. Setup Context
-
-1. If chain starts with `teach` → execute it first, maestro-impeccable handles context loading internally
-2. Otherwise → invoke `$maestro-impeccable` with no args to trigger setup (context + register)
-3. If maestro-impeccable reports PRODUCT.md missing → prepend teach, execute, then resume
-
-## 3. Create Session
-
-Write `.workflow/.maestro/ui-craft-{ts}/status.json` with chain steps before any execution.
-
-## 4. Execute Chain
-
-For each step in chain, sequentially:
-
-```
-Step {n}/{total}: $maestro-impeccable {command} {target}
-```
-
-After each step: update status.json `current_step` and step `status`.
-
-**Rules:**
-- `teach`, `shape`, `craft` are interactive -- do NOT suppress their user gates
-- After `teach` completes → re-run context loader for fresh PRODUCT.md
-- After `craft` completes → the build exists, ready for evaluation
-- Gate steps (critique/audit) → transition to quality gate logic
-
-## 5. Quality Gate
-
-When chain reaches a gate step (critique or audit):
-
-### 5a. Execute Gate Command
-
-```
-$maestro-impeccable critique {target}
-```
-or
-```
-$maestro-impeccable audit {target}
-```
-
-### 5b. Parse Score
-
-From critique output, extract:
-- **score**: Nielsen's total (N/40) -- from "**Total** | | **N/40**" row
-- **P0_count**: count of `[P0]` tagged findings
-- **P1_count**: count of `[P1]` tagged findings
-- **suggested_commands**: list of "$maestro-impeccable <cmd>" from "Suggested command" fields
-
-From audit output, extract:
-- **score**: dimension total (N/20) -- from "**Total** | | **N/20**" row
-- **P0_count**: count of `[P0]` findings
-
-### 5c. Evaluate
-
-```
-critique_pass = (score >= threshold) AND (P0_count == 0)
-audit_pass    = (score >= threshold * 0.5) AND (P0_count == 0)
-```
-
-### 5d. On PASS
-
-→ advance to next chain step
-
-### 5e. On FAIL
-
-1. Collect suggested commands from P0/P1 findings
-2. If no suggestions found → use fallback mapping (see quality_gate_routing)
-3. De-duplicate, cap at 3 commands per iteration
-4. Sort: P0-suggested first
-5. Execute each: `$maestro-impeccable {cmd} {target}`
-6. Re-run gate command (critique/audit)
-7. Increment loop_count
-8. Append to status.json `gate_history`
-
-### 5f. On Max Loops Exceeded
-
-→ force advance to next chain step with warning
-
-## 6. Final Report
-
-Present summary: chain type, critique score with trend, audit score, loop count, commands executed, pass/partial status.
-
-Update status.json: `status: "completed"`, `final_scores`, `completed_at`.
-
-If issues remain → suggest: "Run `$maestro-ui-craft --chain improve {target}` to continue iteration."
-
-</execution>
-
-<quality_gate_routing>
-
-### Finding → Command Fallback Mapping
-
-When critique/audit findings lack explicit "Suggested command", map by category:
-
-| Finding Category | Command |
-|-----------------|---------|
-| Visual hierarchy, layout, spacing, alignment | layout |
-| Color, contrast, palette, monochromatic | colorize |
-| Typography, font, readability, hierarchy | typeset |
-| Animation, motion, transitions, micro-interaction | animate |
-| Copy, labels, error messages, UX writing | clarify |
-| Responsive, mobile, breakpoints, touch targets | adapt |
-| Performance, loading, speed, bundle, jank | optimize |
-| Complexity, overload, clutter, cognitive load | distill |
-| Bland, safe, generic, lacks personality | bolder |
-| Aggressive, overwhelming, loud, overstimulating | quieter |
-| Onboarding, empty state, first-run, activation | onboard |
-| Edge cases, i18n, error handling, overflow | harden |
-| Personality, memorability, joy, delight | delight |
-
-### Commands Never Auto-Selected
-
-| Command | Reason |
-|---------|--------|
-| teach | Project setup (run in S_SETUP only) |
-| shape | Requires user interview |
-| craft | Full build with multiple gates |
-| live | Interactive browser mode |
-| document | Generates DESIGN.md (setup) |
-| extract | Design system extraction (setup) |
-| overdrive | Requires explicit user vision |
-| critique | Gate command, not a fix |
-| audit | Gate command, not a fix |
-
-</quality_gate_routing>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | maestro-impeccable skill not found |
-| E002 | error | No intent or target specified |
-| E003 | error | Invalid --chain type |
-| E004 | error | Invalid --enhance command |
-| E005 | error | Resume session not found |
-| W001 | warning | PRODUCT.md missing, prepending teach to chain |
-| W002 | warning | Max quality gate loops exceeded, forcing continue |
-| W003 | warning | Could not parse score from critique/audit output |
-</error_codes>
-
-<success_criteria>
-- [ ] Intent classified and chain type selected
-- [ ] Context loaded (PRODUCT.md present or taught)
-- [ ] Session dir created with status.json before execution
-- [ ] All chain steps executed via $maestro-impeccable
-- [ ] Quality gate evaluated with parsed scores
-- [ ] Refine loop executed when gate failed (if applicable)
-- [ ] Gate history and scores persisted to status.json
-- [ ] Final report with scores and trend presented
-</success_criteria>

package/.codex/skills/maestro-ui-design/SKILL.md

@@ -1,242 +0,0 @@
----
-name: maestro-ui-design
-description: Generate UI design prototypes, select and solidify as code
-argument-hint: "<phase|topic> [--styles N] [--stack <stack>] [--targets <pages>] [--layouts N] [--refine] [--persist] [--full] [-y] [--style-skill PKG]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, request_user_input
----
-
-<purpose>
-Two workflow paths, auto-selected by skill availability:
-1. **Primary (ui-ux-pro-max)**: Lightweight -- delegates design generation, owns selection and solidification
-2. **Fallback (self-contained)**: Full 4-layer pipeline (style -> animation -> layout -> assembly)
-
-Both produce the same output contract for downstream plan/execute consumption.
-</purpose>
-
-<deferred_reading>
-- [ui-style.md](~/.maestro/workflows/ui-style.md) — read when SKILL_PATH found (primary path)
-- [ui-design.md](~/.maestro/workflows/ui-design.md) — read when SKILL_PATH empty or --full (fallback path)
-- [index.json](~/.maestro/templates/index.json) — read when updating phase metadata
-- [scratch-index.json](~/.maestro/templates/scratch-index.json) — read when operating in scratch mode
-</deferred_reading>
-
-<context>
-$ARGUMENTS -- phase number or topic text, plus optional flags.
-
-**Usage**:
-
-```bash
-$maestro-ui-design "3"                          # phase mode
-$maestro-ui-design "landing page for SaaS"      # scratch mode
-$maestro-ui-design -y "3 --styles 5"            # auto mode, 5 variants
-$maestro-ui-design "3 --style-skill PKG --stack react"
-```
-
-**Flags**:
-- `[topic]`: Phase number or topic text (scratch mode)
-- `-y, --yes`: Auto mode -- skip all interactive selection
-- `--style-skill PKG`: Override ui-ux-pro-max skill path
-- `--styles N`: Number of style variants (default: 3, range: 2-5)
-- `--stack <stack>`: Tech stack for implementation guidelines (default: html-tailwind)
-- `--targets <pages>`: Comma-separated page/component targets
-- `--layouts N`: Number of layout templates per target (default: 2, range: 1-4, fallback path only)
-- `--refine`: Iterate on existing design-ref/ — load current tokens, present refinement options
-- `--persist`: Save design system with hierarchical page overrides
-- `--full`: Force full 4-layer self-contained pipeline
-
-When `--yes` or `-y`: Skip interactive selection, auto-pick top-scored variant, skip brief review.
-
-**Output**: `{scratch_dir}/design-ref/` with MASTER.md, design-tokens.json, animation-tokens.json, selection.json, prototypes/
-</context>
-
-<invariants>
-1. **Output contract is fixed** -- both paths produce MASTER.md + design-tokens.json + animation-tokens.json + selection.json
-2. **Colors in OKLCH** format in design-tokens.json
-3. **WCAG AA** contrast: 4.5:1 text, 3:1 UI elements
-4. **No lorem ipsum** -- use contextual placeholder content
-5. **Agent calls use `run_in_background: false`** for synchronous execution
-6. **Variant contrast** -- each variant must represent a distinctly different design direction
-</invariants>
-
-<execution>
-
-### Step 0: Load UI Specs
-
-Load project UI conventions before generating designs:
-
-```bash
-maestro spec load --category ui
-```
-
-If specs not initialized, continue without — the workflow still produces valid output.
-
-### Step 1: Parse Input and Resolve Target
-
-1. Parse flags from `$ARGUMENTS`: `--styles N`, `--stack`, `--targets`, `--persist`, `--full`, `-y`
-2. **Phase mode** (number): resolve via state.json artifact registry to `.workflow/scratch/{YYYYMMDD}-{type}-{slug}/`
-3. **Scratch mode** (text): create `.workflow/scratch/ui-design-{slug}-{date}/` with minimal index.json
-4. Create output directories: `${PHASE_DIR}/design-ref/prototypes/` and `${PHASE_DIR}/design-ref/layout-templates/`
-
-### Step 2: Detect Skill Availability
-
-Search for `ui-ux-pro-max` script at `skills/ui-ux-pro-max/scripts/search.py` or `$HOME/.claude/plugins/cache/ui-ux-pro-max-skill/ui-ux-pro-max/*/scripts/search.py`.
-
-- If `--style-skill PKG` provided: override detected path
-- If `--full`: force self-contained pipeline regardless of skill availability
-
-### Step 2.5: Refine Mode Branch (if `--refine`)
-
-If `--refine` is set:
-1. Verify `design-ref/` exists in target directory (error E004 if missing)
-2. Read current `design-ref/MASTER.md`, `design-tokens.json`, `animation-tokens.json`
-3. Display current design summary (palette, typography, key components)
-4. `request_user_input`:
-   ```json
-   { "questions": [{ "id": "refine_scope", "header": "Refine", "question": "Which aspects to refine?", "options": [
-     { "label": "Colors & Typography (Recommended)", "description": "Adjust palette, font pairings, and scale." },
-     { "label": "Layout & Spacing", "description": "Adjust grid, spacing tokens, and breakpoints." },
-     { "label": "Full Redesign", "description": "Regenerate all variants from scratch, keeping requirements." }
-   ]}] }
-   ```
-5. Apply refinement: directly edit token files and MASTER.md based on user feedback
-6. Update `selection.json` with refinement metadata (iteration count, changes)
-7. Skip to Step 8 (report)
-
-### Step 3: Gather Requirements Context
-
-1. Read phase context (context.md, brainstorm results, spec references)
-2. Synthesize design brief: product_type, industry, style_keywords, audience
-3. Infer targets from phase goal if not specified (fallback: "home")
-4. **Interactive brief review** (skip if `-y`):
-   - Present synthesized brief (product_type, industry, style_keywords, audience, targets)
-   - `request_user_input`:
-     ```json
-     { "questions": [{ "id": "brief_review", "header": "Brief", "question": "Design brief ready. Proceed with this direction?", "options": [
-       { "label": "Proceed (Recommended)", "description": "Generate variants with current brief." },
-       { "label": "Adjust", "description": "Modify keywords, audience, or targets before generating." }
-     ]}] }
-     ```
-   - **Adjust** → user provides changes, update brief, then proceed
-
-### Step 4: Generate Style Variants
-
-**If SKILL_PATH found (primary path):**
-
-Generate `styleCount` keyword sets with intentional contrast, then call ui-ux-pro-max for each:
-```bash
-python3 "${SKILL_PATH}" "${variant_keywords}" --design-system -p "${project_name}" -f markdown
-```
-
-**If SKILL_PATH empty or --full (fallback path):**
-
-Spawn ui-design-agent to generate variants using 6D attribute space for maximum contrast:
-
-| Dimension | Range | Description |
-|-----------|-------|-------------|
-| mood | formal ↔ playful | Overall emotional tone |
-| density | spacious ↔ dense | Content density and whitespace |
-| contrast | subtle ↔ bold | Visual weight and contrast ratios |
-| rounding | sharp ↔ rounded | Border radius scale (0-24px) |
-| motion | minimal ↔ expressive | Animation intensity and frequency |
-| color-temp | cool ↔ warm | Color temperature bias |
-
-Each variant occupies a distinct region in 6D space — no two variants within 0.3 Euclidean distance.
-
-### Step 5: Present and Select
-
-Present all variants with key attributes (colors, typography, effects, 6D coordinates for fallback path).
-
-**Interactive** (default): `request_user_input` with variants as options:
-```json
-{ "questions": [{ "id": "variant_select", "header": "Style", "question": "Select preferred design variant:", "options": [
-  { "label": "Variant 1 (Recommended)", "description": "Brief: palette + mood + key trait." },
-  { "label": "Variant 2", "description": "Brief: palette + mood + key trait." },
-  { "label": "Variant 3", "description": "Brief: palette + mood + key trait." }
-]}] }
-```
-Options built dynamically from generated variants. User may respond with "Other" to request regeneration with different keywords.
-
-**Auto** (`-y`): select variant 1
-
-### Step 6: Solidify Selected Design
-
-Spawn Agent to extract structured tokens from selected variant: `design-tokens.json` (OKLCH colors, component_styles, typography.combinations, spacing, border_radius, shadows, breakpoints) and `animation-tokens.json` (duration, easing, transitions, keyframes, interactions, reduced_motion).
-
-Write output artifacts:
-- `design-ref/MASTER.md` -- complete design system specification
-- `design-ref/design-tokens.json` -- production-ready tokens
-- `design-ref/animation-tokens.json` -- animation system
-- `design-ref/selection.json` -- selection metadata + rationale
-
-### Step 6.5: Layout Template Generation (fallback path only)
-
-For each target, generate `layoutCount` layout templates:
-- Each template defines `dom_structure` (semantic HTML skeleton) + `css_layout_rules` (grid/flex layout)
-- Write to `design-ref/layout-templates/{target}-layout-{N}.json`
-- Templates vary in content organization: e.g., hero-first vs. feature-grid vs. sidebar-nav
-
-### Step 7: Prototype Generation
-
-**Primary path**: For each target, spawn Agent to generate standalone HTML+CSS prototype from design-tokens.json and animation-tokens.json.
-
-**Fallback path**: Assemble prototype matrix: `styles × layouts × targets`. For each combination:
-- Merge selected style tokens + layout template + target content
-- Generate standalone HTML+CSS prototype
-
-Requirements (both paths): realistic content (no lorem ipsum), SVG icons via CDN, responsive at 375/768/1024px, WCAG AA contrast.
-
-**Fallback path only**: Generate `design-ref/compare.html` — interactive matrix viewer showing all prototypes side-by-side with style/layout/target filtering.
-
-### Step 8: Update State and Report
-
-1. Update index.json with `design_ref` status
-2. Display completion report: phase, variant count + selected, stack, targets, artifact paths
-3. **Next-Step Routing** (skip if `-y` — default to Plan):
-   - `request_user_input`:
-     ```json
-     { "questions": [{ "id": "next_step", "header": "Next Step", "question": "Design system complete. What next?", "options": [
-       { "label": "Plan (Recommended)", "description": "Create execution plan with design reference." },
-       { "label": "Refine", "description": "Iterate on selected design with adjustments." },
-       { "label": "Analyze", "description": "Evaluate feasibility before planning." }
-     ]}] }
-     ```
-     - **Plan** → invoke `maestro-plan {phase}`
-     - **Refine** → invoke `maestro-ui-design {phase} --refine`
-     - **Analyze** → invoke `maestro-analyze {phase}`
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Phase or topic argument required | Prompt user |
-| E002 | error | Phase directory not found | Check phase number |
-| E003 | error | Python not available for ui-ux-pro-max | Fall back to self-contained pipeline |
-| E004 | error | --refine requires existing design-ref/ | Run without --refine first |
-| W001 | warning | Design system returned partial results | Retry with broader keywords |
-| W002 | warning | Prototype rendering failed for one variant | Continue with remaining |
-| W003 | warning | No context.md found, using phase goal only | Continue with phase goal |
-| W004 | warning | ui-ux-pro-max not found, using fallback | Proceed with self-contained pipeline |
-</error_codes>
-
-<success_criteria>
-**Common (both paths)**:
-- [ ] Target resolved (phase or scratch directory)
-- [ ] Requirements context gathered (context.md, brainstorm, or user input)
-- [ ] Style variants generated with intentional contrast
-- [ ] User selected variant (or auto-picked in `-y` mode)
-- [ ] MASTER.md + design-tokens.json + animation-tokens.json + selection.json written
-- [ ] Colors in OKLCH format, WCAG AA contrast met (4.5:1 text, 3:1 UI)
-- [ ] Prototypes generated for all targets with realistic content (no lorem ipsum)
-- [ ] index.json updated with design_ref status
-- [ ] Next-step routing presented (or auto-defaulted with `-y`)
-
-**Primary path (ui-ux-pro-max)**:
-- [ ] ui-ux-pro-max `--design-system` called with product/industry/style keywords
-- [ ] Tokens extracted from ui-ux-pro-max output into structured JSON
-
-**Fallback path (--full or no skill)**:
-- [ ] 6D attribute space used with ≥0.3 Euclidean distance between variants
-- [ ] Layout templates generated per target (`dom_structure` + `css_layout_rules`)
-- [ ] Prototype matrix assembled: selected style × layouts × targets
-- [ ] `compare.html` generated as interactive matrix viewer
-</success_criteria>