@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-2b-localization.md

@@ -1,4 +1,4 @@
-# PHASE 2B — Localization Keys
+# PHASE 2B  -  Localization Keys
 
 Localization key integration for 8 languages (ar, de, en, es, fr, it, ru, tr).
 REF: `reference/localization-naming.md`
@@ -118,7 +118,7 @@ REF: `reference/localization-naming.md`
 |------|-------|
 | Key format | PascalCase.Dot.Notation |
 | No unnecessary suffix | No `.Label`, `.Text`, `.Title` unless disambiguation needed |
-| Complete text | No runtime concatenation — display-ready strings |
+| Complete text | No runtime concatenation  -  display-ready strings |
 | Unique per pattern | One key per unique text pattern |
 | Shared texts | Single key for identical text across contexts |
 | Max 5 levels | Key hierarchy depth ≤ 5 |
@@ -175,7 +175,7 @@ or
 | Result | Action |
 |--------|--------|
 | `✅ Key exists` + `Missing: 0` | Mark status: "Existing" |
-| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete" — needs missing language translations |
+| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete"  -  needs missing language translations |
 | `❌ Key not found` | Mark status: "To Add" |
 
 FAIL (tool error) →
@@ -196,7 +196,7 @@ USER_ACTION_REQUIRED: Options:
 
 ## GATE 5: ADD_MISSING_KEYS
 
-**CRITICAL: Always use `TranslationManagerTool add` to add keys — NEVER edit localization JSON files directly. The tool writes to BOTH suggested and merged files atomically. Manual edits cause suggested/merged drift.**
+**CRITICAL: Always use `TranslationManagerTool add` to add keys  -  NEVER edit localization JSON files directly. The tool writes to BOTH suggested and merged files atomically. Manual edits cause suggested/merged drift.**
 
 For each key with status "To Add" or "Incomplete":
 
@@ -313,7 +313,7 @@ Write `{artifactPath}/pass2/utility_localization.json`:
 
 If no localization keys needed, write `{ "localizationKeys": [] }`.
 
-This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON — never the markdown.
+This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON  -  never the markdown.
 
 ### Markdown Artifact (human-readable)
 
@@ -368,7 +368,7 @@ Before marking complete, verify:
 [ ] Key format: PascalCase.Dot.Notation
 [ ] No unnecessary suffixes (.Label, .Text unless needed)
 [ ] All 8 language translations provided (ar, de, en, es, fr, it, ru, tr)
-[ ] No runtime concatenation — display-ready strings only
+[ ] No runtime concatenation  -  display-ready strings only
 [ ] One key per unique text pattern
 [ ] TranslationManagerTool check passes for all keys
 [ ] TranslationMetadataGenerator completed

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-2c-accessibility.md

@@ -1,9 +1,9 @@
-# PHASE 2C — Accessibility Keys
+# PHASE 2C  -  Accessibility Keys
 
 Accessibility key integration for VoiceOver labels, hints, and values.
 REF: `reference/accessibility.md`
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 2A, Phase 2B (all read from pass1/_index.md independently)
 NEXT: Phase 2D (after all parallel phases complete)
 
