菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | fini-dev-install |
| description | 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. |
Set up local prerequisites that Fini agents expect before normal development starts.
This skill is intentionally narrow. It prepares sibling project context, not app dependencies or runtime builds.
Run this skill when fini-dev sees that .fini-dev-install.done is missing at the Fini repo root.
Run it directly when the user asks to bootstrap, install, or set up the Fini development workspace.
Ensure the sibling wiki repo exists and is usable:
../fini-wiki/FINI_WIKI_REPO, or the GitHub SSH URL for a sibling wiki repository inferred from the current checkout's origin remote.AGENTS.md, _hot.md, _index.md, raw/, pages/, tools/Resolve the current repo root and expected wiki path as ../fini-wiki/.
If ../fini-wiki/ does not exist, clone it with:
git clone <configured-or-inferred-wiki-repo-url> ../fini-wiki
If ../fini-wiki/ exists, verify it is a git repository.
Verify the wiki remote includes the configured or inferred wiki repository URL.
Verify required entries exist: AGENTS.md, _hot.md, _index.md, raw/, pages/, tools/.
Read ../fini-wiki/AGENTS.md so the active session has the wiki schema before wiki-dependent work.
When all checks pass, create .fini-dev-install.done at the Fini repo root.
Use .fini-dev-install.done as a local per-checkout marker.
Write a short plain-text marker with:
The marker is local-only and should be ignored by git.
If any check fails, do not create the marker. Report the failed check and the command or path that needs attention.
../fini-wiki/ except as a result of the initial git clone.fini-wiki for wiki work after setup succeeds.Report the concrete evidence collected:
../fini-wiki/ already existed or was cloned..fini-dev-install.done was created.