ui
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
Profile →npx skills add tw93/Waza --skill ui --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# UI: Build It With a Point of View Prefix your first line with 🥷 inline, not as its own paragraph. If it could have been generated by a default prompt, it is not good enough. ## Outcome Contract - Outcome: a usable interface or visual fix with a clear point of view and no incoherent layout, text, or responsive breakage. - Done when: the real rendered surface or generated artifact has been checked against the user's visual goal and the relevant viewport states. - Evidence: screenshots, rendered UI, source components, design tokens, accessibility constraints, and user-provided references. - Output: the implemented visual change or a precise visual review with the remaining verification gap named. **Output language rule:** Never use U+2014 em dash in any output from this skill. Use commas, colons, or periods instead. **Chinese gut-feel complaints**: when the user says "很傻", "很怪", "突兀", "不协调", "不和谐" about a visual, treat it as an aesthetic rejection, not a debugging symptom. Generated image assets stay in `references/mode-generated-asset.md` even when the complaint arrives with a screenshot; coded or rendered UI surfaces route to `references/mode-screenshot-iteration.md`, not to `/hu
- Outcome Contract
- Durable Context Preflight
- Mode Picker
- Lock the Direction First
- Source repo as reference
- Existing-native-app exception (do not propose wholesale platform restyling)
- App shell exception (sidebar + main workspace)
- Data dashboard exception
- When Asked For Options
- Hard Rules
- Gotchas
- Output: Aesthetic Review
What does the ui skill do?
Produces distinctive, production-grade UI for pages, components, visual interfaces, typography, and screenshot-driven polish. Use when users ask in any language for UI, page, component, frontend, typography, screenshot-grounded visual polish, or complaints that a screen looks unclear, ugly, inconsistent, or visually wrong. Not for backend logic or data pipelines.
How do I install it?
Run `npx skills add tw93/Waza --skill ui --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tw93/Waza, a repository with 6,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.