Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. 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/sourjya/kiro-rails/main/.claude/commands/review-ux-preflight.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/commands/sourjya/kiro-rails/review-ux-preflight)<a href="https://agentmods.dev/commands/sourjya/kiro-rails/review-ux-preflight"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-ux-preflight/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/commands/sourjya/kiro-rails/review-ux-preflight"><img src="https://agentmods.dev/badge/commands/sourjya/kiro-rails/review-ux-preflight.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.00037 | $0.00618 |
| Opus 5 | $0.00018 | $0.00309 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
review-ux-preflight 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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Preflight Review
Before reviewing, read docs/decisions/ ADRs and any UX/design documentation if they exist. Use documented UX decisions to calibrate recommendations.
Run this BEFORE writing implementation code for any UI feature or screen modification.
Input (fill before running)
SCREEN: [What screen or component is being built/modified] PRIMARY_USER: [Who uses this screen most] PRIMARY_TASK: [What the user came here to do] REFERENCE_PATTERN: [Product + screen to compare against, e.g. "Asana task detail"]
Preflight Checklist
Produce answers for ALL 10 points. Do not skip any.
1. Primary User Goal
What is the single most important thing the user wants to accomplish on this screen?
2. Most Common Action
What will the user do most frequently? This action must have the lowest friction.
3. Information Hierarchy
Rank the top 5 elements by importance. The visual weight must match this ranking.
4. Control Placement Rationale
For every interactive control, state: what does it act on, and how far is it from that object? Flag any control that is more than 200px from its target.
5. Pointer Travel Risk
Identify any interaction that requires the user to move across the full screen width. Each such interaction is a friction point.
6. Density Assessment
Is this a data-dense screen (grid, table, list) or a content-focused screen (detail, form, reading)? Apply the matching density rule from UX Non-Negotiables.
7. Reference Pattern Comparison
Compare against the stated reference pattern:
- Is primary content equally or more readable?
- Are actions closer or farther from their target?
- Is whitespace similar or better?
- Is interaction cost lower, equal, or higher?
8. Required States
List all states this screen must handle: default, empty, loading, error, permission-restricted, success. Flag any missing from the current plan.
9. UX Risks
List specific risks this implementation introduces. Examples: "section menu pushed to far-right increases pointer travel", "description area compressed below metadata".
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.
- 11d ago First seen · 76 lines · 37 tokens per session scan A 243f594a61e7
review-ux-preflight is a command published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 618 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 commands, from other repositories
seed-create-component
A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.
sddesign
Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.
craft
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
spec-screenshot
Analyze website screenshots and generate detailed implementation specs.