The Core Workflow ran straight through and tended to fan out a
whole set of screens unprompted. Reframe it as a design
conversation: author one screen, show it, then STOP for explicit
user approval before building the next (loop back to step 2 per
screen). Multi-screen requests become a one-at-a-time queue.
Closes T-307 (under UI epic T-276).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A bare Read only renders the PNG in the transcript; inside clide the proper
way to put an image in the conversation is the clide image show verb (T-249),
which renders a native image card in the live Claude pane.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
After exporting a wireframe PNG, Read it back so it renders in the
conversation — the user is designing with you and should see the result
without opening Frame0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two general-purpose skills for visual design work:
- frame0-wireframe drives Frame0 (local wireframing app) from
JSON source files, with push/pull/export and a batch script.
- d2-diagram wraps the d2 text-to-diagram CLI for architecture
and flow diagrams.
Sourced from settled-reach/main where they were already in use.
Co-Authored-By: Claude <noreply@anthropic.com>
jpmschweitzerandClaude Opus 4.8