设计与 UI
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.
sergekostenchuk · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add sergekostenchuk/ui-ux-agent-skill-system --skill design-critic-skill技能说明
name: design-critic-skill description: 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.
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
- Read references/hierarchy-rubric.md.
- Read references/anti-slop-patterns.md before calling a design "polished".
- Use references/taste-constraints.md to keep critique observable.
- Apply
../../shared/privacy-policy.mdbefore Figma/screenshots/external tools. - Use assets/critique-report.template.md for structured output.
- 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: