@mmerterden/multi-agent-pipeline 11.1.0 → 11.3.0

package/pipeline/skills/shared/external/skill-creator/examples.md

@@ -0,0 +1,65 @@
+# Examples — descriptions & shape
+
+## Descriptions: the discovery lever
+
+**Bad (vague — rarely triggers):**
+```yaml
+description: Helps with navigation
+```
+Why it fails: no "when", no trigger words, no platform — the router can't tell what task this matches.
+
+**Good (what + when + triggers + platform):**
+```yaml
+description: "In-app navigation for a SwiftUI iOS app — the coordinator-per-domain pattern, the tab shell, cross-domain navigation, deep links, and modals. Reach for this when adding a screen, a tab, a deep link, or a modal, or deciding how one screen reaches another."
+```
+Why it works: states the domain, lists concrete triggers ("adding a screen, a tab, a deep link"), names the platform, and implies the boundary.
+
+**Workflow example (action + when to run):**
+```yaml
+description: "Branch, commit, push, and open a PR for this repo. Owns the git/PR spine and house guardrails — type-first branch names, no AI attribution, no force-push, correct base branch. Reach for this whenever a change is ready to ship."
+```
+
+### Recipe
+`<what it covers/does> + <concrete when/trigger phrases> + <platform> + <implied boundary vs siblings>`
+
+---
+
+## Shape: reference vs workflow
+
+**Wrong — a reference skill drifting into a procedure:**
+```markdown
+## Procedures
+1. Open the file
+2. Add the wrapper
+3. Register the route
+4. Build and run
+```
+A reference (knowledge) skill should describe *the rule and where the canonical example lives*, not script the keystrokes.
+
+**Right — reference stays descriptive:**
+```markdown
+## Decision rules
+- New screen in a domain → add `<Name>Screen` under its Presentation layer,
+  wrap content in the domain's container, route via the domain coordinator.
+  Canonical: `<repo>/Features/Profile/ProfileScreen.swift`.
+```
+
+**Right — workflow earns its numbered steps** (deterministic/irreversible spine):
+```markdown
+## Procedures
+1. Pre-flight: `git status` clean? on base branch?
+2. Branch: `git checkout -b <type>/<scope>/<desc>`
+3. Commit: stage; conventional message; strip any AI co-author trailer.
+4. Push; never force-push a protected branch.
+5. PR: `gh pr create --base <base> …` (no AI footer).
+## Verification
+- `git log -1` shows clean message, no AI trailer, correct author.
+```
+
+---
+
+## Leanness: cut what the model already knows
+
+**Bloat:** "PDF files are documents that contain text and images. To read them you first need a library that can parse the binary format…"
+
+**Lean:** "Extract text from PDFs with `pdfplumber`."

package/pipeline/skills/shared/external/skill-creator/label-check.md

