A routing guide and shared format for reviewing an app screen, user flow, feature, or whole product. It chooses the relevant UX checklists and records each item as passed, failed, or not applicable with evidence.

Use it to plan and run structured UX reviews of screens, onboarding, login, checkout, search, notifications, and other product areas.

It prevents important usability issues from being missed when a review crosses visual design, accessibility, content, forms, or errors. It also turns scattered feedback into a consistent report.

ux-review — Skill for Claude Code and Codex by parhamb/design-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add parhamb/design-skills --skill ux-review

Clone the repo

git clone --depth 1 https://github.com/parhamb/design-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/parhamb/design-skills/ux-review/github.svg)](https://agentmods.dev/skills/parhamb/design-skills/ux-review)

Your own site

<a href="https://agentmods.dev/skills/parhamb/design-skills/ux-review"><img src="https://agentmods.dev/badge/skills/parhamb/design-skills/ux-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/parhamb/design-skills/ux-review"><img src="https://agentmods.dev/badge/skills/parhamb/design-skills/ux-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 783 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.00783
Opus 5.5	$0.00024	$0.00313
Sonnet 5.5	$0.00012	$0.00157
Haiku 4.5	$0.00006	$0.00078

Measured 2mo ago against content hash aa960b5b30c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ux-review/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UX Review (Router)

A real UX review almost never fits inside one category. A single screen can raise visual, accessibility, content, and error-handling issues at the same time. This skill maps the request to the category skills to read, and defines the output format every review follows.

Review Process

Identify the scope: a single screen, a flow (onboarding, checkout), a feature (search, notifications), or the whole app.
Select the category skills using the routing table below. Read every skill that applies — most reviews need 3 to 5.
Apply each checklist: mark every item Pass, Fail, or N/A with specific evidence (screen, component, file, or line).
Report using the output format below.

Routing Table

What is being reviewed	Skills to read
Any screen (always)	`ux-visual-design`, `ux-accessibility`, `ux-content`
Onboarding / first run	`ux-help-onboarding`, `ux-user-account`, `ux-safety-privacy`
Login / sign-up / auth	`ux-user-account`, `ux-forms`, `ux-safety-privacy`
Forms / checkout / data entry	`ux-forms`, `ux-error-handling`, `ux-information-architecture`
Search / discovery	`ux-search`, `ux-information-architecture`
Navigation / app structure	`ux-navigation`, `ux-information-architecture`
Settings / preferences	`ux-settings`, `ux-notifications`, `ux-safety-privacy`
Errors / offline / edge cases	`ux-error-handling`, `ux-network`
Notifications	`ux-notifications`, `ux-settings`
AI features / automation	`ux-ai-automation`, `ux-content`
Sharing / favorites / power features	`ux-utility`
Whole app / store readiness	`ux-general` plus every category the app's surfaces touch

Output Format

Structure every review like this:

Summary — 2 to 4 sentences: overall quality, the biggest risk, the biggest strength.
Findings by category — one section per skill applied, containing a table: Item | Verdict (Pass / Fail / N/A) | Evidence | Severity. Severity is Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
Top fixes — the 3 to 5 highest-impact changes, ranked, each with a concrete recommendation (not just a restatement of the problem).

Read the full file on GitHub · 77 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 77 lines · 60 tokens per session scan A aa960b5b30c1

Subscribe to this mod's changes

ux-review is a skill published in the GitHub repository parhamb/design-skills (25 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 783 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Design and UX

ux-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ux-reviewparhamb/design-skills	Skill	25	4mo ago	MIT	A	60	Claude Code, Codex
webgl-holographic-foilnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	41	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	53	Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	78	Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codex	Skill	34k	4d ago	MIT	A	52	Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
accessibilitymicrosoft/hve-core	Skill	1.6k	yesterday	MIT	A	47	Claude Code