Borrowing it
Nothing to install: this file belongs to nicograef/handbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nicograef/handbook/main/.claude/skills/ux-review/SKILL.mdgit clone --depth 1 https://github.com/nicograef/handbookWrote 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.
[](https://agentmods.dev/skills/nicograef/handbook/ux-review)<a href="https://agentmods.dev/skills/nicograef/handbook/ux-review"><img src="https://agentmods.dev/badge/skills/nicograef/handbook/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.
<a href="https://agentmods.dev/skills/nicograef/handbook/ux-review"><img src="https://agentmods.dev/badge/skills/nicograef/handbook/ux-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00044 | $0.00728 |
| Opus 5 | $0.00022 | $0.00364 |
| Sonnet 5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile UX Review
Workflow
1. Scope and set up
- Identify the screens or flows to review; default to the primary user journeys when unspecified.
2. Render at a mobile viewport
- If Playwright MCP tools are available and the app can run, open each key screen at 375×667.
- That viewport is the iPhone SE / small-phone baseline.
- Navigate the flows and take snapshots.
- If the app can't run (no dev server, missing credentials, backend down), fall back to a static review.
- That fallback reviews the frontend source and labels the report static-only, so the user knows screens weren't rendered.
3. Walk the top flows
- Step through each flow as a phone user would, watching for the review-area problems below.
- Capture the screen and the source location for each issue.
4. Map problems to source
- Locate the responsible component for every finding.
- Record the file and line range.
- A finding without a
file:linesanchor is not usable. - Drop it, or keep digging until you can anchor it.
5. Report
- Re-read each flagged location before reporting.
- Drop findings that don't anchor to exact lines.
- Drop findings that don't hold up on re-read.
- Mark any remaining uncertainty as unverified.
- Findings follow the report shape rules.
- One bullet per finding, bold keyword first.
- Fields: Category → What → Where (file:lines) → User Impact → Suggestion → Effort (S/M/L).
- Order findings quick wins first, then consistency fixes to batch.
Review Areas
Workflow Friction
- Error states that are hard to recover from
Mobile-First Quality
- Components that break on narrow screens
- Dense tables or forms without a mobile fallback
- Touch targets smaller than 44×44 CSS px, or spaced less than 8 px apart
- The primary action for a screen not visible at 375×667 without scrolling
UI Consistency
- Same concept labelled differently across screens
- Similar actions with different button labels or placements
- Inconsistent loading, empty, and error states
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.
- 6d ago Changed · -12 lines a217964b5497
- 10d ago First seen · 106 lines · 44 tokens per session scan A d22106a67c32
ux-review is a skill published in the GitHub repository nicograef/handbook (2 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 728 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.