aigd

AIGD Phase 4 · finalize and generate the handoff package. Use this when, after a system is finalized in playtesting, you want to generate the interface contract, acceptance cases, (as needed) art/client/server docs, and the designer-facing acceptance checklist. Produces platform-agnostic handoff artifacts that "another AI can develop directly from". Part of the aigd package; methodology in ../aigd/references/.

AIGD (AI Game Design) main entry / orchestrator. Use this when the user wants to **start a game project from scratch**, is **unsure which phase to use**, wants to **survey or advance the entire development pipeline**, or needs to **maintain the project spine (project charter / manifest)**. This skill only does "read the spine → judge progress → dispatch to the matching sub-skill"; **if a specific step is already clear (concept / build a system / iterate / finalize / sync-back / screenshot capture), use the corresponding sub-skill directly** (aigd-concept / aigd-system / aigd-iterate / aigd-handoff / aigd-sync / aigd-ui-capture). The methodology ships with references/ and does not depend on any specific project.

AIGD cross-cutting action · sync-back integration (a non-linear "last step", triggered after every system's handoff). Use this when, once a system is settled, you need to update the global spec, the overall html prototype (integration demo), the implementation master guide (handoff-package entry point), or mark downstream systems for recheck after a shared item changes. Maintains consistency between the spine and the handoff-package entry point. Part of the aigd package; methodology in ../aigd/references/.

AIGD Phase 2 · single-system design (discussion-driven). Use this when you want to build out a system — rules (-01, tagged with R-numbers), config table (with test data), system html prototype. The source xlsx is optional (read it if given, otherwise rely on interview). Part of the aigd package; full methodology in ../aigd/references/methodology.md.

AIGD Phase 1 · brainstorming & top-level design. Use this when you want to set the concept for a new game, fix the core loop / platform / target users, or split the game into a system list + dependency graph and start the project spine. Produces / revises the project charter + manifest (system list). Part of the aigd package; methodology in ../aigd/references/.

AIGD Phase 3 · playtest iteration. Use this when, after the user playtests the prototype, they want to optimize the rules or change the config table (can be run repeatedly). Only touches the "cheap" artifacts — rules / config / prototype — not the contract / acceptance (those are produced after finalization). Part of the aigd package; methodology in ../aigd/references/.

AIGD · UI screenshot → UI DSL (knowledge-base capture / tool 1). Use this when you want to turn a game UI screenshot (a competitor's or your own) into structured md (type/hierarchy/geometry/interaction/state), so ui_render.py can restore it to a wireframe and it can be accumulated into the patterns/UI-paradigm knowledge base. The authority for the read-the-image recipe and grammar is in ../aigd/references/ui-dsl-spec.md; this skill only orchestrates the flow, it doesn't duplicate the grammar. Part of the aigd package.