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.
Install
$ agentstack add skill-dragoon0x-taste-skills-constraint-evaluation ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Constraint Evaluation
Judge quality within context, not in a vacuum.
How to use
/constraint-evaluationApply 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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Dragoon0x
- Source: Dragoon0x/taste-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.