@@ -0,0 +1,43 @@
+# Label intent check — does a title carry its own meaning?
+
+A label (rule title, section header, principle/constraint name) is the handle a reader grasps *before* the body. If the handle leaks the wrong shape — ambiguous, one-sided, or off-topic — the reader forms the wrong model and the body has to fight it. This is a cheap test that catches that early: have **fresh subagents infer the rule from the label alone**, then compare against your intended meaning. Convergence = the label is self-carrying.
+
+## When to run it
+- Naming a **strict rule** or constraint inside a skill (the kind a reader must obey).
+- A **section header** that gates non-trivial content (phase/principle/constraint names).
+- Any label meant to convey the **whole intent** of its body (not a summary — the intent).
+- Skip it for purely organizational labels ("Examples", "See also") — they carry no intent.
+
+## Inputs (collect first)
+1. **Candidate label** — the exact string under test.
+2. **Surrounding context** — one paragraph: which skill/doc, what adjacent labels cover, the domain concepts in play.
+3. **Intended meaning** — 1–3 sentences of ground truth (what the body says / what the reader should walk away believing). **Not** shown to the inference agents. If you can't state it in 3 sentences, the body is unclear — fix that first.
+
+## Procedure
+**One iteration = 5 parallel subagents**, each given ONLY the label + context (never the body), each forced to commit:
+```
+Context: <surrounding context — 1 paragraph>.
+The label under test is: **"<candidate label>"**
+You have NOT seen the body. From ONLY this label + context, what do you infer it
+enforces / requires / means? 1–2 concrete sentences, under 80 words. Commit — no
+hedging, no clarifying questions.
+```
+Launch all 5 in the **same** message (parallel) so they're independent by construction.
+
+**Convergence (per iteration), comparing the 5 inferences to the intended meaning:**
+- **PASS** — ≥4/5 cover *all* key intent beats (including the bidirectional / edge / scope beat, if the intent has one). Wording drift is fine.
+- **PARTIAL** — they consistently catch one side of a bidirectional rule but miss the other, or over-extend into an adjacent concern. Revise the label, re-run.
+- **FAIL** — inferences diverge wildly or miss the core beat. Revise, re-run.
+
+**Idempotency (after a PASS):** run **2 more rounds**, 5 fresh agents each (3×5 = 15 inferences), same prompt. Require **all 3 rounds PASS** with no new systematic miss — confirms the PASS wasn't luck. A regression in round 2/3 → treat as PARTIAL and iterate.
+
+**Termination:** converged (3/3 PASS) → apply the label. 3 iterations without a PASS → stop, hand back the best candidate + the persistent miss; don't force a label that won't stick.
+
+## Defaults
+5 agents/round · 3 rounds · 80-word inference cap · max 3 iterations before handing back. High-stakes labels (top-level skill names, protocol names) → 7 agents × 3 rounds; throwaway section headers → 3 × 2.
+
+## Anti-patterns
+- **Giving agents the body** — defeats the test (you're checking the label's *self-carrying* power).
+- **Running sequentially** — they'd anchor on each other; must be parallel.
+- **Tweaking one word on a FAIL** — step back and rethink the concept the label names, don't polish a wrong handle.
+- **Accepting "mostly right"** — a label that reliably misses a beat misleads every reader the same way. Fix it, or accept the rule is one-sided and split the body.

package/pipeline/skills/shared/external/skill-creator/scripts/audit-panel.js

