使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill design-critic-skill開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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
bash
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-skillOutput Shape
text
Input:
Evidence type:
Top findings:
Fix brief:
What not to change:
Verification:
Privacy notes:
