@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.0

package/pipeline/skills/shared/core/multi-agent-refactor/SKILL.md

@@ -1,57 +1,99 @@
 ---
 name: multi-agent-refactor
 language: en
-description: "Analyse the project, score it, draft an improvement plan, take approval, develop, then ask whether to sync."
+description: "Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, draft one plan, take approval, develop, then ask whether to sync."
 user-invocable: true
-argument-hint: 'security | tests | performance | docs | ci | deps'
+argument-hint: 'bugs | best-practices | drift | security | tests | performance | docs | ci | deps'
 ---
 
 # Multi-Agent Refactor
 
-**One command. Analyze -> Score -> Plan -> Approval -> Develop -> Sync.**
+**One command. Best-practices + Bug hunt + Upstream drift -> Score -> Plan -> Approval -> Develop -> Sync.**
 
-Analyzes the current project in depth, scores it across 10 categories, plans all improvements, takes approval from the user, applies them, and asks about sync when done.
+Deep-analyses the current project, extracts the global best-practices worth adopting (adapted to our stack), hunts real bugs and improvement areas, checks whether any skills we derived from an upstream source have drifted, scores everything, drafts a single prioritized plan, takes approval, applies the approved items, and asks about sync when done.
 
-**Input**: $ARGUMENTS (optional  -  the area to focus on: "security", "performance", "tests", etc.)
+**Input**: $ARGUMENTS (optional  -  area to focus on: "security", "performance", "tests", "bugs", "best-practices", "drift", etc.)
 
 ## Flow
 
 ```
-Step 0: RESEARCH   Search competing projects on GitHub + Reddit, collect good ideas
-Step 1: SCAN       Scan the project structure (files, LOC, dependencies, CI, tests)
-Step 2: ANALYZE    In-depth analysis across 10 categories
-Step 3: SCORE      Each category out of 10, total /100
-Step 4: PLAN       List all improvements + competitor ideas in priority order
-Step 5: ASK        "Shall I start developing?"  -  take approval from the user
-Step 6: IMPLEMENT  Apply approved improvements in order (lint, test, commit)
-Step 7: VERIFY     Confirm all tests + lint pass
-Step 8: ASK SYNC   "Shall I run multi-agent-sync?"  -  take approval from the user
+Step 0:  BEST-PRACTICES  Research the field, extract the best approaches, ADAPT them to our stack -> plan band A
+Step 0b: DRIFT           Check upstream-derived skills for updates we have not pulled -> plan band D
+Step 1:  SCAN            Scan the project structure (files, LOC, dependencies, CI, tests)
+Step 2:  ANALYZE         10 categories + an explicit BUG HUNT (real defects, not just scores) -> plan bands B, C
+Step 3:  SCORE           Each category out of 10, total /100
+Step 4:  PLAN            Merge bands A (best-practice) + B (bugs) + C (improvements) + D (drift), priority-ordered
+Step 5:  ASK             "Shall I start developing?"  -  take approval
+Step 6:  IMPLEMENT       Apply approved items in order (lint, test, commit)
+Step 7:  VERIFY          Confirm all tests + lint pass
+Step 8:  ASK SYNC        "Shall I run multi-agent-sync?"  -  take approval
 ```
 
-## Step 0: RESEARCH  -  Competitor Analysis
+Plan bands (all four feed the single Step 4 table):
+- **A - Best-practice**: the best field approaches, adapted so they actually fit this repo.
+- **B - Bug**: real defects found in the code (correctness, security, data-loss, crashes).
+- **C - Improvement**: quality/perf/DX gaps surfaced by the 10-category analysis.
+- **D - Drift**: upstream updates to skills we derived from an external source.
 
-Before starting development, research similar projects:
+## Step 0: BEST-PRACTICES  -  research the field, adapt to us
 
-1. **GitHub Search**: `multi-agent pipeline AI development` + `Claude Code pipeline` + `AI coding agent`
-   - Find repos with stars:>10
-   - Read their READMEs
-   - Extract unique features
-2. **Reddit Search**: multi-agent discussions in `r/ClaudeAI`, `r/ChatGPT`, `r/LocalLLaMA`
-3. **For each competitor, record**:
-   - Unique features we do NOT have
-   - Ideas worth adopting
-   - Things they do better than us
-   - Things we do better than them
-4. **Include in the plan**: Add high-impact + low-effort ideas to the PLAN step (P1 priority)
+Do not copy features blindly. The goal is the best *approaches*, reshaped so they are applicable to THIS project's stack, size, and constraints.
+
+1. **Identify the domain** (read README + package/build manifests): kind of project, stack, users.
+2. **Research the best-in-class** for that exact domain:
+   - **GitHub**: search the domain terms + `stars:>50`; read the top repos' READMEs, architecture docs, CI configs, test layout.
+   - **X / Twitter**: search the domain terms + "best practices" / "we switched to" / "lesson learned"; capture what practitioners recommend right now (WebFetch/WebSearch on `x.com` / `twitter.com` threads).
+   - **Reddit**: relevant subreddits for real-world pain points and adopted patterns.
+   - **Web**: "<domain> best practices <current-year>", official style guides, platform guidance.
+3. **For each candidate approach, record**: what it is + source, the concrete benefit, the **adaptation** (exactly how it looks in OUR repo: which file/dir/script and what changes), effort (L/M/H), impact (L/M/H/Critical).
+4. **Discard** approaches that do not fit our stack/scale/constraints  -  and say WHY.
+
+Output (plan band A):
+```
+| Source | Approach | Adaptation to our repo | Effort | Impact | In plan? |
+|--------|----------|------------------------|--------|--------|----------|
+| <repo> | <what>   | <concrete change here> | Low    | High   | Yes (P1) |
+| <repo> | <what>   | does not fit: <reason> | -      | -      | No       |
+```
+Roll the high-impact + low/med-effort survivors into the Step 4 plan as band-A items.
+
+## Step 0b: DRIFT  -  upstream-derived skill check
+
+Some skills/components in this project (or in the marketplace plugins it ships) were derived from an upstream source. Upstream keeps evolving  -  it fixes bugs and adds features. This step detects upstream drift so we can decide whether to pull the improvements back.
+
+The upstream mapping is **configuration, never hardcoded** (it can reference private sources, so it stays out of the shipped skill). Read it from `~/.claude/multi-agent-preferences.json` at `global.derivedSkillSources` (an array). Each entry:
+
+```jsonc
+{
+  "label": "<human name for this derivation>",
+  "localPath": "<repo-relative dir where our derived copy lives>",
+  "upstreamMarketplace": "<installed marketplace name>",   // resolved under ~/.claude/plugins/cache/<marketplace>/
+  "upstreamPlugin": "<plugin name>",
+  "upstreamSkills": ["<skill-a>", "<skill-b>"],            // the upstream skills we took
+  "derivedFromVersion": "<x.y.z>",                         // the version we last synced from
+  "upstreamRepoUrl": "<optional https url>"                // used only if the marketplace is not installed locally
+}
+```
+
+Procedure:
+1. If `global.derivedSkillSources` is missing or empty -> **skip** this step and report "no derived-skill sources configured". Never invent a source.
+2. For each entry, resolve the current upstream version:
+   - **Preferred**: read the newest installed version under `~/.claude/plugins/cache/<upstreamMarketplace>/<upstreamPlugin>/*/` (its `.claude-plugin/plugin.json` `version`), plus that version's `CHANGELOG.md`.
+   - **Fallback**: if the marketplace is not installed locally and `upstreamRepoUrl` is set, `WebFetch` the upstream `plugin.json` + `CHANGELOG.md`.
+   - If neither is reachable, record "upstream unreachable" and move on (do not fail the run).
+3. Compare the resolved upstream version to `derivedFromVersion`:
+   - equal -> "up to date" (no drift)
+   - newer -> **drift**: read the CHANGELOG entries between the two versions, and diff each `upstreamSkills` SKILL.md (+ templates) against our `localPath` copy. Summarize what changed.
+4. Emit the drift table (plan band D):
 
-Output format:
 ```
-| Source | Idea | Effort | Impact | Include in plan? |
-|--------|------|--------|--------|------------------|
-| ralph-loop | Symlink distribution | Low | High | Yes |
-| atelier | Persistent Brain | High | Very high | No (roadmap) |
+| Derivation | Our copy (localPath) | Derived-from | Upstream now | Drift | What changed upstream |
+|------------|----------------------|--------------|--------------|-------|-----------------------|
+| <label>    | <path>               | 0.2.1        | 0.3.0        | YES   | <changelog + diff summary> |
 ```
 