@@ -18,7 +18,7 @@ Accessibility exists to help vision-impaired people **navigate and use** the app
 - If YES → add it (e.g., a button's purpose, a meaningful image description)
 - If NO → do not add it. You are cluttering the experience with useless noise.
 
-Visual state indicators (colors, gradients, tier badges) are information that sighted users consume visually. A vision-impaired user already knows their own loyalty tier, their own account status, their own membership level. Announcing "Elite" or "Classic Plus" on a profile avatar adds zero navigational or functional value — it is noise.
+Visual state indicators (colors, gradients, tier badges) are information that sighted users consume visually. A vision-impaired user already knows their own loyalty tier, their own account status, their own membership level. Announcing "Elite" or "Classic Plus" on a profile avatar adds zero navigational or functional value  -  it is noise.
 
 Do NOT generate per-enum-variant accessibility keys for state that the user already knows or that adds no navigational value. An avatar is "Passenger avatar". A status badge with visible text is just the text. A colored indicator is decorative context, not actionable information.
 
@@ -28,13 +28,13 @@ VoiceOver reads the accessibility tree, NOT the view tree. SwiftUI builds this t
 
 1. **`Text("Hello")` is already accessible.** VoiceOver reads "Hello" with no modifiers. SwiftUI knows it's static text. Adding `.accessibilityLabel("Hello")` duplicates what's already there. Adding `.accessibilityAddTraits(.isStaticText)` adds a trait SwiftUI already assigned.
 
-2. **`Button("Save") { ... }` is already accessible.** VoiceOver reads "Save, Button" — the label AND the trait. Adding `.accessibilityLabel("Save")` or `.accessibilityAddTraits(.isButton)` is redundant.
+2. **`Button("Save") { ... }` is already accessible.** VoiceOver reads "Save, Button"  -  the label AND the trait. Adding `.accessibilityLabel("Save")` or `.accessibilityAddTraits(.isButton)` is redundant.
 
 3. **`Image(decorative: "bg")` is already hidden.** No modifier needed.
 
-4. **`.accessibilityElement(children: .combine)` merges children.** If an HStack contains `Image` + `Text("Confirmed")`, combining them makes VoiceOver read "Confirmed" as one stop — because SwiftUI concatenates the accessible text of all non-hidden children. You do NOT need `.accessibilityLabel("Confirmed")` on top of this — SwiftUI already reads the `Text`.
+4. **`.accessibilityElement(children: .combine)` merges children.** If an HStack contains `Image` + `Text("Confirmed")`, combining them makes VoiceOver read "Confirmed" as one stop  -  because SwiftUI concatenates the accessible text of all non-hidden children. You do NOT need `.accessibilityLabel("Confirmed")` on top of this  -  SwiftUI already reads the `Text`.
 
-5. **`.accessibilityLabel` OVERRIDES, it does not supplement.** When you add `.accessibilityLabel("Confirmed, Success")` to a combined element, VoiceOver reads ONLY "Confirmed, Success" — it ignores the children's text. This is useful when children text is wrong or insufficient. It is HARMFUL when children text is already correct, because now you're maintaining a redundant string.
+5. **`.accessibilityLabel` OVERRIDES, it does not supplement.** When you add `.accessibilityLabel("Confirmed, Success")` to a combined element, VoiceOver reads ONLY "Confirmed, Success"  -  it ignores the children's text. This is useful when children text is wrong or insufficient. It is HARMFUL when children text is already correct, because now you're maintaining a redundant string.
 
 ### When to add NOTHING
 
@@ -45,7 +45,7 @@ If a component is:
 
 Then you need ZERO accessibility modifiers on the container. Maybe `.accessibilityElement(children: .combine)` to group children into one stop. That's it. No `.accessibilityLabel`. No `.accessibilityAddTraits`. No `.accessibilityRemoveTraits`. No `.accessibilityHint`.
 
-A non-interactive badge that shows "Confirmed" in green does NOT need `.accessibilityLabel("Confirmed, Success")`. The user hears "Confirmed" — that's sufficient. "Success" is a visual color cue, not information the VoiceOver user needs or cares about.
+A non-interactive badge that shows "Confirmed" in green does NOT need `.accessibilityLabel("Confirmed, Success")`. The user hears "Confirmed"  -  that's sufficient. "Success" is a visual color cue, not information the VoiceOver user needs or cares about.
 
 ### The question to ask for EVERY modifier
 
@@ -62,7 +62,7 @@ If removing a modifier changes nothing, the modifier should not exist.
 
 1. **Does the component need ANY accessibility work?** If SwiftUI reads it correctly as-is → add NOTHING.
 2. **Are there decorative elements?** → `.accessibilityHidden(true)` on those elements only.
-3. **Should children be grouped?** → `.accessibilityElement(children: .combine)` — then STOP. SwiftUI reads the combined text.
+3. **Should children be grouped?** → `.accessibilityElement(children: .combine)`  -  then STOP. SwiftUI reads the combined text.
 4. **Is the combined text wrong or missing?** → ONLY then add `.accessibilityLabel` with the correct text.
 5. **Is there interactive state VoiceOver can't infer?** (custom toggle, not SwiftUI Toggle) → `.accessibilityValue`.
 6. **Is there a trait SwiftUI can't infer?** (custom tappable view, not Button) → `.accessibilityAddTraits`.
@@ -76,12 +76,12 @@ Most components stop at step 2 or 3. If you reach step 4+, justify WHY in the ar
 |---|---|
 | Adding `.isButton` to a `Button` | SwiftUI already provides it |
 | Adding `.isStaticText` to a `Text` | SwiftUI already provides it |
-| `.accessibilityRemoveTraits(.isButton)` when no Button exists | Removing a trait that was never there — nonsensical |
+| `.accessibilityRemoveTraits(.isButton)` when no Button exists | Removing a trait that was never there  -  nonsensical |
 | `.accessibilityLabel` that duplicates visible text | Overrides SwiftUI's correct reading with a redundant string you now maintain |
 | `.accessibilityLabel("\(text), \(state.rawValue)")` on a non-interactive badge | State name ("Success") is a color cue, not information. VoiceOver user doesn't need it |
 | Adding accessibility modifiers "just in case" | Every modifier is code to maintain. If it adds no value, it adds cost |
-| Labeling every child in a group | VoiceOver stops at each child separately — use `.accessibilityElement(children: .combine)` |
-| Separate key per enum variant | Key bloat — 5+ keys for trivially translatable names |
+| Labeling every child in a group | VoiceOver stops at each child separately  -  use `.accessibilityElement(children: .combine)` |
+| Separate key per enum variant | Key bloat  -  5+ keys for trivially translatable names |
 | `.accessibilityHint` when label is self-explanatory | "Close" button doesn't need hint "Closes this dialog" |
 
 ---
@@ -143,7 +143,7 @@ Only add traits SwiftUI cannot infer. Do NOT add `.isButton` to `Button`, `.isSt
 
 | Rule | Implementation |
 |------|----------------|
-| Add nothing unless it breaks without it | Ask "what breaks if I remove this?" — if nothing, don't add it |
+| Add nothing unless it breaks without it | Ask "what breaks if I remove this?"  -  if nothing, don't add it |
 | No redundant labels | Don't add `.accessibilityLabel` when SwiftUI reads visible text correctly |
 | No redundant traits | Don't add `.isStaticText` to `Text`, `.isButton` to `Button` |
 | No phantom trait removal | Don't `.accessibilityRemoveTraits(.isButton)` when no Button exists |
@@ -151,7 +151,7 @@ Only add traits SwiftUI cannot infer. Do NOT add `.isButton` to `Button`, `.isSt
 | No "button" in label | Trait handles it |
 | No "tap to" in hint | VoiceOver adds "double tap to" |
 | No hint for obvious actions | "Close" button needs no hint |
-| Group related content | `.accessibilityElement(children: .combine)` — then STOP |
+| Group related content | `.accessibilityElement(children: .combine)`  -  then STOP |
 | Hide decorative | `.accessibilityHidden(true)` |
 | One stop per logical element | Group children, don't label each |
 
@@ -164,7 +164,7 @@ tools (Accessibility Inspector, XCUITest). The cascading `UIIdentifierContext`
 ensures each component instance is uniquely identifiable even when the same
 component appears multiple times on a screen.
 
-VoiceOver `.accessibilityLabel` does NOT cascade — labels are human-readable and
+VoiceOver `.accessibilityLabel` does NOT cascade  -  labels are human-readable and
 SwiftUI handles grouping/container semantics naturally via
 `.accessibilityElement(children: .combine)`.
 
@@ -248,16 +248,16 @@ SCAN for accessibility-relevant elements. For each, ask: **does this need a key,
 |-----------------|------|------------------|
 | Button (SwiftUI `Button`) | Hint only if ambiguous | Skip label if button text is visible. Skip hint if action is obvious from label. |
 | Button (custom tappable) | Label + maybe Hint | Skip hint if label makes action clear (e.g., "Close" needs no hint) |
-| Image (meaningful) | Label | — |
-| Image (decorative) | NONE | `.accessibilityHidden(true)` — no key |
+| Image (meaningful) | Label |  -  |
+| Image (decorative) | NONE | `.accessibilityHidden(true)`  -  no key |
 | Input field | Label | Skip if placeholder text serves as label |
 | Toggle/checkbox (interactive) | Value keys | Use `.Selected`/`.NotSelected` for state. Skip label if toggle text is visible. |
-| List item | NONE usually | Skip — use `.accessibilityElement(children: .combine)` to group child content |
-| Header text | NONE | Skip — use `.accessibilityAddTraits(.isHeader)` on the `Text` view, no key needed |
-| Close/dismiss button | Label only | Skip hint — "Close" is self-explanatory |
-| Grouped content | NONE | `.accessibilityElement(children: .combine)` — SwiftUI combines child text |
+| List item | NONE usually | Skip  -  use `.accessibilityElement(children: .combine)` to group child content |
+| Header text | NONE | Skip  -  use `.accessibilityAddTraits(.isHeader)` on the `Text` view, no key needed |
+| Close/dismiss button | Label only | Skip hint  -  "Close" is self-explanatory |
+| Grouped content | NONE | `.accessibilityElement(children: .combine)`  -  SwiftUI combines child text |
 | Static text | NONE | SwiftUI reads `Text` content automatically |
-| Variant state (non-interactive) | NONE | Evaluate through GATE 2B. No `.accessibilityLabel` needed — `.accessibilityElement(children: .combine)` reads visible text |
+| Variant state (non-interactive) | NONE | Evaluate through GATE 2B. No `.accessibilityLabel` needed  -  `.accessibilityElement(children: .combine)` reads visible text |
 | Variant state (interactive) | Value keys | Only for toggles/selections where state changes via user action |
 
 Use `screenshot_response.md` to cross-reference:
@@ -266,7 +266,7 @@ Use `screenshot_response.md` to cross-reference:
 - Whether grouped content should be combined
 
 Use `component_properties.json` to identify:
-- Boolean properties → value states (`.Selected`, `.NotSelected`) — only if interactive
+- Boolean properties → value states (`.Selected`, `.NotSelected`)  -  only if interactive
 - Variant properties → evaluate through GATE 2B
 
 OUTPUT: List of `{ key, purpose, label_en, label_tr }`, filtered through GATE 2B.
@@ -288,7 +288,7 @@ For each variant property or boolean property identified in GATE 2, evaluate whe
    - NO → Continue to step 3
 
 3. **Is this a non-interactive display component?** (Badge, Tag, Chip, Status indicator, Label)
-   - YES → Skip state value keys. Do NOT add `.accessibilityLabel` — use `.accessibilityElement(children: .combine)` only. SwiftUI reads visible text naturally. Visual state (color) is not relevant to VoiceOver.
+   - YES → Skip state value keys. Do NOT add `.accessibilityLabel`  -  use `.accessibilityElement(children: .combine)` only. SwiftUI reads visible text naturally. Visual state (color) is not relevant to VoiceOver.
    - NO → Continue to step 4
 
 4. **Can the state be derived from an enum at runtime?**
@@ -304,9 +304,9 @@ Skip generating separate `.accessibilityValue` state keys when ALL of these are
 4. Visible text or label already provides sufficient context
 
 Instead, recommend in the artifact:
-- Use `.accessibilityElement(children: .combine)` — SwiftUI reads visible text
-- Do NOT add `.accessibilityLabel` with state name — visual state is irrelevant to VoiceOver for non-interactive components
-- Do NOT add `.accessibilityAddTraits(.isStaticText)` — SwiftUI already knows `Text` is static text
+- Use `.accessibilityElement(children: .combine)`  -  SwiftUI reads visible text
+- Do NOT add `.accessibilityLabel` with state name  -  visual state is irrelevant to VoiceOver for non-interactive components
+- Do NOT add `.accessibilityAddTraits(.isStaticText)`  -  SwiftUI already knows `Text` is static text
 
 ### Example: LabelBadge (non-interactive badge)
 
@@ -318,7 +318,7 @@ Evaluation:
 - Step 3: IS a display component (Badge) → Skip
 
 Result: Do NOT generate `LabelBadge.SuccessState`, `LabelBadge.WarningState`, etc.
-Recommend: `.accessibilityElement(children: .combine)` only — no custom `.accessibilityLabel`. Badge text is read naturally by SwiftUI.
+Recommend: `.accessibilityElement(children: .combine)` only  -  no custom `.accessibilityLabel`. Badge text is read naturally by SwiftUI.
 
 OUTPUT: Updated keys list with state keys filtered. Include skipped keys in artifact.
 
@@ -376,7 +376,7 @@ or
 | Result | Action |
 |--------|--------|
 | `✅ Key exists` + `Missing: 0` | Mark status: "Existing" |
-| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete" — needs missing language translations |
+| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete"  -  needs missing language translations |
 | `❌ Key not found` | Mark status: "To Add" |
 
 FAIL (tool error) →
@@ -512,7 +512,7 @@ Write `{artifactPath}/pass2/utility_accessibility.json`:
 
 If no accessibility keys needed, write `{ "accessibilityKeys": [] }`.
 
-This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON — never the markdown.
+This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON  -  never the markdown.
 
 ### Markdown Artifact (human-readable)
 
@@ -540,13 +540,13 @@ Only keys that passed the necessity filter. If this table is empty, the componen
 
 ## Implementation
 
-Show ONLY the modifiers this specific component actually needs. Do NOT include patterns the component doesn't use. If a component needs no accessibility modifiers beyond what SwiftUI provides, say so explicitly — an empty Implementation section is a VALID output.
+Show ONLY the modifiers this specific component actually needs. Do NOT include patterns the component doesn't use. If a component needs no accessibility modifiers beyond what SwiftUI provides, say so explicitly  -  an empty Implementation section is a VALID output.
 
 Ask for EVERY modifier: **"What breaks if I remove this?"** If the answer is "nothing", do not include it.
 
 ```swift
 // EXAMPLE: Non-interactive display component (Badge, Tag, Chip)
-// SwiftUI reads Text content automatically — NO custom label needed
+// SwiftUI reads Text content automatically  -  NO custom label needed
 
 // Decorative element → hide
 iconView
@@ -574,13 +574,13 @@ Before marking complete, verify:
 
 ```
 MINIMALISM CHECKS (do these FIRST):
-[ ] Every modifier justified — no modifier added that SwiftUI already handles
-[ ] No redundant traits — .isButton not added to Button, .isStaticText not added to Text
-[ ] No unnecessary hints — obvious actions (Close, Back, Delete) have no hint
-[ ] No unnecessary labels — visible text not repeated in .accessibilityLabel
-[ ] No unnecessary keys — runtime strings used where possible instead of LocalizedAccessibilityStringKey
-[ ] Grouped content — related children combined into ONE VoiceOver stop, not labeled individually
-[ ] State keys evaluated through GATE 2B — non-interactive states use runtime pattern
+[ ] Every modifier justified  -  no modifier added that SwiftUI already handles
+[ ] No redundant traits  -  .isButton not added to Button, .isStaticText not added to Text
+[ ] No unnecessary hints  -  obvious actions (Close, Back, Delete) have no hint
+[ ] No unnecessary labels  -  visible text not repeated in .accessibilityLabel
+[ ] No unnecessary keys  -  runtime strings used where possible instead of LocalizedAccessibilityStringKey
+[ ] Grouped content  -  related children combined into ONE VoiceOver stop, not labeled individually
+[ ] State keys evaluated through GATE 2B  -  non-interactive states use runtime pattern
 [ ] Each logical element = one VoiceOver announcement (not multiple stops)
 
 CORRECTNESS CHECKS:

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-2d-analytics.md

@@ -1,4 +1,4 @@
-# PHASE 2D — Analytics Events
+# PHASE 2D  -  Analytics Events
 
 Analytics event integration using `UIComponentUtilities` view modifiers.
 REF: `reference/analytics-events.md`
@@ -57,7 +57,7 @@ Extensions: `Sources/UIComponentUtilities/Analytics/`
 Read: {artifactPath}/pass1/_index.md
 Read: {artifactPath}/pass1/design_context_response.json
 Read: {artifactPath}/pass1/component_properties.json
-Read: {artifactPath}/pass2/utility_identifiers.md    # From Phase 2A — use as event IDs
+Read: {artifactPath}/pass2/utility_identifiers.md    # From Phase 2A  -  use as event IDs
 Read: {artifactPath}/IMPLEMENTATION_HISTORY.md
 ```
 
@@ -164,7 +164,7 @@ Write `{artifactPath}/pass2/utility_analytics.json`:
 
 If no analytics events needed, write `{ "analyticsEvents": [] }`.
 
-This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON — never the markdown.
+This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON  -  never the markdown.
 
 ### Markdown Artifact (human-readable)
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-3-orchestrator.md

@@ -1,4 +1,4 @@
-# PHASE 3 — Data Analysis Orchestrator
+# PHASE 3  -  Data Analysis Orchestrator
 
 Orchestrates Phase 3 sub-phases: dispatches sub-agents, collects results, writes pass3/_index.md.
 PREV: Phase 2 (Utility Integration)
@@ -63,9 +63,9 @@ Check the JSON structure:
 
 | Format | Detection | Action |
 |--------|-----------|--------|
-| Normal | `sublayers` is `false` or absent | No action needed — `response` field exists |
+| Normal | `sublayers` is `false` or absent | No action needed  -  `response` field exists |
 | Sublayer | `sublayers` is `true` | Concatenate all `responses` values (see below) |
-| Already normalized | `sublayers` is `true` AND `response` field exists | No action needed — Phase 2 already normalized |
+| Already normalized | `sublayers` is `true` AND `response` field exists | No action needed  -  Phase 2 already normalized |
 
 ### Sublayer normalization (if not already done by Phase 2)
 
@@ -77,7 +77,7 @@ If `sublayers: true` and no `response` field:
 4. Keep the original `sublayers`, `sublayerNodeIds`, and `responses` fields intact (for traceability)
 5. Write the updated JSON back to `{artifactPath}/pass1/design_context_response.json`
 
-After normalization, all sub-phases read the `response` field as usual — no sublayer awareness needed.
+After normalization, all sub-phases read the `response` field as usual  -  no sublayer awareness needed.
 
 ---
 
@@ -103,7 +103,7 @@ PRE-CHECK
 NORMALIZE_DESIGN_CONTEXT
     ↓
 ┌──────────────────────────────────────────────────┐
-│  WAVE 1 — PARALLEL                               │
+│  WAVE 1  -  PARALLEL                               │
 │                                                  │
 │  Scripts (Bash, ~5s):                            │
 │   python3 scripts/phase3-scripts.py wave1        │
@@ -112,15 +112,15 @@ NORMALIZE_DESIGN_CONTEXT
 │     → 3F Utility Integration                     │
 │                                                  │
 │  AI Agents (parallel sub-agents):                │
-│   3A — Component Location          ← required   │
-│   3C — Nested Components           ← required   │
-│   3D — Patterns + Architecture     ← required   │
+│   3A  -  Component Location          ← required   │
+│   3C  -  Nested Components           ← required   │
+│   3D  -  Patterns + Architecture     ← required   │
 │                                                  │
 └──────────────────────────────────────────────────┘
     ↓ wait for all to complete
     ↓
 ┌──────────────────────────────────────────────────┐
-│  WAVE 2 — SEQUENTIAL (depends on 3D output)      │
+│  WAVE 2  -  SEQUENTIAL (depends on 3D output)      │
 │                                                  │
 │  Script (Bash, ~1s):                             │
 │   python3 scripts/phase3-scripts.py 3g           │
@@ -151,7 +151,7 @@ python3 {skillPath}/scripts/phase3-scripts.py wave1 --artifact-path {artifactPat
 This runs 3B, 3E, 3F sequentially (~5-10s total). The script handles skip conditions for 3E automatically.
 
 AI Agents (sub-agents in parallel):
-- 3A, 3C, 3D — each reads from `pass1/` artifacts independently.
+- 3A, 3C, 3D  -  each reads from `pass1/` artifacts independently.
 - `design_context_response.json` is already normalized (flat `response` field) by NORMALIZE_DESIGN_CONTEXT.
 - Each writes its own file to `pass3/`.
 - Wait for ALL (scripts + agents) to complete before Wave 2.
@@ -168,7 +168,7 @@ python3 {skillPath}/scripts/phase3-scripts.py 3g --artifact-path {artifactPath}
 
 | Sub-phase | Skip when |
 |-----------|-----------|
-| 3E | No `pass1/design_context_assets.txt` exists or file is empty (handled by script — writes placeholder automatically) |
+| 3E | No `pass1/design_context_assets.txt` exists or file is empty (handled by script  -  writes placeholder automatically) |
 
 ---
 
@@ -180,11 +180,11 @@ After all sub-phases complete, verify each produced its artifact:
 [ ] pass3/01_component_location.md exists (Phase 3A)
 [ ] pass3/02_token_mapping.md exists (Phase 3B)
 [ ] pass3/03_nested_components.md exists (Phase 3C)
-[ ] pass3/04_patterns.md exists (Phase 3D — patterns section)
-[ ] pass3/04b_component_architecture.md exists (Phase 3D — architecture section)
-[ ] pass3/04b_component_architecture.json exists (Phase 3D — structured, for 3G script)
-[ ] pass3/05_complexity.md exists (Phase 3D — complexity section)
-[ ] pass3/06_assets.md exists (Phase 3E — or skipped placeholder)
+[ ] pass3/04_patterns.md exists (Phase 3D  -  patterns section)
+[ ] pass3/04b_component_architecture.md exists (Phase 3D  -  architecture section)
+[ ] pass3/04b_component_architecture.json exists (Phase 3D  -  structured, for 3G script)
+[ ] pass3/05_complexity.md exists (Phase 3D  -  complexity section)
+[ ] pass3/06_assets.md exists (Phase 3E  -  or skipped placeholder)
 [ ] pass3/08_utility_integration.md exists (Phase 3F)
 [ ] pass3/00_property_coverage.json exists (Phase 3G)
 ```
@@ -214,7 +214,7 @@ The script reads `04b_component_architecture.json`, `00_property_coverage.json`,
 | Result | Action |
 |--------|--------|
 | Exit 0 | Proceed to GATE 3 |
-| Exit 1 | HALT — missing required input files |
+| Exit 1 | HALT  -  missing required input files |
 
 ---
 
@@ -243,7 +243,7 @@ Append to `{artifactPath}/IMPLEMENTATION_HISTORY.md`:
 Write `{artifactPath}/pass3/_index.md`:
 
 ```markdown
-# Pass 3 — Analysis Output
+# Pass 3  -  Analysis Output
 
 Component: {componentName}
 Generated: {ISO_DATE}
@@ -291,7 +291,7 @@ Utility integration: `pass3/08_utility_integration.md`
 [ ] 06_assets.md exists (or skipped placeholder)
 [ ] 07_implementation_spec.md written by spec script (NOT by orchestrator reading files)
 [ ] 08_utility_integration.md exists
-[ ] 00_property_coverage.json exists (Phase 3G — all properties have IMPLEMENT/SKIP/DEFER status)
+[ ] 00_property_coverage.json exists (Phase 3G  -  all properties have IMPLEMENT/SKIP/DEFER status)
 [ ] IMPLEMENTATION_HISTORY.md updated with Phase 3 summary
 [ ] pass3/_index.md written listing ALL pass3 files
 ```
@@ -305,16 +305,16 @@ STATUS: COMPLETE
 PHASE: phase-3
 GATES_PASSED: [PRE_CHECK, NORMALIZE_DESIGN_CONTEXT, DISPATCH_WAVE_1, DISPATCH_WAVE_2, COLLECT_RESULTS, WRITE_IMPLEMENTATION_SPEC, UPDATE_IMPLEMENTATION_HISTORY, WRITE_PASS3_INDEX]
 ARTIFACTS_CREATED:
-  - {artifactPath}/pass3/01_component_location.md (via Phase 3A — AI agent)
-  - {artifactPath}/pass3/02_token_mapping.md (via Phase 3B — script)
-  - {artifactPath}/pass3/03_nested_components.md (via Phase 3C — AI agent)
-  - {artifactPath}/pass3/04_patterns.md (via Phase 3D — AI agent)
-  - {artifactPath}/pass3/04b_component_architecture.md (via Phase 3D — AI agent)
-  - {artifactPath}/pass3/04b_component_architecture.json (via Phase 3D — AI agent)
-  - {artifactPath}/pass3/05_complexity.md (via Phase 3D — AI agent)
-  - {artifactPath}/pass3/06_assets.md (via Phase 3E — script)
-  - {artifactPath}/pass3/08_utility_integration.md (via Phase 3F — script)
-  - {artifactPath}/pass3/00_property_coverage.json (via Phase 3G — script)
+  - {artifactPath}/pass3/01_component_location.md (via Phase 3A  -  AI agent)
+  - {artifactPath}/pass3/02_token_mapping.md (via Phase 3B  -  script)
+  - {artifactPath}/pass3/03_nested_components.md (via Phase 3C  -  AI agent)
+  - {artifactPath}/pass3/04_patterns.md (via Phase 3D  -  AI agent)
+  - {artifactPath}/pass3/04b_component_architecture.md (via Phase 3D  -  AI agent)
+  - {artifactPath}/pass3/04b_component_architecture.json (via Phase 3D  -  AI agent)
+  - {artifactPath}/pass3/05_complexity.md (via Phase 3D  -  AI agent)
+  - {artifactPath}/pass3/06_assets.md (via Phase 3E  -  script)
+  - {artifactPath}/pass3/08_utility_integration.md (via Phase 3F  -  script)
+  - {artifactPath}/pass3/00_property_coverage.json (via Phase 3G  -  script)
   - {artifactPath}/pass3/07_implementation_spec.md (orchestrator)
   - {artifactPath}/pass3/_index.md
 SUMMARY: Data analysis complete. {TOTAL_FILES} analysis files created. Complexity: {SIMPLE/COMPLEX}. {MAPPED}/{TOTAL} tokens mapped. {CONNECTED}/{TOTAL} nested components connected. Ready for Phase 4.

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-3a-location.md

@@ -1,9 +1,9 @@
-# PHASE 3A — Component Location Resolution
+# PHASE 3A  -  Component Location Resolution
 
 Resolve component name, implementation path, and artifact path.
 Uses user input (priority) and registry lookup (fallback).
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 3B, 3C, 3D, 3E, 3F (all read from pass1/ independently)
 
 ---
@@ -67,7 +67,7 @@ componentName = userProvidedName ?? suggestedComponentName
 
 # 2. Build the folder path. Take whichever location source is available,
 #    strip its last segment, and append the resolved componentName.
-#    This guarantees the folder tail always equals componentName —
+#    This guarantees the folder tail always equals componentName  - 
 #    a name override automatically propagates into the folder.
 componentLocation = dirname(userProvidedLocation ?? suggestedComponentLocation) + "/" + componentName
 
@@ -87,7 +87,7 @@ ALL THREE must be resolved:
 ALSO (structural invariant): `basename(componentLocation) == componentName`.
 The last path segment of `componentLocation` MUST equal `componentName` exactly.
 If they differ, HALT with `NEEDS_INPUT` asking the user to reconcile name vs.
-location — do NOT proceed with a mismatched folder/type pair.
+location  -  do NOT proceed with a mismatched folder/type pair.
 
 FAIL (any missing or invariant violated) →
 
@@ -104,7 +104,7 @@ QUESTION: Cannot determine component name and/or implementation location. Please
 OPTIONS:
   1) Provide component name and location manually
   2) Update registry with correct mapping and retry
