菜单
Use when adding, changing, testing, reviewing, or migrating schema-first game state, generated APIs, saves, migrations, DevAPI state commands, or state fixtures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for the items catalog CLI, ownership API, reason tags, quarantine/reconcile, or items state and migrations.
Use for layout-affecting in-game UI work in this repository: new or changed HUDs, game screens, modal/dialogue sheets, menus, bottom navigation, responsive PC/phone layout, floating layers, clipping/scrolling/overflow, hit targets, or visual proof for a changed game UI surface. Forces a short widget/mode inventory before non-trivial edits so agents reuse existing Neotolis UI APIs. Skip for pure copy tweaks, asset swaps, or runtime automation tasks that do not change layout.
Use ONLY after a source-first search (shared asset library + free CC0/OFL sources) finds no fit, to generate real raster art for AI Studio asset workflows: fake shots, icon/source sheets, sprites, UI art, or source images for later asset tools. Generation is the last resort, not the default. Prefer Codex CLI imagegen via `codex exec` and `scripts/codex_imagegen.sh`; use Antigravity/agy CLI only as fallback. Owns raster creation only; nt-asset-workflow coordinates asset tools, catalog/intake handoff, and ai_studio/quality visual acceptance.
Use when the user asks for a full retrospective or analysis of an AI-assisted work session, chat history, agent run, long task, profiling data, slow progress, repeated failures, weak tool/subagent use, context loss, planning gaps, quality risks, or process improvements. Produces one comprehensive evidence-based session review with bottlenecks, causes, better workflow, and concrete changes for future runs.
Use for layout-affecting in-game UI work in this repository: new or changed HUDs, game screens, modal/dialogue sheets, menus, bottom navigation, responsive PC/phone layout, floating layers, clipping/scrolling/overflow, hit targets, or visual proof for a changed game UI surface. Forces a short widget/mode inventory before non-trivial edits so agents reuse existing Neotolis UI APIs. Skip for pure copy tweaks, asset swaps, or runtime automation tasks that do not change layout.
Use when starting or revising a game concept, first GDD, visual GDD, fake gameplay shot, gameplay loop, design pillars, reference pack, implementation handoff, or design-source cleanup for a specific game. Also use when converting loose ideas into scoped first playable requirements, gameplay data, UI flow, risks, and next implementation steps.
| name | nt-game-state-management |
| description | Use when adding, changing, testing, reviewing, or migrating schema-first game state, generated APIs, saves, migrations, DevAPI state commands, or state fixtures. |
Workflow router for the reusable Game State module. Its canonical contract
lives in features/game-state/, not in this skill.
features/game-state/README.md for the public surface, validation,
compatibility, and extension boundaries.features/game-state/INSTALL.md for wiring, generation, verification,
and removal.features/game-state/feature.json for the versioned machine contract.state/*.schema.json before changing call sites, then
inspect features/game-state/scripts/generate_state.py before changing
generated APIs.game_state.* files.py -3.12 features/game-state/scripts/generate_state.py
py -3.12 features/game-state/scripts/generate_state_test.py
Use explicit --schema and --out-dir for game variants or build-local
outputs.
features/game-state/references/contract.md.features/game-state/references/workflow.md.features/game-state/references/review.md.nt-runtime-automation.nt-quality-checks.