design-critique

design-critique is a skill for Claude Code from nota-america/forgecat-agent-profiles. It costs 60 tokens per session (941 once invoked), scanned A, a copy of design-critique, Apache-2.0.

A structured review of a design, mockup, screenshot, or Figma file. It examines how clear, usable, consistent, and visually organised the interface is.

In plain words
What is it for?
Use it to review screens and flows, assess first impressions and usability, and get feedback focused on areas such as mobile or onboarding.
Why use it?
It helps reveal confusing navigation, weak visual hierarchy, unnecessary steps, and inconsistent design choices before or during implementation.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Good fit Use it to review screens and flows, assess first impressions and usability, and get feedback focused on areas such as mobile or onboarding.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nota-america/forgecat-agent-profiles/design-critique
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 nota-america/forgecat-agent-profiles --skill design-critique
Clone the repo
git clone --depth 1 https://github.com/nota-america/forgecat-agent-profiles

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/design-critique/github.svg)](https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/design-critique)
Your own site
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/design-critique"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/design-critique/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-critique

Your own site · 80×15
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/design-critique"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/design-critique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 941 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 98% copy Near-identical to another mod 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.00060 $0.00941
Opus 5 $0.00030 $0.00470
Sonnet 5 $0.00012 $0.00188
Haiku 4.5 $0.00006 $0.00094

Measured 9d ago against content hash 4b90bf0a9ddf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-critique 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 9d 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.

Origin

This is a copy

98% identical to design-critique — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_design/for-claude/.claude/skills/design-critique/SKILL.md · 122 lines

How it starts

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

/design-critique

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_design/CONNECTORS.md).

Get structured design feedback across multiple dimensions.

Usage

/design-critique $ARGUMENTS

Review the design: @$1

If a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design.

What I Need From You

  • The design: Figma URL, screenshot, or detailed description
  • Context: What is this? Who is it for? What stage (exploration, refinement, final)?
  • Focus (optional): "Focus on mobile" or "Focus on the onboarding flow"

Critique Framework

1. First Impression (2 seconds)

  • What draws the eye first? Is that correct?
  • What's the emotional reaction?
  • Is the purpose immediately clear?

2. Usability

  • Can the user accomplish their goal?
  • Is the navigation intuitive?
  • Are interactive elements obvious?
  • Are there unnecessary steps?

3. Visual Hierarchy

  • Is there a clear reading order?
  • Are the right elements emphasized?
  • Is whitespace used effectively?
  • Is typography creating the right hierarchy?

4. Consistency

  • Does it follow the design system?
  • Are spacing, colors, and typography consistent?
  • Do similar elements behave similarly?

5. Accessibility

  • Color contrast ratios
  • Touch target sizes
  • Text readability
  • Alternative text for images

How to Give Feedback

  • Be specific: "The CTA competes with the navigation" not "the layout is confusing"
  • Explain why: Connect feedback to design principles or user needs
  • Suggest alternatives: Don't just identify problems, propose solutions
  • Acknowledge what works: Good feedback includes positive observations
  • Match the stage: Early exploration gets different feedback than final polish

Output

## Design Critique: [Design Name]

### Overall Impression
[1-2 sentence first reaction — what works, what's the biggest opportunity]

### Usability
| Finding | Severity | Recommendation |
|---------|----------|----------------|
| [Issue] | 🔴 Critical / 🟡 Moderate / 🟢 Minor | [Fix] |

### Visual Hierarchy
- **What draws the eye first**: [Element] — [Is this correct?]
- **Reading flow**: [How does the eye move through the layout?]
- **Emphasis**: [Are the right things emphasized?]

### Consistency
| Element | Issue | Recommendation |
|---------|-------|----------------|
| [Typography/spacing/color] | [Inconsistency] | [Fix] |

### Accessibility
- **Color contrast**: [Pass/fail for key text]
- **Touch targets**: [Adequate size?]
- **Text readability**: [Font size, line height]

### What Works Well
- [Positive observation 1]
- [Positive observation 2]

### Priority Recommendations
1. **[Most impactful change]** — [Why and how]
2. **[Second priority]** — [Why and how]
3. **[Third priority]** — [Why and how]

Read the full file on GitHub · 122 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. 9d ago First seen · 122 lines · 60 tokens per session scan A 4b90bf0a9ddf

Subscribe to this mod's changes

design-critique is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 941 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to design-critique, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

build-ui-components-and-systems

A guide for building reusable UI components and design systems: shared visual rules, component interfaces, behavior, accessibility requirements, documentation, packaging, and version management. A design system is a maintained set of parts and rules that multiple screens or products can share.

EverMind-AI/Raven · 101 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens

voice-generative-ui

Design and maintain truthful HomeRail generative UI for voice or text. Use for dashboards, cards, charts, visual reports, screenshot-ready output, or supervised multi-Actor live panels that update in parallel and across follow-ups.

xiaotianfotos/homerail · 50 tokens

aceternity-ui

Add premium animated UI components built with Framer Motion and Tailwind CSS using Aceternity UI. Use when: adding animated effects (3D cards, glowing backgrounds, spotlight effects, moving borders), building visually stunning UIs, creating impressive hero sections and feature showcases in React/Next.js.

TerminalSkills/skills · 65 tokens

accessibility-patterns

WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization.

vibeeval/vibecosystem · 24 tokens