UI/UX design skills for Claude Code and AI agents
npx skills add https://github.com/mae616/design-skills --skill usability-psychologistInstall this skill with the CLI and start using the SKILL.md workflow in your workspace.
A collection of UI/UX design decision skills for Claude Code and AI agents. These skills automatically activate during design, implementation, and review tasks.
npx skills add mae616/design-skills
| Skill | Auto-triggers when... |
|---|---|
ui-designer |
Screen design, component design, design system, information architecture, visual hierarchy |
frontend-implementation |
Design-to-code, component implementation, responsive design, UI fixes |
creative-coder |
Animation, motion design, transitions, scroll effects, micro-UX, interaction design |
accessibility-engineer |
Any UI implementation, forms, interactive components, a11y concerns |
usability-psychologist |
UX review, user confusion, drop-off analysis, form usability, cognitive load issues |
CLAUDE.md (see Setup below)User: "Design a dashboard layout for analytics"
→ ui-designer skill activates
User: "Convert this Figma design to React"
→ frontend-implementation + accessibility-engineer skills activate
User: "Add a smooth page transition"
→ creative-coder skill activates
User: "Users keep abandoning our checkout form"
→ usability-psychologist skill activates
User: "Make this modal keyboard accessible"
→ accessibility-engineer skill activates
Skills support English and Japanese trigger keywords.
PRs welcome for additional language support!
design-skills/
├── skills/
│ ├── ui-designer/
│ │ └── SKILL.md
│ ├── frontend-implementation/
│ │ └── SKILL.md
│ ├── creative-coder/
│ │ └── SKILL.md
│ ├── accessibility-engineer/
│ │ └── SKILL.md
│ └── usability-psychologist/
│ └── SKILL.md
├── package.json
├── README.md
└── LICENSE
To enable automatic skill activation, add the following to your CLAUDE.md, agent.md, or system prompt:
## Design Skills (Auto-apply)
When working on design or UI implementation tasks, apply the following decision frameworks from design-skills:
| Context | Skill | Focus |
|---------|-------|-------|
| Screen/component design | ui-designer | Information architecture → visual hierarchy → componentization |
| Design to code | frontend-implementation | Intent over pixels, structure over magic numbers, states are specs |
| Animation/interaction | creative-coder | Purpose-driven motion, a11y-safe, performance-aware |
| Any UI implementation | accessibility-engineer | Native elements first, minimal ARIA, keyboard baseline |
| UX review/friction | usability-psychologist | Cognitive load, error prevention, consistency |
Key principles:
- States (loading/error/empty/disabled) must be defined—not afterthoughts
- Use tokens/components/patterns instead of one-off solutions
- Accessibility is built-in, not bolted-on
## デザインスキル(自動適用)
デザインやUI実装のタスクでは、以下の判断軸を適用すること:
| コンテキスト | スキル | 観点 |
|-------------|--------|------|
| 画面・コンポーネント設計 | ui-designer | 情報設計→視覚階層→コンポーネント化 |
| デザインから実装 | frontend-implementation | ピクセルより意図、マジックナンバーより構造、状態も仕様 |
| アニメーション・インタラクション | creative-coder | 目的ある動き、a11y安全、パフォーマンス意識 |
| UI実装全般 | accessibility-engineer | ネイティブ要素優先、ARIA最小、キーボード基本 |
| UXレビュー・離脱分析 | usability-psychologist | 認知負荷、エラー防止、一貫性 |
共通原則:
- 状態(loading/error/empty/disabled)は後付けではなく仕様として定義
- 場当たりではなくトークン・コンポーネント・パターンで統一
- アクセシビリティは最初から組み込む
These skills share common principles:
Contributions welcome!
git checkout -b feature/your-feature)MIT