@@ -0,0 +1,83 @@
+// audit-panel.js — Workflow template for the multi-architect skill audit.
+//
+// Run with the Workflow tool. Edit the CONFIG block for your target, then launch.
+// Returns { remaining, clearsBar, verdict }. If clearsBar is false, apply the
+// `remaining` blockers/majors, then RE-RUN A FRESH copy (do NOT resume — agents
+// must read the current files). Loop until clearsBar. See ../audit.md.
+
+export const meta = {
+  name: 'skill-audit-panel',
+  description: 'Adversarial N-architect audit of a skill against the skill-creator rubric',
+  phases: [{ title: 'Audit' }, { title: 'Synthesis' }],
+}
+
+// ── CONFIG — edit these ──────────────────────────────────────────────────────
+const TARGET = `
+- <abs path to SKILL.md>
+- <abs path to each bundled file / script>
+`
+const RUBRIC = `<abs path to reference/skill-creator/SKILL.md> + checklist.md`
+const EXEMPLAR = `<abs path to a known-good skill of the same layer>`
+const GROUND_TRUTH = `<abs path to the real source the skill describes (e.g. the iOS repo), with key facts>`
+// Pick a lens set from audit.md (general or prompt-engineering). [label, brief] pairs:
+const LENSES = [
+  ['discovery', 'description-as-discovery: what+when+trigger words+example; would it activate on a real task?'],
+  ['disambiguation', 'distinct from sibling skills; a reader can tell when to pick this vs a neighbor.'],
+  ['triggers', 'real user phrasings + synonyms are covered.'],
+  ['clarity', 'instructions unambiguous, ordered, single-interpretation; no vague directives.'],
+  ['layer', 'degrees of freedom match the layer (reference=descriptive / workflow=spine / tool=thin-index).'],
+  ['leanness', 'SKILL.md is an index; detail bundled one level deep; no duplication or bloat.'],
+  ['tokens', 'every line load-bearing; nothing restates what the model already knows.'],
+  ['consistency', 'terminology, naming, paths, cross-refs, examples all agree.'],
+  ['misfire', 'would the model over-apply, skip a gate, hallucinate a path, or follow it to a wrong output?'],
+  ['redteam', 'adversarially make it not trigger / trigger wrongly / produce broken output; hunt overclaims (says X, script does not).'],
+]
+// ─────────────────────────────────────────────────────────────────────────────
+
+const COMMON = `
+You are auditing a skill. Read the CURRENT files and report ONLY genuine, specific,
+reproducible findings for YOUR lens. Verify against the rubric + ground truth — do
+not assume. Read-only; do NOT edit. If your lens is clean, return an empty array.
+
+TARGET (the skill under audit):${TARGET}
+RUBRIC (the bar): ${RUBRIC}
+EXEMPLAR (known-good of this layer): ${EXEMPLAR}
+GROUND TRUTH (what the skill describes): ${GROUND_TRUTH}
+
+Each finding: severity (blocker|major|minor|nit), file:location, the problem, the concrete fix.
+`
+
+const FINDING = {
+  type: 'object', additionalProperties: false,
+  properties: {
+    severity: { type: 'string', enum: ['blocker', 'major', 'minor', 'nit'] },
+    location: { type: 'string' }, problem: { type: 'string' }, fix: { type: 'string' },
+  }, required: ['severity', 'location', 'problem', 'fix'],
+}
+const LENS_SCHEMA = {
+  type: 'object', additionalProperties: false,
+  properties: { lens: { type: 'string' }, findings: { type: 'array', items: FINDING } },
+  required: ['lens', 'findings'],
+}
+
+phase('Audit')
+const results = await parallel(LENSES.map(([lens, brief]) => () =>
+  agent(`${COMMON}\n\nYOUR LENS — ${lens}: ${brief}`, { label: `audit:${lens}`, phase: 'Audit', schema: LENS_SCHEMA })
+))
+const all = results.filter(Boolean).flatMap(r => r.findings.map(f => ({ ...f, lens: r.lens })))
+
+phase('Synthesis')
+const SYNTH = {
+  type: 'object', additionalProperties: false,
+  properties: {
+    remaining: { type: 'array', items: { type: 'object', additionalProperties: false,
+      properties: { ...FINDING.properties, lenses: { type: 'string' } },
+      required: [...FINDING.required, 'lenses'] } },
+    clearsBar: { type: 'boolean' },
+    verdict: { type: 'string' },
+  }, required: ['remaining', 'clearsBar', 'verdict'],
+}
+return await agent(
+  `${COMMON}\n\nYou are the SYNTHESIS architect. Below are ${all.length} raw findings from ${LENSES.length} lenses. Dedup overlaps (note which lenses raised each). DROP false positives — verify against the files before keeping; if you cannot reproduce it, drop it. Classify each survivor; set clearsBar=true ONLY if no blockers and no majors remain. One-paragraph verdict.\n\nRAW:\n${JSON.stringify(all, null, 2)}`,
+  { label: 'synthesis', phase: 'Synthesis', schema: SYNTH }
+)

package/pipeline/skills/shared/external/skill-creator/template.md

@@ -0,0 +1,67 @@
+# Skill skeletons
+
+Two skeletons — pick by layer. Both stay lean; push detail into one-level-deep bundled files.
+
+Frontmatter fields used in this toolkit: `name`, `description` (required-quality), `user-invocable`, `argument-hint` (optional), `allowed-tools`.
+
+---
+
+## Reference skill (descriptive — knowledge)
+
+No numbered procedures. Principles + pointers + heuristics.
+
+```markdown
+---
+name: <aspect-noun>          # e.g. navigation — NO platform prefix
+description: <what it covers + when to reach for it + trigger words. Say "iOS/SwiftUI" so the router can disambiguate.>
+user-invocable: true
+allowed-tools: Read, Grep, Glob, Bash, Edit, Write
+---
+
+# <name> — <short title>
+
+> **Layer:** reference (knowledge)
+> **Use when:** <trigger>   **Hand off to:** <sibling skill>
+
+## Scope
+In / out, 1–2 lines.
+
+## Invariants            <!-- non-negotiables + the why -->
+## Conventions & golden paths   <!-- point to canonical files; don't paste code -->
+## Decision rules        <!-- if X do A; when unsure, ask/verify -->
+## Pitfalls              <!-- known traps -->
+## Escape hatches        <!-- when this doesn't apply → which skill -->
+```
+
+---
+
+## Workflow skill (imperative — action)
+
+Has a numbered procedure, but only for the deterministic/irreversible spine. Cite reference skills for judgment. Always include a verification gate.
+
+```markdown
+---
+name: <verb-phrase>         # e.g. branch-and-pr
+description: <what it does + when to run it + trigger words (iOS/SwiftUI).>
+user-invocable: true
+argument-hint: [<step> | ...]
+allowed-tools: Bash, Read
+---
+
+# <name> — <short title>
+
+> **Layer:** workflow (action)
+> **Use when:** <trigger>   **Don't use when:** <hand off>
+
+## Scope
+In / out, 1–2 lines.
+
+## Invariants            <!-- hard rules / guardrails -->
+## Conventions & golden paths   <!-- base branch, auth, canonical commands -->
+## Decision rules        <!-- branch when…, escalate when… -->
+## Procedures            <!-- IMPERATIVE: only deterministic/irreversible steps -->
+1. ...
+## Verification          <!-- IMPERATIVE: prove it worked (build/run/test) -->
+## Pitfalls
+## Escape hatches
+```

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`.
 
-**226 skills** across 5 groups.
+**187 skills** across 2 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
@@ -29,6 +29,7 @@
 | external | `authentication` |  -  | Implement iOS authentication flows with AuthenticationServices and LocalAuthentication. Use when building Sign in with Apple, passkey/WebAut |
 | external | `avkit` |  -  | Create media playback experiences using AVKit. Use when adding video players with AVPlayerViewController, enabling Picture-in-Picture, routi |
 | external | `background-processing` |  -  | Schedule and execute background work on iOS using BGTaskScheduler. Use when registering BGAppRefreshTask for short background fetches, BGPro |
+| external | `backlog` |  -  | The engineering backlog registry for deferred-but-approved work in this codebase. Every job the user defers ('defer it', 'add it to the list |
 | external | `callkit-voip` |  -  | Implement VoIP calling with CallKit and PushKit. Use when building incoming/outgoing call flows, registering for VoIP push notifications, co |
 | external | `ci-cd-pipelines` |  -  | CI/CD pipelines: GitHub Actions workflows, Docker multi-stage builds, environment management, secret management, deployment strategies |
 | external | `clean-code` |  -  | This skill embodies the principles of \"Clean Code\" by Robert C. Martin (Uncle Bob). Use it to transform \"code that works\" into \"code th |
@@ -55,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 |
@@ -157,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 |
@@ -168,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 |
@@ -185,6 +145,7 @@
 | external | `room-database` |  -  | Implement Room database persistence on Android with @Entity, @Dao, @Database, Flow-based reactive queries, TypeConverters for complex types, |
 | external | `search-first` |  -  | \| |
 | external | `shareplay-activities` |  -  | Build shared real-time experiences using GroupActivities and SharePlay. Use when implementing shared media playback, collaborative app featu |
+| external | `skill-creator` |  -  | Author and refine skills for a plugin/toolkit efficiently. Use when creating a new skill, trimming or splitting an existing one, writing a s |
 | external | `speech-recognition` |  -  | Transcribe speech to text using Apple's Speech framework. Use when implementing live microphone transcription with AVAudioEngine, recognizin |
 | external | `spm-build-analysis` |  -  | Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use whe |
 | external | `storekit` |  -  | Implement, review, or improve in-app purchases and subscriptions using StoreKit 2. Use when building paywalls with SubscriptionStoreView or  |

package/pipeline/commands/multi-agent/refactor.md

@@ -1,188 +0,0 @@
----
-description: "Analyse the project, score it, draft an improvement plan, take approval, develop, then ask whether to sync."
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion, WebFetch
----
-
-# Multi-Agent Refactor
-
-**One command. Analyse → Score → Plan → Approval → Develop → Sync.**
-
-Deep-analyses the current project, scores it across 10 categories, drafts every improvement, asks the user for approval, applies them, and asks about sync at the end.
-
-**Input**: $ARGUMENTS (optional  -  area to focus on: "security", "performance", "tests", etc.)
-
-## Flow
-
-```
-Step 0: RESEARCH   Search GitHub + Reddit for competing projects, gather good ideas
-Step 1: SCAN       Walk the project structure (files, LOC, dependencies, CI, tests)
-Step 2: ANALYZE    Deep analysis across 10 categories
-Step 3: SCORE      Each category /10, overall /100
-Step 4: PLAN       List every improvement + competitor idea in priority order
-Step 5: ASK        "Start the work?"  -  wait for user approval
-Step 6: IMPLEMENT  Apply approved improvements one by one (lint, test, commit)
-Step 7: VERIFY     Confirm every test + lint passes
-Step 8: ASK SYNC   "Run multi-agent-sync?"  -  wait for user approval
-```
-
-## Step 0: RESEARCH  -  competitor analysis
-
-Before starting work, scan for similar projects:
-
-1. **GitHub Search**: `multi-agent pipeline AI development` + `Claude Code pipeline` + `AI coding agent`
-   - find repos with stars:>10
-   - read their READMEs
-   - extract their distinct features
-2. **Reddit Search**: multi-agent discussions in `r/ClaudeAI`, `r/ChatGPT`, `r/LocalLLaMA`
-3. **For each competitor, record**:
-   - distinct features we DO NOT have
-   - ideas worth adopting
-   - things they do better than us
-   - things we do better than them
-4. **Add to the plan**: roll the high-impact + low-effort ideas into the PLAN step (P1 priority)
-
-Output format:
-```
-| Source | Idea | Effort | Impact | In plan? |
-|--------|-------|--------|------|--------------|
-| ralph-loop | Symlink distribution | Low | High | Yes |
-| atelier | Persistent Brain | High | Very High | No (roadmap) |
-```
-
-## Step 1: SCAN
-
-```
-- file count, LOC (cloc or wc -l)
-- package.json / Package.swift / build.gradle analizi
-- dependency count (runtime vs dev)
-- Is there a CI/CD pipeline? (.github/workflows/, fastlane/, Makefile)
-- Is there test infrastructure? How many tests? Coverage?
-- Is linter/formatter config in place?
-- Do README, LICENSE, SECURITY.md, CHANGELOG.md exist?
-- Git state: branch count, last commit date, tags
-```
-
-## Step 2: ANALYZE  -  10 categories
-
-| # | Category | What to check |
-|---|----------|-------------------|
-| 1 | **Architecture** | Layer separation, modularity, SOLID, dependency direction |
-| 2 | **Code Quality** | Naming, magic numbers, dead code, complexity, DRY |
-| 3 | **Security** | Hardcoded secrets, input validation, Keychain, ATS, ATT |
-| 4 | **Tests** | Coverage, test pyramid, edge cases, mock/stub quality |
-| 5 | **CI/CD** | Build matrix, lint job, release automation, artifact caching |
-| 6 | **Docs** | README quality, JSDoc / Swift docs, API docs, CHANGELOG |
-| 7 | **Performance** | Bundle size, lazy loading, memory leaks, unnecessary re-renders |
-| 8 | **Accessibility** | a11y labels, tap targets, VoiceOver, Dynamic Type |
-| 9 | **Dependency Management** | Outdated deps, vulnerability scan, lockfile, version pinning |
-| 10 | **DevEx** | Onboarding time, script ergonomics, error messages, debug tooling |
-
-## Step 3: SCORE
-
-Her kategori 10 uzerinden puanlanir. Output format:
-
-```
-+---------------------+-------+
-| Category            | Score |
-+---------------------+-------+
-| Architecture        | 9/10  |
-| Code Quality        | 8/10  |
-| Security            | 9/10  |
-| Tests               | 7/10  |
-| CI/CD               | 8/10  |
-| Docs                | 7/10  |
-| Performance         | 9/10  |
-| Accessibility       | 6/10  |
-| Dependency Mgmt     | 8/10  |
-| DevEx               | 9/10  |
-+---------------------+-------+
-| TOTAL               | 80/100|
-+---------------------+-------+
-```
-
-## Step 4: PLAN
-
-List every improvement found:
-
-```
-| # | Priority | Category | Improvement | Impact |
-|---|---------|----------|-------------|------|
-| 1 | P0 | Security | Remove hardcoded API key | Critical |
-| 2 | P0 | Tests | Missing edge-case tests | High |
-| 3 | P1 | CI/CD | Add Node matrix | Medium |
-| 4 | P1 | Docs | Functions missing JSDoc | Medium |
-| 5 | P2 | DevEx | npm script naming | Low |
-```
-
-Priority levels:
-- **P0**: bugs, security holes, broken functionality  -  MUST fix
-- **P1**: clear quality improvement  -  should be done
-- **P2**: nice-to-have  -  if time allows
-
-## Step 5: ASK  -  user approval
-
-After showing the plan, ask:
-
-> "Found X improvements (P0: N, P1: M, P2: K). Should I start the work?"
-
-Options:
-- "Yes, do all"
-- "Only P0"
-- "P0 + P1 only"
-- (the user may pick specific items)
-
-**NEVER start the work without approval.**
-
-## Step 6: IMPLEMENT
-
-Apply the approved improvements one by one:
-
-1. For each improvement:
-   - apply the change
-   - run the relevant tests
-   - on success, move to the next
-   - On failure, roll back and notify the user
-2. After all changes are done:
-   - run the full lint + test suite
-   - on success, commit
-
-Commit format: `refactor(scope): {short description}`
-
-## Step 7: VERIFY
-
-```bash
-# Lint
-npm run lint 2>/dev/null || swift build 2>/dev/null
-
-# Test
-npm test 2>/dev/null || swift test 2>/dev/null || xcodebuild test 2>/dev/null
-
-# Result
-echo "Lint: PASS/FAIL"
-echo "Test: PASS/FAIL (X/Y passed)"
-```
-
-## Step 8: ASK SYNC
-
-After every improvement is applied, ask:
-
-> "Work is complete. Should I run multi-agent-sync?"
-
-Options:
-- "Yes" → run the `/sync` command (full ecosystem sync)
-- "No" → emit a report and stop
-- "Commit + push only" → push the current repo without sync
-
-## Focus filter
-
-If $ARGUMENTS is set, focus on that category only:
-
-| Input | Focus |
-|-------|------|
-| `security` | Security analysis only |
-| `tests` | Test coverage and quality only |
-| `performance` | Performance optimisation only |
-| `docs` | Docs only |
-| `ci` | CI/CD pipeline only |
-| `deps` | Dependency updates only |
-| (empty) | All 10 categories (default) |

package/pipeline/commands/multi-agent/refs/component-dispatch.md

@@ -1,92 +0,0 @@
-# Component Dispatch (Phase 3 short-circuit)
-
-> **TLDR**  -  When `taskType === "component"` (Figma URL in task description or instruction-driven figma workflow), multi-agent Phase 3 **does not run the TDD loop**. It delegates the entire phase to the `figma-to-component` skill and relays its subphases 3.0 - 3.8 via the existing phase-tracker contract. Implementation lives in the skill; multi-agent's job is classification, dispatch, and state report.
-
-This doc is referenced from `refs/phases/phase-3-dev.md`. Keeping it separate lets `phase-3-dev.md` remain tight (it's already the largest phase doc) and gives the orchestrator-report contract a stable URL for both Claude-side and Copilot-side implementations.
-
-## Entry conditions
-
-Phase 3 checks, in order:
-
-1. `agent-state.json` has `taskType: "component"` (set by Phase 0 Step 7).
-2. `agent-state.json` has a non-null `figmaUrl`.
-
-Either missing → log the anomaly to `agent-log.md` ("component dispatch expected but state incomplete"), fall through to the standard TDD path. Never silently skip the Figma work.
-
-## Orchestrator resolution
-
-```
-project.platform  → orchestrator skill
-────────────────────────────────────────────────────────────────
-ios               → pipeline/skills/figma-ios/figma-to-component/
-android           → pipeline/skills/figma-android/figma-to-component/
-web, multi-*      → HALT with clear error (no web target)
-```
-
-If the chosen skill directory is missing, **halt with a user-visible error**. Do not silently fall back to TDD  -  a component task ran through the bugfix path would produce wrong artefacts and waste review cycles.
-
-## Dispatch call
-
-Emit `→ dispatching figma-to-component <componentName>` via the progress contract, then launch a single agent invocation on the orchestrator skill with:
-
-- `figmaUrl`  -  primary positional argument
-- `agentState`  -  the path to `agent-state.json` so the orchestrator enriches `state.phases["3"].subphases[]`
-- `progressVerbosity`  -  forced to `verbose` when multi-agent runs in `mode: "autopilot"`; otherwise inherits `prefs.global.settings.progressVerbosity`
-- `mode`  -  `"dev"` for `--dev` runs; `"full"` otherwise
-
-## Subphase contract
-
-The orchestrator writes each of its 8 subphases to `state.phases["3"].subphases[]` as it completes, with the shape:
-
-```json
-{
-  "id": "3.4a",
-  "name": "4A-Configuration",
-  "status": "done",
-  "startedAt": "2026-04-16T18:12:02Z",
-  "endedAt":   "2026-04-16T18:13:47Z",
-  "buildStatus": "green",
-  "testStatus": "green"
-}
-```
-
-Multi-agent's `phase-tracker` reads this array without any component-specific code  -  the tracker UI renders one row per subphase under the Phase 3 row. No new phase-tracker field is required.
-
-## Multi-repo report
-
-When multi-repo mode is active (`state.projects.length > 1`), the orchestrator reads `state.projects[]` and runs subphases against the correct per-repo worktree:
-
-- Tokens, accessibility metadata, testing identifiers, localisation keys → `repos.common`
-- View / Configuration / Modifiers / Preview → `repos.components`
-- Wiki markdown → `repos.wiki` (if `wiki.mode === submodule` or `separate-repo`) or `repos.components/.wiki/components/` (if `wiki.mode === in-repo`)
-
-Multi-agent does **not** split the component task into per-repo Phase 3 runs  -  the orchestrator is aware of the repo graph and sequences writes correctly (e.g. token writes to `common` precede component reads in `components`).
-
-## Failure + resume
-
-On orchestrator failure (subphase hits a build/test error that can't auto-fix, or hits retry cap):
-
-1. The orchestrator persists `{subphase, error, buildLog, testLog}` to `state.phases["3"].errors[]`.
-2. Multi-agent increments `state.phases["3"].retryCount`.
-3. Retry re-enters the orchestrator with `phase-<N>` as the argument (the failed subphase), so the skill resumes instead of restarting.
-4. Hard kill at `retryCount === 3` → surface the errors to the user, halt Phase 3. Do not loop indefinitely.
-
-## `--dev` mode behaviour
-
-When multi-agent is invoked with `--dev` (fast path: Init → Dev → Commit → Report), the orchestrator receives `mode: "dev"` and is allowed to elide:
-
-- Subphase 5C (unit tests)  -  structural + snapshot are still required
-- Subphase 7 (wiki)  -  can be deferred; Phase 7 in multi-agent will ask the user whether to run it post-commit
-
-Phase 4 reviewer-skipping is **not** Phase 3's concern  -  Phase 4 decides based on `mode: "dev"` itself.
-
-## Cross-CLI parity
-
-Both Claude Code and Copilot CLI implementations MUST:
-
-- Use the same orchestrator resolution table (ios / android / halt).
-- Emit byte-identical progress lines (`→ dispatching figma-to-component <name>`).
-- Write the same `state.phases["3"].subphases[]` schema.
-- Treat `--dev` the same way (elide 5C + 7 by default, no reviewer skip).
-
-`smoke-cross-cli-behavior.sh` asserts this contract.