agentsclimarketplace

Constraint evaluation

Skill Dragoon0x/taste-skills/skills/judgment/constraint-evaluation

Agent skills for design taste and visual judgment. Hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design

Install
npx -y skills add Dragoon0x/taste-skills --skill constraint-evaluation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.5 KB, as published. Nobody here has run it

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.