@mmerterden/multi-agent-pipeline 8.6.2 → 10.2.0

package/pipeline/skills/figma-android/README.md

@@ -1,4 +1,4 @@
-# figma-android — Android Platform Skills
+# figma-android  -  Android Platform Skills
 
 Platform peer to `pipeline/skills/figma-ios/`.
 
@@ -8,15 +8,15 @@ Platform-specific skills for generating Jetpack Compose components from Figma de
 
 | Skill | Subphase | Sibling in figma-ios |
 |---|---|---|
-| `figma-to-component` | Orchestrator (3.0 – 3.8) | `figma-ios/figma-to-component` |
+| `figma-to-component` | Orchestrator (3.0 - 3.8) | `figma-ios/figma-to-component` |
 | `figma-component-implement` | 3.4 (code gen: Compose) | `figma-ios/figma-component-implement` |
 | `figma-component-test` | 3.5 (Compose Testing + Paparazzi) | `figma-ios/figma-component-test` |
 | `figma-component-code-connect` | 3.6 (Code Connect for Compose) | `figma-ios/figma-component-code-connect` |
-| `figma-component-wiki` | 3.7 (wiki — platform-aware rendering) | `figma-ios/figma-component-wiki` |
+| `figma-component-wiki` | 3.7 (wiki  -  platform-aware rendering) | `figma-ios/figma-component-wiki` |
 
 ## What's NOT here (yet)
 
-The platform-**agnostic** skills — `figma-commit`, `figma-iterate`, `figma-issue`, `figma-review`, `figma-setup`, `figma-validate`, `figma-utility`, `figma-fix`, `figma-mend`, `figma-ui-patterns`, `figma-remote-mcp-auth`, `figma-cli-*`, `performance-*`, etc. — live under [`pipeline/skills/figma-common/`](../figma-common/) (WS-7b ✓). Both iOS and Android orchestrators dispatch there without duplication.
+The platform-**agnostic** skills  -  `figma-commit`, `figma-iterate`, `figma-issue`, `figma-review`, `figma-setup`, `figma-validate`, `figma-utility`, `figma-fix`, `figma-mend`, `figma-ui-patterns`, `figma-remote-mcp-auth`, `figma-cli-*`, `performance-*`, etc.  -  live under [`pipeline/skills/figma-common/`](../figma-common/) (WS-7b ✓). Both iOS and Android orchestrators dispatch there without duplication.
 
 ## Routing
 
@@ -33,4 +33,4 @@ Android orchestrator expects `figmaConfig.build.gradleModule` to be set (e.g. `:
 
 ## Status
 
-All five skills stamped `status: wip-v5` — contracts + skeleton in place, not yet validated against a real Android project. Fill in the reference implementation detail as a downstream integration lands (follow-up issues will be opened per skill).
+All five skills stamped `status: wip-v5`  -  contracts + skeleton in place, not yet validated against a real Android project. Fill in the reference implementation detail as a downstream integration lands (follow-up issues will be opened per skill).

package/pipeline/skills/figma-android/figma-component-code-connect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-component-code-connect
-description: Generate Code Connect for Compose mappings — {Name}.figma.kt registers the composable with Figma's Code Connect so designers see live code snippets for each variant. Android peer to pipeline/skills/figma-ios/figma-component-code-connect.
+description: Generate Code Connect for Compose mappings  -  {Name}.figma.kt registers the composable with Figma's Code Connect so designers see live code snippets for each variant. Android peer to pipeline/skills/figma-ios/figma-component-code-connect.
 user-invocable: true
 argument-hint: <component-name>
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
@@ -9,9 +9,9 @@ sourced-from: derived-from/figma-ios/figma-component-code-connect
 platform: android
 ---
 
-# figma-component-code-connect — Code Connect for Compose
+# figma-component-code-connect  -  Code Connect for Compose
 
-> **WS-7 v5.0.0** — Subphase 3.6 for Android. Generates `{Name}.figma.kt` so Figma's Dev Mode shows Compose usage for every variant of the component, classified by the Figma variant properties read in subphase 3.1.
+> **WS-7 v5.0.0**  -  Subphase 3.6 for Android. Generates `{Name}.figma.kt` so Figma's Dev Mode shows Compose usage for every variant of the component, classified by the Figma variant properties read in subphase 3.1.
 
 ## Output
 

package/pipeline/skills/figma-android/figma-component-implement/SKILL.md

@@ -9,9 +9,9 @@ sourced-from: derived-from/figma-ios/figma-component-implement
 platform: android
 ---
 
-# figma-component-implement — Compose Code Generation
+# figma-component-implement  -  Compose Code Generation
 
-> **WS-7 v5.0.0** — Called by the Android `figma-to-component` orchestrator during subphase 3.4. Reads `agent-state.json.phases["3"].subphases["3.1-gather"]` for the fetched Figma tree + token map and writes Kotlin + Compose artefacts.
+> **WS-7 v5.0.0**  -  Called by the Android `figma-to-component` orchestrator during subphase 3.4. Reads `agent-state.json.phases["3"].subphases["3.1-gather"]` for the fetched Figma tree + token map and writes Kotlin + Compose artefacts.
 
 ## Inputs
 
@@ -37,7 +37,7 @@ Four Kotlin files beside the component's package, plus a README:
 
 ### 1. `{Name}Configuration.kt`
 
-Pure data class. Every variable knob lives here — the composable itself holds no state beyond its `Configuration` parameter. Marked `@Immutable` so Compose can skip recomposition when the instance is `equals`:
+Pure data class. Every variable knob lives here  -  the composable itself holds no state beyond its `Configuration` parameter. Marked `@Immutable` so Compose can skip recomposition when the instance is `equals`:
 
 ```kotlin
 @Immutable
@@ -53,10 +53,10 @@ data class ButtonPrimaryConfiguration(
 
 Rules:
 
-- `@Immutable` OR `@Stable` — never raw. `@Immutable` when all properties are primitives / immutable; `@Stable` when you guarantee structural stability.
+- `@Immutable` OR `@Stable`  -  never raw. `@Immutable` when all properties are primitives / immutable; `@Stable` when you guarantee structural stability.
 - Default values for every property so call sites can use `copy()` idiomatically (fluent-API equivalent).
-- Callbacks typed as named function types (`val onClick: () -> Unit = {}`) — never `Any?`.
-- Enums inside the Configuration's companion or nested scope — mirrors SwiftUI Configuration style.
+- Callbacks typed as named function types (`val onClick: () -> Unit = {}`)  -  never `Any?`.
+- Enums inside the Configuration's companion or nested scope  -  mirrors SwiftUI Configuration style.
 
 ### 2. `{Name}.kt` (the composable)
 
@@ -84,8 +84,8 @@ Rules:
 
 - Signature is always `(configuration: XConfiguration, modifier: Modifier = Modifier)`. The `modifier` param is the caller's slot; nothing else.
 - `testTag` from `testingIds`; `contentDescription` from `accessibility.label` or `stringResource(R.string...)`.
-- No hardcoded `dp` / `Color(0xFF...)` / `TextStyle(...)` — every value reads from `MaterialTheme.*` or the project's theme extension.
-- No `LaunchedEffect` / `rememberCoroutineScope` for stateful behaviour — keep the composable pure. If async is needed, surface it via Configuration callbacks (the caller orchestrates).
+- No hardcoded `dp` / `Color(0xFF...)` / `TextStyle(...)`  -  every value reads from `MaterialTheme.*` or the project's theme extension.
+- No `LaunchedEffect` / `rememberCoroutineScope` for stateful behaviour  -  keep the composable pure. If async is needed, surface it via Configuration callbacks (the caller orchestrates).
 
 ### 3. `{Name}Modifiers.kt`
 

package/pipeline/skills/figma-android/figma-component-test/SKILL.md

@@ -9,9 +9,9 @@ sourced-from: derived-from/figma-ios/figma-component-test
 platform: android
 ---
 
-# figma-component-test — Compose Test Suite
+# figma-component-test  -  Compose Test Suite
 
-> **WS-7 v5.0.0** — Subphase 3.5 for Android. Three-layer test strategy mirroring the iOS peer (ViewInspector → Compose Testing, Snapshot → Paparazzi/Roborazzi, Unit → JUnit).
+> **WS-7 v5.0.0**  -  Subphase 3.5 for Android. Three-layer test strategy mirroring the iOS peer (ViewInspector → Compose Testing, Snapshot → Paparazzi/Roborazzi, Unit → JUnit).
 
 ## Three-layer strategy (Android)
 
@@ -62,7 +62,7 @@ class ButtonPrimaryComposeTest {
 Rules:
 - Prefer `onNodeWithTag(TestingIdentifiers.buttonPrimary)` over `onNodeWithText` when the text is localised.
 - Every interactive state (enabled, disabled, loading) gets a test.
-- No `Thread.sleep` — use `composeRule.waitUntil { ... }` or `runTest` for coroutine flows.
+- No `Thread.sleep`  -  use `composeRule.waitUntil { ... }` or `runTest` for coroutine flows.
 
 ### 2. `{Name}SnapshotTest.kt` (visual)
 
@@ -113,7 +113,7 @@ Covers: fluent modifier semantics, default values, enum exhaustiveness.
 ./gradlew :${module}:recordPaparazziDebug
 ```
 
-On failure — up to 3 auto-fix cycles, then halt.
+On failure  -  up to 3 auto-fix cycles, then halt.
 
 ## Cross-CLI parity
 

package/pipeline/skills/figma-android/figma-component-wiki/SKILL.md

@@ -9,11 +9,11 @@ sourced-from: derived-from/figma-ios/figma-component-wiki
 platform: android
 ---
 
-# figma-component-wiki — Component Wiki (Android)
+# figma-component-wiki  -  Component Wiki (Android)
 
-> **WS-7 v5.0.0** — Android peer to `pipeline/skills/figma-ios/figma-component-wiki`. Identical dispatch contract (Phase 7 Report Step 2 → `{componentName, componentPath, figmaConfig, agentState}` → `{writtenPaths[], committedSha?, pushedRemote?}`). Identical 4-adapter matrix (submodule / in-repo / github-wiki / separate-repo). Only the markdown rendering differs: reads Kotlin composable signature + sibling `README.md` rather than SwiftUI `+Modifiers.swift` + `FIGMA.md`.
+> **WS-7 v5.0.0**  -  Android peer to `pipeline/skills/figma-ios/figma-component-wiki`. Identical dispatch contract (Phase 7 Report Step 2 → `{componentName, componentPath, figmaConfig, agentState}` → `{writtenPaths[], committedSha?, pushedRemote?}`). Identical 4-adapter matrix (submodule / in-repo / github-wiki / separate-repo). Only the markdown rendering differs: reads Kotlin composable signature + sibling `README.md` rather than SwiftUI `+Modifiers.swift` + `FIGMA.md`.
 
-See `pipeline/skills/figma-ios/figma-component-wiki/SKILL.md` for the full adapter table and dispatch contract — shared verbatim.
+See `pipeline/skills/figma-ios/figma-component-wiki/SKILL.md` for the full adapter table and dispatch contract  -  shared verbatim.
 
 ## Android-specific rendering notes
 
@@ -28,8 +28,8 @@ See `pipeline/skills/figma-ios/figma-component-wiki/SKILL.md` for the full adapt
 
 ## Python helpers
 
-Shared with the iOS peer — same `pipeline/scripts/wiki/sidebar-generator.py` and `pipeline/scripts/wiki/status-page.py` land in WS-5b. The helpers are platform-agnostic (they read component markdown files, not Swift or Kotlin sources).
+Shared with the iOS peer  -  same `pipeline/scripts/wiki/sidebar-generator.py` and `pipeline/scripts/wiki/status-page.py` land in WS-5b. The helpers are platform-agnostic (they read component markdown files, not Swift or Kotlin sources).
 
 ## Cross-CLI parity
 
-Byte-identical progress lines, identical adapter dispatch, identical return schema. Wiki layout convergence across iOS and Android is an explicit goal — the same `/components/{Category}/{Name}.md` path structure on every project regardless of platform.
+Byte-identical progress lines, identical adapter dispatch, identical return schema. Wiki layout convergence across iOS and Android is an explicit goal  -  the same `/components/{Category}/{Name}.md` path structure on every project regardless of platform.

package/pipeline/skills/figma-android/figma-to-component/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: figma-to-component
-description: Figma-to-Compose component implementation workflow for Android. Takes a Figma URL and produces a production-ready Jetpack Compose component through the same 8-phase pipeline shape as the iOS peer — data gathering, analysis, code generation, testing, Code Connect, documentation.
+description: Figma-to-Compose component implementation workflow for Android. Takes a Figma URL and produces a production-ready Jetpack Compose component through the same 8-phase pipeline shape as the iOS peer  -  data gathering, analysis, code generation, testing, Code Connect, documentation.
 user-invocable: true
 argument-hint: <figma-url> | phase-<N> | status
 allowed-tools: Task, Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion
@@ -9,9 +9,9 @@ sourced-from: derived-from/figma-ios/figma-to-component
 platform: android
 ---
 
-# figma-to-component — Android Orchestrator
+# figma-to-component  -  Android Orchestrator
 
-> **WS-7 v5.0.0** — Platform peer to `pipeline/skills/figma-ios/figma-to-component`. Same 8-phase shape; platform-specific phases (3-Token Mapping, 4-Code Gen, 5-Tests, 6-Code Connect) target Kotlin / Jetpack Compose / Paparazzi / Code Connect for Compose. Common phases (0-Init, 1-Gather, 2A–2D utilities, 7-Wiki, 8-Cleanup) share logic with the iOS peer — implementations stay in this skill for now; a `figma-common/` refactor lands in WS-7b.
+> **WS-7 v5.0.0**  -  Platform peer to `pipeline/skills/figma-ios/figma-to-component`. Same 8-phase shape; platform-specific phases (3-Token Mapping, 4-Code Gen, 5-Tests, 6-Code Connect) target Kotlin / Jetpack Compose / Paparazzi / Code Connect for Compose. Common phases (0-Init, 1-Gather, 2A-2D utilities, 7-Wiki, 8-Cleanup) share logic with the iOS peer  -  implementations stay in this skill for now; a `figma-common/` refactor lands in WS-7b.
 
 ## Dispatch entry
 
@@ -38,20 +38,20 @@ Called from multi-agent Phase 3 when `state.taskType === "component"` AND `figma
 | 3.0 | Init | no | Node-id parse, registry lookup, worktree confirm |
 | 3.1 | Gather | no | Figma API/MCP fetch, design tokens, properties |
 | 3.2a | Testing identifiers | no | Platform-agnostic semantic IDs (shared with iOS) |
-| 3.2b | Localization | no | Shared strings — lands in `{repos.common}` |
-| 3.2c | Accessibility | partial | `contentDescription` / `Role` / `semantics {}` vs SwiftUI's `.accessibility*` — the generator knows both |
+| 3.2b | Localization | no | Shared strings  -  lands in `{repos.common}` |
+| 3.2c | Accessibility | partial | `contentDescription` / `Role` / `semantics {}` vs SwiftUI's `.accessibility*`  -  the generator knows both |
 | 3.2d | Analytics | no | Shared analytics keys |
 | 3.3 | Token Mapping | **yes** | Maps Figma tokens → MaterialTheme dimensions / colorScheme / typography; outputs a per-project `DesignTokens.kt` if missing |
-| 3.4a | Configuration | **yes** | `{Name}Configuration.kt` — data class with all properties, marked `@Immutable`/`@Stable` for Compose skippability |
-| 3.4b | View | **yes** | `{Name}Screen.kt` or `{Name}.kt` — `@Composable fun {Name}(configuration: {Name}Configuration, modifier: Modifier = Modifier)` |
+| 3.4a | Configuration | **yes** | `{Name}Configuration.kt`  -  data class with all properties, marked `@Immutable`/`@Stable` for Compose skippability |
+| 3.4b | View | **yes** | `{Name}Screen.kt` or `{Name}.kt`  -  `@Composable fun {Name}(configuration: {Name}Configuration, modifier: Modifier = Modifier)` |
 | 3.4c | Docs | no | `README.md` next to the composable |
 | 3.4d | Preview | **yes** | `@Preview` functions covering variants (device, darkMode, RTL, fontScale) |
-| 3.4e | Modifiers | **yes** | Kotlin extension functions on `Modifier` or on the Configuration type — the fluent API the iOS peer expresses as `+Modifiers.swift` |
+| 3.4e | Modifiers | **yes** | Kotlin extension functions on `Modifier` or on the Configuration type  -  the fluent API the iOS peer expresses as `+Modifiers.swift` |
 | 3.5a | Structural tests | **yes** | `createComposeRule()` + semantic matchers (`onNodeWithText`, `onNodeWithTag`, `onNodeWithContentDescription`) |
 | 3.5b | Snapshot | **yes** | Paparazzi or Roborazzi snapshot tests covering light/dark, LTR/RTL, Dynamic Font Scale |
 | 3.5c | Unit | yes (opt) | Logic-only unit tests; `--dev` may elide |
-| 3.6 | Code Connect | **yes** | Code Connect for Compose — `{Name}.figma.kt` with `@FigmaConnect` variant mappings |
-| 3.7 | Wiki | no | Delegates to `figma-component-wiki` — same 4-mode adapter as iOS |
+| 3.6 | Code Connect | **yes** | Code Connect for Compose  -  `{Name}.figma.kt` with `@FigmaConnect` variant mappings |
+| 3.7 | Wiki | no | Delegates to `figma-component-wiki`  -  same 4-mode adapter as iOS |
 | 3.8 | Cleanup | no | Artifact pruning, state finalize |
 
 ## Delegation graph
@@ -61,10 +61,10 @@ figma-to-component (this skill)
 ├─ phase 3.4 (code gen)     → figma-component-implement  (Android peer)
 ├─ phase 3.5 (tests)        → figma-component-test        (Android peer)
 ├─ phase 3.6 (code connect) → figma-component-code-connect (Android peer)
-└─ phase 3.7 (wiki)         → figma-component-wiki        (Android peer — mode-aware adapter)
+└─ phase 3.7 (wiki)         → figma-component-wiki        (Android peer  -  mode-aware adapter)
 ```
 
-The platform-agnostic subphases (3.0–3.3, 3.2a–d, 3.8) use the same logic as the iOS orchestrator — they read `figmaConfig` + Figma API results and write registry entries that don't care about language target. WS-7b extracts those to `pipeline/skills/figma-common/` so both platforms import rather than duplicate.
+The platform-agnostic subphases (3.0-3.3, 3.2a-d, 3.8) use the same logic as the iOS orchestrator  -  they read `figmaConfig` + Figma API results and write registry entries that don't care about language target. WS-7b extracts those to `pipeline/skills/figma-common/` so both platforms import rather than duplicate.
 
 ## Build target resolution
 
@@ -89,7 +89,7 @@ If `build.gradleModule` is missing, halt with a clear "configure `figmaConfig.bu
 
 ## Component output locations
 
-Default layout — override per project via `figmaConfig.repos` and `figmaConfig.artifactBasePath`:
+Default layout  -  override per project via `figmaConfig.repos` and `figmaConfig.artifactBasePath`:
 
 | Artifact | Path |
 |---|---|
@@ -99,7 +99,7 @@ Default layout — override per project via `figmaConfig.repos` and `figmaConfig
 | Instrumented/Compose tests | `{repos.components.path}/src/androidTest/java/.../components/{Category}/{Name}ComposeTest.kt` |
 | Snapshot tests | Beside Compose tests, using Paparazzi's `@get:Rule val paparazzi = Paparazzi(...)` |
 | Code Connect | `{repos.components.path}/src/main/java/.../components/{Category}/{Name}/{Name}.figma.kt` |
-| Component artifacts | `{artifactBasePath}/{Category}/{Name}/` (screenshots, specs — platform-agnostic) |
+| Component artifacts | `{artifactBasePath}/{Category}/{Name}/` (screenshots, specs  -  platform-agnostic) |
 
 ## Design token conventions
 

package/pipeline/skills/figma-common/README.md

@@ -1,42 +1,49 @@
-# figma-common — Platform-agnostic figma-to-component skills
+# figma-common  -  Platform-agnostic figma-to-component skills
 
 Shared skills that both `pipeline/skills/figma-ios/` (SwiftUI) and `pipeline/skills/figma-android/` (Jetpack Compose) dispatch. Moved here by WS-7b of the v5.0.0 rebuild so the platform trees stay lean and there's no duplication.
 
-## What lives here (27 skills)
+## What lives here (31 skills)
 
 **Workflow orchestration:**
 
-- `figma-component-start` — Issue → branches, check out worktree
-- `figma-component-confluence-sync` — Phase 7b: wiki markdown → Confluence XHTML
-- `figma-component-status-update` — Refresh Confluence dashboard
-- `figma-commit` — 14-item review + PR creation
-- `figma-iteration-commit` — Commit to iteration/develop + PR
+- `figma-component-start`  -  Issue → branches, check out worktree
+- `figma-component-confluence-sync`  -  Phase 7b: wiki markdown → Confluence XHTML
+- `figma-component-status-update`  -  Refresh Confluence dashboard
+- `figma-commit`  -  14-item review + PR creation
+- `figma-iteration-commit`  -  Commit to iteration/develop + PR
 
 **Batch + iterate:**
 
-- `figma-iterate` — Auto loop: pick → implement → commit
-- `figma-cli-iterate` — Full CLI iterate (all phases)
-- `figma-cli-lean-iterate` — Iterate skipping test + wiki
-- `figma-cli-iterate-mend` — Re-implement discarded components
-- `figma-cli-skip` — Mark component as skipped
-- `figma-skip` — Skip + update Confluence dashboard
+- `figma-iterate`  -  Auto loop: pick → implement → commit
+- `figma-cli-iterate`  -  Full CLI iterate (all phases)
+- `figma-cli-lean-iterate`  -  Iterate skipping test + wiki
+- `figma-cli-iterate-mend`  -  Re-implement discarded components
+- `figma-cli-skip`  -  Mark component as skipped
+- `figma-skip`  -  Skip + update Confluence dashboard
 
 **Issue + review:**
 
-- `figma-issue` — Create GitHub issue + optional Jira (feeds WS-6 triad)
-- `figma-review` — Interactive review gate (approve / bug / skip)
-- `figma-validate` — Pre-implementation validation
-- `figma-fix` — Targeted bug fix from review findings
-- `figma-mend` — Re-implement component from scratch
+- `figma-issue`  -  Create GitHub issue + optional Jira (feeds WS-6 triad)
+- `figma-review`  -  Interactive review gate (approve / bug / skip)
+- `figma-validate`  -  Pre-implementation validation
+- `figma-fix`  -  Targeted bug fix from review findings
+- `figma-mend`  -  Re-implement component from scratch
+- `figma-evolve-component`  -  Reconcile drift + additively extend an existing component (human-gated)
 
 **Setup + utility:**
 
-- `figma-setup` — Environment setup wizard (MCP, tokens, Code Connect CLI)
-- `figma-remote-mcp-auth` — Figma MCP OAuth flow
-- `figma-utility` — Figma data fetch (screenshots, metadata)
-- `figma-ui-patterns` — UI pattern library index
-- `figma-form-integration` — Form protocol adapter (shared UX)
-- `figma-price-integration` — Price protocol adapter (shared UX)
+- `figma-setup`  -  Environment setup wizard (MCP, tokens, Code Connect CLI)
+- `figma-remote-mcp-auth`  -  Figma MCP OAuth flow
+- `figma-utility`  -  Figma data fetch (screenshots, metadata)
+- `figma-ui-patterns`  -  UI pattern library index
+- `figma-form-integration`  -  Form protocol adapter (shared UX)
+- `figma-price-integration`  -  Price protocol adapter (shared UX)
+
+**Cross-cutting interaction adapters (native-SwiftUI-first; project system via `figma-config` `ui.*`):**
+
+- `figma-navigation`  -  Navigation pattern: headless Output vs self-route; native `NavigationStack` or `ui.navigationSystem`
+- `figma-overlays`  -  Overlay pattern: toast/HUD/alert/data-modal; native `.alert`/`.sheet(item:)` or `ui.overlaySystem`
+- `figma-bottom-sheets`  -  Bottom-sheet/detent pattern: native `.presentationDetents` or `ui.sheetSystem`
 
 **Performance batch:**
 
@@ -46,12 +53,12 @@ Shared skills that both `pipeline/skills/figma-ios/` (SwiftUI) and `pipeline/ski
 
 Platform-specific skills stay under `figma-ios/` or `figma-android/`:
 
-- `figma-to-component` — orchestrator (platform-specific build command)
-- `figma-component-implement` — Swift / Kotlin code generator
-- `figma-component-test` — SwiftUI ViewInspector / Compose Testing
-- `figma-component-code-connect` — Swift / Kotlin Code Connect
-- `figma-component-wiki` — same 4-adapter contract, but platform-aware rendering
+- `figma-to-component`  -  orchestrator (platform-specific build command)
+- `figma-component-implement`  -  Swift / Kotlin code generator
+- `figma-component-test`  -  SwiftUI ViewInspector / Compose Testing
+- `figma-component-code-connect`  -  Swift / Kotlin Code Connect
+- `figma-component-wiki`  -  same 4-adapter contract, but platform-aware rendering
 
 ## Invocation
 
-Both platforms' orchestrators call the same common skill paths — no CLI or platform routing needed. The cross-CLI contract (`refs/cross-cli-contract.md` § 1.1) enforces the inventory.
+Both platforms' orchestrators call the same common skill paths  -  no CLI or platform routing needed. The cross-CLI contract (`refs/cross-cli-contract.md` section 1.1) enforces the inventory.

package/pipeline/skills/figma-common/figma-bottom-sheets/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: figma-bottom-sheets
+description: "Bottom-sheet / detent pattern integration for Figma-to-SwiftUI components — half-sheets, drawers, pinned bottom CTAs, resizable pull-up panels, content-sized sheets, and multi-step in-sheet flows. Native SwiftUI (.sheet + presentationDetents/dragIndicator/backgroundInteraction) by default; an optional project-supplied detent-sheet system when figma-config declares one. Reach for this when a design shows a bottom sheet, half-sheet, bottom drawer, snap points, a sticky footer button, or a wizard-in-a-sheet."
+user-invocable: true
+allowed-tools: Read, Glob, Grep
+status: wip-v5
+sourced-from: upstream/figma-bottom-sheets
+---
+
+# /figma-bottom-sheets  -  Bottom-Sheet / Detent Pattern Integration
+
+## Purpose
+
+Consumed by the figma-to-swiftui pipeline (Phase 3D detection, Phase 4B view) and available ad-hoc, this skill defines how **bottom-anchored, detent-based surfaces** are presented. Sibling of `/figma-overlays` (transient/blocking overlays) and `/figma-navigation` (routing): native-SwiftUI default + a config-driven hook for projects that ship a custom detent-sheet engine.
+
+**Generic by design.** Default is stock SwiftUI `.sheet` + `.presentationDetents`. If `figma-config.json` declares `ui.sheetSystem`, route through that engine by name  -  same rules, project vocabulary. (Some apps replace system sheets because iOS 26 forces a Liquid-Glass floating inset on partial detents with no removal API; that replacement is the custom-system case, not the default.)
+
+---
+
+## Strict Rules (non-negotiable)
+
+1. **The sheet surface is a caller concern; the component is the content.** A reusable component authored from Figma is the sheet's **content**, not the presenter. The caller owns the `isPresented`/`item` binding and the detents. A component that presents itself can't be reused elsewhere.
+2. **No magic numbers.** Detents, corner radius, grabber size, insets come from tokens / figma-config token patterns, never hard-coded literals.
+3. **Detents ascend, max 3.** Pass `[detent]` lowest→highest; the sheet opens at the lowest. Prefer semantic detents (`.medium`, `.large`, `.fraction`, content-height) over pixel heights where possible.
+4. **A bottom sheet is not a modal card and not a navigation push.** Data alert/modal card → `/figma-overlays`; screen routing → `/figma-navigation` (a routed modal may still *render* as a sheet, but navigation owns the routing).
+5. **Native SwiftUI is the default; a custom sheet engine is opt-in via config.** Only use a project detent-sheet system when `ui.sheetSystem.mode == "custom"`.
+
+---
+
+## When to Invoke This Skill
+
+1. **Phase 3D  -  sheet affordance/pattern:** the design is (or contains) a bottom sheet / half-sheet / drawer, a **pinned bottom CTA** bar, a resizable pull-up panel, a **content-sized** sheet, or a **multi-step** in-sheet flow (in-sheet back/next that resizes per step).
+2. **Phase 4B  -  View:** the view is authored as sheet content, or presents a child as a sheet.
+3. **Ad-hoc:** "half sheet", "bottom drawer", "pull-up panel", "snap points", "sticky footer button", "multi-step sheet", "sheet sized to its content".
+
+**Not a bottom sheet (guards):**
+- Toast / HUD / alert / data modal card → `/figma-overlays`.
+- Full screen navigation / tab / deep link → `/figma-navigation`.
+- An inline expandable section within the page flow (not an anchored surface) → plain component content.
+
+---
+
+## Native-first architecture (default)
+
+```
+Caller
+    |  owns isPresented / item + detents; presents the component as content
+    v
+.sheet(item:/isPresented:) {
+    ComponentContent()                    // the Figma-authored component
+      .presentationDetents([.medium, .large])
+      .presentationDragIndicator(.visible)
+      .presentationBackgroundInteraction(.enabled(upThrough: .medium))  // passthrough-ish
+      .presentationCornerRadius(<token>)
+}
+```
+
+- **Half / expandable:** `.presentationDetents([.medium, .large])` or `[.fraction(0.25), .fraction(0.6), .large]`.
+- **Content-sized:** `.presentationDetents([.height(measuredHeight)])` using a height read via a preference key (a `sizeThatFits`/`GeometryReader` measured content height), then scroll past the cap.
+- **Pinned bottom CTA (part of the screen, not a modal):** `.safeAreaInset(edge: .bottom) { CTA() }`  -  reserves space, screen stays interactive. This is NOT a presented sheet.
+- **Backdrop behavior:** dim+block is the `.sheet` default; passthrough/interactive-behind uses `.presentationBackgroundInteraction(.enabled(...))`.
+- **Multi-step in-sheet flow:** drive a `NavigationStack(path:)` *inside* the sheet content for push/pop, resizing detents per step; each step is a headless view emitting `Output` (see `/figma-navigation`). If the target project's custom engine forbids a nested `NavigationStack`, use its engine (config hook).
+- **Overlays over a sheet:** mount the toast/HUD host on the sheet content (`/figma-overlays`), not the root.
+
+Tokens per `reference/ui` + figma-config token patterns.
+
+## Config hook  -  project-supplied detent-sheet engine
+
+When `figma-config.json` declares:
+```jsonc
+"ui": { "sheetSystem": {
+  "mode": "custom",
+  "brandedModifier": "bottomSheet",       // .bottomSheet(isPresented:title:) branded entry
+  "headlessModifiers": ["modalSheet", "dockedSheet", "expandableSheet", "detentNavigationSheet"],
+  "detentType": "SheetDetentType",         // detent enum
+  "backdropType": "Backdrop",              // backdrop enum
+  "cornerRadiusToken": ".Radius.n12"       // branded top-corner token
+}}
+```
+apply the SAME rules via the project's engine (names from config, do NOT hardcode):
+- Use `.{brandedModifier}` for product sheets needing brand chrome; the headless modifiers for unbranded surfaces / CTAs / resizable panels / multi-step flows.
+- Detents/backdrops use `{detentType}`/`{backdropType}` values; corner radius from `{cornerRadiusToken}`.
+- Multi-step flows use the engine's navigation sheet (e.g. `detentNavigationSheet` with a `Navigator<Route>`) rather than a raw nested `NavigationStack`.
+- One container-owned grabber (pass custom headers grabberless if the engine draws the grabber).
+- Present only from the surface's own host  -  never walk the scene/window hierarchy for a "top" controller.
+
+If `mode` is absent or `native`, use the native-first section.
+
+---
+
+## Integration with Phase 3D
+
+Record in `04b_component_architecture.md`:
+
+```markdown
+## Bottom Sheet
+| Signal | Surface | Detents | Owner |
+|---|---|---|---|
+| Half-sheet picker | presented sheet | [.medium, .large] | caller owns isPresented |
+| Sticky "Devam Et" bar | pinned bottom CTA | n/a (safeAreaInset) | part of screen |
+| 3-step add flow | multi-step in-sheet | per-step (content height) | caller drives path |
+```
+
+Property classification addition:
+
+| Classification | When | Swift Pattern |
+|---|---|---|
+| Sheet content | Component is authored to live inside a sheet | plain component; caller adds `.presentationDetents(...)` |
+| Present-child-as-sheet | Component reveals a child surface | caller-owned `isPresented`/`item` + `.sheet` (component emits the trigger intent) |
+| Pinned CTA | Sticky bottom action bar | `.safeAreaInset(edge:.bottom)` at the screen, not a modal |
+
+## Integration with Phase 4B
+- Author the component as sheet **content**; let the caller own presentation + detents.
+- Prefer semantic detents; content-sized sheets measure height via a preference key.
+- Pinned CTA = `.safeAreaInset(edge:.bottom)`, not a presented sheet.
+- Multi-step flow = `NavigationStack` inside the sheet (native) or the engine's nav sheet (custom).
+- If `ui.sheetSystem.mode == custom`, use `{brandedModifier}`/headless modifiers + `{detentType}`/`{backdropType}` per config.
+- Verify on the simulator across detents, backdrop, and drag/dismiss on the project's min + current iOS.
+
+---
+
+## When NOT to Use Bottom-Sheet Integration
+- Toast/HUD/alert/data modal card → `/figma-overlays`.
+- Screen routing/tabs/deep links → `/figma-navigation`.
+- An inline expandable/disclosure within page flow → plain component content.
+
+## Checklist  -  Before Leaving the Skill
+```
+[ ] Component is sheet CONTENT; caller owns isPresented/item + detents
+[ ] Detents ascend, max 3; semantic detents preferred; no magic-number heights
+[ ] Pinned CTA uses safeAreaInset(edge:.bottom), not a presented sheet
+[ ] Content-sized sheet measures height via preference key, then scrolls
+[ ] Multi-step flow uses NavigationStack-in-sheet (native) or engine nav sheet (custom)
+[ ] Corner radius / grabber / insets from tokens, not literals
+[ ] Default native SwiftUI; custom engine only when figma-config ui.sheetSystem.mode == custom
+[ ] Overlays over the sheet mount on the sheet content surface
+```

package/pipeline/skills/figma-common/figma-cli-iterate/SKILL.md

@@ -1,14 +1,19 @@
-# /figma-cli-iterate — Full Pipeline Orchestrator for CLI
+---
+name: figma-cli-iterate
+description: Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
+---
+
+# /figma-cli-iterate  -  Full Pipeline Orchestrator for CLI
 
 ## Purpose
 
 Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
 
-This skill IS the orchestrator. It dispatches **only leaf-phase subagents** — individual phase instruction files that read one doc, execute gates, and return. It never delegates to multi-phase meta-skills.
+This skill IS the orchestrator. It dispatches **only leaf-phase subagents**  -  individual phase instruction files that read one doc, execute gates, and return. It never delegates to multi-phase meta-skills.
 
 ## Forbidden Dispatches
 
-**NEVER dispatch these as subagents — they are orchestrators that would try to dispatch further:**
+**NEVER dispatch these as subagents  -  they are orchestrators that would try to dispatch further:**
 
 - `/figma-to-swift-ui-implement` (Phases 0-4)
 - `/figma-to-swift-ui-test` (Phase 5)
@@ -43,7 +48,7 @@ SCRIPT_DIR      = .instructions/figma/figma-to-swiftui/scripts
 
 ---
 
-## STEP 0 — Pick Issue
+## STEP 0  -  Pick Issue
 
 Same logic as `/figma-iterate` STEP 0. Read `.instructions/figma/figma-iterate/SKILL.md` STEP 0 for details.
 
@@ -51,7 +56,7 @@ Extract from issue body: `componentName`, `figmaUrl`, `nodeId`, `jiraKey`, `regi
 
 ---
 
-## STEP 1 — Start
+## STEP 1  -  Start
 
 Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/SKILL.md` for the full procedure:
 
@@ -61,7 +66,7 @@ Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/S
 4. Registry lookup → `componentLocation`, `artifactPath`
 5. Save specs artifact if acceptance criteria exist
 6. Assign (GitHub + Jira)
-7. **Move GitHub issue to "In Develop" on the Projects V2 board** — required. Read STEP 5 of the start skill. Run both GraphQL mutations: set Status option `bc6c45f7` (In Develop) and Phase option `0577dcda` (Implementation). Do NOT skip this — new issues are created with Status=Todo, so this transition is how the board reflects "someone is working on it".
+7. **Move GitHub issue to "In Develop" on the Projects V2 board**  -  required. Read STEP 5 of the start skill. Run both GraphQL mutations: set Status option `bc6c45f7` (In Develop) and Phase option `0577dcda` (Implementation). Do NOT skip this  -  new issues are created with Status=Todo, so this transition is how the board reflects "someone is working on it".
 
 ---
 
@@ -74,7 +79,7 @@ These 6 rules govern orchestrator behavior. Violations have caused repeated fail
 
 ---
 
-## STEP 2 — Implement (Phases 0-7)
+## STEP 2  -  Implement (Phases 0-7)
 
 This is the core orchestration. Run each phase by dispatching leaf subagents and scripts.
 
@@ -83,7 +88,7 @@ This is the core orchestration. Run each phase by dispatching leaf subagents and
 Before dispatching any Phase 4+ subagent, check if `{artifactPath}/pass0/specs.md` exists. If it does:
 1. Read the specs
 2. Extract concrete requirements
-3. Inject them as **CRITICAL SPEC GATES** in the subagent dispatch prompt — NOT as a sidecar "also read this file" instruction
+3. Inject them as **CRITICAL SPEC GATES** in the subagent dispatch prompt  -  NOT as a sidecar "also read this file" instruction
 
 This ensures spec requirements become indistinguishable from standard gates.
 
@@ -130,7 +135,7 @@ You are executing {Phase Name} of the Figma-to-SwiftUI workflow.
 - GitHub Issue: {issueNumber} (omit if not available)
 
 ## CRITICAL SPEC GATES (only if specs exist)
-{Concrete requirements extracted from specs — phrased as mandatory instructions, not a file reference}
+{Concrete requirements extracted from specs  -  phrased as mandatory instructions, not a file reference}
 
 ## Tool Restrictions
 {from dispatch table}
@@ -146,7 +151,7 @@ Read the return protocol from:
 {relevant reference files from the read-order table in figma-to-swiftui/SKILL.md}
 
 ## Previous Phase Artifacts
-{artifact paths in read order — compact first}
+{artifact paths in read order  -  compact first}
 ```
 
 ### Phase Execution Flow
@@ -183,7 +188,7 @@ If `COMPLETE_WITH_DEFERRED` → dispatch Phase 1 deferred resolution subagent.
 3. Wave 1 (parallel): dispatch 4B + 4C (+ 4A if COMPLEX)
 4. Wave 2 (parallel): dispatch 4D (+ 4E if COMPLEX)
 5. Validate: `bash ${SCRIPT_DIR}/validate-phase4.sh ...`
-6. Build: `xcodebuild build ...` — fix errors if any
+6. Build: `xcodebuild build ...`  -  fix errors if any
 
 **Phase 5**:
 1. Switch to local common: comment out remote URL in Package.swift, add local path
@@ -198,7 +203,7 @@ If `COMPLETE_WITH_DEFERRED` → dispatch Phase 1 deferred resolution subagent.
 
 ---
 
-## STEP 3 — Commit
+## STEP 3  -  Commit
 
 Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the full procedure:
 
@@ -212,13 +217,13 @@ Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the f
 
 ---
 
-## STEP 4 — Loop
+## STEP 4  -  Loop
 
 Same logic as `/figma-iterate` STEP 4. If specific issue → exit after one. If `--count` → decrement. Otherwise → pick next.
 
 ---
 
-## STEP 5 — Output Result
+## STEP 5  -  Output Result
 
 Output EXACTLY this block as your FINAL message. Nothing else after it.
 
@@ -274,4 +279,4 @@ ORCHESTRATOR_RESULT:
 - **Phase HALT**: Show reason, ask user. If resolved → retry phase. If skipped → FAILED for this component, move to next.
 - **Build failure**: Attempt auto-fix. If unfixable → FAILED.
 - **3 consecutive failures**: Stop iteration.
-- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that — run its gates directly in the subagent.
+- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that  -  run its gates directly in the subagent.