ui-ux
Skill1 starsChanged 5 months agoMITView on GitHub
UI/UX and product review for web interfaces — opinionated principles, checklist-driven audits, polish passes on screenshots, and pre-ship UI gates. Uses Playwright to navigate, screenshot, and smoke-test interactions when a URL is available. Triggers on "review my UI", "polish this", "UX audit", "fix the hero", "make it look professional", "ui pass", "design review", attaches screenshot with UI feedback. Use when building or reviewing interfaces and product flows, not generic code review.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- kv0906/cc-skillstheir own version, first seen Nov 8, 2026
- whoamnesia/astudio-aiotheir own version, first seen Nov 8, 2026
- turkeryildirim/ai-skillstheir own version, first seen Nov 1, 2026
- spizganed/skillstheir own version, first seen Oct 25, 2026
- prinx/agentstheir own version, first seen Oct 20, 2026
- psubramanian/Claude-Skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use deploy.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- kv0906/cc-skills★ 42same name
- prangishviliAbe/agent-skills★ 8same name
- turkeryildirim/ai-skills★ 4same name
- whoamnesia/astudio-aio★ 1same name
- asv-digital/skills-claude-code-na-pratica★ 0same name
- prinx/agents★ 0same name
- psubramanian/Claude-Skills★ 0same name
- Sean-Michael/skills★ 0same name
- spizganed/skills★ 0same name
- zoharp/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- architect-enterprise-aiSkill
- author-agent-skillsSkill
- build-agent-harnessesSkill
- build-aiewf-2024-ragSkill
- build-generative-mediaSkill
- build-multimodal-productsSkill
- build-rag-search-stacksSkill
- build-robotics-aiSkill
- build-with-deepmindSkill
- build-with-microsoft-aiSkill
- build-with-openaiSkill
- deploy-public-sector-aiSkill
- design-agent-skillsSkill
- evaluate-with-braintrustSkill
- lead-ai-engineering-teamsSkill
- lead-ai-transformationSkill
- learn-summit-2023-remoteSkill
- learn-summit-2023-talksSkill
- navigate-aie-europe-2026Skill
- navigate-aiewf-2024-keynotesSkill
- observe-ai-productionSkill
- operate-agent-memorySkill
- operate-legal-ai-agentsSkill
- operate-openclaw-agentsSkill
- optimize-llm-inferenceSkill
- plan-sovereign-aiSkill
- price-ai-productsSkill
- run-aiewf-2024-evalsSkill
- run-llm-evalsSkill
- run-summit-2023-workshopsSkill
- secure-ai-agentsSkill
- ship-ai-as-pmSkill
- ship-aiewf-2024-agentsSkill
- train-llms-locallySkill
- architecture-reviewSkill
- chat-failure-auditSkill
- create-a-skillSkill
- cross-model-reviewSkill
- cto-weekly-reviewSkill
- friction-auditSkill
- ig-carouselSkill
- pdf-reportSkill
- raise-prSkill
- reel-editSkill
- research-reportSkill
- ship-checkSkill
- spec-grounded-designSkill
- state-lifetime-decisionSkill
- ste100Skill
- scroll-engineeringSkill
- verify-like-a-userSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 10 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Read the target file(s) or explore the route
- Distinctive: line 49
If screenshot provided — treat it as source of truth for what's wrong visually
- Distinctive: line 55
Read playwright.md. Always run when a URL is reachable (unless review-only on code with no running app).
- Distinctive: line 58
Use Playwright MCP when available.
- Distinctive: line 65
If Playwright cannot run, note why in the report and rely on code review + user screenshots — do not skip silently.
- Distinctive: line 72
Run review-checklist.md against scope and Playwright results.
- Distinctive: line 85
Do not suggest gradients, glow, purple accents, or animation unless user asked.
- Distinctive: line 91
When building or polishing:
- Distinctive: line 95
After edits, state what changed in plain language
- Distinctive: line 99
Re-run Playwright (Step 1b): after implementing — capture after screenshots and confirm failed interaction checks now pass.
- Very specific: line 112
When the audit produced Playwright screenshots (most audit/polish passes do), also emit an HTML version from report-template.html — it …
- Very specific: line 120
Use the .grid2 before/after pattern for any fix you re-screenshotted.
- Very specific: line 123
Keep both in sync — the HTML is the shareable artifact, the .md is the record.
- Very specific: line 125
Update {output_dir}/index.md (link both formats):
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI/UX — Product-Aware Interface Review
Opinionated UI/UX + product review for web apps. Thinks about jobs-to-be-done before pixels. Works with any coding agent.
Supporting files:
- principles.md — product + UI/UX rules (read every time)
- review-checklist.md — structured audit
- playwright.md — browser verification with Playwright
- report-template.md — saved review output (the record)
- report-template.html — shareable HTML report with embedded screenshots
Output: {SKILL_OUTPUT_DIR}/ui-ux/ — see ../OUTPUT.md
Step 0 — Determine Mode
| Mode | When | Output |
| audit | "review my UI", file path given, pre-merge | Findings list + report file |
| polish-pass | screenshot attached, "fix the hero", iterative tweaks | Minimal code diff + short rationale |
| pre-ship | before commit on UI-heavy change | Audit + pair with @ship-check if shipping |
Ask if unclear:
- Scope — file, route, or component?
- Viewport — mobile / desktop / both?
- URL — local dev URL + route (e.g.
http://localhost:3000/dashboard) - Build or review only? — "don't code, plan only" → review only
Step 1 — Load Context
- Read principles.md
- Read the target file(s) or explore the route
- Note existing design system — reuse project components, tokens, patterns
- If screenshot provided — treat it as source of truth for what's wrong visually
Step 1b — Playwright Verification
Read playwright.md. Always run when a URL is reachable (unless review-only on code with no running app).
Use Playwright MCP when available; fallback to project Playwright tests or CLI.
Capture before screenshots + snapshot + console errors. Run interaction smoke checks for the scoped screen (scroll, input, menus, forms, CTAs).
Save artifacts under {output_dir}/screenshots/.
If Playwright cannot run, note why in the report and rely on code review + user screenshots — do not skip silently.
Step 2 — Review
Run review-checklist.md against scope and Playwright results.
For each finding:
- Severity: Critical / Important / Suggestion
- Location:
file:linewhen reviewing code - Issue: one sentence
- Fix: concrete — class change, component swap, copy rewrite, layout adjustment
Prioritize:
- Trust breakers (broken scroll, lost input, silent failures)
- Clarity (hierarchy, next action, copy)
- Polish (spacing, motion, micro-interactions)
Do not suggest gradients, glow, purple accents, or animation unless user asked.
Step 3 — Implement (unless review-only)
When building or polishing:
- Minimal diff — fix what's broken, don't redesign the whole page
- Match existing code style and component library
- One primary change per iteration when user is in screenshot-driven loop
- After edits, state what changed in plain language
Stack defaults from principles: Tailwind, cn(), accessible primitives, h-dvh, motion/react only when needed.
Re-run Playwright (Step 1b) after implementing — capture after screenshots and confirm failed interaction checks now pass.
Step 4 — Write Report (audit / pre-ship modes)
Fill report-template.md — the canonical record.
Path: {output_dir}/review-YYYY-MM-DD-[slug].md
Also generate a shareable HTML report when you have screenshots
When the audit produced Playwright screenshots (most audit/polish passes do), also emit an HTML version from report-template.html — it embeds the screenshots inline (incl. before/after pairs) so the user can read the whole review without opening files one by one.
- Copy
report-template.html→{output_dir}/review-YYYY-MM-DD-[slug].html - Replace every
[[PLACEHOLDER]]; reference screenshots with the relative pathscreenshots/<file>.pngso the report stays portable. - Use the
.grid2before/after pattern for any fix you re-screenshotted. - Open it for the user:
open {output_dir}/review-...html(macOS).
Keep both in sync — the HTML is the shareable artifact, the .md is the record.
Update {output_dir}/index.md (link both formats):
# UI/UX Reviews
| Date | Scope | Verdict | Report |
|------|-------|---------|--------|
| YYYY-MM-DD | [scope] | [verdict] | [md](review-...md) · [html](review-...html) |Step 5 — Output to User
- Verdict: Ship / Ship with fixes / Needs rework
- Top 3 issues (most impact first)
- Report path (if saved)
- Offer to implement fixes — or done if already implemented
For polish-pass: before/after summary in 2–3 bullets, no long essay.
Pair with other skills
@ship-check— run after UI changes before commit@architecture-review— when UX change implies a product/architecture fork (e.g. new nav paradigm)
Edge Cases
- User says "don't code" — audit + plan only
- Conflicting project patterns — follow project, flag deviation from principles as Suggestion
- Backend-only request — decline politely; this skill is UI/UX scoped
- No running dev server — offer to start it, or audit code-only with note
- Playwright MCP unavailable — use
npx playwright testor document skip reason - Whole app redesign — ask for priority screen; do not boil the ocean in one pass
Invocation Examples
@ui-ux review the onboarding flow
@ui-ux audit http://localhost:3000/dashboard — desktop and mobile
polish the hero — dev server on :3000
ui pass before we ship
don't code — give me a plan for the dashboard layoutDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

