ui-design · uizze — Claude Code skill: UI design and setup
The ui-design skill helps design, refine, and review web and mobile interfaces with product examples. Use it for new screens, responsive layouts, redesigns, and UI audits.
Apache-2.0 545 installs ★ 128 updated 2026-10-21
npx skills add uizze/uizze --skill ui-design -a claude-codeWhat ui-design does
ui-design reads the brief, existing UI, components, tokens, assets, and project notes before choosing a workflow. It covers new interfaces, product and dashboard work, polish, simplification, audits, native iOS, and implementation. After the direction is set, it checks important states at representative desktop and mobile sizes.
The skill is made of Markdown playbooks such as new-work.md, operate.md, polish.md, distill.md, audit.md, ios.md, craft.md, and Overdrive. Optional visual lookup can use find_ui_references or find_ui_materials through tools provided by the host. Paid retrieval is optional, so local design work can continue without it.
This is not a background service or executable design engine. Overdrive is opt-in and needs a chosen direction before implementation, which makes it unsuitable as an automatic default for routine UI changes.
What it helps with
- design a new web interface
- refine an existing product screen
- build a responsive mobile layout
- audit an interface without changing it
- inspect states at a reported failing size
Example prompts for the agent
- Design a new product screen around its audience, primary task, key states, and intended result.
- Refine this existing interface while preserving its visual system, then inspect it at desktop and mobile sizes.
- Use Uizze Overdrive on this screen, choose a direction first, and compare the rendered result with the supplied reference.
How to install ui-design
1Skills CLI (Vercel)
npx skills add uizze/uizze --skill ui-design -a claude-code2Manually: put the files in place
~/.claude/skills/ui-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ui-design/
1Skills CLI (Vercel)
npx skills add uizze/uizze --skill ui-design -a codex2Manually: put the files in place
.agents/skills/ui-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add uizze/uizze --skill ui-design -a cursor2Manually: put the files in place
.cursor/skills/ui-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install uizze/uizze skills/ui-design2Manually: put the files in place
.github/skills/ui-design/SKILL.md1Skills CLI (Vercel)
npx skills add uizze/uizze --skill ui-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/uizze/uizze --path skills/ui-designManually: put the files in place
.devin/skills/ui-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add uizze/uizze --skill ui-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ui-design
How do I install ui-design in Claude Code?
Run npx skills add uizze/uizze --skill ui-design -a claude-code, then check ~/.claude/skills/ui-design/SKILL.md.
What does ui-design do?
It guides web and mobile UI design, refinement, implementation, and review. The skill selects a relevant playbook, uses project materials, and inspects important states across target sizes.
Is paid access required for UIZZE visual references?
No. Paid retrieval is optional, and missing access does not block local design work. find_ui_references and find_ui_materials use tools available from the host.
Source text
SKILL.md · Apache-2.0
--- name: ui-design description: Design, build, or improve web and mobile interfaces using real product examples from UIZZE’s 800,000+ web and iOS screens. Use for UI design, UX design, frontend or web design, mobile app UI, responsive layouts, design systems, redesigns, visual polish, interface critique, and requests like “make this UI better.” license: Apache-2.0 metadata: uizze-version: uizze-design-v13 design-stack-version: 4.4.0 --- # Uizze UI Design ## Work from the product Read the brief, existing UI, components, tokens, assets, and any PRODUCT.md or DESIGN.md before designing. The user's request and project constraints outrank this skill. Preserve an established visual system for extensions and polish; replace it only for an approved redesign. A new project does not require those files. Identify the audience, primary task, important states, and intended result. Ask only about missing choices that would materially change the work. A precise request is enough to proceed; do not turn a small fix into a discovery workshop. ## Select the workflow Load the playbook for the requested action, plus the platform and craft guidance needed to execute it: - New interface or major redesign: [new-work](reference/new-work.md) - Product or dashboard work: [operate](reference/operate.md) - Refinement and polish: [polish](reference/polish.md) - Simplification: [distill](reference/distill.md) - Explicit audit: [audit](reference/audit.md), read-only unless fixes were requested - Native iOS: [iOS](reference/ios.md), alongside the action's playbook - Explicit `/overdrive`, “Uizze Overdrive”, or a request for exceptional interaction work: [Overdrive](reference/overdrive.md) For implementation, use [craft](reference/craft.md) after the direction is settled. Load only relevant files; multiple complementary playbooks are allowed. Overdrive is opt-in, not the default for ordinary UI work. It requires a chosen direction before implementation. “Use Uizze Overdrive on this screen” works through this router; a native slash command depends on the host. These are self-contained Markdown playbooks, not an installer, background service, or executable engine. ## Optional Uizze evidence Read [the reference policy](references/uizze-reference-policy.md) before using `find_ui_references` or `find_ui_materials`. Inspect relevant visual evidence when it can inform the layout, state, interaction, or assets. Use the host's available tools, not invented calls or connections. Paid retrieval is optional; missing access does not block local design work. Distinguish an exact reference, a related example, no match, and a service error. Briefly disclose a limitation that affected the result. Never claim an image was inspected or a state was found without evidence. ## Finish Build the requested scope and exercise its important states. Render and inspect the real result at representative desktop/mobile sizes or native device classes, including the user's reported failing size. Compare it with the chosen direction or supplied reference, not just with the absence of runtime errors. Fix material problems in a batch, then render and inspect again. Stop once the requested result is verified; do not keep inventing work. If a bounded pass cannot resolve an issue, report it instead of claiming a pass. When rendering is unavailable, distinguish code checks from visual verification. Keep the handoff concise: what changed, what was actually tested, and any remaining limitation. A skill does not authorize publishing, purchases, new dependencies, account changes, or destructive actions.
© uizze · Apache-2.0 · uizze/uizze
Similar skills
All skills for Frontend and UI →ui-design by other authors comes first.