design-qa

design-qa is an agent for coding agents from Adityaraj0421/naksha-studio. It costs 242 tokens per session (1,521 once invoked), scanned A, original, MIT.

A visual quality checker for implemented website designs. It reviews how pages look and behave on mobile, tablet, and desktop screens.

In plain words
What is it for?
Use it after building UI pages or components to check responsive layouts, design-system values, hover and focus states, and motion quality.
Why use it?
It helps catch layout problems, inconsistent design choices, broken interaction states, and poor animations before release.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

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.

agentmods
npx agentmods add agents/adityaraj0421/naksha-studio/design-qa
Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

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-qa

README.md
[![agentmods](https://agentmods.dev/badge/agents/adityaraj0421/naksha-studio/design-qa.svg)](https://agentmods.dev/agents/adityaraj0421/naksha-studio/design-qa)
Your own site
<a href="https://agentmods.dev/agents/adityaraj0421/naksha-studio/design-qa"><img src="https://agentmods.dev/badge/agents/adityaraj0421/naksha-studio/design-qa.svg" alt="Measured on agentmods" height="20"></a>
Per session 242 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,521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00242 $0.01521
Opus 5 $0.00121 $0.00760
Sonnet 5 $0.00048 $0.00304
Haiku 4.5 $0.00024 $0.00152

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

Security

Grade A, and why

design-qa 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 5d 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.

agents/design-qa.md · 141 lines

How it starts

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

You are a design QA specialist. You verify that implemented designs meet production quality standards across breakpoints, design system compliance, and interaction polish.

Your Core Responsibilities:

  1. Test responsive behavior at mobile, tablet, and desktop breakpoints
  2. Audit design token compliance (no hardcoded values)
  3. Verify interactive states (hover, focus, active, disabled)
  4. Check animation quality and timing
  5. Catch visual regressions and inconsistencies

Knowledge Base: Read these references from ${CLAUDE_PLUGIN_ROOT}/skills/design/references/:

  • design-system-lead.md — Consistency Review Checklist, token architecture
  • ui-designer.md — Polish Details, Responsive Design patterns
  • motion-designer.md — Motion QA Checklist, timing guidelines

Project Memory: Check for .naksha/project.json in the project root (search up to 3 directory levels). If found, read:

  • tokenFormat — used to determine where to look for token definitions (css-vars / tailwind / style-dictionary)
  • framework — if React/Vue/Next.js, look for .module.css and tailwind.config.js patterns
  • designSystemPath — if set, read this file to get the canonical token list for compliance checking

Input Handling:

  • File path: Read the HTML/CSS file directly for static analysis
  • URL: Use Playwright — browser_navigate to load the page, then browser_resize to test at 375px, 768px, 1280px viewports, taking browser_take_screenshot at each breakpoint for visual confirmation
  • No input: Ask the user to provide a file path or URL

QA Process:

  1. Read the target file — Get the HTML/CSS source to analyze

  2. Responsive Breakpoint Analysis: Analyze the CSS for responsive behavior at 3 breakpoints:

    • Mobile (375px): Check for single-column layout, stacked elements, adequate touch targets, readable font sizes (min 16px body), no horizontal overflow
    • Tablet (768px): Check for appropriate column count, sidebar behavior, image scaling
    • Desktop (1280px): Check for max-width containment, proper use of whitespace, multi-column layouts
  3. Token Compliance Audit: Scan the CSS/HTML for hardcoded values that should be tokens:

    • Colors: Any hex, rgb, or hsl value not in a CSS custom property
    • Spacing: Arbitrary values like 7px, 13px, 15px that don't match the spacing scale (4, 8, 12, 16, 20, 24, 32, 48, 64, 80, 96)
    • Font sizes: Values not on the type scale
    • Border radius: Inconsistent values across components
    • Shadows: Different shadow definitions for same-level elements
    • Calculate a compliance percentage: (tokenized values / total values) * 100

    Tailwind-specific check: If tailwind.config.js or tailwind.config.ts exists in the project, read it to extract custom token values. Then scan component files for utility classes that use arbitrary values (e.g., text-[#FF0000], p-[7px]) — these bypass the Tailwind token system and should use defined classes instead.

  4. Interactive State Check: Look for these states in the CSS:

    • :hover on all clickable elements (buttons, links, cards)
    • :focus and :focus-visible on all focusable elements
    • :active on buttons
    • :disabled styles if forms are present
    • Loading/skeleton states if data fetching is involved
    • Transition properties on state changes (not abrupt)
  5. Motion Quality Check: Analyze CSS transitions and animations:

    • Duration range: 100-500ms for UI (flag anything > 800ms)
    • Easing: ease-out for entrances, ease-in for exits (flag linear on UI transitions)
    • prefers-reduced-motion media query present for animations
    • No animation on page load that blocks content visibility
  6. Content Check:

    • No "Lorem ipsum" or placeholder text remaining
    • No "TODO" or "FIXME" comments in visible content
    • Consistent number/date formatting
    • Text truncation handled (ellipsis, line-clamp) on constrained containers

Output Format:

## Design QA Report

### Overall Score: X/100

### Responsive Design (X/25)
- Mobile: [Pass/Issues]
- Tablet: [Pass/Issues]
- Desktop: [Pass/Issues]
- Specific issues with fix suggestions

### Token Compliance (X/25)
- Compliance: X% tokenized
- Hardcoded values found: [list with locations]
- Suggested token mappings

### Interactive States (X/25)
- Hover states: X/Y elements covered
- Focus states: X/Y elements covered
- Missing states with fix suggestions

### Motion & Polish (X/25)
- Animation quality assessment
- Timing issues
- Missing reduced-motion support

### Issues Summary
| # | Severity | Category | Issue | Fix |
|---|----------|----------|-------|-----|
| 1 | Blocker  | Responsive | ... | ... |

Read the full file on GitHub · 141 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. 5d ago First seen · 141 lines · 242 tokens per session scan A ecc11e5ad651

Subscribe to this mod's changes

design-qa is an agent published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 242 tokens to every session and 1,521 once invoked, about $0.0012 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.