@mmerterden/multi-agent-pipeline 8.6.2 → 10.2.0

package/pipeline/skills/figma-common/figma-skip/SKILL.md

@@ -8,7 +8,7 @@ status: wip-v5
 sourced-from: upstream/figma-skip
 ---
 
-# /figma-skip — Mark Component as Skipped
+# /figma-skip  -  Mark Component as Skipped
 
 ## Parse Arguments
 
@@ -32,7 +32,7 @@ Derive filename: `{nodeId with : replaced by -}.json` (e.g., `3-9045.json`).
 
 ## Workflow
 
-### STEP 1 — Resolve Component Name
+### STEP 1  -  Resolve Component Name
 
 ```bash
 COMMON_PATH="${REPO_ROOT}/{repos.common.path}"
@@ -45,7 +45,7 @@ If the registry file already exists at `Shared/Figma/Components/{nodeId}.json`:
 - Read it. If `"skip": true` already set → inform user "Already skipped" and exit.
 - If not skipped → ask user if they want to mark it as skipped (it may have implementation data).
 
-### STEP 2 — Create/Update Registry Entry
+### STEP 2  -  Create/Update Registry Entry
 
 Write `Shared/Figma/Components/{nodeId}.json`:
 
@@ -76,14 +76,14 @@ Write `Shared/Figma/Components/{nodeId}.json`:
 }
 ```
 
-### STEP 3 — Regenerate Catalog
+### STEP 3  -  Regenerate Catalog
 
 ```bash
 cd "${COMMON_PATH}"
 .build/debug/FigmaRegistryUtility catalog
 ```
 
-### STEP 4 — Update Confluence Status Dashboard
+### STEP 4  -  Update Confluence Status Dashboard
 
 ```bash
 python3 "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/confluence-component-status.py"
@@ -92,7 +92,7 @@ python3 "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/confluence-co
 This updates the global Component Implementation Status dashboard on Confluence.
 Requires VPN. If VPN unavailable, inform user and skip.
 
-### STEP 5 — Summary
+### STEP 5  -  Summary
 
 ```
 ## Skip Summary

package/pipeline/skills/figma-common/figma-ui-patterns/SKILL.md

@@ -7,11 +7,11 @@ status: wip-v5
 sourced-from: upstream/figma-ui-patterns
 ---
 
-# /figma-ui-patterns — UI Pattern Index
+# /figma-ui-patterns  -  UI Pattern Index
 
 ## Purpose
 
-Reusable SwiftUI UI-pattern guides, indexed in one place. Each pattern lives in its own sub-markdown under `patterns/` with a self-contained recipe — API shape, SwiftUI techniques, gotchas, and a minimal reference snippet.
+Reusable SwiftUI UI-pattern guides, indexed in one place. Each pattern lives in its own sub-markdown under `patterns/` with a self-contained recipe  -  API shape, SwiftUI techniques, gotchas, and a minimal reference snippet.
 
 This skill is **complementary**, not gating:
 - During **spec-driven** work (figma-to-swiftui pipeline): phases reference patterns by slug when the architecture calls for one.
@@ -31,7 +31,7 @@ This skill is **complementary**, not gating:
     └── <new-pattern>.md
 ```
 
-Each sub-guide is a single markdown file. No deeper nesting — flat under `patterns/`.
+Each sub-guide is a single markdown file. No deeper nesting  -  flat under `patterns/`.
 
 ## How to Use
 
@@ -39,14 +39,14 @@ Each sub-guide is a single markdown file. No deeper nesting — flat under `patt
 
 1. Run `/figma-ui-patterns` to see the index below.
 2. Open `patterns/<slug>.md` for the pattern you need.
-3. Follow the recipe. Sub-guides are self-contained — you should not need to hop between them.
+3. Follow the recipe. Sub-guides are self-contained  -  you should not need to hop between them.
 
 ### As an author (adding a new pattern)
 
 1. Pick a slug: `kebab-case`, descriptive, noun-phrase (`carousel-pager`, `scallop-view`, not `how-to-carousel`).
 2. Create `patterns/<slug>.md` using the template below.
 3. Add a row to the **Index** section of this file.
-4. Keep the guide under ~200 lines. If it grows beyond that, the pattern is probably two patterns — split it.
+4. Keep the guide under ~200 lines. If it grows beyond that, the pattern is probably two patterns  -  split it.
 
 ## Sub-guide Template
 
