Prototype

Prototype

Contract

Inputs

• Question (required): the design question being answered, drawn from the user's prompt or surrounding code. If the question is genuinely ambiguous and the user is reachable, ask before routing.
• Context (required): the surrounding code or page that frames the question. Determines whether to route to LOGIC or UI.
• LOGIC mode also takes: the relevant state, actions, domain terms, and legal-transition rules; a path for the throwaway HTML file; representative scenarios or enough domain rules to derive a happy path, a tricky edge case, and an illegal-action attempt; the main branch the throwaway branch is based on; and a real-code target, required only after the human validates the module.

Procedure

Route

Route before writing because LOGIC and UI variants require different artifact structures.

1. Classify the question:
   • Logic: state machine, edge case, data shape, reducer, API contract, or "does this feel right" → use the LOGIC procedure below.
   • UI: what something should look like, layout, information hierarchy, or "what should this look like" → use the UI procedure below.
2. If ambiguous and the user is not reachable, default: backend module → LOGIC; page or component → UI. State the assumption at the top of the artifact. Done when: the question is classified as LOGIC or UI, or the ambiguity default is stated and recorded on the artifact.

LOGIC procedure

When the question is about business logic, state transitions, or data shape.

1. Bound the change and state the question. Inspect the named paths and current version-control state; bound the change to the throwaway HTML path and, only after validation, the supplied real-code target. Stop if either target would overwrite unrelated work, the main-branch basis is unavailable, or a required domain rule cannot be established without guessing. Write one paragraph at the top of the demo stating the exact question and the state model being tested. This checkpoint prevents the prototype from answering the wrong question. Done when: the change is bounded, no target overwrites unrelated work or guesses a domain rule, and the artifact's top paragraph names the exact question and the state model.
2. Isolate the logic. Put the answerable logic in a single <script> block as a small pure module. Pick the shape that fits the question:
   • Pure reducer: (state, action) => state, for discrete events and a single state value.
   • State machine: explicit states and transitions, when legality of actions depends on current state.
   • Pure functions over a plain data type, when there is no implicit current state.
   • Class or module with a clear method surface, when logic genuinely owns ongoing internal state. Keep it pure: no DOM, no document, no button handlers reaching inside it; the page may call the module, but the module must not call back into the page. This module must be liftable into the real codebase after the question is answered. Done when: the logic sits in one pure module with no DOM or event-handler coupling, and the module's shape matches the question type from the list above.
3. Build the shareable HTML file. One file, plain HTML/CSS/JS, everything inline, opens by double-click. No framework, no bundler, no server. Mark the filename and the visible page as throwaway. Layout, top to bottom:
   • Title and one-line explanation of the question.
   • Current state panel: full relevant state rendered in domain language (not raw JSON), re-rendered after every click so the change is visible. Call out what just changed where it helps a non-developer follow.
   • Free-play buttons: one button per action, always available. Each click dispatches its action and re-renders the state.
   • Guided walkthroughs: tabs, each containing a plain-language description of the scenario and the ordered buttons to press. Clicking a step button performs that action and advances. Each walkthrough resets to a known initial state before running so reruns are deterministic. Cover all three scenario classes: the happy path, a tricky edge case, and an attempt at something that should be illegal. Write every label in domain language, not code. Keep it clean: one accent colour, generous spacing, no animations, no gimmicks. Done when: the HTML file opens by double-click with no server, shows the state panel, free-play buttons, and at least one guided walkthrough per scenario class, and every label is domain language rather than code identifiers.
4. Exercise it, then hand it over. Before surfacing, open the standalone file, exercise free play and all three scenario classes, and confirm that every action visibly produces the modeled state transition, including rejection or handling of the illegal action. Repair only defects that prevent the demo from answering the stated question. Then surface the file. Non-developers (designer, PM, domain expert) should be able to drive it without assistance. Add actions or scenarios only when their feedback requests them; do not infer broader scope. Done when: free play and all three scenario classes produce the modeled transitions, and the file path is surfaced to the user.
5. Capture. When the prototype answers the question: record the exact question and verdict in the commit that adds the demo on a throwaway branch based on the supplied main branch; do not push. Fold the validated reducer, machine, or function set, not the HTML shell, into the real module, and verify the same settled transitions there. The main branch keeps only the folded decision. Done when: the question and verdict are recorded in a throwaway-branch commit, the validated logic is folded into the real codebase with its transitions verified, and the HTML shell never ships as production code.

UI procedure

When the question is about what something should look like.

