interaction-design-board

Generate several self-contained HTML prototypes that each implement a distinct interaction hypothesis, then load them into a Design Board where users perform the same task in every candidate. Structured feedback is captured in feedback.json and the approved decision is frozen in approved.json before implementation starts.

Static mockups show visual styling but cannot demonstrate collapse states, keyboard paths, selection models, or task handoffs. Runnable HTML prototypes let users actually click, expand, filter, and move through states, which is required when the decision depends on behavior rather than appearance.

Use the Design Board when the open question concerns behavior, workflow, hierarchy, or progressive disclosure after clicking or expanding. Use static style exploration tools when the decision is purely visual, such as color, typography, or layout aesthetics.

The builder rejects candidates that are byte-identical to another variant, reference external scripts, styles, or media, use CSS @import, escape the manifest directory, or omit declared interaction states. Every candidate must be a fully self-contained HTML document with inline CSS and JavaScript.

No. The workflow requires the user to operate each candidate, submit structured feedback, and confirm the agent's interpretation, after which approved.json records the selected variant, interaction rules, and exercised states. Implementation begins only after this approval artifact exists.