@mmerterden/multi-agent-pipeline 8.6.2 → 10.2.0

package/pipeline/skills/figma-ios/figma-component-code-connect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-component-code-connect
-description: "Figma Code Connect mapping publisher for implemented SwiftUI components. Creates + publishes .figma.swift registration for a component already built via Phase 4 codegen. Runs standalone (reads source files + fetches Figma property data) or as a Phase 3.6 continuation. iOS platform peer — Android equivalent lives under figma-android/."
+description: "Figma Code Connect mapping publisher for implemented SwiftUI components. Creates + publishes .figma.swift registration for a component already built via Phase 4 codegen. Runs standalone (reads source files + fetches Figma property data) or as a Phase 3.6 continuation. iOS platform peer  -  Android equivalent lives under figma-android/."
 user-invocable: true
 argument-hint: "<figma-url> | --component <name>"
 language: en
@@ -10,11 +10,11 @@ sourced-from: upstream/figma-to-swift-ui-code-connect
 local-overlay: true
 ---
 
-# figma-component-code-connect — Standalone Code Connect Publish
+# figma-component-code-connect  -  Standalone Code Connect Publish
 
 ## Purpose
 
-Creates and publishes Figma Code Connect mapping for an implemented component. Works independently from `/figma-to-swiftui` — reads source files and fetches Figma property data directly. Can also run as a continuation after Phase 5 when full artifacts exist.
+Creates and publishes Figma Code Connect mapping for an implemented component. Works independently from `/figma-to-swiftui`  -  reads source files and fetches Figma property data directly. Can also run as a continuation after Phase 5 when full artifacts exist.
 
 ## Parameters
 
@@ -64,15 +64,15 @@ If Swift file or FIGMA.md missing → HALT. Component not implemented.
 
 | Condition | Action |
 |-----------|--------|
-| `{ComponentName}.figma.swift` exists | **UPDATE** mode — will overwrite |
+| `{ComponentName}.figma.swift` exists | **UPDATE** mode  -  will overwrite |
 | `{ComponentName}.figma.swift` missing | **CREATE** mode |
 
 ### 4. Detect Path: HOT or COLD
 
 | Condition | Path |
 |-----------|------|
-| `{artifactPath}/pass1/component_properties.json` exists | **HOT** — skip Gate 1, go to Gate 2 |
-| Missing | **COLD** — run Gate 1 |
+| `{artifactPath}/pass1/component_properties.json` exists | **HOT**  -  skip Gate 1, go to Gate 2 |
+| Missing | **COLD**  -  run Gate 1 |
 
 ---
 
@@ -80,7 +80,7 @@ If Swift file or FIGMA.md missing → HALT. Component not implemented.
 
 Two-step process: script (Figma REST API) → AI subagent (deduction).
 
-### Step 1: Script — Fetch Component Properties
+### Step 1: Script  -  Fetch Component Properties
 
 ```bash
 python3 .instructions/figma/figma-to-swiftui/scripts/code-connect-data-gather.py \
@@ -94,7 +94,7 @@ This script:
 2. Extracts `componentPropertyDefinitions` from the node document
 3. Writes `pass1/component_properties.json` in the same format Phase 1 produces
 
-### Step 2: AI Subagent — Boolean Classification
+### Step 2: AI Subagent  -  Boolean Classification
 
 Dispatch a subagent (sonnet, 15 turns) to read source files and produce the variant config analysis:
 
@@ -122,7 +122,7 @@ Dispatch as subagent with:
 - componentName, fileKey, nodeId, artifactPath, componentLocation
 - All standard context variables
 
-The phase file is shared with `/figma-to-swiftui` — same templates, same validation, same publish flow.
+The phase file is shared with `/figma-to-swiftui`  -  same templates, same validation, same publish flow.
 
 ---
 
@@ -146,11 +146,11 @@ Updates `codeConnect.ios = true` in the component registry JSON.
 
 | Gate | Instruction | Model | Max Turns |
 |------|-------------|-------|-----------|
-| 0 | Inline (this file) | — | — |
-| 1 Step 1 | Script (`code-connect-data-gather.py`) | — | — |
+| 0 | Inline (this file) |  -  |  -  |
+| 1 Step 1 | Script (`code-connect-data-gather.py`) |  -  |  -  |
 | 1 Step 2 | AI subagent | sonnet | 15 |
 | 2 | `phases/phase-6-code-connect.md` (shared) | opus | 30 |
-| 3 | Script (`phase6-finalize.py`) | — | — |
+| 3 | Script (`phase6-finalize.py`) |  -  |  -  |
 
 ---
 
@@ -170,9 +170,9 @@ These files are shared with `/figma-to-swiftui` phase 6:
 
 ## Notes
 
-- Standalone entry point — does NOT require `/figma-to-swiftui` to have run
+- Standalone entry point  -  does NOT require `/figma-to-swiftui` to have run
 - When called after Phase 5, detects existing artifacts (HOT path) and skips data gathering
 - The data gather script produces the same artifact structure as Phase 1
-- Phase 6 instruction file doesn't know which skill invoked it — fully modular
-- Handles the `figma.config.json` exclude list for broken components (see phase-6 §GATE 5)
+- Phase 6 instruction file doesn't know which skill invoked it  -  fully modular
+- Handles the `figma.config.json` exclude list for broken components (see phase-6 sectionGATE 5)
 - If component has no Figma property definitions → uses STATIC_VALUES strategy automatically

package/pipeline/skills/figma-ios/figma-component-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-component-implement
-description: "Figma → SwiftUI implementation for a single component. Runs Phases 0–4 of the figma-to-swiftui pipeline (init, data gathering, analysis, code generation) and produces a production-ready SwiftUI view. Excludes testing, Code Connect, and wiki — those are separate standalone skills. iOS platform peer — Android equivalent lives under figma-android/."
+description: "Figma → SwiftUI implementation for a single component. Runs Phases 0-4 of the figma-to-swiftui pipeline (init, data gathering, analysis, code generation) and produces a production-ready SwiftUI view. Excludes testing, Code Connect, and wiki  -  those are separate standalone skills. iOS platform peer  -  Android equivalent lives under figma-android/."
 user-invocable: true
 argument-hint: "<figma-url>"
 language: en
@@ -10,11 +10,11 @@ sourced-from: upstream/figma-to-swift-ui-implement
 local-overlay: true
 ---
 
-# figma-component-implement — Standalone Implementation (Phases 0–4)
+# figma-component-implement  -  Standalone Implementation (Phases 0-4)
 
 ## Purpose
 
-Implements a Figma component as a production-ready SwiftUI view. Runs Phases 0–4 of the figma-to-swiftui pipeline: init, data gathering, analysis, and code generation. Does NOT include testing, Code Connect, or Confluence — those are separate standalone skills.
+Implements a Figma component as a production-ready SwiftUI view. Runs Phases 0-4 of the figma-to-swiftui pipeline: init, data gathering, analysis, and code generation. Does NOT include testing, Code Connect, or Confluence  -  those are separate standalone skills.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ This skill stops after Phase 4. To continue:
 
 ## Dispatch Table
 
-All instruction files are in `.instructions/figma/figma-to-swiftui/` — shared with `/figma-to-swiftui`.
+All instruction files are in `.instructions/figma/figma-to-swiftui/`  -  shared with `/figma-to-swiftui`.
 
 | Phase | Instruction (shared) | Model | Max Turns | Tool Restrictions |
 |-------|---------------------|-------|-----------|-------------------|
@@ -99,7 +99,7 @@ All routing logic is identical to `/figma-to-swiftui` SKILL.md:
 - **Phase 3**: Inline routing (PRE-CHECK → NORMALIZE → Wave 1 scripts+3A+3C+3H → missing token resolution → Wave 2 3D → Wave 3 3G → COLLECT → SPEC → INDEX)
 - **Phase 4**: Inline routing (PRE-CHECK → LOAD_SPEC → PREPARE_DIRECTORY → Wave 1 4A+4B+4C → Wave 2 4D+4E → COLLECT → VALIDATE → BUILD → UPDATE_REGISTRY)
 
-Refer to `.instructions/figma/figma-to-swiftui/SKILL.md` for the full routing logic — it is the authoritative source. This skill uses the exact same dispatch procedures, read-order tables, and return parsing.
+Refer to `.instructions/figma/figma-to-swiftui/SKILL.md` for the full routing logic  -  it is the authoritative source. This skill uses the exact same dispatch procedures, read-order tables, and return parsing.
 
 ### Phase 4 registry finalize
 
@@ -113,7 +113,7 @@ python3 .instructions/figma/figma-to-swiftui/scripts/phase4-finalize.py \
     --platform ios
 ```
 
