@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-common/figma-commit/COMMON_REBASE.md

@@ -1,4 +1,4 @@
-# Common Submodule — Rebase, Resolve, Validate & Push
+# Common Submodule  -  Rebase, Resolve, Validate & Push
 
 Handles `{project.slug}-common` branch creation, conflict resolution, regeneration, validation, and PR flow.
 
@@ -18,7 +18,7 @@ Called from `/figma-commit` SKILL.md after code review passes.
 
 ---
 
-## STEP 1 — Stash
+## STEP 1  -  Stash
 
 ```bash
 cd "${COMMON_PATH}"
@@ -27,7 +27,7 @@ git stash push -u -m "figma-commit: ${COMPONENT_PASCAL} pre-branch stash"
 
 Skip if `git status --porcelain` is empty.
 
-## STEP 2 — Fetch & Branch from develop
+## STEP 2  -  Fetch & Branch from develop
 
 ```bash
 cd "${COMMON_PATH}"
@@ -39,7 +39,7 @@ git checkout -b "${BRANCH_NAME}"
 
 If branch already exists → append `-v2`, `-v3`, etc.
 
-## STEP 3 — Pop Stash
+## STEP 3  -  Pop Stash
 
 ```bash
 cd "${COMMON_PATH}"
@@ -49,9 +49,9 @@ git stash pop
 If pop succeeds cleanly → skip to STEP 5.
 If pop fails with conflicts → proceed to STEP 4.
 
-## STEP 4 — Conflict Resolution
+## STEP 4  -  Conflict Resolution
 
-### 4A — Classify conflicted files
+### 4A  -  Classify conflicted files
 
 | File Pattern | Strategy |
 |-------------|----------|
@@ -65,17 +65,17 @@ If pop fails with conflicts → proceed to STEP 4.
 | Source JSONs (see below) | **Union merge** |
 | `Shared/Figma/Components/*.json` | Our version wins (we created/modified it) |
 
-### 4B — Union merge for source JSONs
+### 4B  -  Union merge for source JSONs
 
 For each conflicted source JSON:
 
 ```
 a. Accept OURS (develop) version: git checkout --ours <file> && git add <file>
 b. Manually insert only the NEW keys from the branch (use Edit tool, match existing format exactly)
-c. NEVER use Python json.dump or any JSON serializer — it reformats the entire file
+c. NEVER use Python json.dump or any JSON serializer  -  it reformats the entire file
 d. After manual edits, normalize with the Swift tool:
    .build/debug/UITestingIdentifierTool format
-e. Verify: key count >= develop's count — no key lost
+e. Verify: key count >= develop's count  -  no key lost
 ```
 
 **Source files requiring union merge:**
@@ -83,25 +83,25 @@ e. Verify: key count >= develop's count — no key lost
 | File | Resolution | Format Tool |
 |------|-----------|-------------|
 | `Shared/UITestingIdentifiers/ui-testing-identifiers.json` | Accept ours + insert new keys | `UITestingIdentifierTool format` |
-| `Shared/UIAssets/Colors/*.json` | Accept ours + insert new entries | (manual — match existing format) |
+| `Shared/UIAssets/Colors/*.json` | Accept ours + insert new entries | (manual  -  match existing format) |
 
 **Files that NO LONGER need union merge** (per-key files or gitignored):
 - `*-data-suggested.json` → replaced by `Sources/Suggested/*.json` (per-key files, never conflict)
-- `*-data-merged.json` → gitignored (derived artifact, regenerated in §5)
-- `*-metadata.json` → gitignored (derived artifact, regenerated in §5)
-- `Metadata/identifier-keys.json` → gitignored (derived artifact, regenerated in §5)
+- `*-data-merged.json` → gitignored (derived artifact, regenerated in section5)
+- `*-metadata.json` → gitignored (derived artifact, regenerated in section5)
+- `Metadata/identifier-keys.json` → gitignored (derived artifact, regenerated in section5)
 
-### 4C — Text file union merge
+### 4C  -  Text file union merge
 
-**No longer needed.** `localization-keys.txt` and `accessibility-keys.txt` are gitignored (regenerated in §5).
+**No longer needed.** `localization-keys.txt` and `accessibility-keys.txt` are gitignored (regenerated in section5).
 
-### 4D — Verify no conflict markers remain
+### 4D  -  Verify no conflict markers remain
 
 ```bash
 grep -r "<<<<<<" . --include="*.json" --include="*.swift" --include="*.txt" | head -5
 ```
 
-## STEP 5 — Rebuild Derived Artifacts
+## STEP 5  -  Rebuild Derived Artifacts
 
 All derived artifacts (merged data, metadata, keys.txt, registries, catalogs) are gitignored. Always rebuild them after conflict resolution to guarantee fresh data.
 
@@ -113,7 +113,7 @@ This script rebuilds everything: merge translations from per-key `Sources/Sugges
 
 If the script fails → source JSON likely has invalid syntax from merge. Fix and retry.
 
-## STEP 6 — Validate Integrity
+## STEP 6  -  Validate Integrity
 
 Always fetch develop first so the non-destruction check compares against the latest:
 
@@ -126,21 +126,21 @@ python3 "${REPO_ROOT}/.instructions/figma/figma-commit/validate-localization-syn
 ```
 
 **Must exit 0.** Validates:
-1. Suggested covers merged — every merged key has a corresponding per-key file in `Sources/Suggested/`
-2. All 8 languages present per key — no missing translations
+1. Suggested covers merged  -  every merged key has a corresponding per-key file in `Sources/Suggested/`
+2. All 8 languages present per key  -  no missing translations
 3. No empty suggested values
 4. keys.txt and metadata in sync with merged
 5. Key count non-decreasing vs develop
-6. Non-destruction — no key removed vs develop
+6. Non-destruction  -  no key removed vs develop
 7. Testing identifiers JSON ↔ keys JSON match
 
 If validation fails → fix before committing. Common fixes:
 - **Keys in merged not in suggested**: Add missing per-key file via `TranslationManagerTool add`
-- **Key count decreased**: Key lost during merge — find and restore the per-key file
-- **Empty values**: Translation added without content — provide it
+- **Key count decreased**: Key lost during merge  -  find and restore the per-key file
+- **Empty values**: Translation added without content  -  provide it
 - **Non-destruction violation**: Intentional rename → re-add old key as alias
 
-## STEP 7 — Commit
+## STEP 7  -  Commit
 
 ```bash
 cd "${COMMON_PATH}"
@@ -157,14 +157,14 @@ EOF
 )"
 ```
 
-## STEP 8 — Push
+## STEP 8  -  Push
 
 ```bash
 cd "${COMMON_PATH}"
 git push -u origin "${BRANCH_NAME}"
 ```
 
-## STEP 9 — Create PR (do NOT merge)
+## STEP 9  -  Create PR (do NOT merge)
 
 ```bash
 cd "${COMMON_PATH}"
@@ -190,17 +190,17 @@ EOF
 )"
 ```
 
-**Do NOT merge** — PR is created for review. Merging is a separate manual action.
+**Do NOT merge**  -  PR is created for review. Merging is a separate manual action.
 
 ---
 
 ## Error Handling
 
-- **Stash conflict on pop**: Follow §4 conflict resolution
+- **Stash conflict on pop**: Follow section4 conflict resolution
 - **Branch already exists**: Append `-v2`, `-v3`
 - **Push rejected**: Report error, do NOT force-push
 - **Not on develop**: Warn user, ask confirmation
-- **Rebuild script fails**: Source JSON likely invalid from merge — fix and retry
-- **Validation fails**: Fix before committing — NEVER skip validation
-- **Key count decreased**: STOP — per-key file was lost, check `Sources/Suggested/` for missing files
-- **Same-key conflict in union merge**: Ask user which version to keep — do NOT silently overwrite (only applies to UIAssets Colors and UITestingIdentifiers now)
+- **Rebuild script fails**: Source JSON likely invalid from merge  -  fix and retry
+- **Validation fails**: Fix before committing  -  NEVER skip validation
+- **Key count decreased**: STOP  -  per-key file was lost, check `Sources/Suggested/` for missing files
+- **Same-key conflict in union merge**: Ask user which version to keep  -  do NOT silently overwrite (only applies to UIAssets Colors and UITestingIdentifiers now)

package/pipeline/skills/figma-common/figma-commit/REVIEW.md

@@ -33,7 +33,7 @@ Verify test files exist:
 |------|----------|----------|
 | `{ComponentName}ViewInspectorTests.swift` | Always | `Tests/UIComponentsTests/ViewInspector/Components/.../` |
 | `{ComponentName}SnapshotTests.swift` | Always | `Tests/UIComponentsTests/Snapshot/Components/.../` |
-| Snapshot reference images | Never committed | `__Snapshots__/` is gitignored — generated on-demand via `record: .missing` |
+| Snapshot reference images | Never committed | `__Snapshots__/` is gitignored  -  generated on-demand via `record: .missing` |
 
 **FAIL if:** ViewInspector or Snapshot test file is missing. **FAIL if:** `__Snapshots__/` directory is tracked by git (should be gitignored).
 
@@ -43,7 +43,7 @@ Verify test files exist:
 
 Scan ALL production Swift files (NOT test files) for hardcoded values.
 
-### 2.1 Dimensions — Must Use Tokens or Named Constants
+### 2.1 Dimensions  -  Must Use Tokens or Named Constants
 
 Every numeric `CGFloat` in production code must come from a design token OR a named constant in a `private enum Constants`. Component-specific sizes that don't map to an existing design token (e.g., icon sizes from Figma specs) are valid in `Constants`:
 
@@ -67,7 +67,7 @@ Grep for raw numeric CGFloat values in {ComponentName}.swift and {ComponentName}
 
 **FAIL if:** Any raw inline dimension value found (e.g., `frame(height: 56)`). Named constants in `Constants` enum are PASS.
 
-### 2.2 Colors — Must Use Semantic Tokens
+### 2.2 Colors  -  Must Use Semantic Tokens
 
 Prefer design tokens. No `Color(red:green:blue:)`, no `UIColor` literals, no SwiftUI named colors (`.red`, `.white`).
 
@@ -87,7 +87,7 @@ When a color has no matching design token and must be hardcoded in `Constants`,
 
 **FAIL if:** `Color(red:green:blue:)`, `Color(.sRGB, ...)`, or SwiftUI named colors (`.red`, `.blue`, `.white`, etc.) found in production code.
 
-### 2.3 Typography — Must Use TypographyStyle
+### 2.3 Typography  -  Must Use TypographyStyle
 
 No raw `.font()` calls. All text styling via `.typographyStyle()`.
 
@@ -104,11 +104,11 @@ These raw values are acceptable and should NOT be flagged:
 
 - `0` as zero padding/offset
 - `.infinity` in `frame(maxWidth: .infinity)`
-- Named constants in `private enum Constants` — these are NOT magic numbers
+- Named constants in `private enum Constants`  -  these are NOT magic numbers
 - Numeric values in test files (snapshot frame sizes, assertion values)
 - Numeric values in `#Preview` section labels (e.g., section divider count)
-- Opacity values (`0.0` to `1.0`) — no token system for opacity
-- `lineLimit(1)` — SwiftUI view modifier, not a dimension
+- Opacity values (`0.0` to `1.0`)  -  no token system for opacity
+- `lineLimit(1)`  -  SwiftUI view modifier, not a dimension
 
 ---
 
@@ -327,8 +327,8 @@ bash "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/run-uicomponents
 
 | Level | Meaning | Action |
 |-------|---------|--------|
-| **FAIL** | Blocking — must fix before commit | Fix all FAIL items |
-| **WARN** | Non-blocking — should fix but can commit | Document in PR description |
+| **FAIL** | Blocking  -  must fix before commit | Fix all FAIL items |
+| **WARN** | Non-blocking  -  should fix but can commit | Document in PR description |
 | **PASS** | Compliant | No action needed |
 | **N/A** | Not applicable | SIMPLE components skip Configuration/+Modifiers checks |
 

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

@@ -1,4 +1,9 @@
-# /figma-commit — Review, Branch, Commit & Push
+---
+name: figma-commit
+description: Reviews a Figma component implementation, then creates feature branches across submodules, commits, pushes, and opens PRs. Delegates mobile-common conflict resolution to `COMMON_REBASE.md`.
+---
+
+# /figma-commit  -  Review, Branch, Commit & Push
 
 ## Purpose
 
@@ -8,9 +13,9 @@ Reviews a Figma component implementation, then creates feature branches across s
 
 | Parameter | Required | Default | Description |
 |-----------|----------|---------|-------------|
-| `component-name` | Yes | — | PascalCase component name (e.g., `TurkishButton`) |
+| `component-name` | Yes |  -  | PascalCase component name (e.g., `TurkishButton`) |
 | `--jira` | No | `{jira.projectKey}-124692` | Jira issue key |
-| `--gh` | No | — | GitHub issue number (for branch name construction) |
+| `--gh` | No |  -  | GitHub issue number (for branch name construction) |
 
 ```
 /figma-commit TurkishButton
@@ -21,7 +26,7 @@ Reviews a Figma component implementation, then creates feature branches across s
 
 ## Workflow
 
-### STEP 0 — Resolve Parameters
+### STEP 0  -  Resolve Parameters
 
 1. Parse `component-name`. Convert to kebab-case for branch name.
 2. Parse `--jira` or use default `{jira.projectKey}-124692`.
@@ -48,7 +53,7 @@ Reviews a Figma component implementation, then creates feature branches across s
    - `FIGMA_URL` = from component registry JSON (`confluence.page` field's sibling `figmaUrl`)
    - `CONFLUENCE_IOS_URL` = from component registry JSON (`confluence.ios` field)
 
-### STEP 1 — Code Review & Auto-Fix
+### STEP 1  -  Code Review & Auto-Fix
 
 1. Read `.instructions/figma/figma-commit/REVIEW.md`.
 2. Run the full 13-point review checklist against the component.
@@ -64,9 +69,9 @@ Reviews a Figma component implementation, then creates feature branches across s
 7. If unfixable violations remain → ask user.
 8. If PASS or WARN → proceed.
 
-### STEP 2 — Detect Changes Per Repo
+### STEP 2  -  Detect Changes Per Repo
 
-`git status --porcelain` shows all tracked changes in short format — modified, added, deleted, untracked. Each line starts with a two-character status code (e.g., `M` modified, `??` untracked, `A` added, `D` deleted).
+`git status --porcelain` shows all tracked changes in short format  -  modified, added, deleted, untracked. Each line starts with a two-character status code (e.g., `M` modified, `??` untracked, `A` added, `D` deleted).
 
 ```bash
 HAS_MAIN=$(cd "${REPO_ROOT}" && git status --porcelain | grep -v '^?? {repos.packagesContainer}/Packages/' | head -1)
@@ -76,13 +81,13 @@ HAS_COMMON=$(cd "${REPO_ROOT}/{repos.common.path}" && git status --porcelain | h
 
 **Main repo PR decision**: Skip if only submodule pointer changes (no `.instructions/` or `.claude/skills/` modifications).
 
-### STEP 3 — Common Submodule (if HAS_COMMON)
+### STEP 3  -  Common Submodule (if HAS_COMMON)
 
-**Read and follow `.instructions/figma/figma-commit/COMMON_REBASE.md`** — handles stash, branch, conflict resolution, regeneration, validation, commit, push, and PR for mobile-common.
+**Read and follow `.instructions/figma/figma-commit/COMMON_REBASE.md`**  -  handles stash, branch, conflict resolution, regeneration, validation, commit, push, and PR for mobile-common.
 
-**Do NOT merge the PR** — only create it and push. Merging is done manually by the team.
+**Do NOT merge the PR**  -  only create it and push. Merging is done manually by the team.
 
-### STEP 4 — UIComponents Submodule (if HAS_UICOMPONENTS)
+### STEP 4  -  UIComponents Submodule (if HAS_UICOMPONENTS)
 
 UIComponents rarely has conflicts (new files only). Simple flow:
 
@@ -114,7 +119,7 @@ Refs: ${JIRA_ISSUE}
 EOF
 )"
 
-# Push & PR (do NOT merge — PR only)
+# Push & PR (do NOT merge  -  PR only)
 git push -u origin "${BRANCH_NAME}"
 gh pr create --base develop \
     --title "feat(uicomponents): [${JIRA_ISSUE}] add ${COMPONENT_PASCAL}" \
@@ -137,7 +142,7 @@ EOF
 )"
 ```
 
-### STEP 5 — Main Repo (if skill/instruction changes)
+### STEP 5  -  Main Repo (if skill/instruction changes)
 
 ```bash
 cd "${REPO_ROOT}"
@@ -156,7 +161,7 @@ Refs: ${JIRA_ISSUE}
 EOF
 )"
 
-# Push & PR (do NOT merge — PR only)
+# Push & PR (do NOT merge  -  PR only)
 git push -u origin "${BRANCH_NAME}"
 gh pr create --base develop \
     --title "feat(skills): [${JIRA_ISSUE}] skill updates for ${COMPONENT_PASCAL}" \
@@ -168,7 +173,7 @@ Refs: ${JIRA_ISSUE}"
 
 Skip this step entirely if no `.instructions/` or `.claude/skills/` changes.
 
-### STEP 6 — Summary
+### STEP 6  -  Summary
 
 ```
 ## Commit Summary: ${COMPONENT_PASCAL}
@@ -197,8 +202,8 @@ Always: **common first → uicomponents → main repo**. Common PR must be merge
 - **Branch already exists**: Append `-v2`, `-v3`
 - **Push rejected**: Report error, do NOT force-push
 - **Submodule not on develop**: Warn user, ask confirmation
-- **Common conflicts**: Follow `COMMON_REBASE.md` §4
-- **Validation fails**: Fix before committing — NEVER skip
+- **Common conflicts**: Follow `COMMON_REBASE.md` section4
+- **Validation fails**: Fix before committing  -  NEVER skip
 
 ---
 
@@ -206,6 +211,6 @@ Always: **common first → uicomponents → main repo**. Common PR must be merge
 
 - Always stash before branch creation
 - Submodules branched and pushed independently
-- Review step (Step 1) uses full REVIEW.md checklist — NOT optional
-- PRs are created but NOT merged — merging is a separate manual action
-- No AI attribution in commit messages — follow `GIT_COMMIT_CONVENTION.md`
+- Review step (Step 1) uses full REVIEW.md checklist  -  NOT optional
+- PRs are created but NOT merged  -  merging is a separate manual action
+- No AI attribution in commit messages  -  follow `GIT_COMMIT_CONVENTION.md`

package/pipeline/skills/figma-common/figma-component-confluence-sync/SKILL.md

@@ -1,4 +1,9 @@
-# /figma-to-swift-ui-confluence-sync — Sync Wiki to Confluence
+---
+name: figma-component-confluence-sync
+description: Syncs component documentation from the GitHub Wiki (source of truth) to Confluence. Reads wiki markdown, converts to Confluence XHTML, uploads pages and assets. Requires VPN.
+---
+
+# /figma-to-swift-ui-confluence-sync  -  Sync Wiki to Confluence
 
 ## Purpose
 
@@ -171,9 +176,9 @@ Updates the global Component Implementation Status page on Confluence.
 
 ## Registry flag ownership (architecture-update)
 
-This skill is a **downstream mirror** of the GitHub Wiki. It **does not** own the `status.ios.wiki` flag in the component registry — that flag is set green by `/figma-to-swift-ui-wiki` via `scripts/phase7-finalize.py`, which is upstream of this sync. Confluence URLs are written into `{nodeId}.json.confluence.ios` by the publish script (Gate 4) so downstream readers can link out, but the 4-flag status block is untouched here.
+This skill is a **downstream mirror** of the GitHub Wiki. It **does not** own the `status.ios.wiki` flag in the component registry  -  that flag is set green by `/figma-to-swift-ui-wiki` via `scripts/phase7-finalize.py`, which is upstream of this sync. Confluence URLs are written into `{nodeId}.json.confluence.ios` by the publish script (Gate 4) so downstream readers can link out, but the 4-flag status block is untouched here.
 
-If you run this skill and the `wiki` flag is still gray/yellow, run `/figma-to-swift-ui-wiki` first — that's what owns the flag.
+If you run this skill and the `wiki` flag is still gray/yellow, run `/figma-to-swift-ui-wiki` first  -  that's what owns the flag.
 
 ---
 
@@ -211,8 +216,8 @@ rm -rf ${TEMP_DIR}
 ## Error Handling
 
 - **VPN not connected**: HALT with VPN instructions.
-- **Wiki markdown not found**: HALT — run Phase 7 first.
+- **Wiki markdown not found**: HALT  -  run Phase 7 first.
 - **Confluence token missing**: Prompt user to add to keychain.
 - **XHTML validation failed**: Show violations, retry conversion.
-- **Upload failed (401/403)**: Token expired — prompt refresh.
-- **Upload failed (404)**: Wrong parent page ID — check confluence-page-ids.json.
+- **Upload failed (401/403)**: Token expired  -  prompt refresh.
+- **Upload failed (404)**: Wrong parent page ID  -  check confluence-page-ids.json.

package/pipeline/skills/figma-common/figma-component-start/SKILL.md

@@ -1,4 +1,9 @@
-# /figma-to-swift-ui-start — Start Implementation from GitHub Issue
+---
+name: figma-component-start
+description: Reads a GitHub Issue, extracts component metadata, creates feature branches from `develop` (main repo) / `iteration/develop` (submodules), and checks them out locally. Prepares the workspace to begin implementation.
+---
+
+# /figma-to-swift-ui-start  -  Start Implementation from GitHub Issue
 
 ## Purpose
 
@@ -8,7 +13,7 @@ Reads a GitHub Issue, extracts component metadata, creates feature branches from
 
 | Parameter | Required | Default | Description |
 |-----------|----------|---------|-------------|
-| `<issue-number>` | Yes | — | GitHub issue number from uicomponents repo |
+| `<issue-number>` | Yes |  -  | GitHub issue number from uicomponents repo |
 
 ```
 /figma-to-swift-ui-start #107
@@ -36,19 +41,19 @@ WIKI            = ${REPO_ROOT}/{repos.wiki.path}
 
 ---
 
-## STEP 0 — Parse Issue
+## STEP 0  -  Parse Issue
 
 ```bash
 gh issue view <N> --repo ${GH_REPO} --json number,title,body,labels,assignees
 ```
 
 Extract from the 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
-- **Figma Page** — from `### Figma Page` section
-- **Acceptance Criteria** — from `### Acceptance Criteria` section (if not `_No response_`)
+- **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
+- **Figma Page**  -  from `### Figma Page` section
+- **Acceptance Criteria**  -  from `### Acceptance Criteria` section (if not `_No response_`)
 
 Derive:
 - `COMPONENT_PASCAL` = Component Name (e.g., `ModalsTitle`)
@@ -70,7 +75,7 @@ Print:
 
 ---
 
-## STEP 1 — Fetch Latest
+## STEP 1  -  Fetch Latest
 
 Ensure all repos are up to date with remote:
 
@@ -93,9 +98,9 @@ git pull origin iteration/develop
 
 ---
 
-## STEP 2 — Create Feature Branches
+## STEP 2  -  Create Feature Branches
 
-Create feature branches on **submodules only**. Do NOT create branches on the main repo — it stays on `develop`. The main repo never receives commits from this workflow; submodule refs are updated separately.
+Create feature branches on **submodules only**. Do NOT create branches on the main repo  -  it stays on `develop`. The main repo never receives commits from this workflow; submodule refs are updated separately.
 
 ```bash
 # Common (tokens, localization, accessibility, testing identifiers)
@@ -107,11 +112,11 @@ cd ${UICOMPONENTS}
 git checkout -b ${BRANCH_NAME}
 ```
 
-Wiki submodule stays on `master` — wiki changes are committed directly.
+Wiki submodule stays on `master`  -  wiki changes are committed directly.
 
 ---
 
-## STEP 3 — Registry Lookup
+## STEP 3  -  Registry Lookup
 
 ```bash
 cd ${COMMON}
@@ -119,8 +124,8 @@ cd ${COMMON}
 ```
 
 Collect:
-- `suggestedComponentLocation` — where the Swift files will go
-- `suggestedArtifactPath` — where implementation artifacts go
+- `suggestedComponentLocation`  -  where the Swift files will go
+- `suggestedArtifactPath`  -  where implementation artifacts go
 
 Print:
 
@@ -131,7 +136,7 @@ Artifact Path:      <suggestedArtifactPath>
 
 ---
 
-## STEP 3.5 — Save Specs Artifact
+## STEP 3.5  -  Save Specs Artifact
 
 If the issue has acceptance criteria (not `_No response_`), save them as an artifact that the implementation pipeline can consume.
 
@@ -150,21 +155,21 @@ Write `${suggestedArtifactPath}/pass0/specs.md`:
 
 ## Acceptance Criteria
 
-{ACCEPTANCE_CRITERIA from issue body — verbatim}
+{ACCEPTANCE_CRITERIA from issue body  -  verbatim}
 
 ## Implementation Guidance
 
 {Convert the acceptance criteria into actionable implementation instructions for the AI agent:
 - Rephrase checkbox items as concrete requirements
 - Add technical context where the criteria imply Swift/SwiftUI patterns
-- Preserve the user's intent exactly — don't add or remove requirements}
+- Preserve the user's intent exactly  -  don't add or remove requirements}
 ```
 
 If no acceptance criteria → skip this step. No file created.
 
 ---
 
-## STEP 4 — Assign to Me
+## STEP 4  -  Assign to Me
 
 Assign the GitHub issue to the current user:
 
@@ -174,7 +179,7 @@ gh issue edit <N> --repo ${GH_REPO} --add-assignee @me
 
 ---
 
-## STEP 5 — Update Issue Status (required)
+## STEP 5  -  Update Issue Status (required)
 
 **This step is mandatory. Do not skip it and do not defer it.** The issue
 is on the board with Status=Todo after creation. Moving it to Status=In
@@ -188,7 +193,7 @@ Set the issue phase to "Implementation" and status to "In Develop" on the Projec
 # Get issue node ID
 ISSUE_NODE_ID=$(gh api graphql -f query='{ repository(owner: "{github.org}", name: "{project.slug}-components") { issue(number: <N>) { id } } }' --jq '.data.repository.issue.id')
 
-# Add to project (if not already). This mutation is idempotent — if the
+# Add to project (if not already). This mutation is idempotent  -  if the
 # item already exists it returns the existing item id.
 ITEM_ID=$(gh api graphql -f query='mutation { addProjectV2ItemById(input: { projectId: "{github.projectV2Id}", contentId: "'"$ISSUE_NODE_ID"'" }) { item { id } } }' --jq '.data.addProjectV2ItemById.item.id')
 
@@ -210,12 +215,12 @@ gh api graphql -f query='{ node(id: "'"$ITEM_ID"'") { ... on ProjectV2Item { fie
 ```
 
 Expected output: `In Develop`. If you see anything else (or empty),
-re-fetch the current option IDs and retry — do NOT proceed to implementation
+re-fetch the current option IDs and retry  -  do NOT proceed to implementation
 without the Status set correctly.
 
 ---
 
-## STEP 6 — Summary
+## STEP 6  -  Summary
 
 Print:
 
@@ -241,6 +246,6 @@ Next: `/figma <figma-url>` to run the implementation pipeline.
 - **Issue not found**: Print error and stop.
 - **Issue body missing required fields**: Print which fields are missing, stop.
 - **FigmaRegistryUtility not built**: Run `swift build --product FigmaRegistryUtility` in common.
-- **Branch already exists**: Print warning — checkout existing branch instead of creating.
+- **Branch already exists**: Print warning  -  checkout existing branch instead of creating.
 - **Main repo not on develop**: Fetch and checkout automatically.
 - **Submodule not on iteration/develop**: Fetch and checkout automatically.

package/pipeline/skills/figma-common/figma-component-status-update/SKILL.md

@@ -1,4 +1,9 @@
-# /figma-to-swift-ui-status-update — Confluence Component Status Dashboard
+---
+name: figma-component-status-update
+description: Refreshes the global Component Implementation Status dashboard on Confluence.
+---
+
+# /figma-to-swift-ui-status-update  -  Confluence Component Status Dashboard
 
 ## Purpose
 
@@ -39,11 +44,11 @@ This script:
 4. Generates XHTML with color-coded status table
 5. Uploads to Confluence (updates in-place to avoid version bloat)
 
-The script reads the **architecture-update 4-flag status block** (`status.ios.{implemented,tested,codeConnect,wiki}`) — with fallback to legacy `codeConnect.ios` for any pre-backfill entry. Green/yellow/gray in the XHTML output is derived from `{value, against, implemented.version}`: green if `value=true` and `against >= implemented.version`, yellow if `against < implemented.version`, gray if `value=false`.
+The script reads the **architecture-update 4-flag status block** (`status.ios.{implemented,tested,codeConnect,wiki}`)  -  with fallback to legacy `codeConnect.ios` for any pre-backfill entry. Green/yellow/gray in the XHTML output is derived from `{value, against, implemented.version}`: green if `value=true` and `against >= implemented.version`, yellow if `against < implemented.version`, gray if `value=false`.
 
 ### 3. Output
 
-Report the script output — total components, implemented count, and per-flag status breakdown (implemented / tested / code-connected / wiki counts).
+Report the script output  -  total components, implemented count, and per-flag status breakdown (implemented / tested / code-connected / wiki counts).
 
 ### 4. Per-component sync (optional)
 
@@ -60,7 +65,7 @@ Or bulk:
 python3 .instructions/figma/figma-to-swiftui/scripts/bulk-sync-issues.py
 ```
 
-Bulk sync is already run by the `fix GitHub issues` job — only re-run if multiple registry entries have changed.
+Bulk sync is already run by the `fix GitHub issues` job  -  only re-run if multiple registry entries have changed.
 
 ---