Comprehensive UI/UX and frontend design best practices guide. Contains 42 rules across 8 categories, prioritized by impact to guide accessible, performant, and user-friendly interface development.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionui-designExecute the skills CLI command in your project's root directory to begin installation:
Fetches ui-design from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ui-design. Access via /ui-design in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
95
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
95
stars
Comprehensive UI/UX and frontend design best practices guide. Contains 42 rules across 8 categories, prioritized by impact to guide accessible, performant, and user-friendly interface development.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Accessibility & WCAG Compliance | CRITICAL | access- |
| 2 | Core Web Vitals Optimization | CRITICAL | cwv- |
| 3 | Visual Hierarchy & Layout | HIGH | layout- |
| 4 | Responsive & Mobile-First Design | HIGH | resp- |
| 5 | Typography & Font Loading | MEDIUM-HIGH | typo- |
| 6 | Color & Contrast | MEDIUM | color- |
| 7 | Forms & Validation UX | MEDIUM | form- |
| 8 | Animation & Performance | LOW-MEDIUM | anim- |
access-semantic-html - Use semantic HTML elements for screen readersaccess-keyboard-navigation - Ensure full keyboard navigationaccess-focus-indicators - Provide visible focus indicatorsaccess-alt-text - Provide meaningful alt text for imagesaccess-aria-labels - Use ARIA labels for icon-only controlsaccess-target-size - Ensure minimum touch target size (24×24px)access-heading-hierarchy - Maintain logical heading hierarchycwv-optimize-lcp - Optimize Largest Contentful Paint under 2.5scwv-minimize-cls - Minimize Cumulative Layout Shift under 0.1cwv-improve-inp - Improve Interaction to Next Paint under 200mscwv-responsive-images - Serve responsive images with srcsetcwv-lazy-load-offscreen - Lazy load offscreen images and iframescwv-critical-css - Inline critical CSS and defer the restlayout-visual-hierarchy - Establish clear visual hierarchylayout-whitespace - Use whitespace to improve readabilitylayout-f-pattern - Design for F-pattern reading behaviorlayout-grid-system - Use a consistent grid systemlayout-single-cta - Limit to one primary CTA per screenlayout-proximity-grouping - Group related elements with proximityresp-mobile-first - Design mobile-first with min-width queriesresp-fluid-typography - Use fluid typography with clamp()resp-container-queries - Use container queries for componentsresp-touch-targets - Size touch targets for mobile (44×44px)resp-viewport-meta - Configure viewport meta tag correctlytypo-font-display - Use font-display to control loading behaviortypo-preload-fonts - Preload critical web fontstypo-readable-line-length - Constrain line length (45-75ch)typo-line-height - Set appropriate line height (1.5-1.7)typo-system-font-stack - Use system font stack for UI elementscolor-contrast-ratio - Meet WCAG contrast ratio requirements (4.5:1)color-not-only-indicator - Never use color alone to convey informationcolor-dark-mode - Support dark mode with prefers-color-schemecolor-semantic-palette - Use semantic color names in design tokensform-inline-validation - Use inline validation after field blurform-error-messages - Write actionable error messagesform-labels-above - Place labels above input fieldsform-input-types - Use correct HTML input types for mobileform-autocomplete - Enable browser autocomplete with correct attributesanim-gpu-properties - Animate only GPU-accelerated propertiesanim-will-change - Use will-change sparingly for animation hintsanim-reduced-motion - Respect user motion preferencesanim-duration-easing - Use appropriate animation duration and easingRead individual reference files for detailed explanations and code examples:
For the complete guide with all rules expanded: AGENTS.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pproenca/dot-skills
pproenca/dot-skills
anthropics/claude-code
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
ui-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend ui-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in ui-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
ui-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in ui-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: ui-design is focused, and the summary matches what you get after install.
ui-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: ui-design is focused, and the summary matches what you get after install.
I recommend ui-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
ui-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 40