@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

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

@@ -11,7 +11,7 @@
 ### 1.2 CLI Installation
 Two options:
 - Global: `npm install --global @figma/code-connect@latest` then `figma connect <cmd>`
-- No-install (npx): `npx @figma/code-connect@latest connect <cmd>` — recommended for CI/CD and machines without global install
+- No-install (npx): `npx @figma/code-connect@latest connect <cmd>`  -  recommended for CI/CD and machines without global install
 - Local dependency: if `@figma/code-connect` is a package dependency, just use `npx figma connect <cmd>` from the package root
 
 Current installed version: 1.3.12 (latest available: 1.4.1)
@@ -20,7 +20,7 @@ Current installed version: 1.3.12 (latest available: 1.4.1)
 ```swift
 .package(url: "https://github.com/figma/code-connect", from: "1.2.0")
 ```
-Product: "Figma" library — provides property wrappers only. CLI is npm-based, NOT from SPM.
+Product: "Figma" library  -  provides property wrappers only. CLI is npm-based, NOT from SPM.
 
 ### 1.4 Configuration (figma.config.json)
 ```json
@@ -67,7 +67,7 @@ Component/
 └── FIGMA.md
 ```
 
-### 2.3 Template — Static (No Figma Properties)
+### 2.3 Template  -  Static (No Figma Properties)
 ```swift
 import Figma
 import SwiftUI
@@ -82,7 +82,7 @@ struct ComponentNameFigmaConnect: FigmaConnect {
 }
 ```
 
-### 2.4 Template — Mapped Properties
+### 2.4 Template  -  Mapped Properties
 ```swift
 import Figma
 import SwiftUI
@@ -112,7 +112,7 @@ struct ComponentNameFigmaConnect: FigmaConnect {
 }
 ```
 
-### 2.5 Template — Multi-Variant (string enum)
+### 2.5 Template  -  Multi-Variant (string enum)
 ```swift
 struct PrimaryButtonFigmaConnect: FigmaConnect {
     let component = Button.self
@@ -129,7 +129,7 @@ struct SecondaryButtonFigmaConnect: FigmaConnect {
 }
 ```
 
-### 2.6 Template — Multi-Variant (boolean gate)
+### 2.6 Template  -  Multi-Variant (boolean gate)
 Use a computed `var variant` property when matching on a boolean toggle (e.g., "Label" on/off):
 ```swift
 // Default struct (Label = true, the default)
@@ -150,8 +150,8 @@ struct LabelBadgeIconOnlyFigmaConnect: FigmaConnect {
 ```
 Figma shows the most specific matching struct. When "Label" is toggled off, the icon-only struct renders.
 
-### 2.7 Template — Icon/Symbol (no component)
-For simple icon nodes without component properties — no `let component`, no property wrappers:
+### 2.7 Template  -  Icon/Symbol (no component)
+For simple icon nodes without component properties  -  no `let component`, no property wrappers:
 ```swift
 struct PlusCircleFillIconConnect: FigmaConnect {
     let figmaNodeUrl = "https://figma.com/design/FILE_KEY/?node-id=X-Y"
@@ -182,25 +182,25 @@ var leftIcon: Image? = nil
 ```
 When `hideDefault: true` and value is `nil` (default), the `.leftIcon(...)` line is omitted from the snippet entirely.
 
-**IMPORTANT — hideDefault default value trap:** When using `hideDefault: true` with a mapping, the **default value** determines which mapped result gets hidden. Set the default to the value you want HIDDEN (typically `nil` for optionals):
+**IMPORTANT  -  hideDefault default value trap:** When using `hideDefault: true` with a mapping, the **default value** determines which mapped result gets hidden. Set the default to the value you want HIDDEN (typically `nil` for optionals):
 
 ```swift
-// CORRECT — default=nil: Text=true shows .initials("BT"), Text=false hides it
+// CORRECT  -  default=nil: Text=true shows .initials("BT"), Text=false hides it
 @FigmaBoolean("Text", mapping: [true: "BT", false: nil], hideDefault: true)
 var initials: String? = nil
 
-// WRONG — default="BT": Text=true HIDES .initials("BT"), Text=false shows .initials(nil)
+// WRONG  -  default="BT": Text=true HIDES .initials("BT"), Text=false shows .initials(nil)
 @FigmaBoolean("Text", mapping: [true: "BT", false: nil], hideDefault: true)
 var initials: String? = "BT"  // ← "BT" matches default, so it's hidden!
 ```
 