-The actual GitHub issue sync (labels, body progress table, Projects V2 fields, assignee) runs later when you call `/figma-iteration-commit` — it reads this registry state and invokes `update-issue-from-registry.py` once per node.
+The actual GitHub issue sync (labels, body progress table, Projects V2 fields, assignee) runs later when you call `/figma-iteration-commit`  -  it reads this registry state and invokes `update-issue-from-registry.py` once per node.
 
 ---
 
@@ -177,8 +177,8 @@ Next steps:
 
 ## Notes
 
-- This skill runs Phases 0–4 only — the implementation core
+- This skill runs Phases 0-4 only  -  the implementation core
 - All phase files, scripts, and references are shared with `/figma-to-swiftui`
-- The routing logic is identical — only the scope differs (stops at Phase 4 vs going to Phase 8)
-- Resume mode works the same — `phase-3` resumes Phase 3 from existing artifacts
+- The routing logic is identical  -  only the scope differs (stops at Phase 4 vs going to Phase 8)
+- Resume mode works the same  -  `phase-3` resumes Phase 3 from existing artifacts
 - Can be followed by any combination of the standalone skills in any order

package/pipeline/skills/figma-ios/figma-component-test/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-component-test
-description: "Test generator + runner for implemented SwiftUI Figma components. Produces ViewInspector structural tests, snapshot tests, and XCTest unit tests for a component already built via Phase 4 codegen. Runs standalone (reads source files) or as a Phase 3.5 continuation. iOS platform peer — Android equivalent (Paparazzi/Roborazzi) lives under figma-android/."
+description: "Test generator + runner for implemented SwiftUI Figma components. Produces ViewInspector structural tests, snapshot tests, and XCTest unit tests for a component already built via Phase 4 codegen. Runs standalone (reads source files) or as a Phase 3.5 continuation. iOS platform peer  -  Android equivalent (Paparazzi/Roborazzi) lives under figma-android/."
 user-invocable: true
 argument-hint: "<figma-url> | --component <name>"
 language: en
@@ -10,11 +10,11 @@ sourced-from: upstream/figma-to-swift-ui-test
 local-overlay: true
 ---
 
-# figma-component-test — Standalone Test Generation & Execution
+# figma-component-test  -  Standalone Test Generation & Execution
 
 ## Purpose
 
-Generates and runs ViewInspector, snapshot, and unit tests for an implemented Figma component. Works independently from `/figma-to-swiftui` — reads source files directly. Can also run as a continuation after Phase 4 when full artifacts exist.
+Generates and runs ViewInspector, snapshot, and unit tests for an implemented Figma component. Works independently from `/figma-to-swiftui`  -  reads source files directly. Can also run as a continuation after Phase 4 when full artifacts exist.
 
 ## Parameters
 
