team-ux — Claude Code skill: what it does, how to install
team-ux is a Claude Code skill that writes structured UX design specifications covering user flows, screen states, component catalogs, accessibility rules, and mobile behavior.
MIT ★ 71 updated 2026-11-13
npx skills add sametcelikbicak/opencode-team --skill team-ux -a claude-codeWhat team-ux does
The skill creates UX design specifications in Markdown instead of implementation code or styling values. Every flow step specifies the screen, user choices, and outcomes. If an interaction does not let the user take action, the skill treats the step as redundant.
Specifications require an inventory of every screen across five distinct states: loading, empty, error, populated, and unauthorized. It checks interfaces against WCAG 2.1 AA criteria, enforcing keyboard navigation, visible focus rings, a 4.5:1 contrast ratio, and touch targets of at least 44x44 px. It also details layout adaptations for viewports under 768 px and defines clear microcopy for buttons and system alerts.
What it helps with
- document user journey flows step by step without implementation code
- map interface screens across loading, empty, error, and unauthorized states
- enforce WCAG 2.1 AA accessibility guidelines on interactive layouts
- define responsive rules for tables, modals, and forms under 768 px
Example prompts for the agent
- Write a UX specification for the team checkout flow
- Generate screen states and microcopy for an invoice upload view
- Document mobile behavior and WCAG requirements for the settings modal
How to install team-ux
1Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-ux -a claude-code2Manually: put the files in place
~/.claude/skills/team-ux/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/team-ux/
1Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-ux -a codex2Manually: put the files in place
.agents/skills/team-ux/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-ux -a cursor2Manually: put the files in place
.cursor/skills/team-ux/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sametcelikbicak/opencode-team skills/team-ux2Manually: put the files in place
.github/skills/team-ux/SKILL.md1Skills CLI (Vercel)
npx skills add sametcelikbicak/opencode-team --skill team-ux -a gemini-cli2Platform CLI
gemini skills install https://github.com/sametcelikbicak/opencode-team --path skills/team-uxManually: put the files in place
.devin/skills/team-ux/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about team-ux
How to install team-ux in Claude Code?
Run npx skills add sametcelikbicak/opencode-team --skill team-ux -a claude-code or place the file directly at ~/.claude/skills/team-ux/SKILL.md.
What does the team-ux skill do?
It writes Markdown UX specifications detailing screen flows, component inventories, mobile layout shifts, accessibility checks, and microcopy.
Which screen states are required by team-ux?
The skill mandates five states for every screen: loading, empty, error, populated, and unauthorized access.
Source text
SKILL.md · MIT
---
name: team-ux
description: UX design specification writing. Screen flows, state inventory, component list, accessibility and mobile behavior. The playbook of the ux role.
---
# UX Design Specification
You are writing a **specification**, not pixels. Implementation details are the developer's job.
## 1. Main flow
For each flow:
```
Flow: <what they want to do>
1. <screen> — what the user sees, what they can do, what decision they make
2. <screen> — ...
3. <result screen>
```
Each step must answer "what can the user do here?". If there is no answer, the step is unnecessary.
## 2. Screen inventory
| Screen | Purpose | Entry | Exit | States |
|---|---|---|---|---|
**The states column is mandatory for every screen:**
| State | What is shown | What can be done |
|---|---|---|
| Loading | skeleton loader | cancel |
| Empty | text explaining what to do + a primary action | trigger the action |
| Error | what happened + what will happen | try again / support |
| Populated | the content | interact with the content |
| Unauthorized | access denied + why | go back / support |
The empty state is the most frequently forgotten one and the most expensive one: the user meeting an empty screen on first open kills the product.
## 3. Component inventory
| Component | Where it is used | States | Note |
|---|---|---|---|
If the same button style was copied in three places, it should be a single component. Every repeated interface piece goes in here.
## 4. Accessibility (WCAG 2.1 AA)
Check for each screen:
- **Keyboard**: all interactive elements are keyboard reachable, the tab order is logical, when a modal opens the focus stays inside and Esc closes it.
- **Focus**: a visible focus ring (do not remove it). When the page changes, focus moves to the top.
- **Contrast**: text 4.5:1, large text and icons 3:1.
- **Screen reader**: meaningful `aria-label`, `role`, `aria-live` (for state changes), form errors linked with `aria-describedby`.
- **Color does not carry meaning alone**: an error is not only red, it also has an icon + text.
- **Motion**: `prefers-reduced-motion` is supported.
- **Touch target**: at least 44x44 px.
## 5. Mobile behavior
- Screen < 768px: which components are hidden, which are rearranged?
- Table: horizontal scroll or cards?
- Modal: full screen?
- Form: single column or grouped?
- Is there a bottom navigation, and how many items?
## 6. Tone and microcopy
- Button text: names the action ("Save Invoice", "Send", not "OK").
- Error message: what happened + what to do ("The invoice could not be uploaded. The file must be smaller than 10 MB.")
- Empty state text: what will happen ("You have no invoices yet. Upload your first invoice" + button).
- Confirmation: is it reversible, or not?
## Common mistakes
| Mistake | The right way |
|---|---|
| Giving color codes | Define hierarchy and behavior |
| Only the "happy path" | Empty/error/loading/unauthorized are mandatory |
| Skipping the error state | Show errors on every form field |
| Thinking about accessibility later | An AA check for every screen |
| "John Doe" sample data | Realistic, localized sample data |
## Output format
Markdown. Sections: Main flow / Screen inventory / Component inventory / Accessibility notes / Mobile behavior / Microcopy.
In the user's language (Turkish or English).
© sametcelikbicak · MIT · sametcelikbicak/opencode-team