@mmerterden/multi-agent-pipeline 8.6.2 → 10.0.6

package/pipeline/skills/figma-common/performance-tour/SKILL.md

@@ -1,4 +1,9 @@
-# /performance-tour — Batch Component Production Pipeline
+---
+name: performance-tour
+description: Produces multiple Figma components in a single session. Validates dependencies, determines implementation order, produces each component sequentially with clean subagent contexts, then hands off to review and batch.
+---
+
+# /performance-tour  -  Batch Component Production Pipeline
 
 > Produces multiple Figma components in a single session. Validates dependencies,
 > determines implementation order, produces each component sequentially with clean
@@ -8,9 +13,9 @@
 
 | Parameter | Required | Default | Description |
 |-----------|----------|---------|-------------|
-| `<issue-numbers>` | Yes | — | Comma-separated GitHub issue numbers from uicomponents repo |
-| `--resume` | No | — | Resume an interrupted tour from `_tour_tracker.json` |
-| `--lean` | No | — | Lean mode: skip Phase 5 (testing) and Phase 7 (wiki) for all components. Forwarded to `performance-start --lean` → `performance-swiftui --lean`. |
+| `<issue-numbers>` | Yes |  -  | Comma-separated GitHub issue numbers from uicomponents repo |
+| `--resume` | No |  -  | Resume an interrupted tour from `_tour_tracker.json` |
+| `--lean` | No |  -  | Lean mode: skip Phase 5 (testing) and Phase 7 (wiki) for all components. Forwarded to `performance-start --lean` → `performance-swiftui --lean`. |
 
 ```
 /performance-tour 1000, 1001, 1002
@@ -78,12 +83,12 @@ context loss and conversation timeouts. Written after every state change.
 }
 ```
 
-**CRITICAL:** Write the tracker file after every state change — component status update,
+**CRITICAL:** Write the tracker file after every state change  -  component status update,
 step transition, HALT event, review completion. This is the mechanism that survives context loss.
 
 ---
 
-## STEP 0 — Parse, Validate & Sort
+## STEP 0  -  Parse, Validate & Sort
 
 ### 0a. Parse Issues
 
@@ -95,11 +100,11 @@ gh issue view <N> --repo ${GH_REPO} --json number,title,body,labels,state
 ```
 
 Extract from each issue body:
-- **Component Name** — from `### Component Name (PascalCase)` section
-- **Figma URL** — from `### Figma URL` section
-- **Node ID** — from `### Node ID` section
-- **Registry Name** — from `### Registry Name` section
-- **Jira Key** — from `### Jira Issue` section
+- **Component Name**  -  from `### Component Name (PascalCase)` section
+- **Figma URL**  -  from `### Figma URL` section
+- **Node ID**  -  from `### Node ID` section
+- **Registry Name**  -  from `### Registry Name` section
+- **Jira Key**  -  from `### Jira Issue` section
 
 Validate:
 - Issue is open → if closed, remove from tour with warning
@@ -109,8 +114,8 @@ Validate:
 ### 0b. Validate Each Component
 
 Run `/figma-validate` logic for each issue (inline, not as skill invocation):
-- Criterion 7 (Already Implemented) — if already implemented, remove from tour
-- Criterion 4 (Dependency Readiness) — collect nested dependencies
+- Criterion 7 (Already Implemented)  -  if already implemented, remove from tour
+- Criterion 4 (Dependency Readiness)  -  collect nested dependencies
 
 ### 0c. Build Dependency Graph
 