1. State the plan. Write one line stating the variants, the ?variant= switcher key, and the route or page. Place it in the prototype's location or as a top-of-file comment. Done when: one line names the variant count, the switcher key, and the target route or page, and a reader knows where the variants will live without reading the component code.
2. Default to 3 variants. Cap at 5. More than 5 stops producing radically different variants and starts producing noise. Done when: the variant count is between 3 and 5 inclusive, or fewer if the question genuinely demands fewer and the reason is stated.
3. Draft each variant. Hold each to the page's purpose and data, the project's component library or styling system, and a clear exported component name (VariantA, VariantB, VariantC). Variants must differ structurally in layout, information hierarchy, and primary affordance. Different colours or copy alone do not count. If two drafts are too similar, redo one with explicit "do not use a card grid" guidance. Done when: each variant has a distinct structural layout, and no two variants differ only in colour, copy, or spacing.
4. Choose sub-shape:
   • Sub-shape A (preferred): the route already exists. Render variants on the same route gated by ?variant=. Keep all existing data fetching, params, and auth above the switcher; only the rendered subtree changes per variant.
   • Sub-shape B (last resort): only when the thing being prototyped genuinely has no existing page to host it. Create a throwaway route following the project's routing convention, name it to be obviously a prototype (include prototype in the path), and use the same ?variant= pattern. Done when: sub-shape A or B is chosen and justified, and the chosen shape has a concrete route path recorded.
5. Wire the switcher. On the route, render all variants conditionally and add the floating switcher:

   const variant = searchParams.get('variant') ?? 'A';
   return (
     <>
       {variant === 'A' && <VariantA {...data} />}
       {variant === 'B' && <VariantB {...data} />}
       {variant === 'C' && <VariantC {...data} />}
       <PrototypeSwitcher variants={['A','B','C']} current={variant} />
     </>
   );
   

   Done when: each variant renders conditionally on the ?variant= search param, and the switcher component receives the variant list and current value.
6. Build the floating switcher. Small fixed-position bar at bottom-centre with left arrow, variant label, and right arrow. Clicking an arrow updates the URL search param so the variant is shareable and reload-stable. Keyboard ← and → also cycle; do not intercept when an <input>, <textarea>, or [contenteditable] is focused. Gate on process.env.NODE_ENV !== 'production' so the bar never ships to users. Done when: the switcher updates the URL search param on click and keyboard, the param survives reload, and the bar is gated out of production builds.
7. Hand it over. Surface the URL and the ?variant= keys. Done when: the URL and the list of variant keys are surfaced to the user, and each key is openable by appending it to the URL.
8. Capture. When a variant wins: fold the winner into the real code. On sub-shape A, drop the losing variants and the switcher from main. On sub-shape B, promote the winning variant to a real route. Commit all variants and the verdict to a throwaway branch off main. Done when: the winning variant is the only one on main, losing variants and the switcher are removed from main, and all variants plus the one-line verdict are committed to a throwaway branch that is not main.

Shared rules (apply to both LOGIC and UI)

1. Mark it throwaway from day one. Name it and locate it so a casual reader immediately knows it is not production code. Done when: the artifact's name or path contains prototype and a reader encountering it cold knows it is not production code.
2. Trivial to run. Start a UI prototype with one project command (pnpm <name>, python <path>, bun <path>). Open a logic prototype by double-clicking its single HTML file. Done when: the prototype runs with a single command or double-click and no manual setup is required.
3. No persistence by default. State lives in memory. If the question explicitly involves a database, use a scratch DB or local file with a clear "PROTOTYPE, wipe me" name and include that target in the bounded scope before writing it. Done when: the prototype holds state in memory only, or the scratch store has a name that marks it for deletion.
4. Skip the polish. No tests, no error handling beyond what makes the prototype runnable. Done when: the prototype contains no test files and no error handling beyond what keeps it runnable.
5. Surface the state. After every action (logic) or on every variant switch (UI), display the full relevant state so the user can see what changed. Done when: the state panel re-renders after every action or variant switch, and the full relevant state is visible after each change.
6. Capture the evidence off main. Commit the prototype to a throwaway branch. The main branch keeps only the validated decision. Done when: the prototype artifact and verdict are on a branch that is not main, and main contains only the folded decision.

Failure and recovery

Output

• Decision: one line answering the question. Evidence: the prototype HTML file (LOGIC) or variant components and switcher (UI), committed to a throwaway branch off main. Verdict record: the question, the answer, and the chosen path recorded in the issue or commit message on the throwaway branch.
• LOGIC mode terminal classification: validated, blocked, or non-converged, with the standalone HTML path, the state-model question, the exercised happy-path, edge-case, and illegal-action scenarios, and their observed transitions. For validated, also return the human verdict, the throwaway-branch commit, and the real-code target containing the validated module. Never report or ship the HTML shell as production code.