@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

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

@@ -1,4 +1,4 @@
-# PHASE 4 — Implementation Orchestrator
+# PHASE 4  -  Implementation Orchestrator
 
 Orchestrates Phase 4 sub-phases: dispatches sub-agents to write Swift code, collects results.
 PREV: Phase 3 (Data Analysis)
@@ -54,9 +54,9 @@ Read: {artifactPath}/pass3/05_complexity.md
 ```
 
 EXTRACT:
-- `componentLocation` — Swift package path for the component
-- `complexity` — SIMPLE or COMPLEX
-- `filesToCreate` — list of files from the spec
+- `componentLocation`  -  Swift package path for the component
+- `complexity`  -  SIMPLE or COMPLEX
+- `filesToCreate`  -  list of files from the spec
 
 ---
 
@@ -84,7 +84,7 @@ OPTIONS:
   1) Override (delete existing files and recreate)
   2) Merge (update existing files, keep others)
   3) Choose different location
-SUGGESTED: Option 2 — merge with existing.
+SUGGESTED: Option 2  -  merge with existing.
 COMPLETED_GATES: [PRE_CHECK, LOAD_SPEC]
 CONTEXT:
   Path: {componentLocation}
@@ -120,9 +120,9 @@ PRE-CHECK + LOAD_SPEC + GATE 1
 ┌──────────────────────────────────────────┐
 │  WAVE 1: PARALLEL DISPATCH (sub-agents)  │
 │                                          │
-│   4A — Configuration    ← if COMPLEX     │
-│   4B — View             ← ALWAYS         │
-│   4C — FIGMA.md         ← ALWAYS         │
+│   4A  -  Configuration    ← if COMPLEX     │
+│   4B  -  View             ← ALWAYS         │
+│   4C  -  FIGMA.md         ← ALWAYS         │
 │                                          │
 └──────────────────────────────────────────┘
     ↓ wait for all to complete
@@ -130,7 +130,7 @@ PRE-CHECK + LOAD_SPEC + GATE 1
 ┌──────────────────────────────────────────┐
 │  WAVE 2: SEQUENTIAL                     │
 │                                          │
-│   4D — Preview          ← ALWAYS         │
+│   4D  -  Preview          ← ALWAYS         │
 │   (depends on 4A + 4B)                   │
 │                                          │
 └──────────────────────────────────────────┘
@@ -189,7 +189,7 @@ After all sub-phases complete, verify each produced its file:
 
 ```
 [ ] {componentLocation}/{ComponentName}.swift exists (Phase 4B)
-[ ] {componentLocation}/{ComponentName}Configuration.swift exists (Phase 4A — or SIMPLE skip)
+[ ] {componentLocation}/{ComponentName}Configuration.swift exists (Phase 4A  -  or SIMPLE skip)
 [ ] {componentLocation}/FIGMA.md exists (Phase 4C)
 ```
 
@@ -272,10 +272,10 @@ xcodebuild build \
 ```
 
 **Why this command is portable:**
-- `git rev-parse --show-toplevel` — resolves absolute repo path on any machine, no hardcoded user paths
-- `generic/platform=iOS` — no simulator name, ID, or OS version needed. Works regardless of installed simulators
-- `CODE_SIGNING_ALLOWED=NO` — bypasses development team / provisioning profile requirements. We only need compilation verification, not a runnable binary
-- `-quiet` — suppresses build log noise, only shows errors and warnings
+- `git rev-parse --show-toplevel`  -  resolves absolute repo path on any machine, no hardcoded user paths
+- `generic/platform=iOS`  -  no simulator name, ID, or OS version needed. Works regardless of installed simulators
+- `CODE_SIGNING_ALLOWED=NO`  -  bypasses development team / provisioning profile requirements. We only need compilation verification, not a runnable binary
+- `-quiet`  -  suppresses build log noise, only shows errors and warnings
 
 | Result | Action |
 |--------|--------|
@@ -321,11 +321,11 @@ python3 .instructions/figma/figma-to-swiftui/scripts/phase4-finalize.py \
 
 | Result | Action |
 |--------|--------|
