design-review

design-review is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 38 tokens per session (3,502 once invoked), scanned A, original, MIT.

A structured review of an existing design for accessibility, usability, visual consistency, content, and motion. It can inspect screenshots, Figma links, HTML files, or a running preview.

In plain words
What is it for?
Use it to review a page or interface, check accessibility and interaction patterns, inspect its HTML, and gather prioritised design findings.
Why use it?
It finds quality problems in a design that already exists without changing the design itself. Combining visual and code checks can show both what users see and what the implementation contains.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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 naksha-studio plugin — 47 commands, 7 agents shipped together

Good fit Use it to review a page or interface, check accessibility and interaction patterns, inspect its HTML, and gather prioritised design findings.

Compare 6 commands from other repositories ↓
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 Adityaraj0421/naksha-studio
Claude Code
/plugin install naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

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 design-review

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-review"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,502 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.00038 $0.03502
Opus 5 $0.00019 $0.01751
Sonnet 5 $0.00008 $0.00700
Haiku 4.5 $0.00004 $0.00350

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

Security

Grade A, and why

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/design-review.md · 323 lines

How it starts

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

/design-review

You are conducting a structured design quality audit. This is a review, not a redesign.

Target

Target: $ARGUMENTS

The user will provide one of:

  • A screenshot or image file (.png, .jpg, .gif, .webp) → Visual AI Critique Mode (see Section A)
  • A Figma URL (contains figma.com) → screenshot it, then run Visual AI Critique + code audit
  • An HTML file path → read it and run Code-Level Audit (Section B)
  • A running preview server → take a screenshot for Visual AI Critique, then inspect code
  • "current preview" → inspect whatever is currently being previewed

Dual-mode strategy: When both a visual and code source are available (e.g., preview server), run both Section A (visual) and Section B (code) and merge the findings into a single report.

MCP Fallback: If Preview MCP tools are unavailable, read the HTML source and perform a static code-level audit. If Figma MCP is unavailable, ask the user for a screenshot or file export.


Step 0: Load Project Constraints

Search up to 3 directory levels for .naksha/project.json. If found, extract v5 fields to use as audit criteria throughout this review:

  • constraints.grid → the expected base spacing unit. Flag any spacing value in the design that is NOT a multiple of this unit (e.g., if grid is "8px", flag 13px, 22px, 7px margins).
  • constraints.dark_mode → if false and the design includes dark mode styles (prefers-color-scheme: dark, [data-theme="dark"], etc.), flag as constraint violation: "Dark mode was explicitly ruled out."
  • constraints.breakpoints → the expected responsive breakpoints. Flag missing breakpoints or breakpoints at unexpected values.
  • constraints.max_content_width → if any layout container exceeds this value, flag it.
  • constraints.accessibility_target → sets the required contrast threshold. "WCAG AAA" requires 7:1; "WCAG AA" requires 4.5:1. Use instead of the default 4.5:1 if "WCAG AAA" is set.
  • constraints.out_of_scope → if the design implements something in this list (e.g., dark mode was out-of-scope but is present), flag as a scope violation.
  • constraints.notes → treat each note as an expected design rule. Check for violations.
  • component_patterns → for any component named in this list, check whether the implementation matches the recorded pattern (background, border, radius, padding, etc.). Flag mismatches as pattern deviation.
  • browser_findings (5 most recent) → use as reference context — these are research findings or prior visual captures. Reference them when relevant but do not penalize for deviating from external sites.

Read the full file on GitHub · 323 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 · 323 lines · 38 tokens per session scan A 089f7c35f171

Subscribe to this mod's changes

design-review is a command published in the GitHub repository Adityaraj0421/naksha-studio (318 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 3,502 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-30.