-### @FigmaEnum — prefer implicit shorthand
+### @FigmaEnum  -  prefer implicit shorthand
 Use `.success` instead of `LabelBadgeConfiguration.LabelBadgeState.success` in mappings. The parser captures the expression as-is via `trimmedDescription`, so shorter values produce cleaner snippets:
 ```swift
-// GOOD — clean snippet output
+// GOOD  -  clean snippet output
 @FigmaEnum("State", mapping: ["Success": .success, "Warning": .warning])
 
-// BAD — verbose snippet output
+// BAD  -  verbose snippet output
 @FigmaEnum("State", mapping: ["Success": LabelBadgeConfiguration.LabelBadgeState.success])
 ```
 
@@ -223,9 +223,9 @@ When a designer swaps the icon instance in Figma, Dev Mode renders that specific
 - Useful when the instance swap is always visible and you want the swapped component's Code Connect to render inline.
 
 ### figmaApply
-Conditionally applies view modifiers based on a boolean condition. In Dev Mode, Figma only shows the branch that matches the current property value — keeping snippets clean.
+Conditionally applies view modifiers based on a boolean condition. In Dev Mode, Figma only shows the branch that matches the current property value  -  keeping snippets clean.
 
-**Basic — show modifier only when true:**
+**Basic  -  show modifier only when true:**
 ```swift
 @FigmaBoolean("Disabled", hideDefault: true)
 var disabled: Bool = false
@@ -237,7 +237,7 @@ var body: some View {
 ```
 When `Disabled = false` (default + hideDefault), nothing renders. When `Disabled = true`, snippet shows `.opacity(0.5)`.
 
-**With elseApply — different modifiers per branch:**
+**With elseApply  -  different modifiers per branch:**
 ```swift
 @FigmaEnum("Type", mapping: ["Primary": true, "Secondary": false])
 var isPrimary: Bool = false
@@ -251,7 +251,7 @@ var body: some View {
         }
 }
 ```
-`elseApply` is optional — omit it to show nothing when condition is false.
+`elseApply` is optional  -  omit it to show nothing when condition is false.
 
 **With @FigmaBoolean + chain modifier (project pattern):**
 ```swift
@@ -262,33 +262,33 @@ var showMember: Bool = false
 var memberText: String = "CLASSIC"
 
 var body: some View {
-    CheckinBoardingPassPassengerInfo(passengerName: passengerName, colorVariant: colorVariant)
+    TicketPassengerInfo(passengerName: passengerName, colorVariant: colorVariant)
         .figmaApply(showMember) { $0.membershipInfo(.init(memberId: "TK 12345678", memberClass: memberText)) }
 }
 ```
 Combines `hideDefault` boolean with a chain modifier that passes a nested configuration. When `M&S Member = false`, the `.membershipInfo(...)` line is hidden entirely in Dev Mode.
 
-**Multiple figmaApply — TYPE ERASURE WARNING:**
+**Multiple figmaApply  -  TYPE ERASURE WARNING:**
 
-`figmaApply` returns `some View`, NOT `Self`. This means chaining multiple `figmaApply` calls causes the second call's closure `$0` to be `some View` instead of the concrete view type — resulting in a compile error when calling component-specific modifiers inside the closure.
+`figmaApply` returns `some View`, NOT `Self`. This means chaining multiple `figmaApply` calls causes the second call's closure `$0` to be `some View` instead of the concrete view type  -  resulting in a compile error when calling component-specific modifiers inside the closure.
 
 ```swift
-// ❌ COMPILE ERROR — second $0 is `some View`, not `MyComponent`
+// ❌ COMPILE ERROR  -  second $0 is `some View`, not `MyComponent`
 var body: some View {
     MyComponent(title: title)
         .figmaApply(showIcon) { $0.leftIcon(icon) }      // returns some View
-        .figmaApply(showBadge) { $0.badge(badgeCount) }   // $0 is some View — .badge() not found
+        .figmaApply(showBadge) { $0.badge(badgeCount) }   // $0 is some View  -  .badge() not found
 }
 ```
 
 **The parser supports multiple chained `figmaApply` calls** (it uses a multi-pass while loop to replace each one independently). The limitation is purely a Swift type-checker issue at compile time.
 
-**Workaround — direct modifiers first, single figmaApply last:**
+**Workaround  -  direct modifiers first, single figmaApply last:**
 
 Apply concrete-type modifiers (chain modifiers from Configuration) directly, then place `figmaApply` as the LAST call in the chain since it erases the type:
 
 ```swift
-// ✅ CORRECT — direct modifier preserves type, figmaApply goes last
+// ✅ CORRECT  -  direct modifier preserves type, figmaApply goes last
 @FigmaBoolean("Show Badge", hideDefault: true)
 var showBadge: Bool = false
 
@@ -298,11 +298,11 @@ var isDisabled: Bool = false
 var body: some View {
     MyComponent(title: title)
         .showBadge(showBadge)                              // direct modifier, type preserved
-        .figmaApply(isDisabled) { $0.opacity(0.5) }        // figmaApply last, returns some View — OK
+        .figmaApply(isDisabled) { $0.opacity(0.5) }        // figmaApply last, returns some View  -  OK
 }
 ```
 