@@ -68,7 +68,7 @@ Step-by-step SwiftUI recipe. Which primitives (ScrollView, GeometryReader, Timel
 Numbered list. Common mistakes, platform quirks (iOS version gates, accessibility regressions, performance cliffs).
 
 ## Reference Snippet
-One complete, compilable SwiftUI snippet — under 60 lines. Should run as-is in an Xcode preview.
+One complete, compilable SwiftUI snippet  -  under 60 lines. Should run as-is in an Xcode preview.
 
 ## Related Patterns
 Bullet list of other slugs in this skill (or in `figma-price-integration`, `coreui-forms`, etc.) that commonly co-occur or contrast with this one.
@@ -77,10 +77,10 @@ Bullet list of other slugs in this skill (or in `figma-price-integration`, `core
 ## Authoring Rules
 
 1. **Self-contained.** A reader opening one sub-guide should implement the pattern without hopping.
-2. **SwiftUI-first.** Prefer pure SwiftUI techniques. Drop to UIViewRepresentable only when SwiftUI cannot express the behavior — and say so in Gotchas.
+2. **SwiftUI-first.** Prefer pure SwiftUI techniques. Drop to UIViewRepresentable only when SwiftUI cannot express the behavior  -  and say so in Gotchas.
 3. **Design-token aware.** Use project tokens (`.Text.textPrimary`, `.bodyRegular`, etc.) in snippets, not raw colors/fonts. Keeps examples on-brand.
-4. **No component specifics.** A pattern is generic. If your recipe references `FlightCard` or `TripSummary`, you're writing a component guide, not a pattern guide — move it to the component's wiki instead.
-5. **Validate names before committing.** For the pattern's human-readable title, run `/intent-idempotency-check` if the name isn't already obvious — UI pattern names are easy to get wrong.
+4. **No component specifics.** A pattern is generic. If your recipe references `FlightCard` or `TripSummary`, you're writing a component guide, not a pattern guide  -  move it to the component's wiki instead.
+5. **Validate names before committing.** For the pattern's human-readable title, run `/intent-idempotency-check` if the name isn't already obvious  -  UI pattern names are easy to get wrong.
 
 ## Integration with figma-to-swiftui
 
@@ -94,11 +94,12 @@ Bullet list of other slugs in this skill (or in `figma-price-integration`, `core
 
 | Slug | Pattern | Status |
 |------|---------|--------|
-| `carousel-banner` | Auto-advancing paged banner — single item visible, swipe/tap paging, `CarouselGroup` indicator, configurable interval + loop + pause-on-interaction. | Ready |
-| `scalloped-vstack` | Scalloped VStack (boarding-pass silhouette) — vertical card with semicircular edge cuts + dashed perforation line between segments. `CoreUI.ScallopedVStack`. | Ready |
+| `animated-gradient-border` | Snake/halo gradient stroke crawling the perimeter (promo/featured/premium cards)  -  angular-gradient stroke + animatable progress, corner-radius match, Reduce-Motion gate. Native-SwiftUI recipe; uses a project modifier if one ships. | Ready |
+| `carousel-banner` | Auto-advancing paged banner  -  single item visible, swipe/tap paging, `CarouselGroup` indicator, configurable interval + loop + pause-on-interaction. | Ready |
+| `scalloped-vstack` | Scalloped VStack (boarding-pass silhouette)  -  vertical card with semicircular edge cuts + dashed perforation line between segments. `CoreUI.ScallopedVStack`. | Ready |
 
 ## Anti-patterns
 
 - **Dumping ground.** This is not a place for "here's a snippet I wrote once." A pattern appears here only if it is **reusable across ≥2 real components**.
 - **Pattern-by-component.** If every component gets its own pattern file, the index stops being useful. Generalize first.
-- **Stale snippets.** If a sub-guide's snippet no longer compiles on the project's current Swift/SwiftUI version, fix or remove it — don't leave a broken recipe.
+- **Stale snippets.** If a sub-guide's snippet no longer compiles on the project's current Swift/SwiftUI version, fix or remove it  -  don't leave a broken recipe.

package/pipeline/skills/figma-common/figma-ui-patterns/patterns/animated-gradient-border.md

@@ -0,0 +1,112 @@
+# Animated Gradient Border (Snake / Halo Border)
+
+## When to Use
+
+A component's frame has a stroked border whose color fades around the perimeter as if a **snake / halo of gradient light crawls around the edge** — continuous, looping, usually 2–4pt wide, with a radius matching the host's corner radius. Figma signals: promo banners, premium/featured cards, upsell surfaces, "lit up" states of otherwise calm cards; a spec named "animated / glowing / gradient border" or an endless-loop prototype on the stroke.
+
+**Not** this pattern when:
+- The border is a single, *static* color → `.stroke(...)` / `.overlay(RoundedRectangle().stroke(...))` directly.
+- The gradient is **on the fill**, not the stroke → that's an angular/linear gradient background.
+- It's a **state-transition** pulse (red on error) → `.animation(...)` with color interpolation, not a crawling gradient.
+- The stroke is **dashed/dotted** → different `StrokeStyle`; this pattern draws a solid stroke.
+
+## Minimal API
+
+If the project already ships a gradient-border modifier (some design systems do — check `reference/ui` / the repo), use it and do NOT re-implement the math. Otherwise use this generic modifier shape:
+
+```swift
+view
+    .background(fill)
+    .clipShape(RoundedRectangle(cornerRadius: radius))
+    .animatedGradientBorder(
+        colors: [start.opacity(0.6), middle, end.opacity(0.6)], // faded → solid → faded
+        lineWidth: 2,
+        cornerRadius: radius,          // MUST match the host corner radius
+        isAnimated: !reduceMotion,
+        duration: 3.0
+    )
+```
+
+**Parameter intent:** 3 colors read best (faded→solid→faded); `lineWidth` 1–3pt from tokens; `cornerRadius` must equal the host's; `isAnimated:false` renders a static stroke; `duration` 1.5 urgent / 3 calm / 5+ ambient.
+
+## Technique
+
+A self-contained native-SwiftUI recipe (no external package):
+
+1. **Overlay, don't replace.** Draw the stroke in an `.overlay` of a `RoundedRectangle` so the host keeps its own background/fill.
+2. **Angular gradient stroked along the shape.** `RoundedRectangle(cornerRadius:).stroke(AngularGradient(...), lineWidth:)`. The angular gradient's rotation is driven by an animated angle so the bright spot travels the perimeter.
+3. **Animatable progress 0→1.** Rotate the gradient with `.rotationEffect(.degrees(360 * progress))` on a masked stroke, or animate the `AngularGradient`'s `angle`. Start in `.onAppear` with `withAnimation(.linear(duration:).repeatForever(autoreverses:false)) { progress = 1 }`.
+4. **Halo shape** = the gradient stop distribution (a bright band with faded shoulders); keep the fade symmetric for the "snake" read.
+5. **Static shortcut.** `isAnimated == false` → render the same stroke frozen (or a single-color stroke).
+
+## Gotchas
+
+1. **Corner-radius mismatch is the #1 bug** — the host `cornerRadius` and the border `cornerRadius` must be equal, or the stroke floats off the rounded path.
+2. **Apply the border after `.background`/`.clipShape`** so it overlays the current bounds and clips to the rounded shape.
+3. **Reduce Motion:** read `@Environment(\.accessibilityReduceMotion)` at the call site and pass `isAnimated: !reduceMotion`. A perpetually animating border must respect it.
+4. **Perf on long lists:** a forever-repeating animation per row costs frames and never pauses off-screen. Measure with Instruments before shipping it on `LazyVStack`/`List` rows.
+5. **`onAppear` restarts on every reappear** — don't rely on animation state surviving a re-mount.
+6. **`lineWidth` ≥ `cornerRadius`** produces blobby corners; keep `lineWidth < cornerRadius` for clean corners.
+7. **Use semantic tokens, not raw hex**, so the border follows light/dark + theme (`reference/ui` + figma-config token patterns).
+
+## Reference Snippet
+
+Drop-in preview — pure SwiftUI, no external dependency:
+
+```swift
+import SwiftUI
+
+struct AnimatedGradientBorder: ViewModifier {
+    var colors: [Color]
+    var lineWidth: CGFloat = 2
+    var cornerRadius: CGFloat = 12
+    var isAnimated: Bool = true
+    var duration: Double = 3.0
+    @State private var progress: CGFloat = 0
+
+    func body(content: Content) -> some View {
+        content.overlay(
+            RoundedRectangle(cornerRadius: cornerRadius)
+                .stroke(
+                    AngularGradient(gradient: Gradient(colors: colors + [colors.first ?? .clear]),
+                                    center: .center),
+                    lineWidth: lineWidth
+                )
+                .rotationEffect(.degrees(isAnimated ? 360 * Double(progress) : 0))
+                .mask(RoundedRectangle(cornerRadius: cornerRadius).stroke(lineWidth: lineWidth))
+        )
+        .onAppear {
+            guard isAnimated else { return }
+            withAnimation(.linear(duration: duration).repeatForever(autoreverses: false)) {
+                progress = 1
+            }
+        }
+    }
+}
+
+extension View {
+    func animatedGradientBorder(colors: [Color], lineWidth: CGFloat = 2,
+                               cornerRadius: CGFloat = 12, isAnimated: Bool = true,
+                               duration: Double = 3.0) -> some View {
+        modifier(AnimatedGradientBorder(colors: colors, lineWidth: lineWidth,
+                                        cornerRadius: cornerRadius, isAnimated: isAnimated,
+                                        duration: duration))
+    }
+}
+
+#Preview {
+    Text("Featured")
+        .padding(16)
+        .frame(maxWidth: .infinity, alignment: .leading)
+        .background(Color(.systemBackground))
+        .clipShape(RoundedRectangle(cornerRadius: 12))
+        .animatedGradientBorder(colors: [.blue.opacity(0.6), .blue, .blue.opacity(0.6)],
+                                cornerRadius: 12)
+        .padding()
+}
+```
+
+## Related Patterns
+
+- `carousel-banner` — promo banners often pair an auto-advancing pager with this border on the active card.
+- Price callouts — premium-price surfaces sit inside a card wearing this border; compose it at the card level, not on the price view (see `reference/ui` / `figma-price-integration`).

package/pipeline/skills/figma-common/figma-utility/SKILL.md

@@ -8,13 +8,13 @@ status: wip-v5
 sourced-from: upstream/figma-utility
 ---
 
-# /figma-utility — On-Demand Figma Data Utility
+# /figma-utility  -  On-Demand Figma Data Utility
 
 ## Purpose
 
 Standalone utility for querying Figma data on demand. Exposes Figma REST API and MCP capabilities as simple sub-commands. Does **not** modify any project files or affect other skills.
 
-This is a **read-only data tool** — it fetches and displays Figma data. It does NOT implement, commit, or modify code.
+This is a **read-only data tool**  -  it fetches and displays Figma data. It does NOT implement, commit, or modify code.
 
 ## Parameters
 
@@ -140,7 +140,7 @@ Reset all repo branches (main + submodules) to their remote defaults. Discards l
 - **Requires:** Nothing
 - **Options:** None
 
-**IMPORTANT — run as a single Bash call.** `REPO_ROOT` must be resolved once before any `cd` into submodules; if split into separate Bash calls, `git rev-parse --show-toplevel` inside a submodule returns the submodule root, not the main repo.
+**IMPORTANT  -  run as a single Bash call.** `REPO_ROOT` must be resolved once before any `cd` into submodules; if split into separate Bash calls, `git rev-parse --show-toplevel` inside a submodule returns the submodule root, not the main repo.
 
 ```bash
 REPO_ROOT="$(git rev-parse --show-toplevel)" && \
@@ -267,7 +267,7 @@ If no tokens are found, the script reports what's missing and suggests running `
 ## Independence
 
 This skill is **completely independent** from other Figma skills. It:
-- Has its own script (`figma-utility.py`) — no shared imports
+- Has its own script (`figma-utility.py`)  -  no shared imports
 - Does not read or write implementation artifacts
 - Does not modify the component registry
 - Does not create branches or commits (except `reset-branches` which resets to remote)

package/pipeline/skills/figma-common/figma-utility/scripts/figma-utility.py

@@ -720,7 +720,7 @@ def cmd_whoami():
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Figma Utility — query Figma data via REST API and MCP",
+        description="Figma Utility  -  query Figma data via REST API and MCP",
         formatter_class=argparse.RawDescriptionHelpFormatter,
     )
     parser.add_argument("command", choices=[

package/pipeline/skills/figma-common/figma-validate/SKILL.md

@@ -8,14 +8,14 @@ status: wip-v5
 sourced-from: upstream/figma-validate
 ---
 
-# /figma-validate — Pre-Implementation Component Validation
+# /figma-validate  -  Pre-Implementation Component Validation
 
 ## Purpose
 
 Validates whether a Figma component is ready for the figma-to-swiftui implementation pipeline.
 Runs 6 criteria checks and returns a verdict: **VALID**, **CONDITIONAL**, or **INVALID**.
 
-This is a **read-only diagnostic skill** — it does NOT modify any files.
+This is a **read-only diagnostic skill**  -  it does NOT modify any files.
 
 ## Parameters
 
@@ -80,8 +80,8 @@ gh issue view <N> --repo ${GH_REPO} --json number,title,body
 ```
 
 Extract from the issue body:
-- **Figma URL** — from the line after `### Figma URL` heading
-- **Component Name** — from `### Component Name (PascalCase)` section (informational)
+- **Figma URL**  -  from the line after `### Figma URL` heading
+- **Component Name**  -  from `### Component Name (PascalCase)` section (informational)
 
 ```python
 import json, re
@@ -117,7 +117,7 @@ Seven criteria are checked. Each returns ✅ (pass) or ❌ (fail) with a reason.
 
 ---
 
-### Criterion 1 — Component Registry Presence
+### Criterion 1  -  Component Registry Presence
 
 **Question:** Component registry'de (`component-registry.json`) yer alıyor mu?
 
@@ -131,9 +131,9 @@ Also check `excludePatterns` in `$REGISTRY_CONFIG`:
 - If the component's `pageName` or `sectionName` matches an exclude pattern → ❌ FAIL. Reason: "Component is in an excluded page: {pageName}."
 
 **Known valid file keys** (from registry config):
-- `ps4xrJzhn7WNbfkZs895Bi` — Design System Core
-- `9ipBvrtsq9HlQ175B9k0wx` — Mobile App Components
-- `YSs4g0EeGAW53haB0zz5sa` — Visual Assets
+- `ps4xrJzhn7WNbfkZs895Bi`  -  Design System Core
+- `9ipBvrtsq9HlQ175B9k0wx`  -  Mobile App Components
+- `YSs4g0EeGAW53haB0zz5sa`  -  Visual Assets
 
 If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknown Figma file. Only Design System Core, Mobile App Components, and Visual Assets are supported."
 
@@ -141,7 +141,7 @@ If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknow
 
 ---
 
-### Criterion 2 — Figma Property Structure & Code Connect Strategy
+### Criterion 2  -  Figma Property Structure & Code Connect Strategy
 
 **Question:** Uygulanabilir bir Code Connect stratejisi var mı?
 
@@ -149,7 +149,7 @@ If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknow
 
 1. Fetch component data via Figma REST API:
    ```python
-   # Use python3 urllib.request — curl may be blocked by policy
+   # Use python3 urllib.request  -  curl may be blocked by policy
    import subprocess, urllib.request, json
    token = subprocess.check_output(
        ["security", "find-generic-password", "-s", "FIGMA_ACCESS_TOKEN", "-w"],
@@ -177,32 +177,32 @@ If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknow
 | `COMPONENT` | 0 properties | STATIC_VALUES | ✅ PASS |
 | `COMPONENT` | N/A | STATIC_VALUES | ✅ PASS |
 
-**Pass Condition:** Component has a valid Code Connect strategy — either property mapping (for COMPONENT_SET with ≥1 property) or STATIC_VALUES (for plain COMPONENT).
+**Pass Condition:** Component has a valid Code Connect strategy  -  either property mapping (for COMPONENT_SET with ≥1 property) or STATIC_VALUES (for plain COMPONENT).
 
 **Output:** Always report the detected strategy in the result:
-- `✅ STATIC_VALUES — plain COMPONENT, no variant properties (uses static preview in .figma.swift)`
-- `✅ Property Mapping — 3 enum, 1 string, 2 bool`
-- `❌ COMPONENT_SET with 0 properties — unexpected, needs design review`
+- `✅ STATIC_VALUES  -  plain COMPONENT, no variant properties (uses static preview in .figma.swift)`
+- `✅ Property Mapping  -  3 enum, 1 string, 2 bool`
+- `❌ COMPONENT_SET with 0 properties  -  unexpected, needs design review`
 
 **Warning Flags** (informational, not failures):
-- Property named `"Property 1"` → flag as `UNNAMED_PROPERTY`: "Unnamed property detected — design team should rename."
+- Property named `"Property 1"` → flag as `UNNAMED_PROPERTY`: "Unnamed property detected  -  design team should rename."
 - Property values with likely typos (e.g., `"Standart"`, `"Clasic Plus"`) → flag as `TYPO_DETECTED`.
 
 **Fallback:** If Figma API is unreachable, mark criterion as ⚠️ SKIPPED. Do NOT fail the entire validation.
 
 ---
 
-### Criterion 3 — Design Token Compliance
+### Criterion 3  -  Design Token Compliance
 
 **Question:** Renkler/spacing/typography design token kullanıyor mu?
 
 **Check:**
 
 1. From Figma node data, extract:
-   - **Fill colors** — check if they correspond to known design token hex values
-   - **Text styles** — check if they match `UIAssetTokens` typography styles
-   - **Spacing values** — check if padding/gap values are standard multiples: 2, 4, 8, 12, 16, 24, 32, 48
-   - **Corner radius** — check if values match known radius tokens: 4, 8, 12, 16, 24
+   - **Fill colors**  -  check if they correspond to known design token hex values
+   - **Text styles**  -  check if they match `UIAssetTokens` typography styles
+   - **Spacing values**  -  check if padding/gap values are standard multiples: 2, 4, 8, 12, 16, 24, 32, 48
+   - **Corner radius**  -  check if values match known radius tokens: 4, 8, 12, 16, 24
 2. Optionally cross-reference with the token index:
    ```bash
    cd "${COMMON_PATH}" && .build/debug/FigmaRegistryUtility uitoken-index 2>/dev/null
@@ -210,11 +210,11 @@ If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknow
 
 **Pass Condition:** No hardcoded hex colors outside the design token palette. Spacing uses standard increments.
 
-**Soft Pass:** If token verification is not possible from the API response, mark as ⚠️ ASSUMED PASS with note: "Token compliance could not be fully verified from API — manual visual check recommended."
+**Soft Pass:** If token verification is not possible from the API response, mark as ⚠️ ASSUMED PASS with note: "Token compliance could not be fully verified from API  -  manual visual check recommended."
 
 ---
 
-### Criterion 4 — Nested Dependency Readiness
+### Criterion 4  -  Nested Dependency Readiness
 
 **Question:** Bağımlı olduğu alt bileşenler zaten implemente mi?
 
@@ -225,7 +225,7 @@ If the URL's `fileKey` does not match any of these → ❌ FAIL. Reason: "Unknow
 3. **Resolve the componentId** to a searchable ID using the `components` metadata from the API response.
 4. **Search for implementation** using the decision tree below.
 
-#### Step 3 — ComponentId Resolution (CRITICAL)
+#### Step 3  -  ComponentId Resolution (CRITICAL)
 
 Figma INSTANCE nodes reference a **variant's node ID** (`componentId`), NOT the COMPONENT_SET's node ID. The API response includes a `components` metadata map at `data.nodes[nodeId].components` that provides the `componentSetId` for each variant.
 
@@ -266,7 +266,7 @@ For each child `componentId`, look it up in the component registry (`component-r
                  │                 └──────────┬───────────────────┘
     ┌────────────┼────────────┐          found │         not found
     │            │            │               │              │
-  VA (Y…sa)  DSC (p…Bi)  MAC (9…wx)    ┌─────┴──────┐   UNKNOWN
+  VA (Y...sa)  DSC (p...Bi)  MAC (9...wx)    ┌─────┴──────┐   UNKNOWN
     │            │            │         │status.ios. │   (warn)
     ▼            ▼            ▼         │implemented │
   COMMON     UICOMP       UICOMP        │.value=true?│
@@ -283,7 +283,7 @@ For each child `componentId`, look it up in the component registry (`component-r
 | `ps4xrJzhn7WNbfkZs895Bi` | Design System Core | **UICOMP** | Core UI components |
 | `9ipBvrtsq9HlQ175B9k0wx` | Mobile App Components | **UICOMP** | Flow-based / app-specific components |
 
-**Registry-based shortcuts** (parentPage check — no filesystem search needed):
+**Registry-based shortcuts** (parentPage check  -  no filesystem search needed):
 
 | `parentPage` value | Location | Verification |
 |--------------------|----------|-------------|
@@ -300,7 +300,7 @@ For each child `componentId`, look it up in the component registry (`component-r
 # IMPORTANT: Search on iteration/develop, not current HEAD
 cd "${COMMON_PATH}"
 NODE_DASH="${nodeId//:/-}"
-# 1. Check Components/{nodeId}.json — new status.ios.implemented.value (architecture-update)
+# 1. Check Components/{nodeId}.json  -  new status.ios.implemented.value (architecture-update)
 #    with legacy codeConnect.ios fallback for pre-backfill entries
 git show iteration/develop:Shared/Figma/Components/${NODE_DASH}.json 2>/dev/null | \
   python3 -c "
@@ -342,7 +342,7 @@ git grep -rl "${component_name}" iteration/develop -- 'Sources/UIComponents/Regr
 
 **Pass Condition:** ALL child component instances are either:
 - Already implemented (have a matching `.figma.swift` on `iteration/develop`), OR
-- Have `status.ios.implemented.value = true` in individual `Components/{nodeId}.json` (architecture-update model — with legacy `codeConnect.ios = true` as fallback for pre-backfill entries), OR
+- Have `status.ios.implemented.value = true` in individual `Components/{nodeId}.json` (architecture-update model  -  with legacy `codeConnect.ios = true` as fallback for pre-backfill entries), OR
 - Listed under `parentPage: "Icons"` or `"Logos"` in the component registry, OR
 - Found in `Regroup/` folder (cross-file logos like `MilesAndSmilesLogo`), OR
 - Marked as skipped in registry (`skip: true`), OR
@@ -353,7 +353,7 @@ List the missing dependencies with their Figma names and node IDs.
 
 ---
 
-### Criterion 5 — Atomic Component Scope
+### Criterion 5  -  Atomic Component Scope
 
 **Question:** Atomic (tek başına anlamlı) bir UI parçası mı?
 
@@ -365,8 +365,8 @@ List the missing dependencies with their Figma names and node IDs.
 2. From Figma node data, check dimensions:
    - Width > 500 AND height > 800 → likely a full screen ❌
 3. Check variant count from component properties:
-   - 2–50 variant combinations → reasonable ✅
-   - 0–1 variants → acceptable for STATIC_VALUES components — ⚠️ warn but pass
+   - 2-50 variant combinations → reasonable ✅
+   - 0-1 variants → acceptable for STATIC_VALUES components  -  ⚠️ warn but pass
    - 500+ variants → likely needs splitting ❌
 4. Check component name depth:
    - Name contains `/` separators with 4+ levels (e.g., `A/B/C/D/E`) → ⚠️ warn, may be deeply nested subcomponent
@@ -375,7 +375,7 @@ List the missing dependencies with their Figma names and node IDs.
 
 ---
 
-### Criterion 6 — iOS Platform Applicability
+### Criterion 6  -  iOS Platform Applicability
 
 **Question:** iOS platformu için geçerli mi (Hover-only değil)?
 
@@ -390,11 +390,11 @@ List the missing dependencies with their Figma names and node IDs.
 3. Check for web-only component patterns in the name:
    - `"Breadcrumb"`, `"Sidebar"`, `"Tooltip/Hover"` → ⚠️ flag for review but don't auto-fail
 
-**Pass Condition:** Component is usable on iOS — has non-hover states and is not desktop-only.
+**Pass Condition:** Component is usable on iOS  -  has non-hover states and is not desktop-only.
 
 ---
 
-### Criterion 7 — Already Implemented Check
+### Criterion 7  -  Already Implemented Check
 
 **Question:** Bu component zaten implemente edilmiş mi?
 
@@ -466,8 +466,8 @@ From registry, count how many components on the same `pageName` are implemented
 | Score | Verdict | Meaning |
 |-------|---------|---------|
 | 7/7 ✅ | **VALID** | Ready for `/figma-to-swiftui` implementation pipeline |
-| 6/7 ✅ | **CONDITIONAL** | One criterion failed — may be resolvable |
-| 5/7 or below | **INVALID** | Not ready — requires design-side changes or scope adjustment |
+| 6/7 ✅ | **CONDITIONAL** | One criterion failed  -  may be resolvable |
+| 5/7 or below | **INVALID** | Not ready  -  requires design-side changes or scope adjustment |
 
 **Note on ⚠️ SKIPPED criteria:** A skipped criterion (e.g., Figma API unreachable) counts as a pass for scoring purposes but is noted in the output.
 
@@ -509,7 +509,7 @@ From registry, count how many components on the same `pageName` are implemented
   - Page progress: Explore 12/18 (67%)
 
 ⚠️ Warnings:
-  - UNNAMED_PROPERTY: "Property 1" detected — design team should rename
+  - UNNAMED_PROPERTY: "Property 1" detected  -  design team should rename
 ```
 
 If `--verbose`, expand each criterion with detailed findings.
@@ -539,13 +539,13 @@ These are logged but do NOT affect the VALID/INVALID verdict:
 
 | Flag | Description |
 |------|-------------|
-| `UNNAMED_PROPERTY` | Figma property named "Property 1" — tasarımcı rename etmeli |
+| `UNNAMED_PROPERTY` | Figma property named "Property 1"  -  tasarımcı rename etmeli |
 | `TYPO_DETECTED` | Variant value appears misspelled (e.g., "Standart", "Clasic Plus") |
-| `DESKTOP_CHANNEL` | Component has Desktop/Web channel mapping — iOS'ta kullanılmaz |
-| `MEND_CANDIDATE` | A previous implementation exists in `Discarded/` — use `/figma-mend` instead |
+| `DESKTOP_CHANNEL` | Component has Desktop/Web channel mapping  -  iOS'ta kullanılmaz |
+| `MEND_CANDIDATE` | A previous implementation exists in `Discarded/`  -  use `/figma-mend` instead |
 | `URL_FORMAT_INCONSISTENT` | Node URL uses non-standard format (www vs non-www, `:` vs `-`) |
-| `LOW_VARIANT_COUNT` | 0–1 variants — uses STATIC_VALUES Code Connect strategy |
-| `DEEP_NESTING` | Component name has 4+ path levels — may be a deeply nested subcomponent |
+| `LOW_VARIANT_COUNT` | 0-1 variants  -  uses STATIC_VALUES Code Connect strategy |
+| `DEEP_NESTING` | Component name has 4+ path levels  -  may be a deeply nested subcomponent |
 
 ---
 
@@ -553,7 +553,7 @@ These are logged but do NOT affect the VALID/INVALID verdict:
 
 | Error | Action |
 |-------|--------|
-| Figma API unreachable | Skip Criteria 2, 3, 4, 6 — mark as ⚠️ SKIPPED, continue with Criteria 1, 5, 7 |
+| Figma API unreachable | Skip Criteria 2, 3, 4, 6  -  mark as ⚠️ SKIPPED, continue with Criteria 1, 5, 7 |
 | Registry file not found | Show command: `cd ${COMMON_PATH} && swift build --product FigmaRegistryUtility && .build/debug/FigmaRegistryUtility update` |
 | FigmaRegistryUtility not built | Show: `cd ${COMMON_PATH} && swift build --product FigmaRegistryUtility` |
 | Invalid URL format | Ask user for correct URL via AskUserQuestion |
@@ -593,7 +593,7 @@ The script:
 - Outputs a single JSON object with `results`, `intel`, `warnings`, `score`, `total`, `elapsed_ms`
 - Agent parses the JSON and formats the verdict box
 
-**IMPORTANT — Do NOT create temporary `.py` or `.json` files.** Always use the permanent script above. If for any reason temporary files were created during execution, clean them up before returning the result:
+**IMPORTANT  -  Do NOT create temporary `.py` or `.json` files.** Always use the permanent script above. If for any reason temporary files were created during execution, clean them up before returning the result:
 
 ```bash
 rm -f /tmp/figma_validate*.py /tmp/figma_validate*.json /tmp/figma_qr*.py /tmp/figma_analyze*.py /tmp/figma_lookup*.py
@@ -607,17 +607,17 @@ rm -f /tmp/figma_validate*.py /tmp/figma_validate*.json /tmp/figma_qr*.py /tmp/f
 Never write intermediate results to disk.
 
 **Key rules for speed:**
-- ONE terminal command total (the python3 script) — no sequential shell calls
-- Use `urllib.request` — never `curl` (may be blocked by auto-approval policy)
-- Use `os.walk` / `glob.glob` for file searches — never shell `grep`/`find`
-- Never put `#` comments in shell compound commands — causes `zsh` parse errors
+- ONE terminal command total (the python3 script)  -  no sequential shell calls
+- Use `urllib.request`  -  never `curl` (may be blocked by auto-approval policy)
+- Use `os.walk` / `glob.glob` for file searches  -  never shell `grep`/`find`
+- Never put `#` comments in shell compound commands  -  causes `zsh` parse errors
 
 ---
 
 ## Future Extensibility
 
 Each criterion is self-contained with:
-- A **question** (what it checks — displayed in Turkish for team context)
+- A **question** (what it checks  -  displayed in Turkish for team context)
 - A **check** procedure (how to verify)
 - A **pass condition** (what constitutes success)