-SUGGESTED: Option 1 — provide manually.
+SUGGESTED: Option 1  -  provide manually.
 COMPLETED_GATES: [PRE_CHECK, RESOLVE_COMPONENT_NAME_AND_LOCATION]
 CONTEXT:
   From registry: name={suggestedComponentName or "not found"}, location={suggestedComponentLocation or "not found"}
@@ -136,7 +136,7 @@ OPTIONS:
   1) Override existing (delete and recreate)
   2) Choose different name
   3) Merge with existing (update files)
-SUGGESTED: Option 3 — merge with existing. Existing files will be updated, new files added.
+SUGGESTED: Option 3  -  merge with existing. Existing files will be updated, new files added.
 COMPLETED_GATES: [PRE_CHECK, RESOLVE_COMPONENT_NAME_AND_LOCATION, VALIDATE_RESOLUTION]
 CONTEXT:
   Path: {componentLocation}

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-3b-tokens.md

@@ -1,9 +1,9 @@
-# PHASE 3B — Variable Token Mapping
+# PHASE 3B  -  Variable Token Mapping
 
 Map Figma design variables to Swift design tokens.
 Translates colors, spacing, typography, and images from Figma variable names to Swift usage patterns.
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 3A, 3C, 3D, 3E, 3F (all read from pass1/ independently)
 
 ---