-**Multiple booleans — use direct modifiers + single figmaApply:**
+**Multiple booleans  -  use direct modifiers + single figmaApply:**
 
 When a component has multiple boolean properties, prefer direct modifiers for Bool-to-Bool mappings and reserve `figmaApply` for conditional complex expressions (optional Strings, nested configs):
 
@@ -314,10 +314,10 @@ var whithBaby: Bool = false
 var showBoardingDate: Bool = false
 
 var body: some View {
-    CheckinBoardingPassQrInfoGroup(
+    TicketQrInfoGroup(
         terminalNumber: "1", gateNumber: "G23",
         seatNumber: "24 A", boardingTime: "23:30",
-        qrCodeData: "BOARDING-PASS-QR-DATA"
+        qrCodeData: "TICKET-QR-DATA"
     )
     .whithBaby(whithBaby)                                   // Bool → Bool, direct modifier
     .figmaApply(showBoardingDate) { $0.boardingDate("13 Eyl") }  // Bool → optional String, figmaApply last
@@ -326,7 +326,7 @@ var body: some View {
 
 **If you MUST use multiple figmaApply (e.g., both need elseApply or complex expressions):**
 
-The parser handles it fine — it's only the Swift compiler that objects. Use the comment-out-after-publish pattern:
+The parser handles it fine  -  it's only the Swift compiler that objects. Use the comment-out-after-publish pattern:
 
 1. Write the `.figma.swift` with multiple `figmaApply` calls
 2. Comment out the file content temporarily for `figma connect publish` (parser reads the file directly, not via Xcode build)
@@ -334,7 +334,7 @@ The parser handles it fine — it's only the Swift compiler that objects. Use th
 4. After publish, comment out the body or the entire struct to prevent Xcode build failures:
 
 ```swift
-// Published to Figma Dev Mode — commented to avoid type erasure build error
+// Published to Figma Dev Mode  -  commented to avoid type erasure build error
 // struct MyComponentFigmaConnect: FigmaConnect {
 //     ...
 //     var body: some View {
@@ -346,10 +346,10 @@ The parser handles it fine — it's only the Swift compiler that objects. Use th
 ```
 
 **Preference order for multiple boolean properties:**
-1. **Direct modifier** (`.whithBaby(whithBaby)`) — cleanest, no type erasure
-2. **@FigmaBoolean with mapping** (`mapping: [true: "value", false: nil]`) — for Bool → optional type
-3. **Single figmaApply last** — for complex conditional expressions
-4. **Multiple figmaApply + comment after publish** — last resort when multiple complex conditionals needed
+1. **Direct modifier** (`.whithBaby(whithBaby)`)  -  cleanest, no type erasure
+2. **@FigmaBoolean with mapping** (`mapping: [true: "value", false: nil]`)  -  for Bool → optional type
+3. **Single figmaApply last**  -  for complex conditional expressions
+4. **Multiple figmaApply + comment after publish**  -  last resort when multiple complex conditionals needed
 
 **When to use figmaApply vs direct parameter:**
 - **Direct parameter**: Property maps 1:1 to init/modifier argument (e.g., `@FigmaEnum → colorStyle:`)
@@ -371,12 +371,12 @@ var body: some View {
 ```
 Use when the component uses slot-based composition in Figma (e.g., a list with repeating row children).
 
-**Wildcard matching** — match any or partial layer names:
+**Wildcard matching**  -  match any or partial layer names:
 ```swift
 @FigmaChildren(layers: ["*"])           // all children
 var allItems: AnyView?
 
-@FigmaChildren(layers: ["Icon*"])       // partial match — "IconLeft", "IconRight", etc.
+@FigmaChildren(layers: ["Icon*"])       // partial match  -  "IconLeft", "IconRight", etc.
 var icons: AnyView?
 
 @FigmaChildren(layers: ["Tab 1", "Tab 2", "Tab 3"])  // multiple specific layers
@@ -384,11 +384,11 @@ var tabs: AnyView?
 ```
 Layer name matching is **case sensitive**. The nested instance must have its own separate Code Connect file.
 
-**Slots** — composable sub-areas within component instances where designers can place freeform content. Code Connect does NOT traverse slot children to generate code — it only renders a reference to the slot itself. Use `@FigmaChildren` to capture slot content.
+**Slots**  -  composable sub-areas within component instances where designers can place freeform content. Code Connect does NOT traverse slot children to generate code  -  it only renders a reference to the slot itself. Use `@FigmaChildren` to capture slot content.
 
 ## 3.5 ADVANCED PATTERNS
 
-### Variant restrictions — multiple structs per component
+### Variant restrictions  -  multiple structs per component
 When a single Figma component maps to different Swift types based on variant, create multiple `FigmaConnect` structs pointing to the same node. Figma shows the most specific match:
 ```swift
 // Matches when Type = "Primary"
@@ -409,7 +409,7 @@ struct DangerButtonConnect: FigmaConnect {
 ```
 More specific variant dictionaries take priority. Combine multiple variant properties for fine-grained matching.
 
-### Computed variant — boolean gate for separate structs
+### Computed variant  -  boolean gate for separate structs
 Use a computed `var variant` property for dynamic matching (e.g., boolean toggles):
 ```swift
 struct IconOnlyBadgeConnect: FigmaConnect {
@@ -420,14 +420,14 @@ struct IconOnlyBadgeConnect: FigmaConnect {
 }
 ```
 
-### @FigmaBoolean with custom mapping — non-Bool types
+### @FigmaBoolean with custom mapping  -  non-Bool types
 Map boolean toggles to any Swift type, not just Bool. Useful for optional views:
 ```swift
-// Boolean controls icon presence — maps to optional Image
+// Boolean controls icon presence  -  maps to optional Image
 @FigmaBoolean("Has Icon", mapping: [true: Image(systemName: "star.fill"), false: nil], hideDefault: true)
 var icon: Image? = nil
 
-// Boolean controls text presence — maps to optional String
+// Boolean controls text presence  -  maps to optional String
 @FigmaBoolean("Show Label", mapping: [true: "Default Label", false: nil], hideDefault: true)
 var label: String? = nil
 
@@ -439,7 +439,7 @@ var body: some View {
 ```
 When `Has Icon = false` (default + hideDefault), `.icon(...)` is omitted from snippet entirely.
 
-### @FigmaEnum — map to Bool for figmaApply
+### @FigmaEnum  -  map to Bool for figmaApply
 Convert an enum variant to a boolean condition for use with `figmaApply`:
 ```swift
 @FigmaEnum("State", mapping: ["Disabled": true, "Default": false, "Hover": false, "Active": false])
@@ -501,11 +501,11 @@ The CLI parser uses SwiftSyntax AST analysis. Key behaviors that affect what dev
 
 | Element | Behavior |
 |---------|----------|
-| `//` comments in body | **Stripped** — never appear in snippet |
-| `import` statements beyond Figma/SwiftUI | **Stripped** — `imports: []` always empty |
-| View modifiers (`.renderingMode(.template)`) | **Preserved** — captured via `trimmedDescription` |
-| Property wrapper expressions | **Preserved** — any expression works (e.g., `Image(systemName: "x")`) |
-| `let component = X.self` | **Optional** — only needed for component-level Code Connect |
+| `//` comments in body | **Stripped**  -  never appear in snippet |
+| `import` statements beyond Figma/SwiftUI | **Stripped**  -  `imports: []` always empty |
+| View modifiers (`.renderingMode(.template)`) | **Preserved**  -  captured via `trimmedDescription` |
+| Property wrapper expressions | **Preserved**  -  any expression works (e.g., `Image(systemName: "x")`) |
+| `let component = X.self` | **Optional**  -  only needed for component-level Code Connect |
 
 Do NOT rely on comments or extra imports to communicate with developers in snippets. Use view modifiers or static values in body instead.
 

package/pipeline/skills/figma-ios/figma-to-component/reference/figma-to-swiftui-effects.md

@@ -1,6 +1,6 @@
 # FIGMA/CSS TO SWIFTUI EFFECTS CONVERSION
 
-When translating Figma design properties (which use CSS conventions) to SwiftUI, several values require conversion. Figma's generated code (React+Tailwind) uses CSS units and conventions — these do NOT map 1:1 to SwiftUI.
+When translating Figma design properties (which use CSS conventions) to SwiftUI, several values require conversion. Figma's generated code (React+Tailwind) uses CSS units and conventions  -  these do NOT map 1:1 to SwiftUI.
 
 Source: [Matching drop shadows across CSS, Android, iOS, Figma, and Sketch](https://bjango.com/articles/matchingdropshadows/)
 
@@ -26,10 +26,10 @@ SwiftUI radius = Figma blur / 2
 **When using design tokens:**
 ```swift
 // Token .Effects.effect8 = 8 (Figma blur value)
-// WRONG — passes Figma blur directly
+// WRONG  -  passes Figma blur directly
 .shadow(radius: .Effects.effect8)
 
-// CORRECT — divide by 2 for SwiftUI
+// CORRECT  -  divide by 2 for SwiftUI
 .shadow(radius: .Effects.effect8 / 2)
 ```
 
@@ -47,7 +47,7 @@ ZStack {
 }
 ```
 
-For zero spread (the common case), no workaround needed — just omit.
+For zero spread (the common case), no workaround needed  -  just omit.
 
 ### Inner Shadow
 CSS `box-shadow: inset ...` → SwiftUI has no built-in inner shadow.
@@ -71,7 +71,7 @@ CSS `box-shadow: inset ...` → SwiftUI has no built-in inner shadow.
 SwiftUI blur radius = CSS blur radius / 2
 ```
 
-Same conversion factor as shadows — iOS uses double the standard deviation.
+Same conversion factor as shadows  -  iOS uses double the standard deviation.
 
 ```swift
 // Figma: backdrop-filter: blur(20px)
@@ -89,7 +89,7 @@ Same conversion:
 
 ## 3. OPACITY
 
-Opacity maps 1:1 — no conversion needed.
+Opacity maps 1:1  -  no conversion needed.
 
 ```swift
 // Figma: opacity: 0.5
@@ -101,7 +101,7 @@ For color opacity (e.g., `rgba(0,0,0,0.5)`):
 Color.black.opacity(0.5)
 ```
 
-When using design tokens like `Color.Opacity.Black.opacity50`, verify the token already encodes the correct alpha — don't double-apply.
+When using design tokens like `Color.Opacity.Black.opacity50`, verify the token already encodes the correct alpha  -  don't double-apply.
 
 ---
 
@@ -176,7 +176,7 @@ TimelineView(.periodic(from: .now, by: interval)) { context in
         .animation(.easeInOut(duration: transitionDuration), value: state)
 }
 ```
-Derive state from the timeline date — do NOT mutate `@State` inside the TimelineView closure.
+Derive state from the timeline date  -  do NOT mutate `@State` inside the TimelineView closure.
 
 ---
 

package/pipeline/skills/figma-ios/figma-to-component/reference/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.

package/pipeline/skills/figma-ios/figma-to-component/reference/macros.md

@@ -23,7 +23,7 @@ public struct ComponentConfiguration {
 // GENERATED: .title(_), .title(localized:), .count(_), .isEnabled(_)
 ```
 
-### @GenerateConfiguredInit (LEGACY — being replaced)
+### @GenerateConfiguredInit (LEGACY  -  being replaced)
 
 Applied to View structs. Generates:
 - Default init with `@autoclosure` configuration
@@ -41,14 +41,14 @@ public struct Component: View {
 // GENERATED: init(configuration:), init(configure:), configured(_:)
 ```
 
-### @GenerateViewConfiguration (NEW — preferred)
+### @GenerateViewConfiguration (NEW  -  preferred)
 
 Applied to View structs. Generates ONLY:
-- `configured()` method — post-init configuration transform
+- `configured()` method  -  post-init configuration transform
 
 Does NOT generate:
-- **Inits** — AI writes custom inits tailored to each component's needs
-- **View-level forwarding modifiers** — Swift macros cannot introspect types they're not attached to, so the macro cannot read Configuration struct properties. Phase 4E (AI) writes the +Modifiers file.
+- **Inits**  -  AI writes custom inits tailored to each component's needs
+- **View-level forwarding modifiers**  -  Swift macros cannot introspect types they're not attached to, so the macro cannot read Configuration struct properties. Phase 4E (AI) writes the +Modifiers file.
 
 ```swift
 @GenerateViewConfiguration
@@ -56,7 +56,7 @@ public struct Component: View {
     private let configuration: ComponentConfiguration
     private let action: () -> Void
 
-    // AI-written custom init — required props + closures
+    // AI-written custom init  -  required props + closures
     public init(title: String, action: @escaping () -> Void) {
         self.configuration = .init(title: title)
         self.action = action
@@ -68,7 +68,7 @@ public struct Component: View {
 // NOT GENERATED: init (AI writes), forwarding modifiers (Phase 4E writes +Modifiers.swift)
 ```
 
-**Why:** `@GenerateConfiguredInit` treats config as an opaque blob — it can't distinguish required vs optional props, can't pair data+closure, and generates a configure closure init that is an anti-pattern. `@GenerateViewConfiguration` gives AI full control over init shape while the macro handles only the mechanical `configured()` boilerplate.
+**Why:** `@GenerateConfiguredInit` treats config as an opaque blob  -  it can't distinguish required vs optional props, can't pair data+closure, and generates a configure closure init that is an anti-pattern. `@GenerateViewConfiguration` gives AI full control over init shape while the macro handles only the mechanical `configured()` boilerplate.
 
 **`configured()` is internal API.** It is used ONLY inside +Modifiers forwarding methods and paired modifiers. Consumers use the named forwarding modifiers (`.state()`, `.title()`) and paired modifiers (`.secondaryButton(title) { action }`). Never expose `configured()` in Code Connect, previews, or usage examples.
 
@@ -146,7 +146,7 @@ public struct Component: View {
     public var body: some View { ... }
 }
 
-// Usage — required in init, optional via chain modifiers
+// Usage  -  required in init, optional via chain modifiers
 Component(title: "Hello") { doSomething() }
     .subtitle("World")
     .style(.primary)
@@ -183,7 +183,7 @@ public struct BottomActions: View {
         self.primaryAction = primaryAction
     }
 
-    // Paired modifier — binds title + action atomically
+    // Paired modifier  -  binds title + action atomically
     public func secondaryButton(_ title: String, action: @escaping () -> Void) -> Self {
         var copy = self
         copy.configuration.secondaryButtonTitle = title

package/pipeline/skills/figma-ios/figma-to-component/reference/missing-tokens.md

@@ -13,9 +13,9 @@ Missing tokens from `pass3/02_token_mapping.md` fall into two categories:
 | Category | What It Means | Example |
 |----------|--------------|---------|
 | **Typography alias** | Figma uses a new style name for an existing Swift token | `Caption/Regular/sm` → existing `.xSmallRegular` |
-| **Truly missing** | No Swift token exists — must be added to source | `Black White/25` color not in `Mode.json` |
+| **Truly missing** | No Swift token exists  -  must be added to source | `Black White/25` color not in `Mode.json` |
 
-**How to tell:** Extract font size + weight from the design context for the missing style. Look up the existing registry — if a token with the same size + weight exists, it's an alias. If not, it's truly missing.
+**How to tell:** Extract font size + weight from the design context for the missing style. Look up the existing registry  -  if a token with the same size + weight exists, it's an alias. If not, it's truly missing.
 
 ---
 
@@ -56,7 +56,7 @@ When a missing typography token maps to an existing Swift token (same font size
 }
 ```
 
-**Match by font properties** — extract from design_context_response.json:
+**Match by font properties**  -  extract from design_context_response.json:
 
 | Font Size | Weight 400 (Regular) | Weight 600 (Bold) |
 |-----------|---------------------|-------------------|
@@ -70,7 +70,7 @@ When a missing typography token maps to an existing Swift token (same font size
 | 20 | `.h5Regular` | `.h5` |
 | 24 | `.h3Regular` | `.h3` |
 | 28 | `.h2Regular` | `.h2` |
-| 32 | — | `.h1` |
+| 32 |  -  | `.h1` |
 
 **Verify after adding:**
 ```bash

package/pipeline/skills/figma-ios/figma-to-component/reference/orchestrator-discipline.md

@@ -1,4 +1,4 @@
-# Orchestrator Discipline — Mandatory Rules for Pipeline Execution
+# Orchestrator Discipline  -  Mandatory Rules for Pipeline Execution
 
 These rules apply to every orchestrator skill (`/figma-cli-iterate`, `/figma-cli-lean-iterate`, `/figma-iterate`, `/figma-to-swiftui`, `/performance-swiftui`, `/performance-tour`) and to any agent acting as an orchestrator that dispatches leaf-phase subagents.
 
@@ -10,15 +10,15 @@ Violations of these rules have caused repeated implementation failures. Each rul
 
 The dispatch prompt template specifies which variables to pass to subagents: component name, node ID, artifact path, file key, component location. Pass ONLY these context variables.
 
-Never add sections like "IMPORTANT: form integration is NOT needed" or "IMPORTANT: no UI patterns apply." Those are gate outcomes — the subagent's gates decide them, not the orchestrator. Injecting conclusions pre-decides gate outcomes and defeats the purpose of having gates.
+Never add sections like "IMPORTANT: form integration is NOT needed" or "IMPORTANT: no UI patterns apply." Those are gate outcomes  -  the subagent's gates decide them, not the orchestrator. Injecting conclusions pre-decides gate outcomes and defeats the purpose of having gates.
 
 If the user provides implementation guidance (e.g., "check /figma-form-integration"), pass it as-is: "The user directed: check /figma-form-integration." Do not evaluate and dismiss it.
 
 ---
 
-## Rule 2: Every Dispatch Table Row Executes — Verify Row-by-Row Before Proceeding
+## Rule 2: Every Dispatch Table Row Executes  -  Verify Row-by-Row Before Proceeding
 
-The dispatch table lists phases with their instruction files, models, and wave groupings. Every row executes. No phase is optional unless the table explicitly marks it (e.g., "COMPLEX only" for 4A/4E — skip only if SIMPLE).
+The dispatch table lists phases with their instruction files, models, and wave groupings. Every row executes. No phase is optional unless the table explicitly marks it (e.g., "COMPLEX only" for 4A/4E  -  skip only if SIMPLE).
 
 After completing Wave 1, check the table for Wave 2. After Wave 2, check for remaining phases. Do not move to the next step until every phase in the current step has been dispatched and returned.
 
@@ -39,7 +39,7 @@ If any row is unchecked, you are not done with that step.
 
 ---
 
-## Rule 3: Subagent Fails — Retry, Never Take Over
+## Rule 3: Subagent Fails  -  Retry, Never Take Over
 
 When a subagent times out, errors, or returns HALT:
 
@@ -47,7 +47,7 @@ When a subagent times out, errors, or returns HALT:
 2. **HALT**: Read the HALT reason. Fix the blocking issue. Retry the subagent.
 3. **Error**: Diagnose and retry.
 
-Never take over and write implementation code without reading the phase instruction file the subagent would have read. The subagent reads `phase-4b-view.md` gate-by-gate — if you skip that file and write code from assumptions, you will produce wrong output.
+Never take over and write implementation code without reading the phase instruction file the subagent would have read. The subagent reads `phase-4b-view.md` gate-by-gate  -  if you skip that file and write code from assumptions, you will produce wrong output.
 
 If you must write code directly (after 2+ retries), read the phase instruction file yourself first and follow its gates.
 
@@ -55,7 +55,7 @@ If you must write code directly (after 2+ retries), read the phase instruction f
 
 ## Rule 4: Skills Are Complementary, Not Dismissable
 
-`/figma-form-integration`, `/figma-ui-patterns`, `/figma-price-integration`, `/coreui-forms` — these skills feed INTO phases. They augment Phase 3D, Phase 4A, Phase 4B with domain-specific patterns.
+`/figma-form-integration`, `/figma-ui-patterns`, `/figma-price-integration`, `/coreui-forms`  -  these skills feed INTO phases. They augment Phase 3D, Phase 4A, Phase 4B with domain-specific patterns.
 
 When the user says "check /figma-form-integration":
 - That is a directive to integrate, not a suggestion to evaluate.
@@ -73,9 +73,9 @@ If `{artifactPath}/pass0/specs.md` exists, or if the user provides acceptance cr
 
 1. Read the specs BEFORE dispatching Phase 4+ subagents.
 2. Extract concrete requirements.
-3. Inject them as CRITICAL SPEC GATES in the subagent prompt — per the orchestrator SKILL.md instructions.
+3. Inject them as CRITICAL SPEC GATES in the subagent prompt  -  per the orchestrator SKILL.md instructions.
 
-Do not skip this step. Do not assume specs are empty without checking. The orchestrator SKILL.md has an explicit "Spec Injection" section — follow it.
+Do not skip this step. Do not assume specs are empty without checking. The orchestrator SKILL.md has an explicit "Spec Injection" section  -  follow it.
 
 ---
 
@@ -87,4 +87,4 @@ If for any reason you write implementation code directly (instead of through a s
 2. Follow its gates in order.
 3. Apply every check and validation the file specifies.
 
-Writing code from "I've seen similar components" or "this is a common SwiftUI pattern" without reading the phase file produces code that doesn't follow project conventions — wrong init patterns, missing modifiers, hand-drawn shapes instead of real components.
+Writing code from "I've seen similar components" or "this is a common SwiftUI pattern" without reading the phase file produces code that doesn't follow project conventions  -  wrong init patterns, missing modifiers, hand-drawn shapes instead of real components.

package/pipeline/skills/figma-ios/figma-to-component/reference/remote-mcp-script.md

@@ -48,9 +48,9 @@ python3 scripts/remote-mcp-fetch.py \
 
 The script resolves the OAuth token in this order:
 
-1. **`--mcp-token` CLI arg** — explicit token passed at invocation
-2. **Keychain `FIGMA_MCP_TOKEN`** — dedicated entry stored by `/figma-setup` (CHECK 3b)
-3. **Keychain `Claude Code-credentials`** — extracts `figma-remote` OAuth token via regex
+1. **`--mcp-token` CLI arg**  -  explicit token passed at invocation
+2. **Keychain `FIGMA_MCP_TOKEN`**  -  dedicated entry stored by `/figma-setup` (CHECK 3b)
+3. **Keychain `Claude Code-credentials`**  -  extracts `figma-remote` OAuth token via regex
 
 Fallback #2 is fast (direct keychain lookup). Fallback #3 works but parses a large JSON blob.
 Run `/figma-setup` to pre-store the token for fast access.
@@ -62,7 +62,7 @@ Run `/figma-setup` to pre-store the token for fast access.
 - **Type:** OAuth access token (NOT a personal access token)
 - **Prefix:** `figu_` (vs `figd_` for PATs)
 - **Source:** Claude Code's MCP OAuth flow for `figma-remote` server
-- **PATs do NOT work** with remote MCP — always returns 401
+- **PATs do NOT work** with remote MCP  -  always returns 401
 
 ---
 
@@ -150,4 +150,4 @@ python3 scripts/remote-mcp-fetch.py \
 | Requires Figma Desktop | Yes | No |
 | Works in subagents/CI | Yes (HTTP) | Yes (HTTP) |
 | Code Connect output | Returns ALL platforms | Filters by target platform |
-| Rate limits | Daily cap (varies) | Per plan (see tools.md §1.7) |
+| Rate limits | Daily cap (varies) | Per plan (see tools.md section1.7) |

package/pipeline/skills/figma-ios/figma-to-component/reference/rest-api-script.md

@@ -1,4 +1,4 @@
-# FIGMA REST API — SCRIPT USAGE REFERENCE
+# FIGMA REST API  -  SCRIPT USAGE REFERENCE
 
 How the Phase 1 script (`scripts/phase1-gather.py`) uses the Figma REST API for data that MCP doesn't efficiently provide.
 
@@ -26,7 +26,7 @@ token = subprocess.check_output(
 
 ## Endpoints Used by Phase 1 Script
 
-### 1. Node Data — Component Properties
+### 1. Node Data  -  Component Properties
 
 ```
 GET https://api.figma.com/v1/files/{fileKey}/nodes?ids={nodeId}
@@ -38,7 +38,7 @@ Returns full node JSON including `componentPropertyDefinitions` for the componen
 
 ---
 
-### 2. Screenshot Export — Single Node
+### 2. Screenshot Export  -  Single Node
 
 ```
 GET https://api.figma.com/v1/images/{fileKey}?ids={nodeId}&format=png&scale=2
@@ -46,11 +46,11 @@ GET https://api.figma.com/v1/images/{fileKey}?ids={nodeId}&format=png&scale=2
 
 Returns JSON with `images` map: `{ "nodeId": "https://...s3.amazonaws.com/..." }`. The script downloads the URL to save as `screenshot.png`.
 
-**Why REST not MCP:** MCP `get_screenshot` returns base64 inline (works but larger payload). REST returns a URL — better for scripts that save to disk.
+**Why REST not MCP:** MCP `get_screenshot` returns base64 inline (works but larger payload). REST returns a URL  -  better for scripts that save to disk.
 
 ---
 
-### 3. Batch Screenshot Export — Variants
+### 3. Batch Screenshot Export  -  Variants
 
 ```
 GET https://api.figma.com/v1/images/{fileKey}?ids={id1},{id2},{id3},...&format=png&scale=2
@@ -104,17 +104,17 @@ for node_id, url in data["images"].items():
 
 ---
 
-## REST vs MCP — When to Use What
+## REST vs MCP  -  When to Use What
 
 | Data | Use REST | Use MCP | Reason |
 |------|----------|---------|--------|
-| Component properties/variants | yes | — | MCP doesn't expose raw property defs |
+| Component properties/variants | yes |  -  | MCP doesn't expose raw property defs |
 | Screenshot (single) | ok | ok | Both work; MCP is simpler for inline use |
-| Screenshots (batch) | yes | — | One REST call vs N MCP calls |
-| Design context (code) | — | yes | MCP generates reference code |
-| Metadata (XML hierarchy) | — | yes | MCP returns structured XML |
+| Screenshots (batch) | yes |  -  | One REST call vs N MCP calls |
+| Design context (code) |  -  | yes | MCP generates reference code |
+| Metadata (XML hierarchy) |  -  | yes | MCP returns structured XML |
 | Variable definitions | fallback | primary | MCP preferred; REST 403 on non-Enterprise |
-| Code Connect mappings | — | yes | MCP-only feature |
+| Code Connect mappings |  -  | yes | MCP-only feature |
 
 ---