TRIGGER when user asks to create, update, list, or manage quests, spaces, reminders, or Focus state in Fini. Use the `fini-cli` foundation skill for binary preflight, CLI/app mode selection, JSON output decisions, and safe command sequencing before any action.
Always use this at the start of development work in the Fini repo. Orchestrates which repo-local or gstack skill to load, which Makefile command to prefer, what context to read, and what evidence is required before claiming implementation, debugging, QA, Android, design-to-code, release, or documentation work is complete.
Use this skill for Fini major release preparation, especially when the user asks for Play Store screenshots, Android marketplace screenshots, store listing assets, release screenshot packages, or "major release prep". This skill should trigger even if the user only mentions screenshots, because Fini's canonical store assets live in `docs/play-store/` and must be generated, checked, and reported consistently before a release.
Run and maintain Fini's GitOps release workflow. Use this whenever the user asks to make a release, bump a release version, push a release tag, inspect release readiness, fix release automation, or verify release CI. Releases are initiated by pushing a signed annotated v* tag; `make release` must run `make pre-release-check` before any version commit, branch push, or tag push.
Single source of truth for testing the Fini app: how to run unit, integration, and end-to-end tests, and how to write new ones. Use when the user asks to run tests, write a test, add coverage, debug a failing test, choose a test category, set up a multi-actor scenario, or understand fixtures and harnesses. For Android-only behavior, load `fini-android-testing` instead. For CLI semantics referenced from CLI e2e tests, also load `fini-cli`. For Makefile/CI/script changes around tests, also load `fini-scripting`.
Install or upgrade Fini CLI from the latest GitHub release assets.
Fini Vue frontend implementation conventions for views, templates, rendering decisions, and tests.
Canonical Fini design source = sibling `../fini-design/` HTML/CSS/JS handoff bundle exported from claude.ai/design. Load this skill on ANY of these triggers (auto-trigger first, ask second): 1. User pastes a `https://api.anthropic.com/v1/design/h/<hash>` URL (a Claude Design export link). 2. User asks to "fetch / read / sync / pull / refresh" a design or design bundle, with or without a URL. 3. User asks to "implement / build / translate / port / recreate / wire up" a Fini surface — including Context menu, Quest card, Quest list, Composer / ChatInput, Top nav, Settings section, Device list, Device view, Reminder, Focus view, Active quest panel, Spaces, Energy, Voice model, History, or any prototype filename under `../fini-design/project/preview/`. 4. User says "design a new surface", "refine [surface]", "audit visuals", or "clarify design intent" for Fini. 5. User asks to update/close a Fini GitHub issue whose body cites a `../fini-design/` prototype or wiki grilling note (e.g. `