A game nobody has to explain.

intuitive-game-design is a Claude Code skill for games and interactive experiences a first-time player understands without a tutorial — and that feel right under the hand. It carries three bodies of work: designing and diagnosing intuitiveness, building games around a single mechanic, and implementing sound on the web.

GitHub ↗

A tutorial is what you write when the design did not communicate.

This skill works the other side of that sentence. First, what the shape of a thing tells a player before they read anything — affordances, cognitive load, natural mapping, and the playtest protocols (CARD, ORID) that find out whether it actually landed. Then the handful of milliseconds that decide whether an input feels responsive or broken: variable jump, coyote time, input buffering, and the juice that makes a hit register. Sound is the third part, because on the web a silent game reads as unfinished.

Understand

Affordances, cognitive load, CARD / ORID playtests

Feel

Variable jump, coyote time, input buffering, juice

Hear

Web Audio synthesis, Tone.js, look-ahead rhythm timing

GitHub ↗

Why it matters

If it needs a tutorial, the design is not finished.

Explore other AI Tools →