agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/ui-ux-design/SKILL.md

ui-ux-design

Skill2 starsChanged 6 months agoMITView on GitHub

UI/UX design systems, Figma workflows, accessibility checklists, browser-based visual audit with automated screenshots, component specification patterns, and design-to-code handoff procedures. Use when designing interfaces, creating design systems, auditing accessibility, reviewing existing UI via browser screenshots, specifying components, or preparing design handoff for developers.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prd-generator and security-review.

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.
  • dhzrxSkill

    prd-generator

    Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating a design system:

    line 35
  2. Distinctive:

    Inconsistency map: Document where the same concept is implemented differently

    line 39
  3. Distinctive:

    Follow Atomic Design progression:

    line 58
  4. Distinctive:

    States: Default, hover, focus, active, disabled, loading, error

    line 67
  5. Distinctive:

    When handing off designs to developers, provide:

    line 109

“Common” is measured: kept by at least 6 in 10 of the 18 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI/UX Design

Systematic UI/UX design skill with design system creation guides, Figma workflow patterns, accessibility audit checklists, browser-based visual audit procedures, and design-to-code handoff templates. Produces consistent, accessible, conversion-optimized interfaces.

When to Use

  • Creating or extending a design system (tokens, components, patterns)
  • Designing new pages, features, or user flows
  • Auditing existing UI for accessibility compliance
  • Preparing design specifications for developer handoff
  • Setting up Figma project structure and workflows
  • Reviewing existing UI via automated browser screenshots and heuristic analysis
  • Reviewing UI components against heuristics and platform guidelines

When NOT to Use

  • Writing page content or copy (use content-creation skill)
  • Implementing frontend code (use frontend-engineer role)
  • Conducting SEO audits (use seo-review skill workflow)
  • Writing technical documentation (use docs skill workflow)

Design System Creation

Step 1: Audit Existing UI

Before creating a design system:

  1. Screenshot inventory: Capture all existing screens and components
  2. Pattern extraction: Identify recurring colors, typography, spacing, components
  3. Inconsistency map: Document where the same concept is implemented differently
  4. Priority matrix: Rank components by frequency of use × inconsistency severity

Step 2: Define Foundations

Build from the ground up:

FoundationWhat to DefineToken Naming
ColorBrand, semantic, neutral, overlay palettescolor-{category}-{shade}
TypographyFont families, size scale, weights, line heightsfont-{property}-{size}
SpacingBase unit (4px or 8px), scalespacing-{size}
Border radiusScale from none to fullradius-{size}
ElevationShadow levelsshadow-{level}
MotionDuration, easing curvesmotion-{property}-{variant}
BreakpointsViewport thresholdsbreakpoint-{name}

Step 3: Build Components

Follow Atomic Design progression:

  1. Atoms: Button, Input, Label, Icon, Badge, Avatar, Checkbox, Radio, Toggle
  2. Molecules: Input Group, Search Bar, Card, Dropdown, Tooltip, Alert, Breadcrumb
  3. Organisms: Header, Footer, Sidebar, Form, Data Table, Modal, Navigation

For each component, document:

  • Variants: Primary, secondary, outline, ghost, destructive
  • Sizes: xs, sm, md, lg, xl
  • States: Default, hover, focus, active, disabled, loading, error
  • Accessibility: ARIA role, keyboard behavior, screen reader announcement
  • Responsive: Behavior at each breakpoint
  • Do / Don't: Usage examples and anti-patterns

Step 4: Document and Maintain

  • Publish component library with live examples
  • Version with semantic versioning
  • Changelog for every update
  • Deprecation notices with migration guides

See design-system-checklist.md for the full creation checklist.

Figma Workflow

See figma-workflow.md for detailed Figma project setup, component organization, Auto Layout patterns, and developer handoff procedures.

Quick Reference

Figma ConceptCode Equivalent
Auto LayoutFlexbox / CSS Grid
Component variantsReact props / variant configs
Design tokens (Variables)CSS custom properties
ConstraintsCSS positioning / responsive rules
Component instancesReact component usage

Accessibility Audit

See accessibility-checklist.md for the comprehensive WCAG 2.2 AA audit checklist.

Quick Audit (5-Minute Check)

  1. Tab through the page — can you reach and operate every interactive element?
  2. Zoom to 200% — does content reflow without horizontal scrolling?
  3. Check contrast — do all text elements meet 4.5:1 (normal) / 3:1 (large)?
  4. Screen reader test — do headings, landmarks, and alt text make sense?
  5. Keyboard-only — can you complete the primary task without a mouse?

Design-to-Code Handoff Template

When handing off designs to developers, provide:

## Component: [Name]

### Visual Spec
- Dimensions: [width × height or fluid]
- Spacing: [padding, margin in token values]
- Colors: [background, text, border in token values]
- Typography: [font, size, weight, line-height in token values]
- Border: [width, style, color, radius in token values]
- Shadow: [elevation token]

### Variants
- [variant-name]: [visual differences]

### States
- Default: [spec]
- Hover: [changes from default]
- Focus: [focus indicator spec]
- Active: [changes]
- Disabled: [opacity, cursor, interaction]

### Responsive Behavior
- Mobile (< 640px): [layout changes]
- Tablet (640–1024px): [layout changes]
- Desktop (> 1024px): [default layout]

### Interactions
- [trigger] → [animation: property, duration, easing]

### Accessibility
- Role: [ARIA role if not implicit]
- Keyboard: [key bindings]
- Screen reader: [announcement text]

### Code Reference
- Component: `<ComponentName variant="..." size="..." />`
- Tokens: `--token-name: value`

Integration

  • Follows rules: ui-ux-designer role (design principles, accessibility, design systems)
  • Used by workflows: ui-ux-design skill (primary), feature-dev skill (UI features)
  • Companion resources: design-system-checklist.md, figma-workflow.md, accessibility-checklist.md, visual-audit-checklist.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.