
The design-os-designer skill runs a fixed loop for any rendered UI work: concept, build, check, hand over, adjust. You give it a page or screen, and it assembles an evidence folder, runs the `ui` gate and a three-width render at 375, 768 and 1440 px, and reports exactly which checks passed, failed or never ran. Its best feature is the refusal to grade taste by script: deterministic checks are automated, while clarity and visual quality get handed to a fresh-context critic. The workflow is strict, with an explicit "what goes wrong, do this instead" table and a two-round cap on fixes, which suits teams wanting an auditable trail more than quick mockups. It needs Node 20, runs offline, and skips the browser-dependent checks cleanly when Playwright is missing.
$ npx -y skills add jangtrinh/design-os --skill design-os-designer --agent claude-codeInstalls into .claude/skills of the current project.
One workflow: Concept → Build → Check → Hand over → Adjust. It ships inside the ease-design package,
so it needs no separate install. The scripts are Node 20 or newer, built-ins only, and run offline;
the ui binary does all deterministic checking and this skill never grades taste by script.
Read concepts.md and write the one-sentence concept (surface, primary action, shape,
mode, data, states, widths). Pick a verb from its table and read only that knowledge file, end to end.
Read the numbered rules.md before writing markup. contract.md lists every
ui command and flag this skill uses; call nothing that is not there.
Sponsors