-| Exit 0, `"action": "updated"` | Registry updated — proceed |
-| Exit 0, `"action": "version_bumped"` | Content hash changed, version bumped (other flags auto-yellow) — proceed |
-| Exit 0, `"action": "already_current"` | Byte-identical re-run, no-op — proceed |
-| Exit 0, `"action": "created"` | New registry file created — proceed |
-| Exit 1 | HALT — registry update failed |
+| Exit 0, `"action": "updated"` | Registry updated  -  proceed |
+| Exit 0, `"action": "version_bumped"` | Content hash changed, version bumped (other flags auto-yellow)  -  proceed |
+| Exit 0, `"action": "already_current"` | Byte-identical re-run, no-op  -  proceed |
+| Exit 0, `"action": "created"` | New registry file created  -  proceed |
+| Exit 1 | HALT  -  registry update failed |
 
 **Why this matters:** This is the single source of truth for `status.ios.implemented`. The content hash prevents spurious version bumps on byte-identical re-runs; when content changes, `implemented.version` bumps and any downstream flags (`tested`, `codeConnect`, `wiki`) whose `against` is lower drop to yellow automatically. The subsequent `figma-iteration-commit` step will read this and sync the GitHub issue via `update-issue-from-registry.py`.
 
@@ -373,10 +373,10 @@ Implementation:
 [ ] Phase 3 artifacts loaded (pass3/_index.md, 07_implementation_spec.md)
 [ ] Component directory created (or merged with existing)
 [ ] Git user name retrieved
-[ ] 4A dispatched and completed (if COMPLEX) — Configuration.swift exists
-[ ] 4B dispatched and completed — View.swift exists
-[ ] 4C dispatched and completed — FIGMA.md exists
-[ ] 4D dispatched and completed — LTR + RTL Previews appended to View.swift
+[ ] 4A dispatched and completed (if COMPLEX)  -  Configuration.swift exists
+[ ] 4B dispatched and completed  -  View.swift exists
+[ ] 4C dispatched and completed  -  FIGMA.md exists
+[ ] 4D dispatched and completed  -  LTR + RTL Previews appended to View.swift
 [ ] validate-phase4.sh passed (no violations)
 [ ] xcodebuild passed (exit 0, no compilation errors)
 [ ] phase4-finalize.py passed (status.ios.implemented updated)

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-4a-configuration.md

@@ -1,9 +1,9 @@
-# PHASE 4A — Configuration File
+# PHASE 4A  -  Configuration File
 
 Write the Configuration struct with chain modifier macros.
 Only executed for COMPLEX components (>3 properties).
 
-CONDITIONAL — skip if SIMPLE.
+CONDITIONAL  -  skip if SIMPLE.
 PARALLEL WITH: Phase 4B (View), Phase 4C (FIGMA.md)
 
 ---
@@ -11,14 +11,14 @@ PARALLEL WITH: Phase 4B (View), Phase 4C (FIGMA.md)
 ## CONTEXT VARIABLES
 
 These are provided by the orchestrator in the dispatch prompt:
-- `componentName` — e.g., "LabelBadge"
-- `componentLocation` — e.g., "Sources/UIComponents/.../LabelBadge/"
-- `artifactPath` — path to implementation artifacts
-- `nodeId` — Figma node ID
-- `fileKey` — Figma file key
-- `complexity` — must be COMPLEX for this phase to execute
-- `gitUser` — from `git config user.name`
-- `date` — current date in DD.MM.YYYY format
+- `componentName`  -  e.g., "LabelBadge"
+- `componentLocation`  -  e.g., "Sources/UIComponents/.../LabelBadge/"
+- `artifactPath`  -  path to implementation artifacts
+- `nodeId`  -  Figma node ID
+- `fileKey`  -  Figma file key
+- `complexity`  -  must be COMPLEX for this phase to execute
+- `gitUser`  -  from `git config user.name`
+- `date`  -  current date in DD.MM.YYYY format
 
 ---
 
@@ -31,7 +31,7 @@ STATUS: COMPLETE
 PHASE: phase-4a
 GATES_PASSED: [PRE_CHECK]
 ARTIFACTS_CREATED: none
-SUMMARY: Skipped — SIMPLE component, no configuration file needed.
+SUMMARY: Skipped  -  SIMPLE component, no configuration file needed.
 ```
 
 Read:
@@ -43,7 +43,7 @@ Read:
 
 The `04c_variant_config_analysis.json` (from Phase 3H) provides typed recommendations for each boolean property:
 - `KNOWN_SUBCOMPONENT` entries → use `swiftType` from 3H. Only `dynamicProps` go in config. If 2+ dynamic props → create mini config struct. If 1 → unwrap to single type. If 0 → boolean presence only.
-- `PAIRED_ACTION_SUBCOMPONENT` entries → same as KNOWN_SUBCOMPONENT for data props. The `pairedClosure` is a View dependency — NOT in Configuration. Phase 4B generates the paired modifier.
+- `PAIRED_ACTION_SUBCOMPONENT` entries → same as KNOWN_SUBCOMPONENT for data props. The `pairedClosure` is a View dependency  -  NOT in Configuration. Phase 4B generates the paired modifier.
 - `ICON_BOOLEAN_GATED` entries → use `swiftType` (`Image?` or `Optional3<Image>`)
 - `CONTENT_LEAF` entries → `String?` (nil = hidden)
 
@@ -68,11 +68,11 @@ USER_ACTION_REQUIRED: Run Phase 3 first.
 
 ---
 
-## ARCHITECTURAL RULE — Configuration Purity
+## ARCHITECTURAL RULE  -  Configuration Purity
 
 **Configuration structs hold ONLY declarative, value-type properties.**
 
-Do NOT put these in Configuration — they are direct View dependencies:
+Do NOT put these in Configuration  -  they are direct View dependencies:
 
 | Excluded Type | Where It Lives Instead |
 |---------------|----------------------|
@@ -83,7 +83,7 @@ Do NOT put these in Configuration — they are direct View dependencies:
 
 This separation enables the `+Modifiers` extension (Phase 4E) to safely forward all Configuration properties as view-level chain modifiers.
 
-## ARCHITECTURAL RULE — Only Dynamic Props in Config
+## ARCHITECTURAL RULE  -  Only Dynamic Props in Config
 
 **Sub-component properties that are fixed by the parent's design (static) do NOT go in Configuration.** Only caller-controlled (dynamic) properties are exposed.
 
@@ -106,7 +106,7 @@ ls {componentLocation}/*Configuration.swift 2>/dev/null
 
 ## GATE 2: WRITE_CONFIGURATION
 
-INPUT: `pass3/04b_component_architecture.md` — contains the Final API Design section
+INPUT: `pass3/04b_component_architecture.md`  -  contains the Final API Design section
 
 ### 2.1 Extract from architecture
 
@@ -120,12 +120,12 @@ From the **Final API Design** section, extract:
 
 | Property Pattern | Attribute |
 |------------------|-----------|
-| UUID, ID, identifier | `@IgnoreChainModifier` — immutable, not chainable |
-| Non-localizable String (URL, code, ID) | `@IgnoreLocalization` — no `.title(localized:)` variant |
+| UUID, ID, identifier | `@IgnoreChainModifier`  -  immutable, not chainable |
+| Non-localizable String (URL, code, ID) | `@IgnoreLocalization`  -  no `.title(localized:)` variant |
 | Name conflicts with SwiftUI methods | `@ChainModifierName("customName")` |
-| Closure `() -> Void` | `@IgnoreLocalization` — not a String |
+| Closure `() -> Void` | `@IgnoreLocalization`  -  not a String |
 | Image | No special attribute needed |
-| Optional property | No attribute — macro generates double-optional `T??` in `modified()` automatically |
+| Optional property | No attribute  -  macro generates double-optional `T??` in `modified()` automatically |
 
 ### 2.3 Write file
 
@@ -159,7 +159,7 @@ public struct {ComponentName}Configuration: Sendable {
 
     // MARK: - Enums
 
-    {Enum definitions from architecture — inside the struct if component-specific}
+    {Enum definitions from architecture  -  inside the struct if component-specific}
 
     // MARK: - Properties
 
@@ -205,7 +205,7 @@ public struct {ComponentName}Configuration: Sendable {
     public let title: String
     public let price: Price?
 
-    // Nested PriceRepresentable — only the fields this component uses
+    // Nested PriceRepresentable  -  only the fields this component uses
     public struct Price: PriceRepresentable {
         public let amount: Double
         public let currency: String
@@ -226,7 +226,7 @@ public struct {ComponentName}Configuration: Sendable {
 }
 ```
 
