agentmods.dev

y-plan-design-review

y-plan-design-review is a command for Claude Code from yashs33244/the_y_coding_standard. It costs 106 tokens per session (1,700 once invoked), scanned A, original, MIT.

A design review step for an active software plan. It examines every user interface and user experience surface, meaning what people see and how they use the product.

In plain words
What is it for?
Use it to critique screens and interactions, rate their usability, and add concrete design fixes to the plan.
Why use it?
It finds confusing or incomplete interactions before engineering work begins.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the the-y-coding-standard plugin — 1 skill, 10 commands shipped together

not rated 2repo 3mo ago A scan 106 tokens original MIT

Good fit Use it to critique screens and interactions, rate their usability, and add concrete design fixes to the plan.

Compare 6 commands from other repositories ↓
View source ↗ yashs33244/the_y_coding_standard
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add yashs33244/the_y_coding_standard
Claude Code
/plugin install the-y-coding-standard

Made for: Claude Code.

Or install the-y-coding-standard, the plugin that ships this one along with the rest of its 1 skill, 10 commands.

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.

agentmods badge for y-plan-design-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-plan-design-review/github.svg)](https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-plan-design-review)
Your own site
<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-plan-design-review"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-plan-design-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.

agentmods 80×15 button for y-plan-design-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-plan-design-review"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-plan-design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 106 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,700 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00106 $0.01700
Opus 5 $0.00053 $0.00850
Sonnet 5 $0.00021 $0.00340
Haiku 4.5 $0.00011 $0.00170

Measured 10d ago against content hash 86c70325e86c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

y-plan-design-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 10d 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.

commands/y-plan-design-review.md · 168 lines

How it starts

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

/y-plan-design-review

You are running step 03 of Yash's Sprint Loop: Design Review. This is the "make the user happy" phase. Designer's eye. You read the active plan, find every UI/UX surface, score each on eight dimensions, and propose concrete fixes for any dimension under 7. Output is written back to the plan so the next step (/y-plan-eng-review) inherits the locked UX direction.

The Sprint Loop is: Office Hours -> Core Review -> Design Review -> Eng Review -> Implement -> Test -> Review -> Ship -> Retro. You are the UX gate. Skip you, ship a confused interface.

Pre-flight

  1. List plans/ files matching YYYY-MM-DD-*.md, newest first.
  2. If the user passed a path as an arg, use it. Otherwise:
    • Prefer plans with Status: draft (core-reviewed).
    • If multiple, ask which file to review. Show top 3 by date.
  3. Read the selected plan end to end before asking anything.
  4. Detect stack from the plan and repo:
    • React / Next.js -> load ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/react-nextjs.md for accessibility and component norms.
    • Plain HTML / other -> note that and apply general best practices.
  5. Load ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/agentic-stack.md for plan format.

Workflow

Pass 1: Detect UI surface

From the plan, list every UI / UX surface the feature touches. Categories:

  • Pages or routes
  • Components (new or modified)
  • Forms or inputs
  • Email or notification templates
  • CLI output or developer-facing terminal UX
  • Public docs

If the plan has zero UI / UX surface (pure backend, infra, library):

  1. Say so clearly: "This plan has no UI/UX surface. Design review is not needed."
  2. Suggest /y-plan-eng-review plans/<file>.md and exit politely.
  3. Do not invent UX work.

Pass 2: Score eight dimensions

For each UI surface, score 0-10 on these dimensions. Yash uses these exact eight, no substitutions:

  1. Clarity: can a first-time user explain what this screen does in 5 seconds?
  2. Density: too much on screen, too little, or right.
  3. Hierarchy: is the most important action visually first? Does the eye land in the right place?
  4. Motion: are transitions intentional? Or jarring, missing, or decorative?
  5. Accessibility: keyboard navigation, screen reader labels, color contrast (WCAG AA minimum), focus states.
  6. Mobile: does this work on a 375px viewport without horizontal scroll?
  7. Empty / error / loading states: are all three designed, or only the happy path?
  8. Polish: spacing, type scale, alignment, micro-copy quality.

Read the full file on GitHub · 168 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.

  1. 10d ago First seen · 168 lines · 106 tokens per session scan A 86c70325e86c

Subscribe to this mod's changes

y-plan-design-review is a command published in the GitHub repository yashs33244/the_y_coding_standard (2 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 1,700 once invoked, about $0.0005 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.

Design and UXPlanning
Related

Other commands, from other repositories

profile

Save, load, inspect, update, reset, or delete diagram-design client profiles.

cathrynlavery/diagram-design · 16 tokens

ui-flow-review

Review menus, HUD, navigation, and player flow from a UX perspective.

MRCalderon3D/everything-game-dev-code · 15 tokens

ppt-image2-editable-rebuild

Rebuild image2 or imagegen reference slides as editable PowerPoint decks.

wwe-dog/ppt-image2-editable-rebuild · 15 tokens

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.

imsaif/design-with-claude · 36 tokens

team-ui

Orchestrate UI/UX design team.

striderZA/OpenCodeGameStudios · 11 tokens

p3-ux-wireframes

Creates wireframes (ASCII art) for the most important screens with interaction descriptions.

jonase47/ccpr · 0 tokens