design-critiquer

design-critiquer is a skill for Claude Code, Codex from NickCrew/Claude-Cortex. It costs 76 tokens per session (2,568 once invoked), scanned A, original, MIT.

A workflow guide for running builds, executing tests, and improving the day-to-day tools developers use. It focuses on repeatable steps, clear diagnostics, and useful follow-up actions.

In plain words
What is it for?
Use it when a build or test fails, when analysing test output, or when improving onboarding and developer workflows.
Why use it?
It helps teams run checks consistently and understand failures instead of losing information in ad-hoc commands or incomplete logs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a build or test fails, when analysing test output, or when improving onboarding and developer workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nickcrew/claude-cortex/design-critiquer
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 NickCrew/Claude-Cortex --skill design-critiquer
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickcrew/claude-cortex/design-critiquer.svg)](https://agentmods.dev/skills/nickcrew/claude-cortex/design-critiquer)
Your own site
<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/design-critiquer"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/design-critiquer.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,568 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.00076 $0.02568
Opus 5 $0.00038 $0.01284
Sonnet 5 $0.00015 $0.00514
Haiku 4.5 $0.00008 $0.00257

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

Security

Grade A, and why

design-critiquer 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 4d 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.

skills/design-critiquer/SKILL.md · 179 lines

How it starts

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

Design Critiquer

Overview

This skill provides structured, actionable design critiques grounded in UX principles, visual design fundamentals, and usability heuristics. A good design critique is not a list of personal preferences—it connects observations to user impact and business outcomes. This skill helps you evaluate designs across key dimensions: usability, hierarchy, accessibility, consistency, and clarity. Whether you are reviewing a lo-fi wireframe or a polished high-fidelity mockup, the output is prioritized, constructive feedback that the designer can act on immediately.

When to Use

  • Reviewing wireframes, mockups, or prototypes before development
  • Running a design critique session or design review meeting
  • Evaluating a redesign against the existing product for regression
  • Auditing a live UI for usability and accessibility improvements
  • Peer-reviewing a teammate's design work
  • Self-critiquing your own design before presenting it

When NOT to Use

  • Writing or implementing code (use frontend-design skill instead)
  • Creating marketing materials or campaign assets — different discipline
  • Evaluating brand identity at a strategic level (brand strategy is a separate domain)
  • Legal or compliance review of design assets
  • Performance profiling or technical evaluation of a front-end implementation

Quick Reference

Task Approach
First pass Evaluate from the user's perspective before looking at individual elements
Hierarchy Check: can you read the page in 5 seconds and know what to do?
Accessibility Contrast ratios (4.5:1 text, 3:1 UI), touch targets (44×44px min), focus order
Consistency Same element, same style everywhere — spot deviations from the design system
Usability heuristics Apply Nielsen's 10: visibility, feedback, control, standards, error prevention, etc.
Prioritization Sev 1 (blocks users) → Sev 2 (frustrates users) → Sev 3 (polish/preference)
Tone Critique the design, not the designer; lead with impact, not judgment
Positive feedback Name what works and why — it's as actionable as what doesn't

Read the full file on GitHub · 179 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. 4d ago First seen · 179 lines · 76 tokens per session scan A e5e5796cf023

Subscribe to this mod's changes

design-critiquer is a skill published in the GitHub repository NickCrew/Claude-Cortex (38 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 2,568 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

feedback-de-design

Feedback estruturado e direção em projetos de UI/UX, protótipos e interfaces.

ricneves-ai/flowgrammers-skills · 22 tokens

Prototipagem com Google Stitch

Este especialista auxilia na criação rápida de protótipos interativos usando Google Stitch, transformando Design Docs e requisitos em interfaces funcionais que podem ser testadas e iteradas com feedback contínuo do usuário.

Matheus-Gama-deluna/Maestro · 7 tokens

compiler-port

Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.

react/react · 35 tokens

migrate-vstest-to-mtp

Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…

dotnet/skills · 191 tokens

release-safety

Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.

tamagui/tamagui · 0 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 132 tokens