@@ -170,13 +175,13 @@ Print tour plan:
 
 ```
 ╔══════════════════════════════════════════════════════════════╗
-║  PERFORMANCE TOUR — PLAN                                     ║
+║  PERFORMANCE TOUR  -  PLAN                                     ║
 ╠══════════════════════════════════════════════════════════════╣
 ║                                                              ║
 ║  Execution Order:                                            ║
-║  1. #1000 — ComponentA (independent)                        ║
-║  2. #1002 — ComponentC (independent)                        ║
-║  3. #1001 — ComponentB (depends on: ComponentA)             ║
+║  1. #1000  -  ComponentA (independent)                        ║
+║  2. #1002  -  ComponentC (independent)                        ║
+║  3. #1001  -  ComponentB (depends on: ComponentA)             ║
 ║                                                              ║
 ║  Dependency Graph:                                           ║
 ║  ComponentA ← ComponentB                                     ║
@@ -200,7 +205,7 @@ These 6 rules govern orchestrator behavior across the tour. Rules 2 (every dispa
 
 ---
 
-## STEP 1 — Sequential Produce + Local Commit
+## STEP 1  -  Sequential Produce + Local Commit
 
 For each component in `execution_order`:
 
@@ -208,22 +213,22 @@ For each component in `execution_order`:
 
 Invoke `/performance-start <issue-number> --tour` (add `--lean` if `lean_mode` is `true` in tracker):
 - Parses issue metadata (STEP 0)
-- **SKIPS** fetch + pull (STEP 1) — already done in STEP 0e
-- **SKIPS** branch creation (STEP 2) — staying on iteration/develop
+- **SKIPS** fetch + pull (STEP 1)  -  already done in STEP 0e
+- **SKIPS** branch creation (STEP 2)  -  staying on iteration/develop
 - Runs registry lookup (STEP 3)
 - Saves specs artifact (STEP 3.5)
 - Assigns to me + sets In Progress (STEP 4, 5)
 - Prints summary (STEP 6)
-- Auto-launches `/performance-swiftui <figma-url>` (STEP 6) — with `--lean` if lean mode
+- Auto-launches `/performance-swiftui <figma-url>` (STEP 6)  -  with `--lean` if lean mode
 
 ### 1b. Wait for production to complete
 
-`performance-swiftui` runs Phase 0–7 as a subagent chain (or Phase 0–4 + 6 in lean mode). When it completes:
+`performance-swiftui` runs Phase 0-7 as a subagent chain (or Phase 0-4 + 6 in lean mode). When it completes:
 
 **If COMPLETE:**
 
 ```bash
-# Local commit — all submodules
+# Local commit  -  all submodules
 cd ${COMMON}
 git add -A
 git commit -m "feat(common): [${JIRA_KEY}] add ${COMPONENT_NAME} tokens and keys
@@ -238,7 +243,7 @@ git commit -m "feat(uicomponents): [${JIRA_KEY}] add ${COMPONENT_NAME} component
 Refs: ${JIRA_KEY}
 Tour: performance-tour $(date +%Y%m%d)"
 
-# Wiki commit — SKIP if lean_mode is true
+# Wiki commit  -  SKIP if lean_mode is true
 if [ "$LEAN_MODE" != "true" ]; then
 cd ${WIKI}
 git add -A
@@ -262,7 +267,7 @@ ARTIFACT_PATH="${component.artifact_path}"
 
 # 2. Remove isolated files (component-specific directories)
 rm -rf "${UICOMPONENTS}/${COMPONENT_LOCATION}"
-# Remove test directories if created (skip check in lean mode — tests weren't generated)
+# Remove test directories if created (skip check in lean mode  -  tests weren't generated)
 if [ "$LEAN_MODE" != "true" ]; then
 find "${UICOMPONENTS}/Tests" -type d -name "${COMPONENT_NAME}*" -exec rm -rf {} +
 # Remove snapshot baselines if created
@@ -298,7 +303,7 @@ Add to `halted_components` list.
 Print:
 
 ```
-⚠️ ComponentB HALTED at Phase 4 — build failure
+⚠️ ComponentB HALTED at Phase 4  -  build failure
    Files cleaned up. Proceeding to next component.
    ComponentB can be fixed during review session.
 ```
@@ -309,9 +314,9 @@ After each component (produced or halted), print progress:
 
 ```
 Tour Progress: 2/3 produced, 1/3 halted
-  ✅ #1000 — ComponentA (produced)
-  ❌ #1001 — ComponentB (halted: Phase 4 build failure)
-  🔄 #1002 — ComponentC (in progress...)
+  ✅ #1000  -  ComponentA (produced)
+  ❌ #1001  -  ComponentB (halted: Phase 4 build failure)
+  🔄 #1002  -  ComponentC (in progress...)
 ```
 
 ### 1d. Loop
@@ -329,9 +334,9 @@ Print:
 ║  Produced: 2/3                                               ║
 ║  Halted:   1/3                                               ║
 ║                                                              ║
-║  ✅ #1000 — ComponentA                                       ║
-║  ✅ #1002 — ComponentC                                       ║
-║  ❌ #1001 — ComponentB (Phase 4 build failure)               ║
+║  ✅ #1000  -  ComponentA                                       ║
+║  ✅ #1002  -  ComponentC                                       ║
+║  ❌ #1001  -  ComponentB (Phase 4 build failure)               ║
 ║                                                              ║
 ║  Next: /performance-review-next                              ║
 ║  Or:   /performance-tour --resume                            ║
@@ -340,18 +345,18 @@ Print:
 
 ---
 
-## STEP 2 — Review Session
+## STEP 2  -  Review Session
 
-Invoke `/performance-review-next` — this is a separate skill that reads the tracker
+Invoke `/performance-review-next`  -  this is a separate skill that reads the tracker
 and manages the interactive review loop.
 
 See `.instructions/figma/performance-review-next/SKILL.md` for details.
 
 ---
 
-## STEP 3 — Batch Commit
+## STEP 3  -  Batch Commit
 
-After all components are reviewed, invoke `/performance-iteration-commit-all` — this is
+After all components are reviewed, invoke `/performance-iteration-commit-all`  -  this is
 a separate skill that validates, pushes, and handles issue housekeeping.
 
 See `.instructions/figma/performance-iteration-commit-all/SKILL.md` for details.
@@ -373,7 +378,7 @@ When invoked with `--resume`:
 ╔══════════════════════════════════════════════════════════════╗
 ║  RESUMING TOUR                                               ║
 ╠══════════════════════════════════════════════════════════════╣
