Guides structured evaluation of design options with trade-off analysis. Use this skill when choosing architectures, selecting technologies, evaluating implementation approaches, or making design decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-guidelines-design:design-alternativesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Always propose 2-3 alternatives** with comprehensive analysis for each.
Always propose 2-3 alternatives with comprehensive analysis for each.
DO: Think broadly, consider long-term implications, make trade-offs explicit, document reasoning
DON'T: Rush to first solution, present only one option, ignore future scalability
## Option 1: [Approach Name]
**Advantages:** [Benefits]
**Disadvantages:** [Drawbacks]
**Reasoning:** [Why this makes sense]
**Future Scenarios:** Breaks down when [scenario]
## Option 2: [Alternative]
[Same structure]
## Recommendation
[Based on requirements and future considerations]
npx claudepluginhub kokuyouwind/claude-plugins --plugin dev-guidelines-designAnalyze architectural trade-offs systematically using decision matrices. Use when comparing design options or justifying architectural choices to stakeholders.
Generates 5 probability-weighted alternative options, including at least one unconventional, with trade-offs to challenge default thinking and expose assumptions in decision points.
Generates probability-weighted alternative options to challenge default thinking and expose hidden assumptions. Useful for decision-point analysis.