design-alternatives
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.
When & Why to Use This Skill
This Claude skill facilitates structured decision-making by evaluating multiple design options through rigorous trade-off analysis. It helps developers and architects compare technical solutions, assess long-term scalability, and document the reasoning behind architectural choices to ensure robust and future-proof software design.
Use Cases
- Architectural Decision Records (ADR): Systematically comparing different system architectures, such as monolithic vs. microservices, to determine the best fit for project requirements.
- Technology Stack Selection: Evaluating competing technologies, frameworks, or databases (e.g., SQL vs. NoSQL) by analyzing their advantages, disadvantages, and long-term maintenance costs.
- Implementation Strategy Evaluation: Assessing multiple coding approaches or third-party library integrations for a specific feature to identify potential bottlenecks and scalability concerns before development begins.
| name | design-alternatives |
|---|---|
| description | 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. |
Design Alternatives
Instructions
Core Principle
Always propose 2-3 alternatives with comprehensive analysis for each.
For Each Alternative
- Advantages: Benefits and problems it solves well
- Disadvantages: Drawbacks, limitations, complexities
- Reasoning: Why this is a good or poor choice
- Future Scenarios: When it breaks down, scalability concerns
DO / DON'T
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
Examples
Template
## 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]