+5. For each drifted entry, add a band-D plan item: "port upstream <plugin> <version> changes into <localPath>". Do not auto-apply  -  it goes through Step 5 approval; after porting, bump the entry's `derivedFromVersion`.
+
 ## Step 1: SCAN
 
 ```
@@ -65,7 +107,9 @@ Output format:
 - Git status: branch count, last commit date, tags
 ```
 
-## Step 2: ANALYZE  -  10 Categories
+## Step 2: ANALYZE  -  10 categories + BUG HUNT
+
+### 2a. 10 categories (quality lens)
 
 | # | Category | What is checked |
 |---|----------|-----------------|
@@ -80,6 +124,23 @@ Output format:
 | 9 | **Dependency Management** | Outdated deps, vulnerability scan, lockfile, version pinning |
 | 10 | **DevEx** | Onboarding time, script ergonomics, error messages, debug tooling |
 
+### 2b. BUG HUNT (real defects, not scores)
+
+Category scores measure quality; they do not find the bug that ships. Run an explicit defect hunt IN ADDITION to the scoring:
+
+- Dispatch focused review agents over the highest-risk surfaces: recently changed files, error/edge-path handling, concurrency, external input parsing, resource cleanup, off-by-one boundaries.
+- For each candidate defect, record: **file:line**, the concrete failure scenario (inputs/state -> wrong output/crash), and severity.
+- **Verify before reporting**: only list a bug you can trace to a real failure path; drop the plausible-but-unprovable ones.
+
+Output (plan band B) - every confirmed defect becomes a P0/P1 item:
+```
+| # | Severity | File:line | Defect | Failure scenario |
+|---|----------|-----------|--------|------------------|
+| 1 | Blocking | src/x.ts:42 | unchecked nil deref | empty response -> crash |
+```
+
+Improvement areas surfaced by 2a that are not outright bugs become band-C items.
+
 ## Step 3: SCORE
 
 Each category is scored out of 10. Output format:
@@ -103,45 +164,46 @@ Each category is scored out of 10. Output format:
 +---------------------+-------+
 ```
 
-## Step 4: PLAN
+## Step 4: PLAN  -  one merged, prioritized table
 
-List all the improvements found:
+Merge all four bands into a single plan. Tag each row with its band (A best-practice / B bug / C improvement / D drift).
 
 ```
