Skip to main content
skill CX Codex

generic-ux-designer — Claude Code skill: what it does, how to install

generic-ux-designer — a UX skill for Claude and other coding agents: design-thinking steps, heuristic review and accessibility checks, packaged as checklists the agent follows.

MIT 145 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill generic-ux-designer -a claude-code
Open on GitHub

What generic-ux-designer does

The skill hands the agent a UX frame to work from. Five design-thinking stages, a table for picking a research method per situation, rules on cognitive load and visual hierarchy, then patterns for navigation, forms and feedback. It is one SKILL.md built from tables and checklists.

Reviews get their own tooling: a five-minute heuristic scan across visibility, feedback, consistency, error prevention and recovery, plus a list of violations worth flagging. Findings come out in a fixed shape: the issue, the heuristic it breaks, the user impact, a fix and a priority. Mobile guidance is concrete, with touch targets from 44x44px and 8px of space between them.

Styling and tokens are somebody else's job. The skill sends you to generic-design-system for those and to generic-feature-developer for code architecture, and it wants ui-research loaded first when the work is visual. Several sections lean on companion files such as _shared/UX_PRINCIPLES.md and DESIGN_PATTERNS.md.

What it helps with

  • review a checkout flow before the feature ships
  • pick a research method for a new feature
  • run a quick heuristic pass over an existing screen
  • check touch target sizes and accessibility on mobile
  • write up design-review findings with priorities

Example prompts for the agent

  • Run a heuristic review of the signup screen and give me findings as issue, heuristic, impact, suggestion, priority.
  • Design an onboarding flow: define the problem and success metrics first, then sketch a low-fidelity prototype.
  • Is research worth it here or should we just ship? Walk me through the confidence levels.

How to install generic-ux-designer

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill generic-ux-designer -a claude-code

2Manually: put the files in place

~/.claude/skills/generic-ux-designer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/generic-ux-designer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about generic-ux-designer

How do I install generic-ux-designer in Claude Code?

Run npx skills add travisjneuman/.claude --skill generic-ux-designer -a claude-code. The skill lands at ~/.claude/skills/generic-ux-designer/SKILL.md.

What does generic-ux-designer do?

It gives the agent a UX method: design thinking, research method selection, interaction patterns, accessibility and a critique format. Useful when shaping a new feature or auditing a flow that already exists.

Does it handle visual styling and design tokens?

No. It points to generic-design-system for tokens and visual consistency, and stays focused on how the interface behaves.

Source text

SKILL.md · MIT
---
name: generic-ux-designer
description: Professional UX expertise for any project type. Covers user research, design thinking, interaction patterns, accessibility, and design critique. Use when designing new features, improving UX, conducting design reviews, or evaluating user flows. For visual UI work, combine with ui-research skill.
---

# Generic UX Designer

Professional UX expertise adapting to any project's constraints.

## Combine with Research for Visual Work

For UI/visual design decisions, also use:

```
Skill(ui-research)  # Research inspiration first
```

**References:**

- [UX Principles](../_shared/UX_PRINCIPLES.md) - UX methodology
- [UI Inspiration Sources](../_shared/UI_INSPIRATION_SOURCES.md) - Visual research

## When to Use This Skill

**Use for:**

- Designing new features or flows
- Improving existing user experience
- Conducting design reviews/critiques
- Evaluating user flows and interactions
- Making accessibility decisions
- Choosing between design alternatives

**Don't use when:**

- Visual styling/tokens → use `generic-design-system`
- Code architecture → use `generic-feature-developer`
- Code quality review → use `generic-code-reviewer`

## Design Thinking Process

1. **Empathize** - Understand user needs, pain points, journeys
2. **Define** - Problem statements, personas, success metrics
3. **Ideate** - Brainstorm solutions, explore alternatives
4. **Prototype** - Low-fidelity first, test assumptions
5. **Test** - Usability testing, iterate on data

## Research Decision Guide

### When to Research vs Ship

| Situation            | Action                               |
| -------------------- | ------------------------------------ |
| New product/feature  | Full research (interviews + testing) |
| Incremental change   | Quick critique (heuristic review)    |
| Bug fix              | No research needed                   |
| A/B decision         | Analytics + small test               |
| Controversial design | Stakeholder alignment first          |

### Method Selection

- Need user motivation? → Interviews
- Need usability feedback? → Testing
- Need quick quality check? → Heuristic evaluation
- Need quantitative data? → Surveys/Analytics
- Have no users yet? → Competitor analysis + proto-personas

### Research Scope by Confidence

| Confidence Level           | Action         |
| -------------------------- | -------------- |
| High (established pattern) | Skip research  |
| Medium (some uncertainty)  | Quick critique |
| Low (new territory)        | Full research  |

**Reference:** See UX_PRINCIPLES.md for detailed method frameworks

## User Psychology Applied

### Cognitive Load

