Dragoon0x/taste-skills / skills/judgment/design-ranking
design-ranking
VerifiedRank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
Design Ranking
Rank solutions. Explain the ranking. Separate preference from quality.
How to use
/design-rankingApply ranking constraints when comparing design options in this conversation.
Constraints
Ranking Structure
- MUST rank options explicitly (1st, 2nd, 3rd) with clear reasoning for each position
- MUST state the evaluation criteria before ranking (hierarchy clarity, user task fit, brand alignment, etc.)
- MUST distinguish between "I prefer this" and "this works better" with evidence
- NEVER rank based on visual style alone. Rank based on how well decisions serve the goals.
- SHOULD acknowledge what each option does well, even lower-ranked ones
Quality vs. Preference
- MUST separate personal taste from functional quality
- A dark theme you personally prefer can be worse for the specific use case than a light theme
- SHOULD name the user context when defending a ranking ("for first-time users," "for power users," "for this brand")
- NEVER let trend-alignment influence ranking. Something can be trending and wrong for this context.
Predictive Judgment
- SHOULD predict which option would perform better with real users and explain why
- MUST connect predictions to specific design decisions, not general feelings
- "Version B will have higher engagement because the CTA has more visual weight relative to surrounding elements"
Anti-Patterns
- Ranking everything as "they're all good in different ways" (commit to a judgment)
- Letting execution quality override conceptual quality (a polished bad idea is still a bad idea)
- Ranking based on what's trending rather than what serves the context
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |