Skip to content
cccskills
FreePublished on GitHub

constraint-evaluation

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.

See how to install

Files included (1)

  • SKILL.md1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Constraint Evaluation

Judge quality within context, not in a vacuum.

How to use

  • /constraint-evaluation Apply constraint-aware evaluation to this conversation.

Constraints

Identify the Constraints

  • MUST attempt to identify: team size, timeline, technology, budget, business model, and target audience
  • MUST evaluate quality relative to constraints, not against an ideal with unlimited resources
  • A strong design under tight constraints demonstrates more taste than a mediocre design with unlimited time
  • SHOULD note where constraints were handled gracefully and where they caused visible damage

Essential vs. Incidental Quality

  • MUST distinguish between decisions that are core to the experience and decisions that are execution details
  • Core decisions (hierarchy, information architecture, primary flow) should hold up regardless of constraints
  • Execution details (animation polish, micro-interactions, state coverage) scale with available resources
  • NEVER excuse poor core decisions by pointing to tight constraints

Anti-Patterns

  • Judging a startup MVP against enterprise product standards
  • Ignoring constraints entirely ("this should have better animation" for a 2-week project)
  • Using constraints as an excuse for fundamentally broken hierarchy or flow

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

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

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.

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