prototype

You can create a throwaway prototype to test a design idea by running a single startup command that builds either a logic/state terminal experience or UI variation layouts. It requires no persistence or production polish, enabling rapid validation before committing.

The best way to explore UI layout variations is by generating multiple layouts on a single route. This approach allows you to switch between UI exploration and logic prototyping modes seamlessly to compare designs before making a commitment.

State machine prototyping works by creating a tiny terminal experience to test how a state machine responds to inputs. You can explore logic and state transitions rapidly without building out full application persistence or production features.

You capture findings and decisions from a design exploration by writing them directly to a NOTES.md file. This simple mechanism ensures you record explicit question framing, quick learnings, and the rationale for your next steps.

You do not need any dependencies or database setup to run a throwaway prototype. The process requires minimal setup with a one-command startup, intentionally avoiding persistence and production polish to focus purely on design exploration.

You should avoid using throwaway prototypes when you need production polish, data persistence, or a deployable application. This approach is strictly for fleshing out design questions and validating approaches before committing to a real implementation.