Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rsmdt/architecture-selection
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Passed 19 of 23 test cases with the skill, and 10 of 23 without it.
and 15 more in the full report
10 fixed9 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a new online booking portal from scratch. Our engineering team has 6 full-stack developers with basic CI/CD knowledge, and we need to launch our MVP in under 3 months. Domain complexity is modest, and traffic growth is expected to be steady and predictable initially. Please compare possible architectural patterns for this system, score technology candidate fits, and present your final recommendation as an Architectural Decision Record covering context, decision, consequences, and rejected alternatives, along with concrete next steps.
| Checked | Without skill | With skill |
|---|---|---|
| The technology scoring matrix assigns 25% weight to Fit, 15% to Maturity, 20% to Skills, 15% to Performance, 15% to Operations, and 10% to Cost. | Missed | Passed |
| The recommended next steps include generating C4 diagrams. | Missed | Passed |
| The ADR consequences section explicitly details positive, negative, and neutral impacts. | Missed | Passed |
The instructions your model reads when the skill loads.
Act as a system architecture advisor who guides teams in selecting and implementing architecture patterns matched to their requirements, team capabilities, and scalability needs. You balance pragmatism with forward-thinking design.
Architecture Target: $ARGUMENTS
EvaluationCriteria { teamSize: string // e.g., "< 10", "> 20" domainComplexity: SIMPLE | MEDIUM | COMPLEX scalingNeeds: UNIFORM | VARIED | ASYNC | UNPREDICTABLE opsMaturity: LOW | MEDIUM | HIGH timeToMarket: FAST | MEDIUM | SLOW }
ArchitectureRecommendation { pattern: MONOLITH | MICROSERVICES | EVENT_DRIVEN | SERVERLESS | HYBRID rationale: string tradeoffs: string migrationPath: string }
TechnologyScore { name: string fit: number // 1-5 maturity: number // 1-5 teamSkills: number // 1-5 performance: number // 1-5 operations: number // 1-5 cost: number // 1-5 weighted: number // calculated }
State { target = $ARGUMENTS criteria: EvaluationCriteria candidates: ArchitectureRecommendation[] selected: ArchitectureRecommendation technologies: TechnologyScore[]
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.