About build-isometric-arpg
A development skill for building isometric ARPGs through small, playable slices, from movement and combat to rewards and progression. It is for game developers who need stable runtime boundaries, deterministic review states, and release checks.
Key features
- 01Build a complete playable loop before expanding scope
- 02Use data-driven contracts for game content
- 03Deliver vertical slices with deterministic test states
- 04Keep simulation and contact outcomes authoritative
- 05Validate tests, builds, saves, and gameplay before release
Use cases
- 01Plan an isometric ARPG from menu to progression
- 02Add combat and enemy behavior in playable slices
- 03Test difficult states such as boss phases and save migrations
- 04Verify fresh starts, saved continuation, and retry flows
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/build-isometric-arpgin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMEBuild Isometric ARPG
Build one coherent playable loop before expanding scope: title/menu, character choice, movement, one encounter, reward, progression, and continuation.
Establish the production contract
- Inspect the current game entry point, scene loop, content model, controls, save model, and tests.
- Record the authoritative baseline before integrating dependent work. Preserve unmerged work and do not build from a stale branch.
- Define data-driven contracts for player classes, equipment, enemies, zones, encounters, quests, and review fixtures. Keep authored content separate from runtime state.
Build in vertical slices
Deliver each slice with a playable route and deterministic test state. Prefer this order:
- Movement, camera, collision, target selection, and pause/restart.
- One combat verb plus contact, damage, posture, recovery, and death.
- One enemy with telegraph, decision loop, and counterplay.
- One reward and atomic inventory/progression update.
- One zone transition or objective completion.
Avoid adding a second system until the preceding slice has gameplay proof, automated coverage, and a stable save/load path.
Maintain runtime boundaries
- Keep simulation state deterministic and serializable where possible.
- Consume authoritative contact events; do not infer physics outcomes from visual state.
- Centralize timing, damage, cooldown, and content values. Do not duplicate combat clocks across components.
- Make equipment, pickups, save migration, and reset flows atomic and idempotent.
- Provide review query parameters or fixtures for difficult states such as boss phase changes, empty inventory, interrupted actions, and save migrations.
Validate before release
Run focused unit tests, type/lint checks, production build, and a real playthrough in the repository-approved browser. Verify a fresh start, saved continuation, loss/retry, one complete objective, keyboard/mouse controls, and the intended mobile baseline. Report known baseline failures separately from new failures.