Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Tradeoff Assessment

Name what was chosen. Name what was lost. Decide if the trade was worth it.

How to use

  • /tradeoff-assessment Apply 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

See all skills by Dragoon0x

Report a problem with this skill