菜单
Orchestrate parallel feature development using worktree agents. Use when user wants to implement multiple features in parallel, check feature status, run a feature group, or says "orchestrate", "run features", "implement features", "feature status". Also triggers on `/orchestrate-features`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when capturing an Android emulator screenshot or iOS simulator screenshot, dumping a UI tree, or installing a build to the device — e.g. "screenshot the emulator", "capture Details on the emulator", "зроби скрін емулятора", "які пристрої підключені", "ui dump", or any step in the `feature` / `dev-jump` pipelines that needs an emulator/simulator render. Router for two CLIs — Google's first-party `android-cli` for Android (since 2026-05-21), AlexGladkov's native `claude-in-mobile` binary for iOS. Local-dev only; cloud Claude Code containers and CI have no binary and no emulator/simulator, so capture / device steps are no-ops.
Audit and split monolithic Compose Screen files in the NutriSport KMP project before they become unmanageable. Use when a Screen file feels too long, when you see warnings like "DetailsScreen.kt is 568 lines", when the user says "split this Screen", "розпиляй екран", "decompose composable file", "екран став некерованим", "audit screen size", "файл занадто довгий", "extract sections from this Screen", or after the `feature` pipeline generates a new Screen ≥300 lines. Detects threshold breaches (lines, composable count, nesting, distinct UI concerns), proposes a project-conventional split that respects Route↔Screen contract, Preview discipline, `:core:*` cross-feature rules, and `:shared:ui` design-system rules, then either reports (audit-only) or executes the refactor with compile + composition test verification. Always invoke this skill instead of free-handing a Screen split — it bakes in the project's split-point heuristics so the result lands in the right module first try.
Use when verifying the visual/design fidelity of a specific Android screen via the `claude-in-mobile` skill (Android transport: `android-cli`) — bypasses full user flows by launching the debug app directly on the target screen via the `nutrisport://` deep-link scheme. Activates on requests like "verify the PaymentCompleted design", "check Details screen візуально", "screenshot the Cart", "відкрий цей екран на емуляторі", "як виглядає Checkout на емуляторі", "перевір верстку Profile", or any visual / design-system / Figma-fidelity check on a screen that lives behind a multi-step flow. Saves time when the screen is static or terminal (PaymentCompleted, Details) and the agent would otherwise have to walk through several prerequisite screens with form data. Android debug build only — iOS visual verification stays manual.
Translate Figma frames into Compose Multiplatform code following NutriSport's design system. Use this skill whenever the user asks to implement a UI screen, build a component from a Figma frame, "translate this Figma to Compose", "use design from Figma", or references the project's Figma file (URL, frame name, or node ID). Handles Figma Dev Mode MCP calls (selection check, get_design_context, get_variable_defs, get_screenshot), color/font/component mapping to :shared:ui, dark theme verification, preview and test scaffolding.
Discipline rules для Figma MCP на Pro-плані ($20: 10 calls/min, 200 calls/day). Prefer get_design_context, scope by nodeId, anti-runaway guard, no-retry on 429, behavioral session cache, per-screen interleaving (Rule 11). Activate before any series of Figma MCP calls — особливо bootstrap-сценарії, feature-pipeline runs з ≥5 screens, або довгі handoff-сесії. Triggers: "Figma MCP", "rate limit", "get_design_context", "get_metadata", "node-id", "figma file key", "Figma бюджет", "429", any sequence of mcp__figma-dev-mode__* calls.
Firebase operations for the NutriSport project via the firebase-tools CLI plus a zero-dependency FCM HTTP v1 sender — NO always-on Firebase MCP. Use when the user wants to read or roll back Remote Config, upload Crashlytics native symbols or R8 mapping files, distribute a build via Firebase App Distribution, list / inspect Firebase apps, or send a test FCM push notification (especially while working on push notifications). Triggers on "firebase", "remote config", "crashlytics symbols", "mapping file", "app distribution", "send test push", "FCM", "тестовий пуш", "відправ пуш", "remote config rollback", "firebase apps list", or any Firebase task on this repo that isn't pure client-SDK Kotlin code. NOT for Firestore/Auth data CRUD (no CLI surface — those need the Admin SDK / Console, deliberately out of scope here). NOT for editing google-services.json (that is a Firebase Console + applicationId concern).
| name | orchestrate-features |
| description | Orchestrate parallel feature development using worktree agents. Use when user wants to implement multiple features in parallel, check feature status, run a feature group, or says "orchestrate", "run features", "implement features", "feature status". Also triggers on `/orchestrate-features`. |
| disable-model-invocation | true |
Orchestrate feature implementation using parallel worktree agents.
/orchestrate-features all — run all groups (A, B, C, D, then E)
/orchestrate-features group:A — run Group A features (01, 03, 10)
/orchestrate-features group:B — run Group B features (04→06→05→07)
/orchestrate-features 01,03 — run specific features by number
/orchestrate-features status — show status of all features
You are orchestrating NutriSport feature implementation. Read the orchestrator and feature files first:
.claude/features/00-orchestrator.md for parallel groups, merge order, and conflict matrix.claude/rules/plan-mode.md for status conventions.claude/features/all:Launch agents for Groups A, B, C, D in parallel (each in a worktree). Wait for all to complete. Then launch Group E (tests).
group:X:Launch agent(s) for the specified group:
01,03):Check conflict matrix. If no conflicts, launch in parallel worktrees. If conflicts exist, run sequentially.
status:Read all feature files and report their Status field in a table.
Agent(
subagent_type="general-purpose",
isolation="worktree",
prompt="Implement feature NN. Read .claude/features/NN-name.md for full spec. Follow .claude/rules/ for conventions. Update feature file status to IN_PROGRESS at start and IMPLEMENTED when done."
)
IMPLEMENTEDBLOCKED, report error, continue with independent features