UX Expert
ux-expert/
UX research and design critique for your agent: research plans, personas, storyboards, heuristic reviews and measured design forensics, with at most three priority actions.

UX research and design critique, the reasoning BEFORE a wireframe and the judgment AFTER a build.
Why use it
- Design decisions defended by taste instead of evidence.
- "Analyze this design" answered with guessed hex codes and invented font sizes.
- A reviewer who recites all ten heuristics and prioritizes nothing.
What it does
research, pick the method that fits the question × product stage, and mine the free evidence first.personas, 2-4 relevance-tested personas, each carrying its provenance (grounded, or clearly labelled proto).storyboard, one persona · one scenario · one path, with an emotion per panel.heuristics, Nielsen H1-H10 applied selectively: critique, or design guidance handed to the designer.review, the combined lens (usability · cognitive load/conversion · craft · a11y · AI-product) with a verdict and max 3 priority actions.analysis, design forensics: measured hexes, type scale, spacing ladder, contrast pairs, composition metrics, tokens.
Benefits
- Numbers, not opinions. Every hex, size and ratio is measured, anything inferred is labelled.
- Findings you can act on today: 3-5 issues, each with its cost, and max 3 priority actions.
- Know who you're designing for before the first wireframe, and whether the build served them after.
- No turf wars. It critiques and routes; it never touches your design system or your code.
Install
Download this skill and copy the ux-expert folder to .claude/skills/ux-expert/ in your project, or to ~/.claude/skills/ux-expert/ to use it in every project. Claude Code finds it on its own; you can also call it with /ux-expert.
Part of the Web Dev Design Pipeline bundle. To get the whole set as a Claude Code plugin: /plugin marketplace add endorphin-ai/hasbrains-agent-kit, then /plugin install web-dev@hasbrains-agent-kit.
Source: endorphin-ai/hasbrains-agent-kit. License: MIT.
Files (29)
Files
-
- ai-product-ux.md
- cognitive-load-and-conversion.md
- design-forensics-scripts.md
- eight-dimensions-and-tokens.md
- example.md
- honest-rendering.md
- journey-empathy-and-prioritization.md
- nielsen-heuristics.md
- persona-craft.md
- research-method-matrix.md
- storyboard-craft.md
- verification-instruments.md
- visual-craft-rules.md
- FORMAT.md
- README.md
- SKILL.md
- VOICE.md
# AI Product UX — Inputs, Wayfinding, Tuners, Governors, Trust, Identifiers
> **Source**: adapted from [tommyjepsen/awesome-ux-skills](https://github.com/tommyjepsen/awesome-ux-skills) (`general-design-review.md`).
> **Load when**: Reviewing an AI/agentic feature — the scope/trust/control/accountability questions plus the input-pattern, wayfinding, tuner, governor, trust-builder and identifier checklists.
---
## AI Product Review
AI features need all normal UX checks plus additional checks for scope, trust, control, and accountability.
Start with these questions:
- What is the AI acting on?
- What can it change, send, delete, spend, remember, or reveal?
- What is the worst case if it is wrong?
- Can the user understand, steer, stop, undo, and verify the AI?
- Is the AI clearly disclosed as AI?
### AI Inputs
Pick the input pattern that fits the task:
| User need | Good pattern |
|---|---|
| Explore freely | Open input |
| Repeat a structured task | Template or madlibs |
| Fill many fields or records | Auto-fill with preview |
| Edit selected content | Inline action or inpainting |
| Try again | Regenerate with recoverable versions |
| Build from a seed | Expand |
| Change structure | Restructure |
| Change style | Restyle |
| Run a workflow | Chained action |
| Compress source material | Summary |
| Interpret across sources | Synthesis |
Universal rules:
- Make scope explicit before running.
- Preview changes before committing.
- Preserve undo/version history.
- Mark AI-generated or AI-edited content until accepted.
- Show cost for bulk, long-running, or chained work.
### AI Wayfinding
Blank AI inputs are rarely enough. Help users understand what is possible.
Use:
- **Initial CTAs** that are specific, not "ask anything."
- **Suggestions** tied to the current context.
- **Examples and galleries** that show useful outcomes.
- **Templates** for complex repeatable tasks.
- **Nudges** only when they match the user's current state.
- **Follow-ups** after generation to refine, extend, or act.
- **Prompt details** when users can learn from or remix good outputs.
- **Randomize** for creative exploration, not serious high-stakes tasks.
Prefer contextual guidance over generic onboarding.
### AI Tuners
Tuners let users shape AI behavior without becoming prompt engineers.
Useful tuner families:
- **Attachments**: ground the AI in specific files, URLs, selections, or examples.
- **Connectors**: link AI to live systems such as Drive, Slack, Notion, CRM, or code.
- **Filters**: restrict sources or exclude unwanted terms, styles, or content.
- **Model management**: expose active model and allow switching when useful.
- **Modes**: bundle behavior into understandable presets like research, creative, tutor, or agent.
- **Parameters**: expose advanced knobs only when users need them.
- **Preset styles**: curated style choices with previews.
- **Saved styles**: reusable personal or team style profiles.
- **Voice and tone**: control how generated output sounds, separate from the AI's own personality.
Review principle: active state must always be visible. Hidden model, mode, source, style, or autonomy level damages trust.
### AI Governors
Governors keep users meaningfully in control as AI becomes more autonomous.
Use stronger governors when actions are expensive, irreversible, public, security-sensitive, or hard to clean up.
Patterns to consider:
- **Action plan**: show intended steps before execution.
- **Verification**: require approval before risky actions.
- **Controls**: stop, pause, resume, queue, or cancel.
- **Cost estimates**: show credits, time, tokens, or money before committing.
- **Draft mode**: cheap lower-fidelity run before final output.
- **Sample response**: full-quality preview on a small subset.
- **Citations and references**: connect claims to source material.
- **Stream of thought**: show plan, execution state, tool calls, and evidence.
- **Memory controls**: show what is remembered and allow edit/delete/off.
- **Branches and variations**: explore without overwriting the original.
- **Shared vision**: show what the AI can currently see or access.
Calibrate friction:
- High-stakes and infrequent: strong confirmation.
- Low-stakes and frequent: passive indicators or undo.
- High-stakes and frequent: rules, preferences, and configurable approval.
### AI Trust Builders
Trust means users neither under-trust nor over-trust the system.
Review for:
- **Caveats**: clear, specific limits near the moment of decision.
- **Consent**: explicit permission for recording, analysis, training, or sharing.
- **Data ownership**: clear controls for retention, training, deletion, and export.
- **Disclosure**: label AI actors, AI actions, and AI-generated content.
- **Footprints**: visible and logged traces of prompts, sources, models, approvals, costs, and edits.
- **Incognito mode**: private sessions that do not affect memory, training, or history.
- **Watermarking/provenance**: durable origin signals for shared synthetic content.
Do not rely on disclaimers alone. Pair warnings with evidence, controls, and recoverability.
### AI Identifiers
AI identity should be coherent with the product and honest about capability.
Review:
- **Name**: Does it set the right expectation? Is AI disclosure still clear?
- **Avatar**: Does it communicate state without implying false human competence?
- **Color**: Does it distinguish AI affordances accessibly and consistently?
- **Iconography**: Are common AI actions recognizable, or are icons decorative noise?
- **Personality**: Does the tone serve the task without over-validating, misleading, or encouraging unhealthy attachment?
The identity should help users understand the AI's role, not turn it into a novelty layer.