prototype

Overview

Resolves visual / interaction decisions in spec authoring by generating throwaway UI variants. Three default variants (max 5, MIN 2 valid else NEEDS_CONTEXT); each differs on at least one axis (layout / density / motion). Status state machine: triggered → generating → awaiting_selection → resolved (alt: need_context, bypassed). Decisions land in .omo/notepads/<plan>/decisions.md as [proto] entries.

Two rendering paths:

• Brownfield — same existing route serves ?variant=A|B|C|E; floating bottom-bar switcher for live comparison. Throwaway code lives in .omo/throwaway-worktree/<feature>/ worktree.
• Greenfield — own static HTML generator outputs .omo/prototypes/<plan>/{variant-A,B,C,index}.html; does not delegate to build-gate-visual-review (its <script> ban is incompatible with the floating switcher).

职责边界:/prototype is throwaway spec-authoring scaffolding. It does not produce production UI, does not deploy, and does not enforce meisijiya-frontend-taste in the same way designer-handoff does. The exemption template is [taste:exempt] (see §3.3). Selected variant feeds spec §3.5 via [PROTO-RESOLVE] marker replacement.

When to Use

Use when: