prototype

Build a throwaway prototype to validate design decisions by running a single command that generates either a logic prototype for state models or a UI variant for visual exploration. The artifact is single-use, stores no persistence, and documents the outcome in a NOTES.md file.

Exploring UI variations for a single route is best handled by a throwaway UI prototype, which lets you rapidly test multiple visual options. It runs from one command, creates no persistent storage, and captures the final design choice in NOTES.md.

Use a logic prototype instead of a UI prototype when you need to validate state models or business rules rather than visual layouts. This approach tests core logic rapidly, runs from a single command, and records the validation outcome in a NOTES.md file.

You can run a prototype without setting up database persistence because these artifacts are single-use and store no data unless explicitly defined. This allows you to test design questions immediately without configuring a persistent storage layer.

Document design exploration decisions automatically through a NOTES.md file generated by the prototype. This file captures the validated design question and outcome, ensuring clear handover and guiding future engineering or UX work based on the throwaway artifact.