WhipUI
Two skills in one thin package for coding agents: WhipUI builds from a spec, WhipDesign turns a rough request into UX and visual work.
Make AI-built frontends feel designed.
WhipDesign
Reads the brief: whether a page is needed, what goes on it, the concept, UX intent, art and asset direction, motion.
WhipUI
Carries it out: routing, a design fingerprint (Project DNA), specialist skills loaded as needed, and rendered critique.
Install
Installs into the project, not into global settings, for Codex, Claude Code and VS Code agents.
npx whipui initWhere it stands
It started as help for following a design brief and grew toward a fuller design harness. Newer models handle more on their own, so some layers may no longer be needed.
- Exists now
- npm 0.1.0 → 1.2.0 (11 Aug – 14 Sep 2026), 5 GitHub releases; installs per project with npx whipui init for Codex, Claude Code and VS Code agents.
- Looks useful
- In my own use it helps AI follow the brief, give elements a reason, and think about UX more explicitly.
- Still unproven
- Any measured drop in generic output, or a measured quality gain.
- That the current architecture is the right one.
- May become unnecessary
- Layers that newer models already handle on their own.