Experimental Front-End Command Lab

Generative UI Kill-Switch

Chat with Claude, Codex, and Pi and render visual tooling as JSON-defined interfaces. This surface is rebuilt for contrast, rhythm, and live design stress-testing.

Open Preview GalleryReadyAgent: claudeRuntime: ready

Live Render Stream

Session 66579490

Tip

Try: “Show a dashboard with a quarterly chart and motion status card.”

Front-end Ruleset

Visual Priority Stack

Use one dominant visual stack per response; avoid style drift between sibling sections.
Prioritize semantic naming and layout intention over decorative variation.
If a component is interactive, define outcome, labels, and state transitions clearly.
Charts must always show titles, units, axis context, and readable contrast.
Data forms must define field purpose, validation need, and submit intent.
Motion must be purposeful: one clear pattern for each status class.
Avoid one-component monocultures; use Stack/Grid to create hierarchy and rhythm.
Treat JSON-render specs as production surfaces: strict schema, strict semantics, strict fallback plan.

All incoming assistant visuals are rendered through the JSON render schema and custom component registry for predictable, testable output.