jpmschweitzer/clide
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

T-307: gate frame0-wireframe skill on per-screen approval

Browse Source 
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>
This commit is contained in:
jpmschweitzer
2026-06-10 11:41:57 +02:00
co-authored by Claude Opus 4.8
parent 9619613d4e
commit bbf1c84fd2
3 changed files with 24 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/frame0-wireframe/SKILL.md
+18 -2
View File
@@ -32,8 +32,14 @@ Always check first:
## Core Workflow
Wireframing is a **design conversation, not a batch job.** Produce **one screen
at a time**, show it, and **stop for the user's reaction** before authoring the
next. Each shown screen is a checkpoint — never fan out a whole set of
wireframes unprompted, even if the user described several screens up front.
1. **Health check** — verify Frame0 is running
2. **Write wireframe JSON** — to `docs/design/wireframes/{category}/{name}.json`
2. **Write wireframe JSON** — to `docs/design/wireframes/{category}/{name}.json`.
Author **one** screen.
3. **Push to Frame0** — `frame0-sync.py push <file.json>`
4. **Export PNG** — `frame0-sync.py export <file.json> <output.png>`
5. **Show it inline** — surface the exported PNG in the conversation so the
@@ -45,7 +51,17 @@ Always check first:
way to put an image in the clide conversation — a bare `Read` only shows
it in the transcript, not in the UI the user is looking at.
- **Otherwise**: `Read` the PNG so it renders inline in the transcript.
6. **Clean up** — delete test/scratch pages from Frame0 when done
6. **STOP and wait for approval** — after showing a screen, pause and ask the
user for feedback. Do **not** author, push, or export the next screen until
they give an explicit go-ahead. Iterate on the current screen until they're
happy, then proceed to the next one — looping back to step 2 for each.
7. **Clean up** — delete test/scratch pages from Frame0 when done
> **Multi-screen requests are still one-at-a-time.** If the user asks for
> several screens, treat it as a queue: build the first, show it, get approval,
> then move on. The only exception is an explicit, unambiguous instruction to
> generate a batch without stopping (and even then prefer the batch-export
> dry-run + approval flow below).
### Scripts