@@ -100,7 +100,7 @@ Map each resolved token to its Swift usage pattern:
 
 ### Typography dual usage
 
-Typography tokens have two usage modes — include BOTH in the output:
+Typography tokens have two usage modes  -  include BOTH in the output:
 
 **1. Typography modifier (for Text views with full style):**
 ```swift

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-3c-nested.md

@@ -1,9 +1,9 @@
-# PHASE 3C — Nested Component Resolution
+# PHASE 3C  -  Nested Component Resolution
 
 Resolve nested/child components referenced by this component.
 Reads FIGMA.md from connected components to extract init signatures and usage patterns.
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 3A, 3B, 3D, 3E, 3F (all read from pass1/ independently)
 
 ---
@@ -62,8 +62,8 @@ Also scan `design_context_response.json` for components that appear in the desig
 - Look for instance references in the Figma design context code
 
 OUTPUT: Two lists:
-1. **Connected** — in code_connect_map with source path
-2. **Unconnected** — referenced in design but NOT in code_connect_map
+1. **Connected**  -  in code_connect_map with source path
+2. **Unconnected**  -  referenced in design but NOT in code_connect_map
 
 If NO nested components found (component is self-contained):
 - Write artifact noting "No nested components"
@@ -83,14 +83,14 @@ For example, if codeConnectSrc is `Sources/UIComponents/Components/Buttons/TextL
 `Sources/UIComponents/Components/Buttons/TextLink/FIGMA.md`
 
 EXTRACT from each FIGMA.md:
-- **Init signature** — the public init with parameter names and types
-- **Variant mapping** — how Figma variants map to Swift properties
-- **First usage example** — the recommended integration pattern
+- **Init signature**  -  the public init with parameter names and types
+- **Variant mapping**  -  how Figma variants map to Swift properties
+- **First usage example**  -  the recommended integration pattern
 
 If FIGMA.md does not exist for a connected component:
 - Read the Swift source file directly
 - Extract the public init from the source code
-- Mark as "No FIGMA.md — signature from source"
+- Mark as "No FIGMA.md  -  signature from source"
 
 ---
 
@@ -113,8 +113,8 @@ QUESTION: {COUNT} nested component(s) not found in Code Connect. These are used
 OPTIONS:
   1) Implement dependencies first (pause this component)
   2) Continue without (will need manual implementation inline or stub)
-  3) These are not real dependencies — ignore them
-SUGGESTED: Option 2 — continue. Unconnected components will be documented for later implementation.
+  3) These are not real dependencies  -  ignore them
+SUGGESTED: Option 2  -  continue. Unconnected components will be documented for later implementation.
 COMPLETED_GATES: [PRE_CHECK, EXTRACT_NESTED_COMPONENTS, READ_FIGMA_MD]
 CONTEXT:
   Unconnected components:
@@ -166,9 +166,9 @@ LabelBadge(text: statusText, state: .success)
 
 | Component | Figma Node | Resolution |
 |-----------|-----------|------------|
-| CustomIcon | 789:012 | Continue without — will implement inline |
+| CustomIcon | 789:012 | Continue without  -  will implement inline |
 
-OR: None — all nested components are connected.
+OR: None  -  all nested components are connected.
 
 ## Inline Components