-**For form data:** When the architecture identifies a `FORM_PATTERN` (component embeds 1+ form-capable sub-components — Selectbox, Checkbox, Radio, TextboxTextarea, DatepickerSchedule), read the `/figma-form-integration` skill at `.instructions/figma/figma-form-integration/SKILL.md`. Define a nested `Section` class conforming to `FormSection` (annotated with `@FormSection @Observable`) with ONLY the form fields this component renders. The `section` lives on Configuration; static labels/placeholders remain as Configuration strings:
+**For form data:** When the architecture identifies a `FORM_PATTERN` (component embeds 1+ form-capable sub-components  -  Selectbox, Checkbox, Radio, TextboxTextarea, DatepickerSchedule), read the `/figma-form-integration` skill at `.instructions/figma/figma-form-integration/SKILL.md`. Define a nested `Section` class conforming to `FormSection` (annotated with `@FormSection @Observable`) with ONLY the form fields this component renders. The `section` lives on Configuration; static labels/placeholders remain as Configuration strings:
 
 ```swift
 @GenerateChainModifiers
@@ -280,7 +280,7 @@ public struct {ComponentName}Configuration: Sendable {
     public let title: String
     public let badge: BadgeSection?
 
-    // Nested sub-configuration (no @GenerateChainModifiers — only top-level gets it)
+    // Nested sub-configuration (no @GenerateChainModifiers  -  only top-level gets it)
     public struct BadgeSection: Sendable {
         public let text: String
         public let style: BadgeStyle
@@ -314,8 +314,8 @@ Verify the written file:
 [ ] All enums defined with correct cases
 [ ] Init has sensible defaults (empty string, nil for optionals, first enum case or required)
 [ ] Struct is Sendable
-[ ] NO manual modified() method — macro handles it
-[ ] NO manual chain methods — macro handles it
+[ ] NO manual modified() method  -  macro handles it
+[ ] NO manual chain methods  -  macro handles it
 [ ] @IgnoreChainModifier on non-chainable properties
 [ ] @IgnoreLocalization on non-localizable String properties
 [ ] Correct imports: SwiftUI, UIMacros

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-4b-view.md

@@ -1,9 +1,9 @@
-# PHASE 4B — View Implementation + Preview
+# PHASE 4B  -  View Implementation + Preview
 
 Write the main View struct and Preview.
-This is the most critical implementation phase — it produces the actual SwiftUI component.
+This is the most critical implementation phase  -  it produces the actual SwiftUI component.
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 4A (Configuration), Phase 4C (FIGMA.md)
 
 ---
@@ -11,15 +11,15 @@ PARALLEL WITH: Phase 4A (Configuration), Phase 4C (FIGMA.md)
 ## CONTEXT VARIABLES
 
 These are provided by the orchestrator in the dispatch prompt:
-- `componentName` — e.g., "LabelBadge"
-- `componentLocation` — e.g., "Sources/UIComponents/.../LabelBadge/"
-- `artifactPath` — path to implementation artifacts
-- `nodeId` — Figma node ID
-- `fileKey` — Figma file key
-- `complexity` — SIMPLE or COMPLEX
-- `gitUser` — from `git config user.name`
-- `date` — current date in DD.MM.YYYY format
-- `issueNumber` — GitHub issue number (e.g., "340"). May be empty if not available.
+- `componentName`  -  e.g., "LabelBadge"
+- `componentLocation`  -  e.g., "Sources/UIComponents/.../LabelBadge/"
+- `artifactPath`  -  path to implementation artifacts
+- `nodeId`  -  Figma node ID
+- `fileKey`  -  Figma file key
+- `complexity`  -  SIMPLE or COMPLEX
+- `gitUser`  -  from `git config user.name`
+- `date`  -  current date in DD.MM.YYYY format
+- `issueNumber`  -  GitHub issue number (e.g., "340"). May be empty if not available.
 
 ---
 
@@ -28,7 +28,7 @@ These are provided by the orchestrator in the dispatch prompt:
 Read all required analysis files **in this order** (compact context first, large files last):
 
 ```
-{artifactPath}/pass1/component_summary.json            → Component overview (~100 lines) — READ FIRST
+{artifactPath}/pass1/component_summary.json            → Component overview (~100 lines)  -  READ FIRST
 {artifactPath}/pass3/00_property_coverage.json          → Property mandate (IMPLEMENT/SKIP/DEFER)
 {artifactPath}/pass3/07_implementation_spec.md          → Compiled blueprint
 {artifactPath}/pass3/04b_component_architecture.md      → API shape, enums, properties
@@ -56,7 +56,7 @@ Read effects conversion reference (shadows, blur, gradients, animations):
 
 **(strict) CSS effect lookup:** If `design_context_response.json` contains any of `backdrop-blur-[...]`, `backdrop-filter`, `filter: blur(...)`, `box-shadow`, `linear-gradient(...deg, ...)`, you MUST apply the mapping from `figma-to-swiftui-effects.md` verbatim. Cite the section number in a code comment next to the translated line.
 
-**ANTI-PATTERN — do NOT reach for system Materials:** CSS `backdrop-blur-[Npx]` maps to `.blur(radius: N/2)` per effects-reference §2 — NOT to `.ultraThinMaterial`, `.regularMaterial`, or `.thinMaterial`. iOS Materials adapt their tint based on underlying content (darker on dark backgrounds, lighter on light) which does not match CSS `backdrop-filter` semantics. Use a plain gradient/fill + `.blur(radius:)` following the reference. If a stroke border must stay sharp, put it in an overlay above the blurred layer.
+**ANTI-PATTERN  -  do NOT reach for system Materials:** CSS `backdrop-blur-[Npx]` maps to `.blur(radius: N/2)` per effects-reference section2  -  NOT to `.ultraThinMaterial`, `.regularMaterial`, or `.thinMaterial`. iOS Materials adapt their tint based on underlying content (darker on dark backgrounds, lighter on light) which does not match CSS `backdrop-filter` semantics. Use a plain gradient/fill + `.blur(radius:)` following the reference. If a stroke border must stay sharp, put it in an overlay above the blurred layer.
 
 If any required file is missing:
 
@@ -125,7 +125,7 @@ private enum Constants {
 **Constants Placement Rule:**
 - Constants MUST be `private enum Constants` nested INSIDE the View struct, NOT at file scope
 - Place it as the first item inside the struct, before `// MARK: - Properties`
-- Token values (`.Spacing.*`, `.Radius.*`, `Color.*`, `.Size.*`) are used directly in the body — do NOT wrap them in Constants
+- Token values (`.Spacing.*`, `.Radius.*`, `Color.*`, `.Size.*`) are used directly in the body  -  do NOT wrap them in Constants
 
 ---
 
@@ -173,7 +173,7 @@ If `00_property_coverage.json` does not exist, skip this gate (backward compatib
 public struct {ComponentName}: View {
     // MARK: - Properties
 
-    {All properties from Final API Design — public let}
+    {All properties from Final API Design  -  public let}
 
     // MARK: - Initialization
 
@@ -193,11 +193,11 @@ public struct {ComponentName}: View {
 }
 ```
 
-**CRITICAL — Type Placement:**
+**CRITICAL  -  Type Placement:**
 - ALL component-specific enums/types MUST be nested inside the View struct (SIMPLE) or Configuration struct (COMPLEX)
 - **For COMPLEX components: ALL data model types MUST be defined inside `{ComponentName}Configuration`, NOT inside the View struct.** The View then exposes them via `public typealias` for backwards-compatible API: `public typealias MyType = {ComponentName}Configuration.MyType`
 - NEVER define them as top-level types outside the struct
-- NEVER define data model types inside a COMPLEX View struct — they belong in Configuration
+- NEVER define data model types inside a COMPLEX View struct  -  they belong in Configuration
 - Name them WITHOUT the component prefix: `Size` not `{ComponentName}Size`, `State` not `{ComponentName}State`
 - Extensions on nested types use `extension {ComponentName}.TypeName { }` after the struct closing brace
 
@@ -263,18 +263,18 @@ public struct {ComponentName}: View {
 
 **CRITICAL for COMPLEX:**
 - `@GenerateViewConfiguration` macro generates ONLY:
-  - `configured(_:)` method — post-init configuration transform
-- **AI writes the custom init** — the macro does NOT generate inits
-- **Phase 4E writes +Modifiers** — View-level forwarding modifiers (`.state()`, `.title()`, etc.) are written by AI in +Modifiers.swift because Swift macros cannot introspect the Configuration struct
+  - `configured(_:)` method  -  post-init configuration transform
+- **AI writes the custom init**  -  the macro does NOT generate inits
+- **Phase 4E writes +Modifiers**  -  View-level forwarding modifiers (`.state()`, `.title()`, etc.) are written by AI in +Modifiers.swift because Swift macros cannot introspect the Configuration struct
 - Init includes **required dynamic props** as direct parameters + **required closures**
 - Optional props with defaults → set via chain modifiers (generated by macro)
-- Configuration is `private let` — the macro-generated `configured()` method reconstructs via init, not mutation
+- Configuration is `private let`  -  the macro-generated `configured()` method reconstructs via init, not mutation
 
 **Init generation rules:**
 1. **Required props** = Configuration props that have no sensible default (the component is meaningless without them). These become init parameters. AI infers this from component semantics, not from whether a default exists in config.
 2. **Required closures** = Always-present actions (e.g., primary button action). These become init parameters.
 3. **Optional config props** = Props with defaults or optional props. Set via chain modifiers, NOT init params.
-4. **Paired action closures** = From `PAIRED_ACTION_SUBCOMPONENT`. NOT in init — set via paired modifiers.
+4. **Paired action closures** = From `PAIRED_ACTION_SUBCOMPONENT`. NOT in init  -  set via paired modifiers.
 
 ### With dependencies (Bindings, ObservedObjects)
 
@@ -453,24 +453,24 @@ Static props from 3H `staticProps` are hardcoded in the View body. Only dynamic
 if let title = configuration.secondaryButtonTitle {
     TurkishButton { secondaryAction?() }
         .title(title)
-        .style(.ghost)       // static — hardcoded from 3H staticProps
+        .style(.ghost)       // static  -  hardcoded from 3H staticProps
         .size(.default)      // static
         .colorTheme(.brand)  // static
 }
 ```
 
-### 4.7 Layer text — static vs dynamic
+### 4.7 Layer text  -  static vs dynamic
 
 Texts from Figma layers are classified in `pass3/04_patterns.md` (Layer Text Classification table) as STATIC or DYNAMIC.
 
 - **DYNAMIC** texts → MUST use the corresponding Configuration property: `Text(configuration.currencyCode)`, NOT `Text("TRY")`
 - **STATIC** texts → use localization key if available (`Text(.Price.totalAmount)`), or hardcode only if truly fixed structural text (separators like "/", operators like "+")
 
-**Never hardcode text that represents variable data.** If a text looks like sample data (a price, an amount, a percentage, a currency code, a date), it MUST come from a configuration property. If no matching property exists in the architecture, HALT — the architecture is incomplete.
+**Never hardcode text that represents variable data.** If a text looks like sample data (a price, an amount, a percentage, a currency code, a date), it MUST come from a configuration property. If no matching property exists in the architecture, HALT  -  the architecture is incomplete.
 
 ### 4.7.1 Price pattern rendering
 
-When the architecture identifies a **price pattern** (§1.5.1 in Phase 3D), use `CurrencyTextRenderer` for rendering:
+When the architecture identifies a **price pattern** (section1.5.1 in Phase 3D), use `CurrencyTextRenderer` for rendering:
 
 ```swift
 // Create a style with the component's fonts
@@ -480,7 +480,7 @@ let style = CurrencyTextStyle(
     color: .Text.textWhite
 )
 
-// Render as AttributedString — handles placement, formatting, grouping
+// Render as AttributedString  -  handles placement, formatting, grouping
 Text(CurrencyTextRenderer.attributedString(
     value: amount,           // Double
     currencyCode: currencyCode,  // String
@@ -488,11 +488,11 @@ Text(CurrencyTextRenderer.attributedString(
 ))
 ```
 
-Do NOT manually place currency code left/right — `CurrencyTextRenderer` resolves placement from `CurrencyFormatProvider`. Do NOT format the amount as String — pass `Double`, the renderer formats it.
+Do NOT manually place currency code left/right  -  `CurrencyTextRenderer` resolves placement from `CurrencyFormatProvider`. Do NOT format the amount as String  -  pass `Double`, the renderer formats it.
 
 ### 4.7.1a Attributed text rendering (multi-font)
 
-When a text has mixed typography (§1.5.1a in Phase 3D), use `AttributedString.format()` from `UIExtensions`. The highlight value can be a dynamic prop or a localization key — use `.localized` (no args) to keep `%@` placeholders intact:
+When a text has mixed typography (section1.5.1a in Phase 3D), use `AttributedString.format()` from `UIExtensions`. The highlight value can be a dynamic prop or a localization key  -  use `.localized` (no args) to keep `%@` placeholders intact:
 
 ```swift
 // Highlight from localization key (static but styled differently)
@@ -510,7 +510,7 @@ Text(template.format(highlight))
 
 ### 4.7.2 Image asset rendering
 
-When the architecture identifies image assets (§1.5.2 in Phase 3D):
+When the architecture identifies image assets (section1.5.2 in Phase 3D):
 
 **DYNAMIC images (remote):**
 ```swift
@@ -522,7 +522,7 @@ RemoteImage(url: configuration.imageURL)
     .clipShape(RoundedRectangle(cornerRadius: .Radius.radius8))
 ```
 
-Do NOT embed Figma placeholder photos as bundled assets — they are sample data. The component takes a `URL` and loads the real image at runtime.
+Do NOT embed Figma placeholder photos as bundled assets  -  they are sample data. The component takes a `URL` and loads the real image at runtime.
 
 **STATIC images (bundled):**
 ```swift
@@ -550,7 +550,7 @@ if isExpanded {
 - **Container:** Apply `.animation(.easeInOut(duration: 0.25), value: isExpanded)` on the outer VStack so SwiftUI animates the height change
 - **Tap:** Toggle via `.onTapGesture { withAnimation { isExpanded.toggle() } }` on the header row
 
-Do NOT use `DisclosureGroup` — it has limited styling control. Build the expand/collapse manually for pixel-perfect Figma match.
+Do NOT use `DisclosureGroup`  -  it has limited styling control. Build the expand/collapse manually for pixel-perfect Figma match.
 
 ### 4.8 @ViewBuilder for complex conditional views
 
@@ -608,12 +608,12 @@ INPUT: `pass3/08_utility_integration.md` → Accessibility section
 
 Apply ONLY what the analysis specifies. If the analysis says 0 accessibility keys and no modifiers, add NOTHING.
 
-**CRITICAL — No unnecessary accessibility annotations:**
+**CRITICAL  -  No unnecessary accessibility annotations:**
 - Accessibility is for vision-impaired users to **navigate and use** the app
-- Ask: "Does a vision-impaired person need this information?" — if NO, do not add it
+- Ask: "Does a vision-impaired person need this information?"  -  if NO, do not add it
 - Do NOT generate per-enum-variant accessibility keys for visual state the user already knows (loyalty tier, color-coded status)
 - Do NOT add `localizedAccessibilityName` computed properties on enums unless Phase 2C explicitly defined those keys
-- If any accessibility text IS needed, it MUST use `LocalizedAccessibilityStringKey` — never hardcode English strings
+- If any accessibility text IS needed, it MUST use `LocalizedAccessibilityStringKey`  -  never hardcode English strings
 
 **Before adding ANY modifier, ask: "What breaks if I remove this?"** If the answer is "nothing", do not add it.
 
@@ -622,11 +622,11 @@ Apply ONLY what the analysis specifies. If the analysis says 0 accessibility key
 icon.accessibilityHidden(true)
 
 // Group children into single VoiceOver stop
-// SwiftUI reads visible Text automatically — do NOT add .accessibilityLabel on top
+// SwiftUI reads visible Text automatically  -  do NOT add .accessibilityLabel on top
 .accessibilityElement(children: .combine)
 
 // Do NOT add .accessibilityLabel when SwiftUI reads visible text correctly
-// Do NOT add .accessibilityAddTraits(.isStaticText) to Text — SwiftUI already knows
+// Do NOT add .accessibilityAddTraits(.isStaticText) to Text  -  SwiftUI already knows
 // Do NOT add .accessibilityRemoveTraits(.isButton) when there is no Button
 // Do NOT announce visual state (color) for non-interactive display components
 ```
@@ -664,21 +664,21 @@ Before marking complete, verify:
 [ ] Paired modifiers present for each PAIRED_ACTION_SUBCOMPONENT from 3H
 [ ] Every config property (including data props from paired modifiers) will get a forwarding modifier in Phase 4E
 [ ] Static sub-component props hardcoded in body (from 3H staticProps)
-[ ] Manual init present (if SIMPLE — no macro)
+[ ] Manual init present (if SIMPLE  -  no macro)
 [ ] SwiftDoc with Figma link above struct declaration
 [ ] Constants enum: private, nested inside View struct, no raw numbers in body (or omitted if no component-specific constants)
 [ ] ALL tokens from pass3/02_token_mapping.md applied (no hardcoded colors/spacing/fonts)
-[ ] No hardcoded sample/placeholder text — all DYNAMIC layer texts use configuration properties (per pass3/04_patterns.md classification)
+[ ] No hardcoded sample/placeholder text  -  all DYNAMIC layer texts use configuration properties (per pass3/04_patterns.md classification)
 [ ] Layout matches Figma: correct stacks, spacing, alignment, padding
 [ ] State-driven styling via computed properties (not inline switch in body)
 [ ] Nested components use exact init signatures from pass3/03_nested_components.md
 [ ] Testing identifiers applied per pass3/08_utility_integration.md (or skipped if 0)
 [ ] Accessibility modifiers applied per pass3/08_utility_integration.md (or skipped if 0)
 [ ] Analytics modifiers applied per pass3/08_utility_integration.md (or skipped if 0)
-[ ] No invented utility modifiers — only what analysis specifies
-[ ] NO Preview code in this file — Phase 4D handles Preview separately
+[ ] No invented utility modifiers  -  only what analysis specifies
+[ ] NO Preview code in this file  -  Phase 4D handles Preview separately
 [ ] Every IMPLEMENT property from 00_property_coverage.json has a Swift init parameter (if coverage file exists)
-[ ] ALL types nested inside View or Configuration struct — no top-level enums
+[ ] ALL types nested inside View or Configuration struct  -  no top-level enums
 ```
 
 ---

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-4c-documentation.md

@@ -1,9 +1,9 @@
-# PHASE 4C — FIGMA.md Documentation
+# PHASE 4C  -  FIGMA.md Documentation
 
 Write the FIGMA.md file for the component.
-This file is the bridge between Figma and code — used by other phases (Phase 3C nested lookup) and developers.
+This file is the bridge between Figma and code  -  used by other phases (Phase 3C nested lookup) and developers.
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 4A (Configuration), Phase 4B (View)
 
 ---
@@ -11,14 +11,14 @@ PARALLEL WITH: Phase 4A (Configuration), Phase 4B (View)
 ## CONTEXT VARIABLES
 
 These are provided by the orchestrator in the dispatch prompt:
-- `componentName` — e.g., "LabelBadge"
-- `componentLocation` — e.g., "Sources/UIComponents/.../LabelBadge/"
-- `artifactPath` — path to implementation artifacts
-- `nodeId` — Figma node ID
-- `fileKey` — Figma file key
-- `complexity` — SIMPLE or COMPLEX
-- `gitUser` — from `git config user.name`
-- `date` — current date in DD.MM.YYYY format
+- `componentName`  -  e.g., "LabelBadge"
+- `componentLocation`  -  e.g., "Sources/UIComponents/.../LabelBadge/"
+- `artifactPath`  -  path to implementation artifacts
+- `nodeId`  -  Figma node ID
+- `fileKey`  -  Figma file key
+- `complexity`  -  SIMPLE or COMPLEX
+- `gitUser`  -  from `git config user.name`
+- `date`  -  current date in DD.MM.YYYY format
 
 ---
 
@@ -73,7 +73,7 @@ Build the header metadata block.
 ```
 
 Where the init shows required dynamic props + required closures:
-- No required props → `{ComponentName}().modifier(value)` (unlikely — most have at least one required prop)
+- No required props → `{ComponentName}().modifier(value)` (unlikely  -  most have at least one required prop)
 - Required prop + closure → `{ComponentName}(title: "value") { action() }.modifier(value)`
 - With binding → `{ComponentName}(page: $page, title: "value").modifier(value)`
 - With paired modifier → `{ComponentName}(title: "value") { action() }.secondaryButton("title") { action() }`
@@ -83,7 +83,7 @@ Where the init shows required dynamic props + required closures:
 - Node ID uses colon format (`6893:6879`), not dash format
 - For SIMPLE: **Component** shows the init signature with parameter labels
 - For COMPLEX: **Init** shows the custom init + chain modifier pattern (preferred usage)
-- Trailing closure syntax ONLY when there is an actual closure dependency — NOT for configuration
+- Trailing closure syntax ONLY when there is an actual closure dependency  -  NOT for configuration
 
 ---
 
@@ -125,7 +125,7 @@ Show ALL init parameters with their types and defaults. Match the exact init fro
 - List every chainable property from the Configuration
 - Skip properties marked `@IgnoreChainModifier` (UUIDs, IDs)
 - Include `(localized:)` variant for String properties NOT marked `@IgnoreLocalization`
-- These are auto-generated by `@GenerateChainModifiers` — document what the macro produces
+- These are auto-generated by `@GenerateChainModifiers`  -  document what the macro produces
 
 ---
 
@@ -192,7 +192,7 @@ If no nested View components (only inline Text/Image) → skip.
 ```markdown
 ## Nested Components
 
-- **{ChildComponent}** — [{ChildComponent} FIGMA.md](relative/path/to/FIGMA.md)
+- **{ChildComponent}**  -  [{ChildComponent} FIGMA.md](relative/path/to/FIGMA.md)
 ```
 
 **Rules:**
@@ -254,7 +254,7 @@ COMPLEX components use a **custom init** with required dynamic props + required
 ```
 
 **Rules:**
-- Show ONLY the preferred pattern: required props in init + chain modifiers — FIGMA.md is consumed by AI (Phase 3C nesting), keep it compact
+- Show ONLY the preferred pattern: required props in init + chain modifiers  -  FIGMA.md is consumed by AI (Phase 3C nesting), keep it compact
 - Required dynamic props and required closures go in init
 - Optional config props → chain modifiers
 - Paired sub-components → paired modifiers (`.secondaryButton("title") { action }`)
@@ -315,7 +315,7 @@ Skip if there's nothing noteworthy beyond what's obvious from the API.
 [ ] First usage example is the recommended pattern
 [ ] Usage shows 2-4 examples covering major variants
 [ ] All Variants table (if ≤10 combinations)
-[ ] No implementation details — only public API surface
+[ ] No implementation details  -  only public API surface
 ```
 
 ---