UI review and polish skill.
Turns Claude Code, Codex, Cursor or any other AI coding agent into a careful UI reviewer: it scans the code, looks at the rendered page and hands you a ranked list of fixes.
Small details decide whether an interface feels finished. This skill gives your agent a repeatable last check: a bundled scanner reads your JSX, HTML and CSS for known defects and AI giveaways, then the agent opens the page on phone, tablet and desktop sizes in dark and light, ranks every finding from broken to refinement, and either reports the list or fixes the top ranks.
- Skill
wensity-polish- Plan
- Included with Wensity Pro
- Loads when
- Asking to polish, review, audit or QA a page, component or app
- Works in
- Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Gemini CLI, OpenCode
- Format
- Agent Skills (SKILL.md), plain files in your project
- Pack
- One of the Wensity design skills for AI coding agents
Install
1. Sign in once. The CLI asks for an API token from your dashboard and saves it, so you never paste it into a chat.
pnpm dlx wensity@latest login
npx wensity@latest login
yarn dlx wensity@latest login
bunx wensity@latest login
2. Add the skill. It goes into every agent the CLI finds in your project.
pnpm dlx wensity@latest skills add wensity-polish
npx wensity@latest skills add wensity-polish
yarn dlx wensity@latest skills add wensity-polish
bunx wensity@latest skills add wensity-polish
UI review and polish comes with Wensity Pro, together with every Pro skill, component, block and template.
Get ProWhen it loads
You never call a skill by name. Your agent reads the short description at the top of every installed skill and loads this one when the work calls for it. Requests like these bring it in:
- Do a polish review of the components in src/ and tell me what to fix.
- This page feels off. Polish it before I ship.
- Audit the UI of the settings page for accessibility and states.
What it covers
- Scope and mode
- Reviews only what you named or what changed, and either reports or fixes depending on what you asked.
- The scanner
- Finds eyebrow labels, gradient text, glows, hover lifts, missing focus styles, unlabeled images, tiny inputs and more, with file and line.
- The rendered look
- Phone, tablet and desktop widths, both themes, keyboard paths, slow loads, reduced motion and 200% text.
- Twelve categories
- Hierarchy, layout, type, color, surfaces, motion, states, responsive, accessibility, copy, generic tells and craft details.
- Ranked findings
- Broken, visibly off and refinement, merged so twelve buttons with no focus ring are one finding.
- The fix pass
- Top ranks fixed directly, larger changes asked about first.
Fix it live
Pick a component and watch the review come in, worst problems first. Press a finding to apply its fix in the preview.
Sign in to Ledgerly
Don't have an account?
Tick a finding to apply its fix in the preview.
With the skill: Every finding says what is wrong, where and exactly what to change, grouped from broken to refinement, so each one can be applied.
Key rules
- Patterns, not verdicts
- Every scanner hit is opened and confirmed before anything changes.
- Look at it
- Code review misses most visual problems, so the page is rendered whenever possible.
- Respect decisions
- A rule in your DESIGN.md beats a rule in the skill.
- Review means review
- Asked for a review, the agent reports and changes nothing until you pick.
- One finding per problem
- Duplicates are merged and the list is ordered by rank, then by how visible it is.
- Say what was not checked
- If the page could not be rendered, the report says so.
Sweep one category at a time
A team billing screen, reviewed category by category. Pick one to outline what it caught and read why it matters.
0 of 10 fixed
Billing
Team billing
Oops! Something went wrong.
Team plan
8 of 10 seats used
$96 a month
Renews on the 1st of each month
HierarchyCaught
Two filled buttons in the header, so nothing says which one matters.
Keep Upgrade plan filled and make Download invoices a quiet secondary.
Files
Everything installs as plain files in your project, in a folder named after the skill.
SKILL.md- Scope, the review steps, ranking and the report format.
scripts/scan.mjs- A read-only scanner for common UI defects. Exits with an error on high findings.
references/checklist.md- The full checklist by category.
Works well with
Design director
ProThe core workflow: read, plan, review against generic UI, build and critique. Routes to every other skill.
Accessibility and UI states
ProEvery interaction and data state, plus keyboard, touch, zoom, forced colors and screen readers.
Color and dark mode
ProOKLCH role tokens, true neutral greys, one accent, both themes, and a script that checks contrast and gamut.