@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

package/pipeline/skills/figma-common/performance-tour/SKILL.md

@@ -1,423 +0,0 @@
----
-name: performance-tour
-description: Produces multiple Figma components in a single session. Validates dependencies, determines implementation order, produces each component sequentially with clean subagent contexts, then hands off to review and batch.
----
-
-# /performance-tour  -  Batch Component Production Pipeline
-
-> Produces multiple Figma components in a single session. Validates dependencies,
-> determines implementation order, produces each component sequentially with clean
-> subagent contexts, then hands off to review and batch commit.
-
-## Parameters
-
-| Parameter | Required | Default | Description |
-|-----------|----------|---------|-------------|
-| `<issue-numbers>` | Yes |  -  | Comma-separated GitHub issue numbers from uicomponents repo |
-| `--resume` | No |  -  | Resume an interrupted tour from `_tour_tracker.json` |
-| `--lean` | No |  -  | Lean mode: skip Phase 5 (testing) and Phase 7 (wiki) for all components. Forwarded to `performance-start --lean` → `performance-swiftui --lean`. |
-
-```
-/performance-tour 1000, 1001, 1002
-/performance-tour 200, 201, 202, 203, 204
-/performance-tour 1000, 1001, 1002 --lean
-/performance-tour --resume
-```
-
----
-
-## Constants
-
-```
-REPO_ROOT       = git repo root (auto-detect)
-GH_REPO         = {github.componentsRepo}
-COMMON          = ${REPO_ROOT}/{repos.common.path}
-UICOMPONENTS    = ${REPO_ROOT}/{repos.components.path}
-WIKI            = ${REPO_ROOT}/{repos.wiki.path}
-TRACKER_FILE    = ${REPO_ROOT}/_tour_tracker.json
-MAX_COMPONENTS  = 5
-```
-
----
-
-## Tour Tracker File
-
-The `_tour_tracker.json` is the **single source of truth** for the entire tour. It survives
-context loss and conversation timeouts. Written after every state change.
-
-```json
-{
-  "tour_start": "2026-04-07T10:00:00Z",
-  "lean_mode": false,
-  "issues": [1000, 1001, 1002],
-  "execution_order": [1000, 1002, 1001],
-  "components": {
-    "1000": {
-      "name": "ComponentA",
-      "node_id": "2820:25995",
-      "figma_url": "https://www.figma.com/design/...",
-      "jira_key": "{jira.projectKey}-129850",
-      "artifact_path": "ImplementationArtifacts/...",
-      "component_location": "Sources/.../ComponentA",
-      "status": "produced",
-      "phase_halted": null,
-      "halt_reason": null,
-      "commit_sha": {
-        "common": null,
-        "uicomponents": null,
-        "wiki": null
-      },
-      "files_created": [],
-      "perf_tracker_path": "ImplementationArtifacts/.../_perf_tracker.json"
-    }
-  },
-  "dependency_graph": {
-    "1001": ["1000"]
-  },
-  "current_step": "STEP_1",
-  "current_component": 1002,
-  "halted_components": [],
-  "produced_components": [1000],
-  "reviewed_components": [],
-  "committed_components": []
-}
-```
-
-**CRITICAL:** Write the tracker file after every state change  -  component status update,
-step transition, HALT event, review completion. This is the mechanism that survives context loss.
-
----
-
-## STEP 0  -  Parse, Validate & Sort
-
-### 0a. Parse Issues
-
-Parse comma-separated issue numbers from arguments.
-
-```bash
-# For each issue number:
-gh issue view <N> --repo ${GH_REPO} --json number,title,body,labels,state
-```
-
-Extract from each issue body:
-- **Component Name**  -  from `### Component Name (PascalCase)` section
-- **Figma URL**  -  from `### Figma URL` section
-- **Node ID**  -  from `### Node ID` section
-- **Registry Name**  -  from `### Registry Name` section
-- **Jira Key**  -  from `### Jira Issue` section
-
-Validate:
-- Issue is open → if closed, remove from tour with warning
-- Issue is not blocked → if has `blocked` label, remove from tour with warning
-- Required fields exist → if missing, HALT entire tour
-
-### 0b. Validate Each Component
-
-Run `/figma-validate` logic for each issue (inline, not as skill invocation):
-- Criterion 7 (Already Implemented)  -  if already implemented, remove from tour
-- Criterion 4 (Dependency Readiness)  -  collect nested dependencies
-
-### 0c. Build Dependency Graph
-
-For each component, check if any of its nested child INSTANCE node IDs match another
-component in this tour:
-
-```python
-# For each component pair (A, B):
-#   Does A's Figma node contain B's node ID as a child instance?
-#   Does B's Figma node contain A's node ID as a child instance?
-```
-
-If component B depends on component A (B uses A as nested child):
-- Record in `dependency_graph`: `{ "B_issue": ["A_issue"] }`
-- B must be produced AFTER A
-
-If circular dependency detected → HALT tour, report the cycle.
-
-### 0d. Topological Sort
-
-Sort components by dependency order:
-1. Components with no dependencies first
-2. Components that others depend on, before their dependents
-3. Independent components in original issue order
-
-```python
-# Simple topological sort (Kahn's algorithm)
-# Input: dependency_graph
-# Output: execution_order (list of issue numbers)
-```
-
-### 0e. Fetch Latest (ONE TIME)
-
-```bash
-cd ${COMMON}
-git fetch origin
-git checkout iteration/develop
-git pull origin iteration/develop
-
-cd ${UICOMPONENTS}
-git fetch origin
-git checkout iteration/develop
-git pull origin iteration/develop
-
-cd ${WIKI}
-git fetch origin
-git checkout master
-git pull origin master
-```
-
-### 0f. Initialize Tracker
-
-Create `_tour_tracker.json` with all parsed data, dependency graph, and execution order.
-If `--lean` flag is present, set `"lean_mode": true` in the tracker.
-
-Print tour plan:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PERFORMANCE TOUR  -  PLAN                                     ║
-╠══════════════════════════════════════════════════════════════╣
-║                                                              ║
-║  Execution Order:                                            ║
-║  1. #1000  -  ComponentA (independent)                        ║
-║  2. #1002  -  ComponentC (independent)                        ║
-║  3. #1001  -  ComponentB (depends on: ComponentA)             ║
-║                                                              ║
-║  Dependency Graph:                                           ║
-║  ComponentA ← ComponentB                                     ║
-║  ComponentC (independent)                                    ║
-║                                                              ║
-╚══════════════════════════════════════════════════════════════╝
-
-Proceed? (yes/no)
-```
-
-Wait for user confirmation before proceeding to STEP 1.
-
----
-
-## required PRE-READ
-
-Before proceeding to STEP 1 (production loop), read:
-  .instructions/figma/figma-to-swiftui/reference/orchestrator-discipline.md
-
-These 6 rules govern orchestrator behavior across the tour. Rules 2 (every dispatched component must complete), 3 (on HALT retry, never take over), and 4 (complementary skills are not dismissable) apply directly to the tour's sequential produce + HALT cleanup flow.
-
----
-
-## STEP 1  -  Sequential Produce + Local Commit
-
-For each component in `execution_order`:
-
-### 1a. Start (performance-start --tour)
-
-Invoke `/performance-start <issue-number> --tour` (add `--lean` if `lean_mode` is `true` in tracker):
-- Parses issue metadata (STEP 0)
-- **SKIPS** fetch + pull (STEP 1)  -  already done in STEP 0e
-- **SKIPS** branch creation (STEP 2)  -  staying on iteration/develop
-- Runs registry lookup (STEP 3)
-- Saves specs artifact (STEP 3.5)
-- Assigns to me + sets In Progress (STEP 4, 5)
-- Prints summary (STEP 6)
-- Auto-launches `/performance-swiftui <figma-url>` (STEP 6)  -  with `--lean` if lean mode
-
-### 1b. Wait for production to complete
-
-`performance-swiftui` runs Phase 0-7 as a subagent chain (or Phase 0-4 + 6 in lean mode). When it completes:
-
-**If COMPLETE:**
-
-```bash
-# Local commit  -  all submodules
-cd ${COMMON}
-git add -A
-git commit -m "feat(common): [${JIRA_KEY}] add ${COMPONENT_NAME} tokens and keys
-
-Refs: ${JIRA_KEY}
-Tour: performance-tour $(date +%Y%m%d)"
-
-cd ${UICOMPONENTS}
-git add -A
-git commit -m "feat(uicomponents): [${JIRA_KEY}] add ${COMPONENT_NAME} component
-
-Refs: ${JIRA_KEY}
-Tour: performance-tour $(date +%Y%m%d)"
-
-# Wiki commit  -  SKIP if lean_mode is true
-if [ "$LEAN_MODE" != "true" ]; then
-cd ${WIKI}
-git add -A
-git commit -m "docs: [${JIRA_KEY}] add ${COMPONENT_NAME} wiki documentation
-
-Refs: ${JIRA_KEY}
-Tour: performance-tour $(date +%Y%m%d)"
-fi
-```
-
-Update tracker: set component status to `"produced"`, record files created.
-
-**If HALT:**
-
-Run selective cleanup (tracker-guided):
-
-```bash
-# 1. Identify HALT'd component's files from tracker/artifact
-COMPONENT_LOCATION="${component.component_location}"
-ARTIFACT_PATH="${component.artifact_path}"
-
-# 2. Remove isolated files (component-specific directories)
-rm -rf "${UICOMPONENTS}/${COMPONENT_LOCATION}"
-# Remove test directories if created (skip check in lean mode  -  tests weren't generated)
-if [ "$LEAN_MODE" != "true" ]; then
-find "${UICOMPONENTS}/Tests" -type d -name "${COMPONENT_NAME}*" -exec rm -rf {} +
-# Remove snapshot baselines if created
-find "${UICOMPONENTS}/Tests" -path "*/__Snapshots__/${COMPONENT_NAME}*" -exec rm -rf {} +
-fi
-
-# 3. Remove component's keys from shared files
-# Read artifact's {nodeId}.json for key list
-# Use common-utility to remove keys:
-cd ${COMMON}
-swift run UITestingIdentifierTool remove --component ${COMPONENT_NAME} 2>/dev/null || true
-# For localization and accessibility: regenerate from remaining components
-swift package plugin --allow-writing-to-package-directory update-localizations-dev
-swift package plugin --allow-writing-to-package-directory update-accessibility-dev
-
-# 4. Remove Code Connect file if created
-find "${UICOMPONENTS}" -name "${COMPONENT_NAME}.figma.swift" -exec rm -f {} +
-
-# 5. Remove wiki file if created (skip in lean mode)
-if [ "$LEAN_MODE" != "true" ]; then
-find "${WIKI}" -name "${COMPONENT_NAME}*" -exec rm -f {} +
-fi
-
-# 6. Verify working tree is clean for this component
-git -C "${COMMON}" diff --name-only
-git -C "${UICOMPONENTS}" diff --name-only
-git -C "${WIKI}" diff --name-only
-```
-
-Update tracker: set component status to `"halted"`, record `phase_halted` and `halt_reason`.
-Add to `halted_components` list.
-
-Print:
-
-```
-⚠️ ComponentB HALTED at Phase 4  -  build failure
-   Files cleaned up. Proceeding to next component.
-   ComponentB can be fixed during review session.
-```
-
-### 1c. Progress Update
-
-After each component (produced or halted), print progress:
-
-```
-Tour Progress: 2/3 produced, 1/3 halted
-  ✅ #1000  -  ComponentA (produced)
-  ❌ #1001  -  ComponentB (halted: Phase 4 build failure)
-  🔄 #1002  -  ComponentC (in progress...)
-```
-
-### 1d. Loop
-
-Continue to next component in `execution_order`. After all components processed:
-
-Update tracker: `current_step = "STEP_2"`.
-
-Print:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PRODUCTION COMPLETE                                         ║
-╠══════════════════════════════════════════════════════════════╣
-║  Produced: 2/3                                               ║
-║  Halted:   1/3                                               ║
-║                                                              ║
-║  ✅ #1000  -  ComponentA                                       ║
-║  ✅ #1002  -  ComponentC                                       ║
-║  ❌ #1001  -  ComponentB (Phase 4 build failure)               ║
-║                                                              ║
-║  Next: /performance-review-next                              ║
-║  Or:   /performance-tour --resume                            ║
-╚══════════════════════════════════════════════════════════════╝
-```
-
----
-
-## STEP 2  -  Review Session
-
-Invoke `/performance-review-next`  -  this is a separate skill that reads the tracker
-and manages the interactive review loop.
-
-See `.instructions/figma/performance-review-next/SKILL.md` for details.
-
----
-
-## STEP 3  -  Batch Commit
-
-After all components are reviewed, invoke `/performance-iteration-commit-all`  -  this is
-a separate skill that validates, pushes, and handles issue housekeeping.
-
-See `.instructions/figma/performance-iteration-commit-all/SKILL.md` for details.
-
----
-
-## Resume Mode (`--resume`)
-
-When invoked with `--resume`:
-
-1. Read `_tour_tracker.json`
-2. Check `current_step` and `current_component`
-3. Resume from where it left off:
-   - If in STEP 1: continue producing remaining components
-   - If in STEP 2: invoke `/performance-review-next`
-   - If in STEP 3: invoke `/performance-iteration-commit-all`
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  RESUMING TOUR                                               ║
-╠══════════════════════════════════════════════════════════════╣
-║  Last state: STEP 1  -  producing ComponentC (#1002)          ║
-║  Produced:   1 (ComponentA)                                  ║
-║  Halted:     1 (ComponentB)                                  ║
-║  Remaining:  1 (ComponentC)                                  ║
-║                                                              ║
-║  Resuming production of ComponentC...                        ║
-╚══════════════════════════════════════════════════════════════╝
-```
-
----
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| No issues provided | HALT: "Provide at least 2 issue numbers" |
-| Issue not found / closed | Remove from tour, warn, continue with remaining |
-| All issues invalid | HALT: "No valid issues for tour" |
-| Circular dependency | HALT: "Circular dependency detected: A → B → A" |
-| FigmaRegistryUtility not built | Build it: `cd ${COMMON} && swift build --product FigmaRegistryUtility` |
-| Submodule not on iteration/develop | STEP 0e handles this (fetch + checkout) |
-| 3 consecutive HALTs | HALT tour: "Multiple consecutive failures. Review halted components before continuing." |
-| Tracker file missing (--resume) | HALT: "No tour in progress. Start a new tour." |
-| Tracker file corrupt | HALT: "Tracker file corrupt. Check _tour_tracker.json manually." |
-
----
-
-## Guardrails
-
-> **NEVER push during STEP 1.** All commits are local only. Push happens in STEP 3
-> via `/performance-iteration-commit-all`.
-
-> **NEVER create feature branches.** Stay on `iteration/develop` for all submodules.
-> Use `--tour` flag when invoking `performance-start`.
-> Use `--lean` flag when invoking `performance-start` if tour is in lean mode.
-
-> **NEVER skip STEP 0e (fetch latest).** The working tree must start from latest
-> remote `iteration/develop` to minimize rebase conflicts at push time.
-
-> **ALWAYS write tracker after every state change.** This is the recovery mechanism.
-
-> **ALWAYS clean up after HALT.** Do not leave half-produced files in the working tree.
-> The next component must start with a clean incremental state.

package/pipeline/skills/figma-ios/REVIEW_CHECKLIST.md

@@ -1,67 +0,0 @@
-# Figma-iOS Skill Review Checklist
-
-> **Status: WIP  -  v5.0.0 pass 1 (markdown only).** Every skill in this directory was imported from an upstream source via `pipeline/scripts/import-figma-skills.sh`. Placeholders have been applied, personal-data smoke is green, but **no skill is production-ready until it passes this checklist**. Common skills were moved to `pipeline/skills/figma-common/` in WS-7b  -  only platform-specific skills (orchestrator + implement + test + code-connect + wiki) remain here.
-
-## Scope of this pass
-
-- ✅ Markdown files transformed: `SKILL.md`, `phases/*.md`, `reference/*.md`, top-level support files (e.g. `halt-return-protocol.md`).
-- ❌ Python/shell scripts **not** imported in this pass  -  hardcoded paths beyond the placeholder map require manual review. Scheduled for WS-2b.
-
-## Per-skill review gates
-
-For each skill listed below, a reviewer must confirm:
-
-1. **Frontmatter accuracy**  -  `description`, `argument-hint`, `allowed-tools`, `user-invocable` reflect the generic behaviour. Remove `status: wip-v5` when passed.
-2. **Placeholder coverage**  -  run `grep -E '\{(github|jira|repos|build|confluence|project|user)\.' SKILL.md`  -  every placeholder must resolve from `figma-project-config.schema.json` v2.0.0. Any unresolved placeholder either extends the schema or becomes a literal default.
-3. **No upstream bleed**  -  `grep -riE 'turkish|dijital|thy\.com|PVT_[A-Za-z0-9]+' skill/` returns nothing. (Guarded by `smoke-personal-data.sh` globally.)
-4. **Cross-references**  -  internal links point at the new names (no `figma-to-swift-ui-*`). Script references either resolve under `scripts/` once WS-2b lands, or are explicitly commented as TODO.
-5. **Progress-contract adoption**  -  add the `<!-- progress-contract: applied -->` marker once the skill emits `→ <verb> <object>` lines per `refs/progress-contract.md`.
-6. **Android parity note**  -  for component-implement/component-test, note which bits are iOS-only so WS-7 can write the Android peer.
-7. **Smoke green**  -  `smoke-figma-skill-import.sh`, `smoke-personal-data.sh`, `smoke-commands-skills-parity.sh`, `smoke-progress-contract.sh`.
-
-## Skills to review (32)
-
-| Skill | Source upstream | Reviewed? | Notes |
-|---|---|---|---|
-| figma-cli-iterate | figma-cli-iterate | ⬜ | Batch iterate runner |
-| figma-cli-iterate-mend | figma-cli-iterate-mend | ⬜ | Batch mend runner |
-| figma-cli-lean-iterate | figma-cli-lean-iterate | ⬜ | Iterate without test+wiki |
-| figma-cli-skip | figma-cli-skip | ⬜ | Skip a component |
-| figma-commit | figma-commit | ⬜ | 14-item review + PR |
-| figma-component-code-connect | figma-to-swift-ui-code-connect | ⬜ | Renamed |
-| figma-component-confluence-sync | figma-to-swift-ui-confluence-sync | ⬜ | Renamed |
-| figma-component-implement | figma-to-swift-ui-implement | ⬜ | Renamed. Android peer needed (WS-7). |
-| figma-component-start | figma-to-swift-ui-start | ⬜ | Renamed. Issue → branches. |
-| figma-component-status-update | figma-to-swift-ui-status-update | ⬜ | Renamed. Confluence dashboard refresh. |
-| figma-component-test | figma-to-swift-ui-test | ⬜ | Renamed. Android peer needed (WS-7). |
-| figma-component-wiki | figma-to-swift-ui-wiki | ⬜ | Renamed. WS-5 wiki mode integration. |
-| figma-fix | figma-fix | ⬜ | Targeted bug fix |
-| figma-form-integration | figma-form-integration | ⬜ | Form protocol adapter |
-| figma-issue | figma-issue | ⬜ | GitHub + Jira issue creation. WS-6 triad source. |
-| figma-iterate | figma-iterate | ⬜ | Auto loop |
-| figma-iteration-commit | figma-iteration-commit | ⬜ | Batch iteration commit |
-| figma-mend | figma-mend | ⬜ | Re-implement from scratch |
-| figma-price-integration | figma-price-integration | ⬜ | Price protocol adopter |
-| figma-remote-mcp-auth | figma-remote-mcp-auth | ⬜ | Figma MCP OAuth |
-| figma-review | figma-review | ⬜ | Interactive review |
-| figma-setup | figma-setup | ⬜ | Env wizard |
-| figma-skip | figma-skip | ⬜ | Skip + update Confluence |
-| figma-to-component | figma-to-swiftui | ⬜ | **Orchestrator.** Renamed to platform-agnostic name. Biggest review surface. |
-| figma-ui-patterns | figma-ui-patterns | ⬜ | Pattern library |
-| figma-utility | figma-utility | ⬜ | Figma data fetch |
-| figma-validate | figma-validate | ⬜ | Pre-impl validation |
-| performance-iteration-commit-all | performance-iteration-commit-all | ⬜ | Batch validate + push |
-| performance-review-next | performance-review-next | ⬜ | Interactive batch review |
-| performance-start | performance-start | ⬜ | Perf-tracked start |
-| performance-swiftui | performance-swiftui | ⬜ | Perf-optimized pipeline |
-| performance-tour | performance-tour | ⬜ | Batch produce components |
-
-## Follow-up workstreams that consume this output
-
-- **WS-2b**  -  Import Python/shell scripts with transform + manual review.
-- **WS-4**  -  Reduce Phase 3 dispatch to single `figma-to-component` call.
-- **WS-5**  -  Wiki mode adapter; update `figma-component-wiki`.
-- **WS-6**  -  Issue → Jira → Wiki triad; extend `figma-issue` + `figma-component-wiki`.
-- **WS-7**  -  Android peer skills (`figma-component-implement-android`, `figma-component-test-android`).
-- **WS-8**  -  Cross-CLI parity matrix expansion.
-- **WS-11**  -  Add `<!-- progress-contract: applied -->` marker + `→ <verb>` lines to each skill.

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

@@ -1,178 +0,0 @@
----
-name: figma-component-code-connect
-description: "Figma Code Connect mapping publisher for implemented SwiftUI components. Creates + publishes .figma.swift registration for a component already built via Phase 4 codegen. Runs standalone (reads source files + fetches Figma property data) or as a Phase 3.6 continuation. iOS platform peer  -  Android equivalent lives under figma-android/."
-user-invocable: true
-argument-hint: "<figma-url> | --component <name>"
-language: en
-platform: ios
-status: wip-v5
-sourced-from: upstream/figma-to-swift-ui-code-connect
-local-overlay: true
----
-
-# figma-component-code-connect  -  Standalone Code Connect Publish
-
-## Purpose
-
-Creates and publishes Figma Code Connect mapping for an implemented component. Works independently from `/figma-to-swiftui`  -  reads source files and fetches Figma property data directly. Can also run as a continuation after Phase 5 when full artifacts exist.
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| Figma URL | Yes | `https://www.figma.com/design/{fileKey}/...?node-id={nodeId}` |
-
-```
-/figma-code-connect https://www.figma.com/design/9ipBvrtsq9HlQ175B9k0wx/?node-id=2073-17454
-```
-
----
-
-## Parse Arguments
-
-Extract from Figma URL:
-```
-https://www.figma.com/design/{fileKey}/{fileName}?node-id={nodeId}
-```
-Convert `-` to `:` in node-id.
-
----
-
-## Gate 0: Preliminary Check
-
-### 1. Resolve Component
-
-```bash
-cd {repos.common.path}
-.build/debug/FigmaRegistryUtility lookup --node-id '{nodeId}'
-```
-
-Extract: `componentName`, `suggestedComponentLocation`, `suggestedArtifactPath`.
-
-### 2. Verify Prerequisites
-
-| Check | Required | Source |
-|-------|----------|--------|
-| `{componentLocation}/{ComponentName}.swift` | Yes | Component must be implemented |
-| `{componentLocation}/FIGMA.md` | Yes | Must have variant mapping |
-| Figma Access Token (Keychain) | Yes | For parse + publish |
-| `figma` CLI or npx | Yes | For parse + publish |
-
-If Swift file or FIGMA.md missing → HALT. Component not implemented.
-
-### 3. Check Existing Code Connect
-
-| Condition | Action |
-|-----------|--------|
-| `{ComponentName}.figma.swift` exists | **UPDATE** mode  -  will overwrite |
-| `{ComponentName}.figma.swift` missing | **CREATE** mode |
-
-### 4. Detect Path: HOT or COLD
-
-| Condition | Path |
-|-----------|------|
-| `{artifactPath}/pass1/component_properties.json` exists | **HOT**  -  skip Gate 1, go to Gate 2 |
-| Missing | **COLD**  -  run Gate 1 |
-
----
-
-## Gate 1: Property Accumulation (COLD path only)
-
-Two-step process: script (Figma REST API) → AI subagent (deduction).
-
-### Step 1: Script  -  Fetch Component Properties
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/code-connect-data-gather.py \
-    --file-key "{fileKey}" \
-    --node-id "{nodeId}" \
-    --artifact-path "{artifactPath}"
-```
-
-This script:
-1. Calls Figma REST API: `GET /v1/files/{fileKey}/nodes?ids={nodeId}`
-2. Extracts `componentPropertyDefinitions` from the node document
-3. Writes `pass1/component_properties.json` in the same format Phase 1 produces
-
-### Step 2: AI Subagent  -  Boolean Classification
-
-Dispatch a subagent (sonnet, 15 turns) to read source files and produce the variant config analysis:
-
-| Source | Derives |
-|--------|---------|
-| FIGMA.md (variant mapping table) | Property names, values, Swift mappings |
-| Swift source (enums, types, optionals) | Boolean → Swift type classification |
-| `pass1/component_properties.json` | Figma property types (VARIANT, BOOLEAN, TEXT) |
-
-Writes: `pass3/04c_variant_config_analysis.json`
-
-After this step, phase-6 can't distinguish HOT from COLD.
-
----
-
-## Gate 2: Code Connect Generation + Publish
-
-Delegate to the shared phase instruction:
-
-```
-.instructions/figma/figma-to-swiftui/phases/phase-6-code-connect.md
-```
-
-Dispatch as subagent with:
-- componentName, fileKey, nodeId, artifactPath, componentLocation
-- All standard context variables
-
-The phase file is shared with `/figma-to-swiftui`  -  same templates, same validation, same publish flow.
-
----
-
-## Gate 3: Registry Update
-
-Run the Phase 6 finalize script:
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/phase6-finalize.py \
-    --node-id '{nodeId}' \
-    --file-key '{fileKey}' \
-    --component-name '{componentName}' \
-    --platform ios
-```
-
-Updates `codeConnect.ios = true` in the component registry JSON.
-
----
-
-## Dispatch Table
-
-| Gate | Instruction | Model | Max Turns |
-|------|-------------|-------|-----------|
-| 0 | Inline (this file) |  -  |  -  |
-| 1 Step 1 | Script (`code-connect-data-gather.py`) |  -  |  -  |
-| 1 Step 2 | AI subagent | sonnet | 15 |
-| 2 | `phases/phase-6-code-connect.md` (shared) | opus | 30 |
-| 3 | Script (`phase6-finalize.py`) |  -  |  -  |
-
----
-
-## Shared Resources
-
-These files are shared with `/figma-to-swiftui` phase 6:
-
-| Resource | Used By |
-|----------|---------|
-| `phases/phase-6-code-connect.md` | Gate 2 |
-| `reference/code-connect.md` | Gate 2 |
-| `scripts/phase6-finalize.py` | Gate 3 |
-| `scripts/validate-phase6.sh` | Gate 2 (inside phase-6) |
-| `figma.config.json` (in uicomponents) | Gate 2 (publish) |
-
----
-
-## Notes
-
-- Standalone entry point  -  does NOT require `/figma-to-swiftui` to have run
-- When called after Phase 5, detects existing artifacts (HOT path) and skips data gathering
-- The data gather script produces the same artifact structure as Phase 1
-- Phase 6 instruction file doesn't know which skill invoked it  -  fully modular
-- Handles the `figma.config.json` exclude list for broken components (see phase-6 sectionGATE 5)
-- If component has no Figma property definitions → uses STATIC_VALUES strategy automatically