Small games.
High standards.

A small game should do only a few things, communicate them clearly, and make at least one of them feel excellent.

Content volume must never hide a weak core. The first minute must contain a satisfying decision or action before levels, narrative, progression, or collectibles are added.

• One primary emotion.
• One supporting emotion.
• One emotional dynamic it deliberately avoids.
• One to four meaningful verbs.
• A complete loop lasting roughly 30 seconds to 3 minutes.

game-name/
├── index.html
├── style.css
├── game.js
├── genome.json
└── README.md

No framework, engine, build tool, backend, login, or remote database is required for this production line.

A new concept must differ from recent games through at least three dimensions: primary verb, primary emotion, decision structure, spatial topology, input rhythm, session structure, visual language, or feedback style.

Changing colors or characters without changing the experience does not create a new game.

The Play Lab optimizes for the desire to return, not compulsion. A player should come back because there is something meaningful to learn, discover, create, or share—not because they fear losing something artificial.

1. Load without runtime errors.
2. Explain the goal and controls.
3. Respond to the primary action.
4. Reach a complete outcome.
5. Restart immediately.
6. Expose a short ?test=1 validation path.
7. Receive human play and record the resulting lesson.

A prototype is complete when it can be played without its creator, communicates its rules, contains a short complete arc, has clear feedback and closure, restarts immediately, passes validation, has been played by another person, and records what the next game should learn.