Performance

Make procedural isometric art that reads as designed rather than as programmer output — buildings, trees, towers, terrain shading, palettes,...

Making a game produce the same result twice — same seed, same world, same pixel. Use when a replay diverges, when two runs of the same code...

Numbers that grow — production, resources, prices, upgrades, capacity, and progress that keeps accruing while the tab is closed. Use for an...

Putting numbers, buttons, messages and panels on top of a game — a resource counter, a price, a build button, a toast, a dialog, floating +5...

Taps, drags, pinch-zoom, keyboard and camera control in an isometric game. Use for tap to place or select, drag to pan, pinch or wheel to zo...

Build a playable isometric game from one sentence, end to end — scaffold, code, run it in a browser, look at it, fix it. Use when someone sa...

Keeping a player's progress across a reload, a crash and a version bump. Use for saving a game, autosave, load, "my save is gone", "it forgo...

Sound and music with no audio files — synthesized clicks, chimes, thumps, ambience and a soundtrack. Use when adding sound effects, audio fe...

The wiring order for a Lattice game — canvas, surface, camera, palette, light, depth sorter, loop and input — and the shape a first build sh...

The failures in a Lattice game that produce no error and a plausible-looking wrong result — a black screen, a tap that opens the wrong thing...

Terrain, elevation, roads, paths and walkers in an isometric world. Use when adding hills, a heightfield, a river, a coastline, a road or a...

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...

Use when you need to resolve an in-progress git merge/rebase conflict.

A relentless interview that asks every frontier question at once, round by round.