blueprint-screens
Skill113 starsChanged 19 days agoMITView on GitHub
Use when iterating on the look of a Happy desktop screen or flow (onboarding, setup, settings, any full-window page) and the person wants to see screenshots fast — render the screens in the Blueprint, capture them in one browser at a couple of window sizes, and show them for feedback.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- guided-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Look at the PNGs yourself before showing them.
- Very specific: line 54
Keep the flow page; it is the Blueprint coverage for those screens.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blueprint screens for design review
The fastest loop for reviewing UI: render the real happy-desktop-ui components
in the Blueprint, capture them as PNGs, show the person, take feedback, repeat.
This is a design-review loop, not a test. It does not replace the rendering
contracts in DESIGN.md, and it is not a reason to write tests.
Rules
- One browser. Chromium only. No Firefox/WebKit passes while iterating.
- Two window sizes. The window Happy opens at, 1100 × 760, and its minimum,
720 × 640 (
packages/happy-desktop-electron/sources/main/main.ts). Add a size only when the person asks for one. - One happy path. Show the screens in the order a person meets them. Add an error or edge state only when it is what is being reviewed.
- Real components, fixture props. Blueprint pages compose the shipped components with props only; never bootstrap the app. If a screen does not exist in the Blueprint yet, add it — that is the change the app will import.
- Show results early. Capture the current state before changing anything, so every iteration can be compared with a "before".
Steps
- Find or add the flow page. A flow page lives in
packages/happy-desktop-ui/dev/pages/<Name>Page.tsx, exports acomponentNumber(P-…for product pages), and renders each screen in aFullScreenSpecimenwithwindow={{ width, height }}and ascreen="<NN>-<step>-<width>x<height>"name.OnboardingFlowPage.tsx(#onboarding-flow) is the reference. Capture. Chromium needs reviewed full-access execution on macOS:
pnpm blueprint:screens onboarding-flow --out .context/screens/onboarding-flow/beforeOptions:
--only 1100x760(substring filter on screen names),--scale 1(default 2× retina),--settle 1500(ms to let scenes and fades land). Output: one folder per window size (1100x760/,720x640/), each holding that size's screens in flow order, plus anindex.htmlcontact sheet. A full run takes about 20 seconds.- Look at the PNGs yourself before showing them; fix anything obviously broken.
- Show the person:
open <out>/index.html(full access), and list what changed. - Iterate on the components, then capture to a new folder (
after-1,after-2, …) so each round can be compared with the previous one.
When the person approves
Keep the flow page; it is the Blueprint coverage for those screens. Then follow
the normal workflow: pnpm --filter happy-desktop-ui typecheck, build what you
touched, pnpm format, and sync to main only when asked.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

