review-design
Skill234 starsChanged 3 months agoMITView on GitHub
Reviews frontend components for design quality and UI/UX standards. Use when checking component styling, responsiveness, accessibility, or when asked to review a design.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- pauljasperdev/skillstheir own version, first seen Nov 16, 2026
- CsHeng/agent-skillstheir own version, first seen Nov 9, 2026
- dorian-akhs/skillstheir own version, first seen Nov 8, 2026
- alo-exp/silver-bullettheir own version, first seen Nov 1, 2026
- timholy/claude_configtheir own version, first seen Oct 20, 2026
- WhorideChicken/first-playabletheir own version, first seen Oct 11, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- timholy/claude_config★ 75same name
- gtrabanco/agentic-workflow★ 23same name
- mgiovani/cc-arsenal★ 8same name
- alo-exp/silver-bullet★ 7same name
- CsHeng/agent-skills★ 3same name
- WhorideChicken/first-playable★ 3same name
- dirkkok101/skills★ 2same name
- herohua/skills★ 1same name
- dorian-akhs/skills★ 0same name
- Jagoda11/the-jagoda-toolkit★ 0same name
1 more not listed
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 repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-options-classSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- init-verifySkill
- manage-file-storageSkill
- new-endpointSkill
- new-entitySkill
- new-featureSkill
- new-pageSkill
- polish-uiSkill
- review-dependabotSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Resolve scope: If argument provided, find matching .svelte files.
- Very specific: line 21
If screenshots for this change exist under docs/sessions/assets/, Read them too and judge the rendered result, not just the classes
- Distinctive: line 24
Cross-reference related components: - check siblings in the same feature folder for consistency
- Distinctive: line 86
Check for patterns that break across the three main browser engines:
- Distinctive: line 141
Read the full component source, not just snippets - context matters
- Distinctive: line 143
Check the actual rendered context (parent layout) to understand spacing/sizing in practice
“Common” is measured: kept by at least 6 in 10 of the 10 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
Reviews frontend components for design quality, UI/UX best practices, and project standards.
Argument: file path, component name, or glob pattern. If omitted, reviews all files changed on the current branch vs the repo default branch.
References
- Design tokens and standards - colors, spacing, breakpoints, touch targets
Steps
- Resolve scope: If argument provided, find matching
.sveltefiles. If omitted, get changed files viagit diff $(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/master) --name-only -- '*.svelte' - Read every file in scope in full - understand the complete component, not just fragments
- If screenshots for this change exist under
docs/sessions/assets/, Read them too and judge the rendered result, not just the classes
- If screenshots for this change exist under
- Read the design tokens reference for project standards
- Check the parent layout/page that renders each component - understand the context it lives in
- Cross-reference related components - check siblings in the same feature folder for consistency
Design Checklist
Responsive Design
- Mobile-first: base styles target 320px, then
sm:/md:/lg:/xl:breakpoints - No hardcoded widths that break on small screens (except
max-w-*constraints) - Padding scales with breakpoints (
p-4 sm:p-6 lg:p-8) - flat large padding wastes mobile space - Content grids use
lg:grid-cols-2(notxl:) sincemax-w-7xlensures sufficient width - Dialog grids start with
grid-cols-1base before responsive breakpoints - Full-height layouts use
h-dvhnoth-screen - Flex children with text have
min-w-0, icons/badges haveshrink-0 - Text doesn't overflow containers - check long names, emails, URLs with
truncateorbreak-all
Touch & Interaction
- All interactive elements meet 44px minimum touch target (
min-h-11orh-11) - Buttons use default size with
w-full sm:w-autopattern - Button wrapper uses
flex flex-col gap-2 sm:flex-row sm:justify-end - No
size="sm"orsize="lg"on action/submit buttons - Action buttons are right-aligned (not left-aligned or centered)
- Clickable text elements (links styled as text) still meet touch target minimums
- Disabled states are visually distinct and non-interactive
Logical CSS (RTL Support)
- No physical margin/padding:
ms-*/me-*/ps-*/pe-*instead ofml-*/mr-*/pl-*/pr-* - No physical positioning:
start-*/end-*instead ofleft-*/right-* - No
text-left/text-right- usetext-start/text-end - No
border-l/border-r- useborder-s/border-e - No
space-x-*- usegap-*
Theming & Colors
- All colors use semantic design tokens (
bg-background,text-muted-foreground,border-destructive) - No hardcoded colors (
text-gray-500,bg-white,#fff,rgb(...)) - UI works in both light and dark mode - check contrast, borders, shadows
- Muted backgrounds use
/40or similar opacity variants, not solid colors that clash
Typography & Spacing
- Minimum font size is
text-xs(12px) - nothing smaller - Consistent spacing within the component and with sibling components
- Headings use consistent sizing per hierarchy level across the app
- No orphaned labels or empty states without user guidance
Dialogs & Modals
- No scrollbars in dialogs - content fits the viewport
- No
overflow-y-autoon dialog containers - Compact spacing and responsive sizing to avoid scroll
- Width constraint:
max-w-[calc(100%-2rem)]mobile,sm:max-w-lgdesktop (or similar)
Safe Area & Viewport
- Fixed/sticky elements account for
env(safe-area-inset-*)where relevant - Bottom-fixed elements use
pb-[max(...,env(safe-area-inset-bottom,0px))]pattern - Animations use
motion-safe:prefix
Cross-Browser Compatibility
Check for patterns that break across the three main browser engines:
WebKit (Safari / iOS Safari)
- No
-webkit-prefixed properties without standard fallback dvh/svhunits used instead ofvhfor full-height layouts (iOS URL bar)gapon flex containers (supported since Safari 14.1 - verify no older target)- No
backdrop-filterwithout-webkit-backdrop-filterfallback if used overscroll-behaviorpresent on scroll containers (Safari 16+)- Date/time inputs work (Safari has limited
<input type="date">styling)
Blink (Chrome / Edge / Opera)
- No reliance on Chrome-only CSS (
:has()is fine - supported everywhere now) - Scrollbar styling uses both
::-webkit-scrollbarandscrollbar-width/scrollbar-colorif customized
Gecko (Firefox)
text-overflow: ellipsisworks (Firefox requiresoverflow: hidden+white-space: nowrapexplicitly)- CSS
@propertyusage has fallbacks (limited Firefox support before v128) - No
-moz-prefixed properties without standard fallback - Nested CSS
@layerrules work (Firefox 97+)
General
- No CSS features below the project's browser target without fallbacks
env(safe-area-inset-*)uses fallback values:env(safe-area-inset-top, 0px)notenv(safe-area-inset-top)- Font stacks include fallbacks for system fonts across OS (Apple, Windows, Linux)
prefers-color-schemeandprefers-reduced-motionmedia queries used correctly
Consistency
- Patterns match existing components in the same feature folder
- Card layouts, form structures, error handling, and button placement match the rest of the app
- Loading states follow existing patterns (spinner icon with
animate-spin) - Error display follows existing patterns (
getErrorMessage+ toast or inlineAlert) - Empty states are handled with user-friendly messaging
Accessibility
- Interactive elements have visible focus styles (inherited from shadcn unless custom)
- Icon-only buttons have
aria-labelorsr-onlytext - Form inputs have associated labels
- Color is not the only indicator of state (add icons or text alongside color changes)
- Semantic HTML:
<nav>,<main>,<header>,<section>used appropriately
Output Format
Report findings per component as:
- PASS - what meets standards (brief)
- FAIL - violations that must be fixed (with file path, line number, and fix)
- WARN - suggestions for improvement (not blockers)
End with a summary: total components reviewed, FAIL count, WARN count, and overall verdict.
Rules
- Research only - do NOT modify any files
- Read the full component source, not just snippets - context matters
- Compare against sibling components for consistency violations
- Check the actual rendered context (parent layout) to understand spacing/sizing in practice
- Be strict on logical CSS, touch targets, and theme tokens - these are hard rules
- Be practical on spacing/sizing - flag only clear violations, not subjective preferences
Does 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.

