skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
sergekostenchuk/ui-ux-agent-skill-system76 installs

design-critic-skill

Critique UI visual quality with observable design criteria. Use this skill whenever the user asks for visual critique, design review, polish, hierarchy, spacing, typography, contrast risk, consistency, brand fit, anti-slop review, screenshot critique, Figma frame critique, or a fix brief for a weak interface. Keep findings actionable and evidence-labeled. Do not require Attention Insight, Khroma, or external screenshot upload for normal local critique.

How do I install this agent skill?

npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill design-critic-skill
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is safe for use. It provides UI design critiques using observable rubrics and anti-slop patterns. It prioritizes local data processing and requires explicit user consent for external tools. No malicious behavior or data exfiltration risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Design Critic Skill

Use this specialist when the main need is visual quality judgment and actionable polish, not full implementation or automated audit.

Operating Modes

  • screenshot-critique: review a screenshot or image.
  • figma-critique: review a provided Figma frame/context.
  • code-context-critique: critique likely visual issues from source and local screenshots.
  • fix-brief: convert critique into implementation instructions for webapp or marketing skills.

Required Workflow

  1. Read references/hierarchy-rubric.md.
  2. Read references/anti-slop-patterns.md before calling a design "polished".
  3. Use references/taste-constraints.md to keep critique observable.
  4. Apply ../../shared/privacy-policy.md before Figma/screenshots/external tools.
  5. Use assets/critique-report.template.md for structured output.
  6. Mark evidence type: screenshot, Figma, source, browser, or Manual.

Critique Rules

  • Findings must map to observable issues: hierarchy, grouping, scan path, contrast risk, spacing, type scale, affordance, consistency, content density, or action priority.
  • Avoid vague taste claims without fix direction.
  • Do not invent accessibility, DOM, performance, or analytics evidence.
  • Optional cloud tools can support ideation only after approval and cannot replace local judgment.

Validation

python3 $CODEX_SKILLS_DIR/.system/skill-creator/scripts/quick_validate.py $CODEX_SKILLS_DIR/design-critic-skill
python3 $CODEX_SKILLS_DIR/senior-skill-architect/scripts/lint_production_skill.py $CODEX_SKILLS_DIR/design-critic-skill

Output Shape

Input:
Evidence type:
Top findings:
Fix brief:
What not to change:
Verification:
Privacy notes:

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/design-critic-skill">View design-critic-skill on skillZs</a>