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 で公開
tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
含まれるファイル（1）
- SKILL.md1.7 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Tradeoff Assessment
Name what was chosen. Name what was lost. Decide if the trade was worth it.
How to use
/tradeoff-assessmentApply tradeoff analysis constraints to this conversation.
Constraints
Tradeoff Structure
- MUST name both sides: "This prioritizes X at the cost of Y"
- MUST evaluate whether the tradeoff serves the primary user goal
- MUST avoid false binaries. Often there's a third option that reduces the tradeoff.
- NEVER present a decision as having no downsides. Every choice trades something.
Common Design Tradeoffs
- Density vs. clarity (more information per screen vs. easier scanning)
- Speed vs. polish (shipping fast vs. refining details)
- Flexibility vs. simplicity (more options vs. fewer decisions)
- Consistency vs. context (following the system vs. breaking it for a specific case)
- Innovation vs. convention (novel interactions vs. familiar patterns)
Evaluation
- SHOULD rate tradeoffs as: well-made (right thing was prioritized), questionable (unclear if the right thing was prioritized), or poor (wrong thing was prioritized)
- MUST explain the rating with reference to user goals, not personal preference
- SHOULD suggest how to mitigate the downside of a well-made tradeoff
Anti-Patterns
- Pretending a design has no tradeoffs
- Treating every tradeoff as equally important (some are critical, some are cosmetic)
- Optimizing for secondary concerns while neglecting primary ones
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新