fini

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

Validate the Fini Android app on a real device or emulator through a device-automation workflow. Use this when users ask to verify Android behavior, prove navigation and state changes, debug mobile-only issues, or execute app automation against `com.fini.app`.

Use for the daily Fini GitHub issue and pull request report, stale PR attention callout, and delegation recommendation. Summarizes open Fini issues and PRs, recommends the next issue or PR to finish, and uses the configured Fini Dev Telegram targets for daily reports and implementation progress updates.

Use this when an autonomous coding agent, remote agent, or other delegated agent is asked to implement, debug, verify, or report progress on Fini repository work. This is a behavior overlay for agents: load `fini-dev` for Fini development mechanics, then use this skill to organize scope, autonomy, Telegram topic coordination, progress updates, blockers, verification evidence, and handoff discipline. If work arrives from the Telegram `Create` topic, always route it through `fini-create-ticket` as ticket intake before treating it as implementation work.

Use this to install, repair, or verify local Fini autonomous dev-agent schedules. This Fini repo skill defines the portable contract only; host-specific OpenClaw cron scripts, credentials, locks, and runtime state live in the agent environment.

Use when participating in the Fini Dev Telegram group, routing Fini development work across predefined topics, creating issue topics, or discussing Fini agent/process improvements.

Use this for first-run Fini repository setup before normal development work. Ensures required sibling project context exists, especially cloning and verifying ../fini-wiki from FINI_WIKI_REPO when missing, then records evidence for fini-dev bootstrap.

Create and draft Fini repository tickets, GitHub issues, and Jira tickets from Fini product, design, engineering, QA, Android, sync, release, or wiki context. Use when the user asks to create a ticket, draft an issue, write acceptance criteria, file a bug, turn a plan into a Fini issue, or capture follow-up work for this repo; use fini-wiki for durable ticket storage.

Shared foundation for using the Fini app binary and CLI interface. Use from other Fini skills when they need binary preflight, CLI/app mode selection, JSON vs human output decisions, runtime CLI smoke checks, or safe command sequencing. This is mostly a shared workflow layer; user-facing quest, space, reminder, and focus management should usually route through `fini`.

Shared foundation for Fini app version metadata and version invariants. Use when changing package versions, About version display, CLI version output, Android version naming, Tauri/Cargo/npm metadata, or CI release version sync. For operational releases, release tags, and release workflow runbooks, use fini-release and load this skill only for metadata semantics. Depends on fini-scripting when implementation touches Makefile, npm scripts, cargo xtask, or CI command architecture.

Use this for Fini wiki work: querying existing project knowledge from the sibling fini-wiki repo, or saving durable raw source material there. Trigger when the user asks what the wiki says, needs product/domain/terminology/historical/architecture context, asks about prior decisions or current project semantics, or asks to save/document/capture/write plans, decisions, research, summaries, tickets, implementation results, design handoffs, or context into the wiki raw folder. Raw capture is the default save mode; full ingestion requires an explicit user request. For Fini questions that may depend on historical product context, query the wiki even if the user does not explicitly say 'wiki'.

Shared foundation for Fini repo automation architecture. Use when adding or changing Makefile targets, npm scripts, cargo xtask commands, CI command orchestration, release/build/package tooling, or any repo-local automation entry point.