-║  Last state: STEP 1 — producing ComponentC (#1002)          ║
+║  Last state: STEP 1  -  producing ComponentC (#1002)          ║
 ║  Produced:   1 (ComponentA)                                  ║
 ║  Halted:     1 (ComponentB)                                  ║
 ║  Remaining:  1 (ComponentC)                                  ║

package/pipeline/skills/figma-ios/REVIEW_CHECKLIST.md

@@ -1,23 +1,23 @@
 # Figma-iOS Skill Review Checklist
 
-> **Status: WIP — v5.0.0 pass 1 (markdown only).** Every skill in this directory was imported from an upstream source via `pipeline/scripts/import-figma-skills.sh`. Placeholders have been applied, personal-data smoke is green, but **no skill is production-ready until it passes this checklist**. Common skills were moved to `pipeline/skills/figma-common/` in WS-7b — only platform-specific skills (orchestrator + implement + test + code-connect + wiki) remain here.
+> **Status: WIP  -  v5.0.0 pass 1 (markdown only).** Every skill in this directory was imported from an upstream source via `pipeline/scripts/import-figma-skills.sh`. Placeholders have been applied, personal-data smoke is green, but **no skill is production-ready until it passes this checklist**. Common skills were moved to `pipeline/skills/figma-common/` in WS-7b  -  only platform-specific skills (orchestrator + implement + test + code-connect + wiki) remain here.
 
 ## Scope of this pass
 
 - ✅ Markdown files transformed: `SKILL.md`, `phases/*.md`, `reference/*.md`, top-level support files (e.g. `halt-return-protocol.md`).
-- ❌ Python/shell scripts **not** imported in this pass — hardcoded paths beyond the placeholder map require manual review. Scheduled for WS-2b.
+- ❌ Python/shell scripts **not** imported in this pass  -  hardcoded paths beyond the placeholder map require manual review. Scheduled for WS-2b.
 
 ## Per-skill review gates
 
 For each skill listed below, a reviewer must confirm:
 
-1. **Frontmatter accuracy** — `description`, `argument-hint`, `allowed-tools`, `user-invocable` reflect the generic behaviour. Remove `status: wip-v5` when passed.
-2. **Placeholder coverage** — run `grep -E '\{(github|jira|repos|build|confluence|project|user)\.' SKILL.md` — every placeholder must resolve from `figma-project-config.schema.json` v2.0.0. Any unresolved placeholder either extends the schema or becomes a literal default.
-3. **No upstream bleed** — `grep -riE 'turkish|dijital|thy\.com|PVT_[A-Za-z0-9]+' skill/` returns nothing. (Guarded by `smoke-personal-data.sh` globally.)
-4. **Cross-references** — internal links point at the new names (no `figma-to-swift-ui-*`). Script references either resolve under `scripts/` once WS-2b lands, or are explicitly commented as TODO.
-5. **Progress-contract adoption** — add the `<!-- progress-contract: applied -->` marker once the skill emits `→ <verb> <object>` lines per `refs/progress-contract.md`.
-6. **Android parity note** — for component-implement/component-test, note which bits are iOS-only so WS-7 can write the Android peer.
-7. **Smoke green** — `smoke-figma-skill-import.sh`, `smoke-personal-data.sh`, `smoke-commands-skills-parity.sh`, `smoke-progress-contract.sh`.
+1. **Frontmatter accuracy**  -  `description`, `argument-hint`, `allowed-tools`, `user-invocable` reflect the generic behaviour. Remove `status: wip-v5` when passed.
+2. **Placeholder coverage**  -  run `grep -E '\{(github|jira|repos|build|confluence|project|user)\.' SKILL.md`  -  every placeholder must resolve from `figma-project-config.schema.json` v2.0.0. Any unresolved placeholder either extends the schema or becomes a literal default.
+3. **No upstream bleed**  -  `grep -riE 'turkish|dijital|thy\.com|PVT_[A-Za-z0-9]+' skill/` returns nothing. (Guarded by `smoke-personal-data.sh` globally.)
+4. **Cross-references**  -  internal links point at the new names (no `figma-to-swift-ui-*`). Script references either resolve under `scripts/` once WS-2b lands, or are explicitly commented as TODO.
+5. **Progress-contract adoption**  -  add the `<!-- progress-contract: applied -->` marker once the skill emits `→ <verb> <object>` lines per `refs/progress-contract.md`.
+6. **Android parity note**  -  for component-implement/component-test, note which bits are iOS-only so WS-7 can write the Android peer.
+7. **Smoke green**  -  `smoke-figma-skill-import.sh`, `smoke-personal-data.sh`, `smoke-commands-skills-parity.sh`, `smoke-progress-contract.sh`.
 
 ## Skills to review (32)
 
@@ -58,10 +58,10 @@ For each skill listed below, a reviewer must confirm:
 
 ## Follow-up workstreams that consume this output
 
-- **WS-2b** — Import Python/shell scripts with transform + manual review.
-- **WS-4** — Reduce Phase 3 dispatch to single `figma-to-component` call.
-- **WS-5** — Wiki mode adapter; update `figma-component-wiki`.
-- **WS-6** — Issue → Jira → Wiki triad; extend `figma-issue` + `figma-component-wiki`.
-- **WS-7** — Android peer skills (`figma-component-implement-android`, `figma-component-test-android`).
-- **WS-8** — Cross-CLI parity matrix expansion.
-- **WS-11** — Add `<!-- progress-contract: applied -->` marker + `→ <verb>` lines to each skill.
+- **WS-2b**  -  Import Python/shell scripts with transform + manual review.
+- **WS-4**  -  Reduce Phase 3 dispatch to single `figma-to-component` call.
+- **WS-5**  -  Wiki mode adapter; update `figma-component-wiki`.
+- **WS-6**  -  Issue → Jira → Wiki triad; extend `figma-issue` + `figma-component-wiki`.
+- **WS-7**  -  Android peer skills (`figma-component-implement-android`, `figma-component-test-android`).
+- **WS-8**  -  Cross-CLI parity matrix expansion.
+- **WS-11**  -  Add `<!-- progress-contract: applied -->` marker + `→ <verb>` lines to each skill.

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.