tobihagemann/turbo / claude/skills/user-experience
user-experience
VerifiedApply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path holds together. Use when scoping, planning, or assessing a change to what users see or do.
User Experience
Apply this lens to any user-facing change, both before committing to an approach and when judging a built experience. Keep the work anchored to what the user is trying to accomplish.
Lead with the user's goal rather than a list of surface fixes. A pile of small corrections ("relabel this", "move that") is a sign the underlying flow was never examined. Start from intent and work down to detail.
Scope: this lens covers whether a change serves the user and whether the path through it is coherent. Visual and aesthetic craft — typography, color, spacing, motion polish — is a separate concern and stays out of scope here.
Understanding
Establish what the user actually needs before shaping a solution.
- Name the user and the job they came to do.
- Separate the stated request from the goal behind it, and solve the goal.
- Ground claims about user needs in evidence (observed behavior, recurring reports, real usage). Flag a need that is assumed rather than known.
Bridging
Translate the need into the right solution rather than the first one that comes to mind.
- Check that the solution addresses the goal, not just the visible symptom.
- Weigh whether the change adds a step, a screen, or a concept the user must learn, and whether that cost is justified.
- Check whether an indicator or notice the change adds repeats what an existing surface already tells the user, and prefer relying on that surface.
- Prefer the path that removes work for the user over one that adds configuration or choices.
- Watch for solving a builder's convenience at the user's expense.
Flowing
Trace the path the user takes from end to end.
- Follow the full journey: how the user arrives, the change itself, and what happens after.
- Walk the unhappy paths in the running software when it can be run: empty states, seeded defaults, errors, interruptions, first-time versus returning use. Flag any of these judged from source alone.
- Confirm the user always knows what just happened and what to do next.
- Surface friction: redundant steps, dead ends, and points where the user must hold state in their head.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |