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 で公開
design-ranking
Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
含まれるファイル（1）
- SKILL.md1.9 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Design Ranking
Rank solutions. Explain the ranking. Separate preference from quality.
How to use
/design-rankingApply ranking constraints when comparing design options in this conversation.
Constraints
Ranking Structure
- MUST rank options explicitly (1st, 2nd, 3rd) with clear reasoning for each position
- MUST state the evaluation criteria before ranking (hierarchy clarity, user task fit, brand alignment, etc.)
- MUST distinguish between "I prefer this" and "this works better" with evidence
- NEVER rank based on visual style alone. Rank based on how well decisions serve the goals.
- SHOULD acknowledge what each option does well, even lower-ranked ones
Quality vs. Preference
- MUST separate personal taste from functional quality
- A dark theme you personally prefer can be worse for the specific use case than a light theme
- SHOULD name the user context when defending a ranking ("for first-time users," "for power users," "for this brand")
- NEVER let trend-alignment influence ranking. Something can be trending and wrong for this context.
Predictive Judgment
- SHOULD predict which option would perform better with real users and explain why
- MUST connect predictions to specific design decisions, not general feelings
- "Version B will have higher engagement because the CTA has more visual weight relative to surrounding elements"
Anti-Patterns
- Ranking everything as "they're all good in different ways" (commit to a judgment)
- Letting execution quality override conceptual quality (a polished bad idea is still a bad idea)
- Ranking based on what's trending rather than what serves the context
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新