agentleFS
Sign inStart free
Data-WiseData-Wise/craft/skills/design/frontend-designer/SKILL.md

frontend-designer

Skill4 starsChanged 13 days agoMITView on GitHub

This skill should be used when the user asks to "design a UI", "plan component architecture", "improve accessibility", "optimize frontend performance", or discusses UI/UX patterns. Provides pragmatic frontend design guidance with ADHD-friendly patterns.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use wizards for multi-step processes

    line 66
  2. Distinctive:

    Start with Tailwind/Bootstrap, customize later

    line 74
  3. Distinctive:

    Use proven component libraries (shadcn/ui, Headless UI)

    line 75
  4. Distinctive:

    When analysis is needed, I will:

    line 88
  5. Distinctive:

    Delegate to agents: when feasible:

    line 91
  6. Very specific:

    Run in background: - Use Task tool with run_in_background: true

    line 95
  7. Distinctive:

    When activated, I provide:

    line 114

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

Frontend Designer Skill

Auto-activated when: User discusses UI/UX, component architecture, accessibility, or frontend design decisions.

Core Capabilities

1. Component Architecture

  • Component composition patterns
  • Props vs state decisions
  • Component reusability strategies
  • Folder structure (colocation vs separation)
  • Design system integration

2. UI/UX Patterns

  • Layout patterns (grid, flexbox, responsive)
  • Navigation patterns (tabs, drawer, breadcrumbs)
  • Form design (validation, error handling, multi-step)
  • Loading states and skeletons
  • Empty states and error boundaries

3. Accessibility (A11y)

  • WCAG compliance checklist
  • Semantic HTML
  • ARIA labels and roles
  • Keyboard navigation
  • Screen reader compatibility
  • Color contrast (ADHD-friendly palettes)

4. Performance

  • Code splitting strategies
  • Lazy loading images/components
  • Virtual scrolling for long lists
  • Debouncing/throttling user input
  • Bundle size optimization

ADHD-Friendly Design Patterns

Visual Hierarchy:

  • Clear focus states (bold borders, high contrast)
  • Reduce visual clutter (progressive disclosure)
  • Consistent spacing (8px grid system)
  • Limited color palette (3-5 colors max)

Interaction Design:

  • Immediate feedback (loading spinners, success states)
  • Undo/redo capabilities
  • Auto-save (reduce "did I save?" anxiety)
  • Confirmation dialogs for destructive actions
  • Keyboard shortcuts for common actions

Cognitive Load Reduction:

  • One primary action per screen
  • Hide advanced options behind "Advanced" toggle
  • Use wizards for multi-step processes
  • Provide templates/presets
  • Clear error messages with next steps

Design Philosophy: Solid Indie

Ship Fast Principles:

  • Start with Tailwind/Bootstrap, customize later
  • Use proven component libraries (shadcn/ui, Headless UI)
  • Mobile-first responsive design
  • Accessibility from day one (easier than retrofitting)

Anti-Patterns to Avoid:

  • ❌ Custom design system before 10K users
  • ❌ Over-abstraction (generic <Button> with 20 props)
  • ❌ Premature animation (ship functionality first)
  • ❌ Pixel-perfect designs (80% is shipping)

Delegation Strategy

When analysis is needed, I will:

  1. Quick assessment - Identify design problem
  2. Delegate to agents when feasible:
    • ux-ui-designer agent for comprehensive UX review
    • experienced-engineer agent for component architecture
    • accessibility specialist for a11y audit
  3. Run in background - Use Task tool with run_in_background: true
  4. Synthesize results - Provide actionable design recommendations

Example Activation

User: "I need to design a form for creating tasks with due dates and tags"

Skill activates and provides:
1. Form layout recommendation (vertical, clear labels)
2. Accessibility checklist (ARIA labels, keyboard nav)
3. UX patterns (inline validation, auto-save, success feedback)
4. Component structure (controlled vs uncontrolled inputs)
5. Delegates UX review to ux-ui-designer agent (background)
6. Returns with comprehensive form implementation plan

Output Format

When activated, I provide:

Immediate Response

  • Pattern Recognition: Identify the UI/UX problem
  • Quick Recommendation: Suggest proven pattern
  • Accessibility Note: Key a11y considerations
  • ADHD-Friendly Tip: Cognitive load reduction suggestion

Delegated Analysis (Background)

  • Launch appropriate agent for UX/accessibility review
  • Provide progress updates
  • Synthesize findings

Final Output

  • Recommended approach with rationale
  • Component structure (props, state, composition)
  • Accessibility checklist (WCAG items to address)
  • Code example (React/Vue component structure)
  • Next steps (what to build first)

Integration with Existing Workflow

  • Auto-activates during /brainstorm for UI/UX discussions
  • Works with /next (suggests frontend implementation steps)
  • Integrates with /done (captures design decisions, patterns used)

Pattern Library Integration

Common patterns I'll reference:

PatternUse CaseExample
Progressive DisclosureComplex formsShow advanced fields behind toggle
Optimistic UICreate/update actionsShow success immediately, rollback on error
Skeleton ScreensLoading statesShow layout while data loads
Virtual ScrollingLong listsRender only visible items
Toast NotificationsNon-blocking feedbackSuccess/error messages that auto-dismiss

Remember: This skill auto-activates based on keywords. Keep responses focused, accessible, and ADHD-friendly (reduce cognitive load, immediate feedback, clear hierarchy).

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.

Check your setup, free