w-ui — Claude Code skill: UI work and installation
w-ui — a Claude Code skill for building or reshaping user-facing interfaces around a project’s existing tokens and accessible interactions. It checks rendered screens on desktop and mobile.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a claude-codeWhat w-ui does
w-ui guides an agent through a small, complete UI change, then checks how it renders and how its main interactions behave. It starts by examining the project’s tokens and shared components when they exist. The layout should account for the surface’s purpose, mobile use, visible focus, and keyboard navigation.
The workflow covers loading, empty, error, success, and overflow states where relevant. It calls for reviewing screenshots and fixing observed issues, with at most one further verification pass. Browser tools are needed for visual inspection; a type check does not replace it. The skill rules out adding a new animation library. Playwright E2E is used only if an existing spec covers the path.
What it helps with
- build a user-facing screen from a brief
- adapt a UI to existing project tokens and shared components
- check keyboard navigation and interface states
- spot visual issues across desktop and mobile layouts
Example prompts for the agent
- Build a settings screen using the project’s existing tokens and components.
- Reshape this page for mobile and check its keyboard navigation.
- Add loading, error, and empty states to this screen.
How to install w-ui
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a claude-code2Manually: put the files in place
~/.claude/skills/w-ui/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-ui/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a codex2Manually: put the files in place
.agents/skills/w-ui/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a cursor2Manually: put the files in place
.cursor/skills/w-ui/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-ui2Manually: put the files in place
.github/skills/w-ui/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-uiManually: put the files in place
.devin/skills/w-ui/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ui -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 w-ui
How do I install w-ui in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-ui -a claude-code. The skill file is at ~/.claude/skills/w-ui/SKILL.md.
What does w-ui do?
It guides UI changes that use a project’s existing tokens and components, then checks rendering and interactions such as keyboard navigation.
How does w-ui verify a UI change?
It calls for reviewing desktop and mobile screens, exercising key interactions, and fixing observed issues. Visual inspection requires browser tools; a type check is not a substitute.
Source text
SKILL.md · MIT
--- name: w-ui description: Build or reshape UI with purpose, existing tokens, accessible interactions, and bounded rendered verification. disable-model-invocation: true --- Build or reshape a user-facing surface. Planning a feature without UI work stays on `/w-plan`. Installing a primitive stays on `/w-shadcn`. Do not invent `PRODUCT.md` or `DESIGN.md`. Follow existing tokens and root `DESIGN.md` when present. Do not install animation libraries or design-detector hooks. Load `frontend-design` for visual direction, `composition-patterns` for reusable APIs, and `web-design-guidelines` for the UI code checklist. Durable jobs live in matching MDX/README/`DESIGN.md`. 1. Name the job, the person, and the surface mode: Operate (app/task), Persuade (marketing), or Read (docs). 2. Use the brief, existing screens, or a stated aesthetic. If the repo has tokens and shared components, inspect those first. 3. Prefer shared primitives. Compose at the second call site. Do not extract a compound API for a one-off route. Do not lift server data into a client provider. 4. Mobile-first layout, visible focus, keyboard path, `prefers-reduced-motion`. Do not add a new motion library. 5. Cover loading, empty, error, success, and overflow as applicable. 6. Implement the smallest slice that completes the job. 7. Inspect desktop and mobile together. Exercise primary interactions and keyboard navigation. Critique screenshots. Fix evidenced issues in one batch. Confirm with at most one more pass, then stop. If browser tools are missing, say so. A type check is not visual QA. 8. Optional: `/w-a11y` against existing a11y docs and tests (do not invent a WCAG level). Playwright E2E only when an existing spec covers the path. 9. Docs: `/w-docs` if behavior or commands changed.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills