Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
無料GitHub で公開
critique-vocabulary
Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.
含まれるファイル（1）
- SKILL.md1.8 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Critique Vocabulary
Say exactly what you mean. Kill vague words.
How to use
/critique-vocabularyApply precise vocabulary constraints to all design feedback in this conversation.
Constraints
Banned Words
- NEVER use these in design feedback: clean, modern, sleek, nice, cool, interesting, beautiful, ugly, minimal, bold, intuitive, seamless, stunning, pop, vibe
- MUST replace every banned word with a specific observation about hierarchy, weight, rhythm, density, contrast, proportion, consistency, or spacing
Replacement Vocabulary
| Instead of... | Use... |
|---|---|
| "It feels cluttered" | "The information density is high relative to the content hierarchy. Nothing signals where to start." |
| "It looks boring" | "The visual rhythm is flat. Every section has the same scale and spacing." |
| "Make it pop" | "The CTA doesn't have enough visual separation from surrounding elements." |
| "Something feels off" | "The spacing between these groups seems inconsistent. Is this relationship intentional?" |
| "It's not polished" | "The border radius is inconsistent between these elements." |
| "Explore other directions" | "The current approach prioritizes X. What happens if we prioritize Y instead?" |
Feedback Structure
- MUST use: Observation > Principle > Question
- Observation: what you specifically see
- Principle: why it matters
- Question: what to explore (not what to do)
Anti-Patterns
- Giving feedback in the form of commands ("make the button blue")
- Using technical jargon to sound authoritative without actually being specific
- Being vague-positive ("looks great!") which teaches nothing
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新