-| # | Priority | Category | Improvement | Impact |
-|---|----------|----------|-------------|--------|
-| 1 | P0 | Security | Remove hardcoded API key | Critical |
-| 2 | P0 | Testing | Missing edge case tests | High |
-| 3 | P1 | CI/CD | Add Node matrix | Medium |
-| 4 | P1 | Documentation | Functions missing JSDoc | Medium |
-| 5 | P2 | DevEx | npm script naming | Low |
+| # | Priority | Band | Category | Item | Impact |
+|---|----------|------|----------|------|--------|
+| 1 | P0 | B | Security | Remove hardcoded API key (src/x:12) | Critical |
+| 2 | P0 | B | Testing | Fix nil-deref on empty response (src/y:42) | High |
+| 3 | P1 | A | CI/CD | Adopt matrix build (adapt: .github/workflows/ci.yml) | Medium |
+| 4 | P1 | D | Skills | Port upstream <plugin> 0.3.0 fixes into <localPath> | Medium |
+| 5 | P2 | C | DevEx | Rename npm scripts for consistency | Low |
 ```
 
 Priority levels:
 - **P0**: Bug, security hole, broken functionality  -  fix without fail
-- **P1**: Clear quality improvement  -  should be done
+- **P1**: Clear quality improvement or high-value adopted best-practice / drift port  -  should be done
 - **P2**: Nice-to-have  -  if there is time
 
-## Step 5: ASK  -  Approval from the User
+## Step 5: ASK  -  approval from the user
 
 After showing the plan, ask:
 
-> "I found X improvements (P0: N, P1: M, P2: K). Shall I start developing?"
+> "I found X items (P0: N, P1: M, P2: K) across bugs, best-practices, improvements, and upstream drift. Shall I start developing?"
 
 Options:
 - "Yes, do all of them"
 - "Do only the P0 ones"
 - "Do only P0 + P1"
+- "Only the bugs (band B)"
 - (the user can make a specific selection)
 
 **NEVER start developing without approval.**
 
 ## Step 6: IMPLEMENT
 
-Apply approved improvements in order:
+Apply approved items in order:
 
-1. For each improvement:
-   - Make the change
+1. For each item:
+   - Make the change (for band D, port the upstream diff into `localPath`, then bump that entry's `derivedFromVersion`)
    - Run the relevant tests
    - If successful, move to the next
    - If it fails, revert and notify the user
@@ -167,7 +229,7 @@ echo "Test: PASS/FAIL (X/Y passed)"
 
 ## Step 8: ASK SYNC
 
-After all improvements are applied, ask:
+After all approved items are applied, ask:
 
 > "Development complete. Shall I run multi-agent-sync?"
 
@@ -178,14 +240,17 @@ Options:
 
 ## Focus filter
 
-If $ARGUMENTS is specified, focus on that category only:
+If $ARGUMENTS is specified, focus on that band/category only:
 
 | Input | Focus |
 |-------|-------|
+| `bugs` | Bug hunt only (band B) |
+| `best-practices` | Field research + adapted plan only (band A) |
+| `drift` | Upstream derived-skill drift only (band D) |
 | `security` | Security analysis only |
 | `tests` | Test coverage and quality only |
 | `performance` | Performance optimization only |
 | `docs` | Documentation only |
 | `ci` | CI/CD pipeline only |
 | `deps` | Dependency updates only |
-| (empty) | All 10 categories (default) |
+| (empty) | Everything (default) |

package/pipeline/skills/shared/core/multi-agent-sync/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: multi-agent-sync
 language: en
-description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and remote-control."
+description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, and website."
 user-invocable: true
 argument-hint: 'release | "change description"'
 ---
@@ -10,35 +10,30 @@ argument-hint: 'release | "change description"'
 
 **Single command. Full ecosystem sync. No argument required.**
 
-When invoked, it synchronizes all 6 targets in order. It detects what changed, updates only the stale ones, and reports the result.
+When invoked, it synchronizes all targets in order. It detects what changed, updates only the stale ones, and reports the result.
 
 **Input**: $ARGUMENTS (optional  -  `release` or a change description to apply to all targets)
 
-## Targets (always all 6)
+## Targets
 
 | # | Target | Path | Direction |
 |---|-------|-----|-----|
-| 0 | Figma source (opt-in) | `prefs.global.figmaSource.path` -> `pipeline/skills/figma-ios/` + `figma-common/` | <- upstream |
 | 1 | Claude Code (source of truth) | `~/.claude/commands/multi-agent.md` + `~/.claude/commands/multi-agent/` + `~/.claude/agents/` + `~/.claude/scripts/` | source |
 | 2 | Copilot CLI | `~/.copilot/copilot-instructions.md` + `~/.copilot/skills/` | <- from Claude |
 | 3 | multi-agent-pipeline repo | `~/multi-agent-pipeline/pipeline/` | <- from Claude (genericized) |
 | 4 | Website | `{owner}/{website-host}` | <- version + features |
-| 5 | Remote Control | `{owner}/remote-control` | <- pipeline references |
 
 ## Default Behavior (no argument)
 
 Run all steps automatically:
 
 ```
-Step 0: FIGMA_SYNC  (opt-in) pipeline/scripts/sync-figma-source.sh
-                    -- incremental pull from upstream if figmaSource.path is set
 Step 1: DETECT      Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 37 sub-command skills)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 36 sub-command skills)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
-Step 5: REMOTE      Pipeline references -> remote-control README
-Step 6: Commit      Commit + push all changed repos
-Step 7: Report      Summary: synced targets, changed files, deploy status
+Step 5: Commit      Commit + push all changed repos
+Step 6: Report      Summary: synced targets, changed files, deploy status
 ```
 
 If nothing is stale -> report "All targets up to date" and stop.
@@ -118,22 +113,6 @@ git push origin main  # Vercel auto-deploy
 ```
 
 
-## Remote Control Sync (Step 5)
-
-```bash
-REMOTE_DIR="$HOME/remote-control"
-[ ! -d "$REMOTE_DIR" ] && gh repo clone {owner}/remote-control "$REMOTE_DIR"
-cd "$REMOTE_DIR" && git pull origin main
-```
-
-| File | To sync |
-|-------|--------------|
-| `README.md` | Pipeline feature description |
-| `src/index.ts` | Help text / chip labels (if any) |
-
-Update only if the pipeline's public-facing features changed.
-
-
 ## Release Flow
 
 When invoked with the `release` argument:
