NutriSport

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).

Weekly review of infrastructure changes for the NutriSport portfolio docs. Activates on "/infra-weekly", "/infra-review", "weekly infra", "тижневий ревʼю інфри", "що ми зробили цього тижня в інфрі", or any time the user mentions Sunday review of infra wins. Scans the last 7 days of git commits, diff'd files in .claude/{hooks,skills,rules,settings*}, gradle/libs.versions.toml, and build-logic/, then drafts portfolio entries against docs/infrastructure/templates/entry.md and updates docs/infrastructure/WEEKLY_LOG.md. User work: ~15 minutes confirming and editing drafts.

Аналізує Android build-файли і ProGuard/R8 keep rules проєкту NutriSport — знаходить redundant broad rules, рекомендує точкові заміни, перевіряє що конфігурація мініфікації відповідає Google best practices. Викликати коли додається нова бібліотека, після падіння release, перед релізом, або явним `/skill r8-analyzer`.

Set up Sentry crash and error reporting in a Kotlin Multiplatform + Compose Multiplatform app (Android + iOS) using the unified sentry-kotlin-multiplatform SDK. Use this whenever the user wants to add Sentry, wire crash / error / observability reporting into a KMP project, configure dSYM or ProGuard/R8 mapping upload, initialize SentrySDK, scrub PII via beforeSend, add a crash smoke test, or decide between Sentry and Firebase Crashlytics (run both or migrate). Triggers on: Sentry, crash reporting, error monitoring, observability, sentry-kotlin-multiplatform, SentrySDK, dSYM, sentry-cli, beforeSend, DSN, SENTRY_AUTH_TOKEN.

Write human-sounding documentation free of AI patterns for the NutriSport KMP project. Activates when editing any .md file, writing README, ARCHITECTURE, CHANGELOG, CONTRIBUTING, PR descriptions, commit messages, release notes, pitch documents, portfolio descriptions, project descriptions for job applications. Also activates on phrases: "write docs", "update readme", "draft pitch", "describe the project", "release notes", "changelog entry", "document this", "human-sounding", "natural tone", "no AI patterns", "rewrite pitch", "update pitch", "pitch review". Enforces Wikipedia-based anti-AI-pattern rules plus NutriSport-specific documentation and pitch rules. Use this skill even for small .md edits and single-paragraph rewrites.

Pull live crash data from Firebase Crashlytics via MCP, correlate with source code, and generate an analysis report with proposed fix. Use when user says "analyze crashes", "check crashlytics", "what's crashing in production", "crashlytics issue", "production crashes", or provides a Crashlytics issue ID.

Read a Tracey session dump file, map events to code paths, reconstruct the user journey, and identify where things went wrong. Use when user provides a crash dump, says "replay this session", "what happened before the crash", "analyze this dump", "tracey dump", or provides a path to a replay JSON file.

Analyze Kover coverage report and provide prioritized recommendations. Use when user asks about test coverage, coverage gaps, what to test next, coverage analysis, or says "analyze coverage", "show coverage", "what needs tests". Also triggers on `/kover-analyze` with optional module filter argument.

Scaffold a new feature module with all boilerplate following NutriSport Clean Architecture. Use this skill when the user wants to add a new screen, create a new feature module, or says "new feature", "add screen", "create module for X". Handles module creation, navigation registration, DI wiring, and Gradle setup.

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`.

Generate tests for a Kotlin class following NutriSport conventions. Use this skill whenever the user asks to write tests, add test coverage, create unit tests, or says "test this", "cover this", "write tests for X". Also use when user mentions a specific ViewModel, UseCase, Mapper, or Repository and wants it tested. Handles both pure use case tests and ViewModel tests with Turbine/Mokkery.