- Reduce choices (Hick's Law)
- Chunk information (Miller's Law)
- Progressive disclosure
- Minimize memory load

### Visual Hierarchy

- Size indicates importance
- Contrast draws attention
- Whitespace groups elements
- F-pattern/Z-pattern reading

## Interaction Patterns

### Navigation

| Pattern    | Use Case                    |
| ---------- | --------------------------- |
| Top nav    | Simple sites, < 7 items     |
| Side nav   | Complex apps, many sections |
| Bottom nav | Mobile apps, < 5 items      |
| Tabs       | Related content sections    |

### Forms

- Single column layout
- Inline validation
- Smart defaults
- Progress indicators

### Feedback

| Pattern  | Use Case            |
| -------- | ------------------- |
| Toast    | Non-blocking info   |
| Modal    | Blocking/important  |
| Inline   | Contextual feedback |
| Skeleton | Loading states      |

## Mobile Considerations

- Touch targets: 44x44px minimum
- 8px spacing between targets
- Thumb-friendly placement
- Bottom sheets for actions

## Accessibility (UX Perspective)

| Aspect    | Approach                         |
| --------- | -------------------------------- |
| Vision    | High contrast, scalable text     |
| Motor     | Large targets, keyboard nav      |
| Cognitive | Simple language, clear structure |
| Hearing   | Captions, visual indicators      |

## Heuristic Evaluation in Practice

### Quick Scan (5 minutes)

| Heuristic        | Quick Check                          |
| ---------------- | ------------------------------------ |
| Visibility       | Is current state obvious?            |
| Feedback         | Does every action have response?     |
| Consistency      | Do similar things look/work similar? |
| Error Prevention | Can user easily make mistakes?       |
| Recovery         | Can user undo/fix errors?            |

### Common Violations to Flag

- Hidden system state (loading with no indicator)
- Silent failures (action with no feedback)
- Inconsistent patterns (different buttons for same action)
- Destructive without confirm (delete with no undo)
- Jargon in user-facing text

### Presenting Findings

```
Issue: [What's wrong]
Heuristic: [Which violated]
Impact: [User consequence]
Suggestion: [How to fix]
Priority: P0/P1/P2
```

## Design Critique Framework

| Aspect        | Questions                     |
| ------------- | ----------------------------- |
| Usability     | Can users complete tasks?     |
| Clarity       | Is purpose immediately clear? |
| Consistency   | Follows established patterns? |
| Hierarchy     | Most important stands out?    |
| Feedback      | Users know system state?      |
| Accessibility | Works for everyone?           |

## UX Patterns

### Empty States

1. Explain what goes here
2. Guide to first action
3. Show example content

### Loading States

1. Skeleton screens > spinners
2. Progress for long operations
3. Optimistic UI when safe

### Error States

1. Explain what happened
2. Suggest how to fix
3. Don't blame user

## UX Output Checklist

Before presenting UX recommendation:

- [ ] User problem clearly defined
- [ ] Solution addresses root cause (not symptom)
- [ ] Accessibility considered
- [ ] Edge cases identified
- [ ] Implementation complexity noted
- [ ] Success metrics defined

## Design Review Checklist

- [ ] Primary task achievable
- [ ] Clear visual hierarchy
- [ ] Keyboard navigable
- [ ] Touch targets sized
- [ ] Copy clear and helpful

## See Also

- [UX Principles](./../_shared/UX_PRINCIPLES.md) - Research methods, heuristics, psychology
- [Design Patterns](./../_shared/DESIGN_PATTERNS.md) - Visual patterns and components
- `generic-design-system` - For tokens, styling, visual consistency
- `generic-feature-developer` - For implementation architecture
- Project `CLAUDE.md` - Project-specific constraints

**READ UX_PRINCIPLES.md for:**

- Full research method frameworks → methods section
- Complete Nielsen heuristics → evaluation section
- Quick critique workflow → critique section

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Design →

From the same set117

The whole set →
codebase-documenter codebase-documenter turns a repository into readable docs: README, architecture overview, onboarding guide, API reference and code comments. Handy when someone new has to understand the project. CX Codex +1 145installs impact-report-writer The impact-report-writer skill helps structure program impact reports, choose outcome metrics, and plan data visualizations. Use it for annual reports or program evaluations. CX Codex +1 145installs frontend-enhancer frontend-enhancer polishes the visual side of a web app: palette, layout, motion, component states. Useful when the UI still reads as a stock starter. CX Codex +1 145installs status-report-generator The status-report-generator Claude Code skill builds project status reports from Git activity, task context, and milestone tracking. It can create weekly updates, sprint reviews, and stakeholder reports. CX Codex +1 145installs performance-engineering performance-engineering — a skill for Claude Code designed for full-stack web application performance optimization. Activates when Core Web Vitals drop, bundle sizes increase, or page response times degrade. CX Codex +1 144installs authentication-patterns authentication-patterns — a Claude Code skill for authentication and authorization patterns. It comes into play when building login flows, MFA, SSO, or access-control models. CX Codex +1 144installs i18n-localization The i18n-localization Claude Code skill guides internationalization and localization work. It activates for translation setup, locale-specific formatting, and adapting an app for multiple regions. CX Codex +1 143installs vue-development vue-development — a Claude Code skill for building Vue 3 applications with the Composition API and Script Setup. Guides state setup in Pinia, custom composables, and Nuxt 3 full-stack tasks. CX Codex +1 143installs

Project sponsors

Companies that keep this analytics open