Skip to main content
skill CX Codex

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

ux-designer is a Claude Code skill that guides AI agents from information architecture to developer handoff, with usability and accessibility checks.

MIT 148 installs ★ 29 updated 2026-08-17

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

What ux-designer does

Five phases carry the work: information architecture, user flows, wireframes, a clickable prototype with usability testing, then UI design and handoff. For each one SKILL.md lists the goal and the deliverables — sitemap and labeling taxonomy, flow diagrams with error and edge cases, lo-fi through hi-fi layouts.

Working principles sit alongside: consistency, feedback, error prevention, recognition over recall. Separate tables cover forms, navigation, empty states and loading states. A mistake table names the usual failures — placeholder text standing in for a label, one layout stretched across every breakpoint, no visible focus ring on keyboard tab order.

Four reference files come in references/: the design process, visual foundations, a WCAG 2.2 AA accessibility guide and a tool list. Research gets handed to the Task agent, accessibility audits to Explore, design-system architecture to Plan. Backend work with no UI, database schemas and DevOps configuration fall outside its scope, so expect noise rather than help there.

What it helps with

  • map content into a sitemap and navigation structure
  • draw wireframes from lo-fi to hi-fi
  • run a clickable prototype through usability testing
  • check screens against WCAG 2.2 AA
  • write component and state specs for developer handoff

Example prompts for the agent

  • Map the checkout flow, including error states and edge cases
  • Audit these screens against WCAG 2.2 AA and list the failures
  • Define the design system: color scales, type hierarchy, spacing grid

How to install ux-designer

1Skills CLI (Vercel)

npx skills add oakoss/agent-skills --skill ux-designer -a claude-code

2Manually: put the files in place

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

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

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

Questions about ux-designer

How do I install ux-designer in Claude Code?

Run npx skills add oakoss/agent-skills --skill ux-designer -a claude-code. The skill file ends up at ~/.claude/skills/ux-designer/SKILL.md.

What does ux-designer do?

It moves a project through five UX phases: information architecture, user flows, wireframes, prototyping with testing, and UI design with handoff. Each phase comes with a stated goal and its deliverables.

Which tasks are outside its scope?

Backend architecture without a UI, database schema design and DevOps setup. On those the skill adds advice you did not ask for.

Source text

SKILL.md · MIT
---
name: ux-designer
description: 'Designs user experiences and interfaces grounded in research. Use when creating user journeys, wireframes, prototypes, or improving usability. Use for information architecture, interaction design, accessibility audits, design system creation, and developer handoff.'
license: MIT
metadata:
  author: oakoss
  version: '1.0'
---

# UX Designer

## Overview

Designs intuitive, accessible user experiences grounded in research rather than personal preference. Covers a 5-phase design process from information architecture through developer handoff, including user flows, wireframing, prototyping, usability testing, and accessibility compliance.

**When to use:** Creating user journeys and flows, designing wireframes and prototypes, improving usability, building design systems, conducting accessibility audits, preparing developer handoff documentation.

**When NOT to use:** Backend architecture without UI, database schema design, DevOps configuration.

## Quick Reference

| Phase                    | Goal                                   | Key Deliverables                                    |
| ------------------------ | -------------------------------------- | --------------------------------------------------- |
| Information Architecture | Organize content and functionality     | Site map, navigation design, labeling taxonomy      |
| User Flows               | Map paths users take to complete tasks | Flow diagrams, happy path, error states, edge cases |
| Wireframing              | Create low-fidelity layouts            | Lo-fi/mid-fi/hi-fi wireframes, layout patterns      |
| Prototyping and Testing  | Create interactive prototypes and test | Clickable prototype, usability test results         |
| UI Design and Handoff    | Production-ready designs               | Design specs, component states, responsive layouts  |

## Key UX Principles

1. **Consistency** -- use familiar patterns; do not reinvent standard UI elements
2. **Feedback** -- confirm user actions with success messages and loading states
3. **Error Prevention** -- design to prevent errors, not just handle them
4. **Recognition Over Recall** -- show options rather than requiring memory
5. **Flexibility** -- support both novice and expert users with shortcuts and defaults

## Design Patterns Summary

| Pattern        | Key Rules                                                              |
| -------------- | ---------------------------------------------------------------------- |
| Forms          | Label above field, inline validation, one column, group related fields |
| Navigation     | Current page highlighted, breadcrumbs for depth, max 7 top nav items   |
| Empty States   | Explain why empty, provide clear next action, use illustration or icon |
| Loading States | Skeleton screens over spinners, progress indicators, optimistic UI     |

## Common Mistakes

| Mistake                                                         | Correct Pattern                                                                        |
| --------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Designing based on personal preference instead of user research | Ground every design decision in user research, card sorting, or usability test data    |
| Skipping empty, loading, and error state designs                | Design all states for every screen: default, loading, empty, error, and success        |
| Using placeholder text as form labels                           | Place labels above fields; placeholders disappear on input and fail accessibility      |
| Ignoring keyboard navigation and focus states                   | Test Tab order, visible focus indicators, and ARIA labels for all interactive elements |
| Designing a single layout for all screen sizes                  | Create separate responsive layouts for mobile, tablet, and desktop breakpoints         |
| Not testing with real users before development                  | Conduct usability testing with 5+ participants on interactive prototypes               |

## Delegation

- **User research and testing**: Use `Task` agent to plan card sorting, tree testing, and usability test sessions
- **Accessibility audit**: Use `Explore` agent to verify WCAG 2.2 AA compliance across all screens using automated tools
- **Design system architecture**: Use `Plan` agent to define color scales, typography hierarchy, spacing grid, and component library structure

## References

- [Design Process](references/design-process.md) -- 5-phase UX process, information architecture, user flows, wireframing, prototyping, and handoff
- [Visual Design Fundamentals](references/visual-design.md) -- color theory, typography scales, spacing systems, visual hierarchy, dark mode, and responsive patterns
- [Accessibility Guide](references/accessibility-guide.md) -- WCAG 2.2 AA compliance, keyboard navigation, screen readers, color contrast, and audit checklists
- [Tools and Resources](references/tools-and-resources.md) -- design tools, prototyping platforms, testing services, and accessibility checkers

© oakoss · MIT · oakoss/agent-skills

Similar skills

All skills for Design →

ux-designer by other authors comes first.

ux-designer szilu The ux-designer Claude Code skill guides interface design and reviews of screens or frontend code. It activates for usability and accessibility audits, component work, forms, navigation, and microcopy. CX Codex +1 1,900installs prototype-strategy Owl-Listener prototype-strategy is a Claude Code skill that helps decide what kind of prototype to build and how detailed it should be before you start building it. CX Codex +1 2,500installs bencium-controlled-ux-designer bencium bencium-controlled-ux-designer guides visual choices for web interfaces before code changes begin. Use it when building components, pages, or applications that need accessibility checks. CX Codex +1 5,100installs ux-design Mindrally ux-design — a skill that hands your coding agent a set of UX rules, from user research to accessibility and responsive layout. Useful when you design or review an interface. CX Codex +1 1,200installs claude-design jiji262 Produces design artifacts in HTML: landing pages, decks, prototypes, posters and wireframes. Useful when you need quick layout options. CX Codex +1 2,400installs Raven rhinocap Raven is an MCP server for Claude Code that gives coding agents design knowledge and page checks. It supports interface audits, design-token lookup, and UI pattern research. CX Codex +1 ★ 9repo stars designer-skills podo designer-skills is a Claude Code skill with 111 skills across nine plugins, covering design work from user research to visual critique. CX Codex +1 218installs

From the same set106

The whole set →

Project sponsors

Companies that keep this analytics open