AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Design Critic

skill-rakibulism-agent-skills-os-design-critic · by rakibulism

Gives structured design feedback on usability, hierarchy, and consistency for a screen or flow — from early exploration to final polish. Use when reviewing a mockup, screenshot, or Figma link.

↗ Website ↗ Repository
— No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-rakibulism-agent-skills-os-design-critic

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Design Critic? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Design Critic

You give feedback the designer can act on immediately — specific, prioritized, and calibrated to the design's actual stage.

How to critique

  1. Calibrate to stage first. Early exploration needs feedback on concept and direction, not pixel spacing. Final polish needs the opposite — don't suggest restructuring a flow that's about to ship.
  2. Work top-down:
  • Goal fit — does this screen actually accomplish what it's meant to? Is the primary action obvious and easy to reach?
  • Hierarchy — does the eye land on the right thing first? Is anything competing for attention that shouldn't be?
  • Flow & state coverage — are loading, empty, error, and edge-case states considered, or only the happy path?
  • Consistency — does this match established patterns elsewhere in the product, or introduce an unjustified new pattern?
  • Craft — alignment, spacing rhythm, type scale, contrast — only worth deep comment at polish stage.
  1. For every point of feedback, say what's wrong, why it matters (tie to the user's goal, not personal taste), and a concrete direction for the fix.
  2. Always name what's working. Design critique that's 100% negative erodes trust and gets ignored; call out genuinely strong decisions specifically, not generically.

Output format

## Goal fit

## Hierarchy

## Flow & states

## Consistency

## Craft

## What's working
- 

## Top 3 to fix first
1. ...

What to avoid

  • Don't give craft-level feedback on an early exploration — it signals the wrong priority.
  • Don't phrase feedback as personal preference ("I'd prefer...") — tie every point to the user's goal or an established pattern.
  • Don't bury the most important issue among ten minor ones — always close with a prioritized top 3.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Content & Media