@@ -146,9 +125,8 @@ When invoked with the `release` argument:
 5. Commit + TAG  git commit + git tag v{VERSION}
 6. PUSH          git push --tags -> release.yml auto-publish
 7. WEBSITE       Version + features -> {website-host}
-8. REMOTE        Update remote-control references
-9. COPILOT       Copilot CLI instructions + skills sync
-10. Report        Summary: version, touched repos, deploy status
+8. COPILOT       Copilot CLI instructions + skills sync
+9. Report        Summary: version, touched repos, deploy status
 ```
 
 

package/pipeline/skills/shared/external/compose-components/SKILL.md

@@ -251,27 +251,27 @@ fun AppTheme(
 
 ```kotlin
 private val LightColorScheme = lightColorScheme(
-    primary = Color(0xFFE31837),
+    primary = Color(0xFF6750A4),
     onPrimary = Color.White,
-    primaryContainer = Color(0xFFFFDAD6),
-    onPrimaryContainer = Color(0xFF410002),
-    secondary = Color(0xFF775653),
+    primaryContainer = Color(0xFFEADDFF),
+    onPrimaryContainer = Color(0xFF21005D),
+    secondary = Color(0xFF625B71),
     onSecondary = Color.White,
-    secondaryContainer = Color(0xFFFFDAD6),
-    onSecondaryContainer = Color(0xFF2C1513),
-    surface = Color(0xFFFFFBFF),
-    onSurface = Color(0xFF201A19),
+    secondaryContainer = Color(0xFFE8DEF8),
+    onSecondaryContainer = Color(0xFF1D192B),
+    surface = Color(0xFFFFFBFE),
+    onSurface = Color(0xFF1C1B1F),
     error = Color(0xFFBA1A1A),
     onError = Color.White,
 )
 
 private val DarkColorScheme = darkColorScheme(
-    primary = Color(0xFFFFB4AB),
-    onPrimary = Color(0xFF690005),
-    primaryContainer = Color(0xFF93000A),
-    onPrimaryContainer = Color(0xFFFFDAD6),
-    surface = Color(0xFF201A19),
-    onSurface = Color(0xFFEDE0DE),
+    primary = Color(0xFFD0BCFF),
+    onPrimary = Color(0xFF381E72),
+    primaryContainer = Color(0xFF4F378B),
+    onPrimaryContainer = Color(0xFFEADDFF),
+    surface = Color(0xFF1C1B1F),
+    onSurface = Color(0xFFE6E1E5),
 )
 ```
 

package/pipeline/skills/skills-index.md

@@ -3,7 +3,7 @@
 > Auto-generated by `pipeline/scripts/build-skills-index.mjs`  -  do not hand-edit.
 > Regenerate with `node pipeline/scripts/build-skills-index.mjs`.
 
-**228 skills** across 5 groups.
+**187 skills** across 2 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
@@ -56,42 +56,6 @@
 | external | `energykit` |  -  | Query grid electricity forecasts and submit load events using EnergyKit to help users optimize home electricity usage. Use when building sma |
 | external | `eventkit-calendar` |  -  | Create, read, and manage calendar events and reminders using EventKit and EventKitUI. Use when adding events to the user's calendar, creatin |
 | external | `fastapi-pro` |  -  | Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async p |
-| figma-common | `figma-bottom-sheets` |  -  | Bottom-sheet / detent pattern integration for Figma-to-UI components (iOS SwiftUI + Android Jetpack Compose) — half-sheets, drawers, pinned  |
-| figma-common | `figma-cli-iterate` |  -  | Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `OR |
-| figma-common | `figma-cli-iterate-mend` |  -  | Runs the complete Figma-to-SwiftUI mend pipeline for a single issue whose component already exists under `Discarded/` and must be re-impleme |
-| figma-common | `figma-cli-lean-iterate` |  -  | Runs a lean Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-4) → code connect (phase 6) → commit. Skips |
-| figma-common | `figma-cli-skip` |  -  | CLI variant of /figma-skip  -  fetches origin iteration/develop on mobile-common, marks a Figma component as skipped in the registry, commit |
-| figma-common | `figma-commit` |  -  | Reviews a Figma component implementation, then creates feature branches across submodules, commits, pushes, and opens PRs. Delegates mobile- |
-| figma-android | `figma-component-code-connect` | android | Generate Code Connect for Compose mappings  -  {Name}.figma.kt registers the composable with Figma's Code Connect so designers see live code |
-| figma-ios | `figma-component-code-connect` | ios | Figma Code Connect mapping publisher for implemented SwiftUI components. Creates + publishes .figma.swift registration for a component alrea |
-| figma-common | `figma-component-confluence-sync` |  -  | Syncs component documentation from the GitHub Wiki (source of truth) to Confluence. Reads wiki markdown, converts to Confluence XHTML, uploa |
-| figma-android | `figma-component-implement` | android | Generate a Jetpack Compose component (Configuration data class + Composable + Modifier extensions + Preview + README) from gathered Figma da |
-| figma-ios | `figma-component-implement` | ios | Figma → SwiftUI implementation for a single component. Runs Phases 0-4 of the figma-to-swiftui pipeline (init, data gathering, analysis, cod |
-| figma-common | `figma-component-start` |  -  | Reads a GitHub Issue, extracts component metadata, creates feature branches from `develop` (main repo) / `iteration/develop` (submodules), a |
-| figma-common | `figma-component-status-update` |  -  | Refreshes the global Component Implementation Status dashboard on Confluence. |
-| figma-android | `figma-component-test` | android | Generate Compose Testing + Paparazzi/Roborazzi snapshot + unit tests for a Jetpack Compose component. Android peer to pipeline/skills/figma- |
-| figma-ios | `figma-component-test` | ios | Test generator + runner for implemented SwiftUI Figma components. Produces ViewInspector structural tests, snapshot tests, and XCTest unit t |
-| figma-android | `figma-component-wiki` | android | Component wiki generation for Android. Dispatches to the same 4-mode adapter set as the iOS peer (submodule / in-repo / github-wiki / separa |
-| figma-ios | `figma-component-wiki` |  -  | Generate component wiki documentation with a pluggable adapter. Reads component source + FIGMA.md, renders markdown, then delegates publicat |
-| figma-common | `figma-evolve-component` |  -  | On-demand reconcile-and-extend for an ALREADY-implemented UI component (iOS SwiftUI or Android Jetpack Compose). Heals drift from current Fi |
-| figma-common | `figma-fix` |  -  | Applies a targeted fix for a bug filed during component review (via `/figma-review`), re-runs affected pipeline phases, closes the bug sub-i |
-| figma-common | `figma-form-integration` |  -  | Form pattern integration for Figma-to-SwiftUI components. Guides FormSection/FormField adoption  -  when a component embeds form-capable sub |
-| figma-common | `figma-issue` |  -  | Creates and manages GitHub Issues for Figma component implementations. |
-| figma-common | `figma-iterate` |  -  | Picks the next available component issue and runs the full pipeline end-to-end: start → implement → commit. Loops until no more issues are a |
-| figma-common | `figma-iteration-commit` |  -  | NEVER create branches on the main repo (REPO_ROOT). Do not create `iteration/develop` or any other branch on the main repo. Do not commit to |
-| figma-common | `figma-mend` |  -  | Re-implements discarded components from scratch using the figma-to-swiftui workflow, preserving old implementation as complementary referenc |
-| figma-common | `figma-navigation` |  -  | Navigation pattern integration for Figma-to-UI components (iOS SwiftUI + Android Jetpack Compose). Guides how a component reaches other scre |
-| figma-common | `figma-overlays` |  -  | Overlay pattern integration for Figma-to-UI components (iOS SwiftUI + Android Jetpack Compose) — toasts/snackbars, blocking loading HUDs, al |
-| figma-common | `figma-price-integration` |  -  | Price pattern integration for Figma-to-SwiftUI components. Guides PriceRepresentable protocol adoption when a component displays price data. |
-| figma-common | `figma-remote-mcp-auth` |  -  | Runs Figma Remote MCP OAuth flow to obtain and store a token in macOS Keychain. Requires OAuth client credentials. |
-| figma-common | `figma-review` |  -  | Guided review session for a Figma component implementation. Resolves the component, finds or creates the GitHub issue, shows relevant code,  |
-| figma-common | `figma-setup` |  -  | One-time environment setup for Figma-to-SwiftUI workflow. Verifies MCP connectivity, API credentials, Code Connect CLI, and FigmaRegistryUti |
-| figma-common | `figma-skip` |  -  | Marks a Figma component as skipped in the component registry and updates the Confluence status dashboard. |
-| figma-android | `figma-to-component` | android | Figma-to-Compose component implementation workflow for Android. Takes a Figma URL and produces a production-ready Jetpack Compose component  |
-| figma-ios | `figma-to-component` |  -  | Figma-to-SwiftUI component implementation workflow. Takes a Figma URL and produces a production-ready SwiftUI component through 8 phases  -  |
-| figma-common | `figma-ui-patterns` |  -  | Index of reusable SwiftUI UI-pattern guides (carousels, scroll tricks, animations, shaped views like scallops, pagers, parallax, gestures).  |
-| figma-common | `figma-utility` |  -  | On-demand Figma data utility. Fetch screenshots, metadata, properties, tokens, design context, Code Connect mappings, node data, component l |
-| figma-common | `figma-validate` |  -  | Pre-implementation validation for Figma components. Checks 7 criteria: (1) Registry presence, (2) Code Connect strategy, (3) Design token co |
 | external | `firebase` |  -  | You're a developer who has shipped dozens of Firebase projects. You've seen the \"easy\" path lead to security breaches, runaway costs, and  |
 | external | `github-actions-templates` |  -  | Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications. |
 | core | `google-play-compliance` |  -  | Google Play Store publication compliance  -  bundletool + aapt2 + apksigner orchestration + 21-rule policy catalog with Play Console error c |
@@ -158,7 +122,7 @@
 | core | `multi-agent-setup` |  -  | First-run setup wizard: keychain token discovery, Git Identity onboarding, and pipeline preparation. |
 | core | `multi-agent-stack` |  -  | Select the active stack for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json (ios/android/mobile/backend/fr |
 | core | `multi-agent-status` |  -  | Show every multi-agent task's ID, phase, branch, and status. |
-| core | `multi-agent-sync` |  -  | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and remote-control. |
+| core | `multi-agent-sync` |  -  | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, and website. |
 | core | `multi-agent-test` |  -  | UI Bug Hunter  -  iOS Simulator (simctl) + Android Emulator (adb). Auto-detects platform. Screenshot + tap + analyze on the booted device. T |
 | core | `multi-agent-update` |  -  | Update the pipeline to the latest version: git pull, install, migrate. |
 | external | `musickit-audio` |  -  | Integrate Apple Music playback, catalog search, and Now Playing metadata using MusicKit and MediaPlayer. Use when adding music search, Apple |
@@ -169,11 +133,6 @@
 | external | `passkit-wallet` |  -  | Integrate Apple Pay payments and Wallet passes using PassKit. Use when adding Apple Pay buttons, creating payment requests, handling payment |
 | external | `pdfkit` |  -  | Display and manipulate PDF documents using PDFKit. Use when embedding PDFView to show PDF files, creating or modifying PDFDocument instances |
 | external | `pencilkit-drawing` |  -  | Add Apple Pencil drawing with PKCanvasView, PKToolPicker, PKDrawing serialization/export, stroke inspection, and PencilKit/PaperKit handoffs |
-| figma-common | `performance-iteration-commit-all` |  -  | Reads `_tour_tracker.json`, validates all reviewed components in a single build+test cycle, pushes all local commits in a single push per su |
-| figma-common | `performance-review-next` |  -  | Reads `_tour_tracker.json`, presents a dashboard of produced components, and guides the user through reviewing each one. Fix commits are sep |
-| figma-common | `performance-start` |  -  | Identical to `/figma-to-swift-ui-start` for Steps 0-5. After printing the summary (Step 6), automatically invokes `/performance-swiftui <fig |
-| figma-common | `performance-swiftui` |  -  | Performance-optimized Figma-to-SwiftUI workflow. Same phases as figma-to-swiftui but with model downgrades on deterministic phases, parallel |
-| figma-common | `performance-tour` |  -  | Produces multiple Figma components in a single session. Validates dependencies, determines implementation order, produces each component seq |
 | external | `permissionkit` |  -  | Create child communication safety experiences using PermissionKit to request parental permission for children. Use when building apps that i |
 | external | `photos-camera-media` |  -  | Implement, review, or improve photo picking, camera capture, and media handling in iOS apps using PhotoKit and AVFoundation. Use when workin |
 | external | `play-store-review` |  -  | Prepare Android apps for Google Play Store review and compliance. Covers Google Play policy requirements, content rating questionnaire, targ |