How a Premise Becomes a Playable Experience
A working pattern for turning loose ideas into experiences you can pick up. Six steps, repeated until the project feels honest.
- 00
Premise
The spark. The what-if that makes the project worth building before constraints are invited.
- 01
Prompt
Concept, framing, constraints, and the experience goal. What should the player or reader actually get to experience?
- 02
Prototype
First functional shape. A rough build that lets the idea be tried instead of just described.
- 03
Playtest
Trial runs. Watching where players get stuck, surprised, or pulled deeper than expected.
- 04
Patch
Repair and refinement. Rewrites, sharpened UX, and trimming the parts that overreach.
- 05
Publish
Packaging the project so others can browse, try, or build from it without a manual.
Playtesting and Patching continues.
Most AI portfolios show outputs. Most prompt libraries show recipes. Most demos show isolated experiments.
AI XP Design Studio focuses on the experience layer: how AI becomes playable, navigable, useful, characterful, and strange. The projects in the archive are studies in that layer — small enough to ship, specific enough to learn from.
Playable, not promptable
If the only way in is a clever prompt, it isn't done. Each project ships with an interaction model.
Small, honest scope
A scene, not a saga. One verb, then maybe two. The fastest way to learn something is to finish it.
Refusal as design
Some patterns are out: fake metrics, generic hype, dashboard clutter, sci-fi UI noise. Restraint is a feature.
Ready to browse the work?
Open the library — over three dozen projects across five lenses.