review-design

review-design is a skill for Claude Code from fpindej/netrock. It costs 30 tokens per session (1,867 once invoked), scanned A, original, MIT.

A frontend review workflow for checking user-interface components against design and usability standards. Frontend means the part of an application people see and use.

In plain words
What is it for?
Use it to review Svelte components or changed files, compare them with project design rules, and assess their surrounding page and rendered screenshots.
Why use it?
It helps catch problems with styling, mobile layouts, accessibility, responsiveness, and consistency before a change is shipped.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it to review Svelte components or changed files, compare them with project design rules, and assess their surrounding page and rendered screenshots.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fpindej/netrock/review-design
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.

Any agent
npx skills add fpindej/netrock --skill review-design
Clone the repo
git clone --depth 1 https://github.com/fpindej/netrock

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/fpindej/netrock/review-design.svg)](https://agentmods.dev/skills/fpindej/netrock/review-design)
Your own site
<a href="https://agentmods.dev/skills/fpindej/netrock/review-design"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/review-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,867 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00030 $0.01867
Opus 5 $0.00015 $0.00933
Sonnet 5 $0.00006 $0.00373
Haiku 4.5 $0.00003 $0.00187

Measured 8d ago against content hash 282a72529f83, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

review-design 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 8d 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.

.claude/skills/review-design/SKILL.md · 146 lines

How it starts

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

Reviews frontend components for design quality, UI/UX best practices, and project standards.

Argument: file path, component name, or glob pattern. If omitted, reviews all files changed on the current branch vs the repo default branch.

References

Steps

  1. Resolve scope: If argument provided, find matching .svelte files. If omitted, get changed files via git diff $(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/master) --name-only -- '*.svelte'
  2. Read every file in scope in full - understand the complete component, not just fragments
    • If screenshots for this change exist under docs/sessions/assets/, Read them too and judge the rendered result, not just the classes
  3. Read the design tokens reference for project standards
  4. Check the parent layout/page that renders each component - understand the context it lives in
  5. Cross-reference related components - check siblings in the same feature folder for consistency

Design Checklist

Responsive Design

  • Mobile-first: base styles target 320px, then sm: / md: / lg: / xl: breakpoints
  • No hardcoded widths that break on small screens (except max-w-* constraints)
  • Padding scales with breakpoints (p-4 sm:p-6 lg:p-8) - flat large padding wastes mobile space
  • Content grids use lg:grid-cols-2 (not xl:) since max-w-7xl ensures sufficient width
  • Dialog grids start with grid-cols-1 base before responsive breakpoints
  • Full-height layouts use h-dvh not h-screen
  • Flex children with text have min-w-0, icons/badges have shrink-0
  • Text doesn't overflow containers - check long names, emails, URLs with truncate or break-all

Touch & Interaction

  • All interactive elements meet 44px minimum touch target (min-h-11 or h-11)
  • Buttons use default size with w-full sm:w-auto pattern
  • Button wrapper uses flex flex-col gap-2 sm:flex-row sm:justify-end
  • No size="sm" or size="lg" on action/submit buttons
  • Action buttons are right-aligned (not left-aligned or centered)
  • Clickable text elements (links styled as text) still meet touch target minimums
  • Disabled states are visually distinct and non-interactive

Read the full file on GitHub · 146 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 146 lines · 30 tokens per session scan A 282a72529f83

Subscribe to this mod's changes

review-design is a skill published in the GitHub repository fpindej/netrock (232 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 1,867 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.

Related

Other skills, from other repositories

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…

aps08/fullstack-clean-architecture · 77 tokens

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI…

spinspire/pocketbase-sveltekit-starter · 76 tokens

modern-css

Proactively apply when creating design systems, component libraries, or any frontend application. Triggers on CSS Grid, Subgrid, Flexbox, Container Queries, :has(), @layer, @scope, CSS nesting, @property, @function, if(), oklch, color-mix, light-dark, relative color, @starting-style, scroll-driven animations, view…

ccheney/robust-skills · 181 tokens

shadcn-sveltekit-design

Use when building, redesigning, beautifying, or refactoring SvelteKit pages and reusable components with shadcn-svelte, Bits UI, or the shadcn-svelte MCP. Trigger on landing pages, dashboards, marketing sites, app shells, forms, navbars, tables, dialogs, responsive layouts, theming, icon selection, and requests to…

Michael-Obele/shadcn-svelte-mcp · 99 tokens

创建主题

A set of rules for creating or changing frontend visual themes through configuration. It covers colors, interface components, effects, backgrounds, naming, accessibility, and how preset themes are registered.

jianchen08/Agent-os-open · 83 tokens

cratis-components-styling

Style and theme an application built on Cratis Components — the stylesheet imports an app must make, the --cratis- design-token layer and the PrimeReact token chain behind it, choosing between the baseline theme, a styled preset, a custom palette, and fully unstyled, dark mode, the PrimeReact pass-through prop, and…

Cratis/AI · 122 tokens