@@ -63,15 +63,15 @@ If Swift file missing → HALT. Component not implemented.
 
 | Condition | Action |
 |-----------|--------|
-| ViewInspector + Snapshot tests exist | **UPDATE** mode — regenerate and re-record |
+| ViewInspector + Snapshot tests exist | **UPDATE** mode  -  regenerate and re-record |
 | Tests missing | **CREATE** mode |
 
 ### 4. Detect Path: HOT or COLD
 
 | Condition | Path |
 |-----------|------|
-| `{artifactPath}/pass5/_test_index.md` exists | **HOT** — skip Gate 1, go to Gate 2 |
-| Missing | **COLD** — run Gate 1 |
+| `{artifactPath}/pass5/_test_index.md` exists | **HOT**  -  skip Gate 1, go to Gate 2 |
+| Missing | **COLD**  -  run Gate 1 |
 
 ---
 
@@ -84,7 +84,7 @@ AI subagent (sonnet, 20 turns) reads source files and produces the test index +
 | Source | Derives |
 |--------|---------|
 | `{ComponentName}.swift` (init signature, enums, types) | Variant axes, complexity (SIMPLE/COMPLEX), optional properties |
-| FIGMA.md (variant mapping table) | Snapshot matrix — which property combinations to test |
+| FIGMA.md (variant mapping table) | Snapshot matrix  -  which property combinations to test |
 | FIGMA.md (parameters table) | Parameter types, defaults |
 | Component registry JSON (testingIdentifiers) | Accessibility identifier test cases |
 | `{ComponentName}Configuration.swift` (if COMPLEX) | Configuration properties, chain modifiers |
@@ -98,7 +98,7 @@ The subagent writes:
 {artifactPath}/pass3/04b_component_architecture.md  (if missing)
 {artifactPath}/pass3/04_patterns.md                  (if missing)
 {artifactPath}/pass3/05_complexity.md                (if missing)
-{artifactPath}/pass2/utility_identifiers.json        (if missing — from registry)
+{artifactPath}/pass2/utility_identifiers.json        (if missing  -  from registry)
 ```
 
 The `_test_index.md` contains:
@@ -135,7 +135,7 @@ Dispatch subagents:
 | Condition | Action |
 |-----------|--------|
 | Component has ViewModel/model logic | Dispatch `phases/phase-5c-unit.md` (sonnet, 30 turns) |
-| Pure View + Configuration | Skip — N/A |
+| Pure View + Configuration | Skip  -  N/A |
 
 ---
 
@@ -176,7 +176,7 @@ The script records `against = status.ios.implemented.version`, so the flag will
 | Result | Action |
 |--------|--------|
 | Exit 0, `"action": "updated"` / `"already_current"` / `"created"` | Proceed |
-| Exit 1 | HALT — verify node-id matches registry |
+| Exit 1 | HALT  -  verify node-id matches registry |
 
 GitHub issue sync (labels, Progress table, Projects V2 fields) runs later when `/figma-iteration-commit` invokes `update-issue-from-registry.py`.
 
@@ -186,13 +186,13 @@ GitHub issue sync (labels, Progress table, Projects V2 fields) runs later when `
 
 | Gate | Instruction | Model | Max Turns |
 |------|-------------|-------|-----------|
-| 0 | Inline (this file) | — | — |
+| 0 | Inline (this file) |  -  |  -  |
 | 1 | AI subagent | sonnet | 20 |
 | 2 (5A) | `phases/phase-5a-viewinspector.md` (shared) | sonnet | 40 |
 | 2 (5B) | `phases/phase-5b-snapshot.md` (shared) | sonnet | 40 |
 | 2 (5C) | `phases/phase-5c-unit.md` (shared) | sonnet | 30 |
-| 3 | Script (`run-uicomponents-tests.sh`) | — | — |
-| 4 | Script (`phase5-finalize.py`) | — | — |
+| 3 | Script (`run-uicomponents-tests.sh`) |  -  |  -  |
+| 4 | Script (`phase5-finalize.py`) |  -  |  -  |
 
 ---
 
@@ -211,9 +211,9 @@ GitHub issue sync (labels, Progress table, Projects V2 fields) runs later when `
 
 ## Notes
 
-- Standalone entry point — does NOT require `/figma-to-swiftui` to have run
+- Standalone entry point  -  does NOT require `/figma-to-swiftui` to have run
 - When called after Phase 4, detects existing artifacts (HOT path) and skips data accumulation
-- Phase 5A/5B/5C instruction files don't know which skill invoked them — fully modular
+- Phase 5A/5B/5C instruction files don't know which skill invoked them  -  fully modular
 - Always switches to local common dependency for test execution, reverts after
 - Snapshot tests run twice: first to record, second to verify
 - If component already has tests (UPDATE mode), deletes old snapshots before re-recording

package/pipeline/skills/figma-ios/figma-component-wiki/SKILL.md

@@ -9,9 +9,9 @@ sourced-from: upstream/figma-to-swift-ui-wiki
 local-overlay: true
 ---
 
-# figma-component-wiki — Component Wiki Documentation
+# figma-component-wiki  -  Component Wiki Documentation
 
-> **WS-5 v5.0.0 — locally overlaid.** `local-overlay: true` in frontmatter tells `sync-figma-source.sh` + `import-figma-skills.sh` to skip this file so this v5-specific contract (4-adapter dispatch) isn't flattened on every sync.
+> **WS-5 v5.0.0  -  locally overlaid.** `local-overlay: true` in frontmatter tells `sync-figma-source.sh` + `import-figma-skills.sh` to skip this file so this v5-specific contract (4-adapter dispatch) isn't flattened on every sync.
 
 ## Dispatch contract (Phase 7 Report Step 2)
 
@@ -36,7 +36,7 @@ Emit progress line `→ writing wiki {componentName} (mode: {mode})` as the firs
 | mode | when to pick | path layout | push semantics |
 |---|---|---|---|
 | `submodule` | Team versions the wiki as a git submodule (source project's native layout). | `{repos.wiki.path}/FigmaComponents/{Category}/{Name}/{Name}.md` + `assets/` | Commit into submodule's `{repos.wiki.branch}`, push. Updates parent repo's submodule pointer. |
-| `in-repo` | Simple projects without a separate wiki repo (default). | `{repos.components.path}/.wiki/components/{Category}/{Name}.md` | No push — commits with the component change in Phase 6. |
+| `in-repo` | Simple projects without a separate wiki repo (default). | `{repos.components.path}/.wiki/components/{Category}/{Name}.md` | No push  -  commits with the component change in Phase 6. |
 | `github-wiki` | Team uses GitHub's built-in wiki (`{org}/{repo}.wiki.git`). | `{repo}.wiki.git/{Category}/{Name}.md` | Clone `.wiki.git`, add/commit, push. Idempotent over re-renders. |
 | `separate-repo` | Wiki in a separate GitHub repo (not submodule, not `.wiki`). | Remote repo's configured branch; same file layout as submodule. | Clone on demand to `~/.cache/multi-agent/wiki/{slug}/`, commit, push. |
 
@@ -45,37 +45,37 @@ Every adapter:
 1. Receives identical rendered markdown (content identical across layouts).
 2. Generates `_Sidebar.md` via `pipeline/scripts/wiki/sidebar-generator.py` (ships in a follow-up).
 3. Updates `ComponentImplementationStatus.md` via `pipeline/scripts/wiki/status-page.py` (ships in a follow-up).
-4. Is idempotent — re-running on unchanged component produces no diff.
+4. Is idempotent  -  re-running on unchanged component produces no diff.
 
 ## Failure contracts
 
-- `submodule` — submodule path missing → return error, no partial commit.
-- `in-repo` — target dir not writable → return error; Phase 6 commit picks up the `.wiki/` change on its next run if paths eventually exist.
-- `github-wiki` — wiki repo not enabled on GitHub → suggest enabling and skip (return success with `writtenPaths: []`).
-- `separate-repo` — remote unreachable → cache the markdown under `~/.cache/multi-agent/wiki/{slug}/pending/` and return a warning; next run retries.
+- `submodule`  -  submodule path missing → return error, no partial commit.
+- `in-repo`  -  target dir not writable → return error; Phase 6 commit picks up the `.wiki/` change on its next run if paths eventually exist.
+- `github-wiki`  -  wiki repo not enabled on GitHub → suggest enabling and skip (return success with `writtenPaths: []`).
+- `separate-repo`  -  remote unreachable → cache the markdown under `~/.cache/multi-agent/wiki/{slug}/pending/` and return a warning; next run retries.
 
 ## Markdown rendering (mode-agnostic)
 
 Reads `componentPath` + sibling `FIGMA.md` (variant matrix, usage examples). Writes:
 
-- `{Name}.md` — component page (overview, parameters, variants, code examples, tokens, accessibility notes).
-- `{Name}/assets/` — design screenshots.
-- `_Sidebar.md` — navigation (regenerated by the sidebar script).
-- `ComponentImplementationStatus.md` — status dashboard (regenerated).
+- `{Name}.md`  -  component page (overview, parameters, variants, code examples, tokens, accessibility notes).
+- `{Name}/assets/`  -  design screenshots.
+- `_Sidebar.md`  -  navigation (regenerated by the sidebar script).
+- `ComponentImplementationStatus.md`  -  status dashboard (regenerated).
 
 ---
 
-## Legacy content (upstream — submodule-mode reference)
+## Legacy content (upstream  -  submodule-mode reference)
 
 Everything below is the original `/figma-to-swift-ui-wiki` skill content, preserved as the reference implementation for the `submodule` adapter.
 
 ---
 
-# /figma-to-swift-ui-wiki — Standalone Wiki Documentation
+# /figma-to-swift-ui-wiki  -  Standalone Wiki Documentation
 
 ## Purpose
 
-Generates GitHub Wiki documentation for an implemented Figma component. Works independently from `/figma-to-swiftui` — reads source files and artifacts directly. Can also run as a continuation after Phase 6 when full artifacts exist.
+Generates GitHub Wiki documentation for an implemented Figma component. Works independently from `/figma-to-swiftui`  -  reads source files and artifacts directly. Can also run as a continuation after Phase 6 when full artifacts exist.
 
 The wiki is the **source of truth** for component documentation. Confluence pages are synced from the wiki via `/figma-to-swift-ui-confluence-sync`.
 
@@ -190,7 +190,7 @@ If the component is **missing** from `_Sidebar.md`, re-run the sidebar generator
 python3 .instructions/figma/figma-to-swiftui/scripts/sidebar-generator.py --wiki-root ${wikiRoot}
 ```
 
-This regenerates the entire sidebar from the wiki directory structure. If the component's wiki folder exists, it will appear in the output. If it still doesn't appear after regeneration, the wiki folder structure is incorrect — HALT and ask the user to verify the component's wiki directory path.
+This regenerates the entire sidebar from the wiki directory structure. If the component's wiki folder exists, it will appear in the output. If it still doesn't appear after regeneration, the wiki folder structure is incorrect  -  HALT and ask the user to verify the component's wiki directory path.
 
 ---
 
@@ -241,7 +241,7 @@ The script records `against = status.ios.implemented.version`, so the flag drops
 | Result | Action |
 |--------|--------|
 | Exit 0, `"action": "updated"` / `"already_current"` / `"created"` | Proceed |
-| Exit 1 | HALT — verify node-id matches registry |
+| Exit 1 | HALT  -  verify node-id matches registry |
 
 GitHub issue sync runs later via `/figma-iteration-commit` → `update-issue-from-registry.py`.
 
@@ -267,7 +267,7 @@ Wiki documentation complete:
 
 ## Error Handling
 
-- **Component not implemented**: HALT — run implementation first.
+- **Component not implemented**: HALT  -  run implementation first.
 - **FigmaRegistryUtility not built**: Run `swift build --product FigmaRegistryUtility`.
 - **Wiki submodule not initialized**: Run `git submodule update --init` on the wiki path.
 - **Push fails**: Check if wiki submodule is on `master` and remote is accessible.

package/pipeline/skills/figma-ios/figma-to-component/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-to-component
-description: Figma-to-SwiftUI component implementation workflow. Takes a Figma URL and produces a production-ready SwiftUI component through 8 phases — data gathering, analysis, code generation, testing, Code Connect, and documentation.
+description: Figma-to-SwiftUI component implementation workflow. Takes a Figma URL and produces a production-ready SwiftUI component through 8 phases  -  data gathering, analysis, code generation, testing, Code Connect, and documentation.
 user-invocable: true
 argument-hint: <figma-url> | phase-<N> | status
 allowed-tools: Task, Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion
@@ -8,7 +8,7 @@ status: wip-v5
 sourced-from: upstream/figma-to-swiftui
 ---
 
-# /figma — Figma-to-SwiftUI Workflow Orchestrator
+# /figma  -  Figma-to-SwiftUI Workflow Orchestrator
 
 ## Parse Arguments
 
@@ -50,7 +50,7 @@ These 6 rules govern orchestrator behavior. Violations have caused repeated fail
 0 (Init) → 1 (Gather) → 2A → 2B → 2C → 2D → 3 (Analysis) → 4 (Implementation) → 5A → 5B → 5C → 6 (Code Connect) → 7 (Wiki Markdown)
 ```
 
-This skill dispatches Phase 2 and Phase 5 sub-phases directly — no orchestrator subagent.
+This skill dispatches Phase 2 and Phase 5 sub-phases directly  -  no orchestrator subagent.
 
 When `phase-7` is invoked:
 1. Dispatch `phase-7a` (generate two wiki pages: main + iOS, plus assets into wiki submodule).
@@ -113,6 +113,21 @@ Bundled in `.instructions/figma/figma-to-swiftui/reference/`. Include relevant p
 | `reference/viewinspector.md` | 5A |
 | `reference/snapshot-testing.md` | 5D |
 
+## Complementary integration skills
+
+Cross-cutting skills in `figma-common/` that feed Phase 3D / 4A / 4B when the design triggers them (see `reference/orchestrator-discipline.md` Rule 4). Native-SwiftUI-first; project specifics come from `figma-config` `ui.*` hooks.
+
+| Skill | Phase 3D trigger | Purpose |
+|-------|------------------|---------|
+| `/figma-form-integration` | form-capable sub-components | FormField/FormSection modeling |
+| `/figma-price-integration` | currency+amount / Price instance | PriceRepresentable modeling |
+| `/figma-ui-patterns` | scroll/motion/shape signal | reusable technique recipes (incl. `animated-gradient-border`) |
+| `/figma-navigation` | tab/back/push/deep-link affordance | headless Output; native NavigationStack or `ui.navigationSystem` |
+| `/figma-overlays` | toast/HUD/alert/data-modal | caller-owned; native `.alert`/`.sheet(item:)` or `ui.overlaySystem` |
+| `/figma-bottom-sheets` | sheet/drawer/pinned-CTA/multi-step | sheet content; native `.presentationDetents` or `ui.sheetSystem` |
+
+Related workflow: `/figma-evolve-component` reconciles + extends an already-implemented component (drift-heal + additive extend, human-gated)  -  distinct from a fresh build here, `/figma-mend` (rebuild), and `/figma-fix` (review bug).
+
 ---
 
 ## Dispatch Procedure
@@ -133,10 +148,10 @@ You are executing {Phase Name} of the Figma-to-SwiftUI workflow.
 - Artifact Path: {artifactPath}
 - Component Location: {componentLocation}
 - GitHub Issue: {issueNumber} (omit if not available)
-- Wiki Path: {wikiPath} (Phase 7 only — `{repos.wiki.path}`)
+- Wiki Path: {wikiPath} (Phase 7 only  -  `{repos.wiki.path}`)
 
 ## Tool Restrictions
-{from dispatch table — e.g., "Do NOT use the Edit tool."}
+{from dispatch table  -  e.g., "Do NOT use the Edit tool."}
 
 ## Your Instructions
 Read and STRICTLY FOLLOW your phase instructions gate-by-gate from this file:
@@ -149,18 +164,18 @@ Read the return protocol from:
 
 ## Specs (if present)
 - {artifactPath}/pass0/specs.md
-Read and incorporate specs alongside phase instructions. Both are inputs you must follow — phase instructions define methodology and coding standards, specs define acceptance criteria and design intent. Neither overrides the other.
+Read and incorporate specs alongside phase instructions. Both are inputs you must follow  -  phase instructions define methodology and coding standards, specs define acceptance criteria and design intent. Neither overrides the other.
 
 ## Reference Files (read during execution if needed)
 - .instructions/figma/figma-to-swiftui/{reference path}
 
 ## Previous Phase Artifacts (read in this order)
-{use the Read-Order Table below — list file PATHS only, do not embed content}
+{use the Read-Order Table below  -  list file PATHS only, do not embed content}
 ```
 
 ### 2. Dispatch
 
-**Phase 1 (script):** Run directly via Bash — no subagent needed:
+**Phase 1 (script):** Run directly via Bash  -  no subagent needed:
 
 ```bash
 python3 .instructions/figma/figma-to-swiftui/scripts/phase1-gather.py \
@@ -175,7 +190,7 @@ The script tries remote MCP first, falls back to local MCP automatically.
 
 **If `status` = `COMPLETE_WITH_DEFERRED`:**
 Design context was deferred (too many sublayers). All other artifacts are present.
-Do NOT ask the user — dispatch a **Phase 1 subagent** for deferred resolution:
+Do NOT ask the user  -  dispatch a **Phase 1 subagent** for deferred resolution:
 
 ```
 Agent(
@@ -230,13 +245,13 @@ After each phase completes, update IMPLEMENTATION_HISTORY.md with phase status,
 
 ---
 
-## Phase 2 Routing (inline — do NOT read phase-2-orchestrator.md)
+## Phase 2 Routing (inline  -  do NOT read phase-2-orchestrator.md)
 
 **Do NOT read `phase-2-orchestrator.md`. All routing logic is here. Subagents read their own docs.**
 
 1. **PRE-CHECK**: Read `IMPLEMENTATION_HISTORY.md` (already in context). Verify `pass1/_index.md` exists.
-2. **NORMALIZE**: Check `pass1/design_context_response.json` — if `sublayers: true` and no `response` field, concatenate `responses` values into `response` field and write back.
-3. **REGISTRY_LOOKUP**: `cd {repos.common.path} && .build/debug/FigmaRegistryUtility utility-lookup --node-id '{nodeId}'` — pass result as `registryData` context to subagents.
+2. **NORMALIZE**: Check `pass1/design_context_response.json`  -  if `sublayers: true` and no `response` field, concatenate `responses` values into `response` field and write back.
+3. **REGISTRY_LOOKUP**: `cd {repos.common.path} && .build/debug/FigmaRegistryUtility utility-lookup --node-id '{nodeId}'`  -  pass result as `registryData` context to subagents.
 4. **Wave 1 (parallel)**: Dispatch 2A + 2B + 2C as subagents (each reads its own instruction doc by path).
 5. **Wave 2**: Dispatch 2D as subagent (depends on 2A output).
 6. **FINALIZE (script)**:
@@ -250,7 +265,7 @@ After each phase completes, update IMPLEMENTATION_HISTORY.md with phase status,
 
 ---
 
-## Phase 3 Routing (inline — do NOT read phase-3-orchestrator.md)
+## Phase 3 Routing (inline  -  do NOT read phase-3-orchestrator.md)
 
 **Do NOT read `phase-3-orchestrator.md`. Subagents read their own docs. Scripts handle deterministic phases.**
 
@@ -260,14 +275,14 @@ After each phase completes, update IMPLEMENTATION_HISTORY.md with phase status,
    - **Scripts**: `python3 .instructions/figma/figma-to-swiftui/scripts/phase3-scripts.py wave1 --artifact-path '{artifactPath}'` (runs 3B+3E+3F, ~5s)
    - **Subagents**: 3A (`phase-3a-location.md`, sonnet, 20 turns), 3C (`phase-3c-nested.md`, sonnet, 20 turns), 3H (`phase-3h-variant-config.md`, opus, 25 turns)
 4. **MISSING TOKEN RESOLUTION**: After Wave 1, check `pass3/02_token_mapping.md` for missing tokens (lines with "⚠️ not found"). If any exist, dispatch a subagent:
-   - **Subagent** (`general-purpose`, opus, 25 turns) — reads `reference/missing-tokens.md` for procedure, resolves each missing token by:
+   - **Subagent** (`general-purpose`, opus, 25 turns)  -  reads `reference/missing-tokens.md` for procedure, resolves each missing token by:
      - **Typography**: Adding alias entries to `typography-registry.json` (match font size + weight to existing Swift tokens)
      - **Colors**: Adding to `Shared/UIAssets/Colors/*.json` (source), running `swift package plugin --allow-writing-to-package-directory generate-ui-assets`, adding to `ui-token-index.json`
      - **Variables**: Using `FigmaRegistryUtility ui-token-lookup` / `ui-token-index` to verify
    - Pass artifact path and token mapping path as context. Subagent updates token mapping after resolution.
    - If 0 missing tokens, skip this step entirely.
 5. **Wave 2 (parallel)**: Launch simultaneously:
-   - **Subagent**: 3D (`phase-3d-patterns.md`, opus, 30 turns) — reads 3H output (`pass3/04c_variant_config_analysis.json`)
+   - **Subagent**: 3D (`phase-3d-patterns.md`, opus, 30 turns)  -  reads 3H output (`pass3/04c_variant_config_analysis.json`)
 6. **Wave 3**: `python3 .instructions/figma/figma-to-swiftui/scripts/phase3-scripts.py 3g --artifact-path '{artifactPath}'` (depends on 3D JSON output)
 7. **COLLECT**: Verify 12 artifacts exist in `pass3/` (10 original + 2 from 3H).
 8. **SPEC (script)**: `python3 .instructions/figma/figma-to-swiftui/scripts/phase3-scripts.py spec --artifact-path '{artifactPath}'`
@@ -276,38 +291,38 @@ After each phase completes, update IMPLEMENTATION_HISTORY.md with phase status,
 
 ---
 
-## Phase 4 Routing (inline — do NOT read phase-4-orchestrator.md)
+## Phase 4 Routing (inline  -  do NOT read phase-4-orchestrator.md)
 
 **Do NOT read `phase-4-orchestrator.md`. Subagents read their own docs. Orchestrator stays lean.**
 
 1. **PRE-CHECK**: Verify `pass3/_index.md` exists.
-2. **LOAD_SPEC**: Read `pass3/07_implementation_spec.md` and `pass3/05_complexity.md` — extract `componentLocation`, `complexity` (SIMPLE/COMPLEX).
+2. **LOAD_SPEC**: Read `pass3/07_implementation_spec.md` and `pass3/05_complexity.md`  -  extract `componentLocation`, `complexity` (SIMPLE/COMPLEX).
 3. **PREPARE_DIRECTORY**: `mkdir -p {componentLocation}`. Get `gitUser` via `git config user.name`. Get `date` in DD.MM.YYYY format.
 4. **Wave 1 (parallel)**: Dispatch subagents:
-   - **4A** (`phase-4a-configuration.md`, opus, 30 turns) — **COMPLEX only** (skip if SIMPLE). Writes `{ComponentName}Configuration.swift`.
-   - **4B** (`phase-4b-view.md`, opus, 40 turns) — **ALWAYS**. Writes `{ComponentName}.swift`.
-   - **4C** (`phase-4c-documentation.md`, sonnet, 20 turns) — **ALWAYS**. Writes `FIGMA.md`.
-   - Pass to each: componentName, componentLocation, artifactPath, nodeId, fileKey, complexity, gitUser, date, issueNumber (from IMPLEMENTATION_HISTORY.md `GitHub Issue` field — extract the number after `#`).
+   - **4A** (`phase-4a-configuration.md`, opus, 30 turns)  -  **COMPLEX only** (skip if SIMPLE). Writes `{ComponentName}Configuration.swift`.
+   - **4B** (`phase-4b-view.md`, opus, 40 turns)  -  **ALWAYS**. Writes `{ComponentName}.swift`.
+   - **4C** (`phase-4c-documentation.md`, sonnet, 20 turns)  -  **ALWAYS**. Writes `FIGMA.md`.
+   - Pass to each: componentName, componentLocation, artifactPath, nodeId, fileKey, complexity, gitUser, date, issueNumber (from IMPLEMENTATION_HISTORY.md `GitHub Issue` field  -  extract the number after `#`).
 5. **Wave 2 (parallel)**: Dispatch subagents that depend on 4A+4B:
-   - **4D** (`phase-4d-preview.md`, sonnet, 20 turns) — appends Preview to `{ComponentName}.swift`.
-   - **4E** (`phase-4e-modifiers.md`, sonnet, 20 turns) — **COMPLEX only** (skip if SIMPLE). Writes `{ComponentName}+Modifiers.swift`.
+   - **4D** (`phase-4d-preview.md`, sonnet, 20 turns)  -  appends Preview to `{ComponentName}.swift`.
+   - **4E** (`phase-4e-modifiers.md`, sonnet, 20 turns)  -  **COMPLEX only** (skip if SIMPLE). Writes `{ComponentName}+Modifiers.swift`.
 6. **COLLECT**: Verify `{ComponentName}.swift`, `{ComponentName}Configuration.swift` (if COMPLEX), `{ComponentName}+Modifiers.swift` (if COMPLEX), `FIGMA.md` exist.
-7. **VALIDATE**: `bash .instructions/figma/figma-to-swiftui/scripts/validate-phase4.sh "{componentLocation}" "{ComponentName}" "{artifactPath}/pass3/00_property_coverage.json"` — fix violations if any.
-8. **BUILD**: `xcodebuild build -project "$(git rev-parse --show-toplevel)/{build.xcodeproj}" -scheme {build.scheme} -destination 'generic/platform=iOS' CODE_SIGNING_ALLOWED=NO -quiet` — fix compilation errors if any.
+7. **VALIDATE**: `bash .instructions/figma/figma-to-swiftui/scripts/validate-phase4.sh "{componentLocation}" "{ComponentName}" "{artifactPath}/pass3/00_property_coverage.json"`  -  fix violations if any.
+8. **BUILD**: `xcodebuild build -project "$(git rev-parse --show-toplevel)/{build.xcodeproj}" -scheme {build.scheme} -destination 'generic/platform=iOS' CODE_SIGNING_ALLOWED=NO -quiet`  -  fix compilation errors if any.
 9. **UPDATE HISTORY**: Append Phase 4 summary.
 
 ---
 
-## Phase 5 Routing (inline — do NOT read phase-5-orchestrator.md)
+## Phase 5 Routing (inline  -  do NOT read phase-5-orchestrator.md)
 
 **Do NOT read `phase-5-orchestrator.md`. Subagents read their own docs.**
 
 1. **PRE-CHECK**: Verify Phase 4 complete (component Swift file exists at `{componentLocation}`).
 2. **Wave 1 (parallel)**: Dispatch subagents:
-   - **5A** (`phase-5a-viewinspector.md`, sonnet, 40 turns) — ViewInspector structure + accessibility tests.
-   - **5B** (`phase-5b-snapshot.md`, sonnet, 40 turns) — Snapshot tests for all Figma variants.
-3. **Wave 2 (conditional)**: **5C** (`phase-5c-unit.md`, sonnet, 30 turns) — Unit tests. Only if component has ViewModel/model logic. N/A for pure View + Configuration.
-4. **TEST EXECUTION**: Run all tests via script — sequentially, NOT parallel (shared DerivedData lock):
+   - **5A** (`phase-5a-viewinspector.md`, sonnet, 40 turns)  -  ViewInspector structure + accessibility tests.
+   - **5B** (`phase-5b-snapshot.md`, sonnet, 40 turns)  -  Snapshot tests for all Figma variants.
+3. **Wave 2 (conditional)**: **5C** (`phase-5c-unit.md`, sonnet, 30 turns)  -  Unit tests. Only if component has ViewModel/model logic. N/A for pure View + Configuration.
+4. **TEST EXECUTION**: Run all tests via script  -  sequentially, NOT parallel (shared DerivedData lock):
    a. **Switch to local common dependency**: In `{repos.components.path}/Package.swift`, comment out the `.package(url: "...{project.slug}-common...", ...)` line and add `.package(path: "../{project.slug}-common"),` below it. This is needed because the SPM package resolves dependencies from remote git, but Phase 2 adds identifiers/keys to the local editable copy.
    b. **Run tests**:
       ```bash
@@ -323,7 +338,7 @@ After each phase completes, update IMPLEMENTATION_HISTORY.md with phase status,
 
 ## Phase 6 Routing
 
-Phase 6 is dispatched as a single subagent. After the subagent returns COMPLETE, run the finalization script as a safety net (idempotent — safe to run even if the subagent already ran it):
+Phase 6 is dispatched as a single subagent. After the subagent returns COMPLETE, run the finalization script as a safety net (idempotent  -  safe to run even if the subagent already ran it):
 
 ```bash
 python3 .instructions/figma/figma-to-swiftui/scripts/phase6-finalize.py \
@@ -341,24 +356,24 @@ Parse stdout JSON. Verify `"status": "ok"`. Update IMPLEMENTATION_HISTORY.md wit
 
 When building the `Previous Phase Artifacts` section of the dispatch prompt, list artifacts in this order. Compact artifacts go FIRST so the subagent establishes context before large files consume the context window.
 
-Every phase must be independently operable from a clean session — all artifacts remain accessible on disk. This table is a **read-ordering preference**, not a prohibition.
+Every phase must be independently operable from a clean session  -  all artifacts remain accessible on disk. This table is a **read-ordering preference**, not a prohibition.
 
 | Phase | Read FIRST (compact) | Read SECOND (if detail needed) |
 |-------|---------------------|-------------------------------|
 | 2A-2D | `pass1/component_summary.json` | `pass1/design_context_response.json`, `pass1/component_properties.json` |
-| 3A | `pass1/component_summary.json`, `IMPLEMENTATION_HISTORY.md` | — |
+| 3A | `pass1/component_summary.json`, `IMPLEMENTATION_HISTORY.md` |  -  |
 | 3B | `pass1/component_summary.json`, `pass1/variable_defs_response.json` | `pass1/design_context_response.json` (for binding context) |
-| 3C | `pass1/component_summary.json`, `pass1/code_connect_map_response.json` | — |
+| 3C | `pass1/component_summary.json`, `pass1/code_connect_map_response.json` |  -  |
 | 3D | `pass1/component_summary.json`, `pass1/component_properties.json` | `pass1/design_context_response.json`, `pass1/metadata_response.xml` |
-| 3E | `pass1/component_summary.json`, `pass1/design_context_assets.txt` | — |
+| 3E | `pass1/component_summary.json`, `pass1/design_context_assets.txt` |  -  |
 | 3F | `pass1/component_summary.json`, `pass2/utility_*.md` | `pass1/design_context_response.json` |
-| 3G | `pass1/component_summary.json`, `pass3/04b_component_architecture.md` | — |
+| 3G | `pass1/component_summary.json`, `pass3/04b_component_architecture.md` |  -  |
 | 4A | `pass3/04b_component_architecture.md`, `pass3/05_complexity.md`, `pass3/00_property_coverage.json` | `pass1/component_summary.json` |
 | 4B | `pass1/component_summary.json`, `pass3/00_property_coverage.json`, `pass3/07_implementation_spec.md`, `pass3/02_token_mapping.md`, `pass3/04b_component_architecture.md`, `pass3/04_patterns.md`, `pass3/03_nested_components.md`, `pass3/08_utility_integration.md`, `pass1/screenshot.png` | `pass1/design_context_response.json` (for complex layout detail) |
 | 4C | `pass3/07_implementation_spec.md`, `pass3/04b_component_architecture.md`, `pass3/00_property_coverage.json` | `pass1/component_summary.json` |
 | 4D | `{componentLocation}/{ComponentName}.swift`, `{componentLocation}/{ComponentName}Configuration.swift` (if exists) | `pass3/04_patterns.md` |
-| 4E | `{componentLocation}/{ComponentName}Configuration.swift`, `{componentLocation}/{ComponentName}.swift` | — |
-| 6 | `pass1/component_properties.json`, `{sourceLocation}/FIGMA.md`, `{sourceLocation}/{componentName}.swift` | — |
+| 4E | `{componentLocation}/{ComponentName}Configuration.swift`, `{componentLocation}/{ComponentName}.swift` |  -  |
+| 6 | `pass1/component_properties.json`, `{sourceLocation}/FIGMA.md`, `{sourceLocation}/{componentName}.swift` |  -  |
 
 ---
 

package/pipeline/skills/figma-ios/figma-to-component/halt-return-protocol.md

@@ -22,7 +22,7 @@ SUMMARY: {one-line description of what was accomplished}
 STATUS: HALT
 PHASE: phase-{N}
 GATE: {gate-id that failed}
-REASON: {exact reason — copy from instruction if applicable}
+REASON: {exact reason  -  copy from instruction if applicable}
 COMPLETED_GATES: [gates that passed before halt]
 ARTIFACTS_CREATED: [files written before halt, or "none"]
 USER_ACTION_REQUIRED: {what the user must fix before retry}
@@ -52,6 +52,6 @@ CONTEXT: {relevant data the user needs to make the decision}
 2. STOP after outputting the block. Do not call any more tools.
 3. Every gate you pass must appear in GATES_PASSED or COMPLETED_GATES.
 4. Every file you created must appear in ARTIFACTS_CREATED.
-5. Never output a STATUS block mid-execution — only at the very end.
+5. Never output a STATUS block mid-execution  -  only at the very end.
 6. If you encounter multiple failures, report the FIRST one.
 7. If a HALT condition says to check for USER_DECISION in the prompt first, do so before halting.