{"enrichment":{"faq":[{"a":"Architecture Selection helps you evaluate patterns\u2014monolith, microservices, serverless, and event-driven\u2014against your specific requirements. Score candidates using weighted criteria including team size, domain complexity, scaling needs, and operational maturity. The skill guides you through trade-off analysis so you avoid resume-driven choices and premature optimization, then documents your decision using ADR format for future reference.","q":"How do I pick the right architecture pattern for my system?"},{"a":"Architecture Selection breaks down key trade-offs: monoliths offer simpler deployment and lower ops overhead but limit independent scaling; microservices enable team autonomy and targeted scaling but require mature DevOps practices. The skill helps you assess whether your team's operational maturity, domain complexity, and scaling requirements justify microservices' added complexity, or whether a monolith better fits your current stage.","q":"What are the monolith vs microservices tradeoffs I should consider?"},{"a":"Architecture Selection compares serverless and microservices across criteria like cost predictability, latency requirements, vendor lock-in tolerance, and team expertise. Serverless suits event-driven workloads with variable traffic and minimal ops burden; microservices work better for complex domains needing fine-grained control. The skill helps you weight these factors against your system's actual constraints rather than hype.","q":"When should I use serverless vs microservices architecture?"},{"a":"Architecture Selection recognizes that team size and operational maturity directly influence which patterns are viable. Smaller teams typically benefit from monoliths or managed serverless to minimize ops overhead; larger teams with DevOps expertise can sustain microservices. The skill assesses your team's capabilities as a weighted criterion, helping you choose an architecture your organization can actually operate effectively.","q":"How does team size affect architecture selection?"},{"a":"Architecture Selection provides migration paths by first documenting your current architecture's constraints, then identifying service boundaries aligned with your domain. It helps you stage the transition\u2014perhaps starting with a strangler pattern or extracting high-value services first\u2014while assessing team readiness and ops maturity. The skill ensures your migration plan matches your team's capacity rather than forcing a risky big-bang rewrite.","q":"How do I plan a migration from monolith to microservices?"},{"a":"Architecture Selection guides you through ADR (Architecture Decision Record) format: capture the decision, context, alternatives considered, trade-offs, and consequences. This creates a searchable record of why you chose your pattern, making it easier to revisit decisions later and onboard new team members. The skill helps you document not just the choice but the reasoning behind it.","q":"What should I document when making an architecture decision?"}],"shadow_tags":["system-design","pattern-selection","scalability-planning","migration-strategy","technology-evaluation","ops-readiness","distributed-systems","architectural-tradeoffs","team-capability-fit","infrastructure-planning"],"summary_rewrite":"Architecture Selection helps teams pick the best system design by evaluating patterns against team size, domain complexity, scaling needs, and operational maturity. It scores candidates using weighted criteria, documents trade-offs, and provides migration paths\u2014avoiding resume-driven choices and premature optimization. Use it to design new systems, plan migrations, or review existing architectures."},"files":[{"bytes":4927,"path":"plugins/team/skills/development/architecture-selection/SKILL.md","sha256":"0668709271c464f442ab6267eb9ccfcc6e2e6c761d79fe3d01c50ef1b4e03986","url":"https://skillfed.io/files/rsmdt/the-startup/architecture-selection/2c4f4d8f/SKILL.md"}],"id":"rsmdt/the-startup/architecture-selection","links":{"html":"https://skillfed.io/rsmdt/the-startup/architecture-selection","md":"https://skillfed.io/rsmdt/the-startup/architecture-selection.md","repo":"https://github.com/rsmdt/the-startup"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":42,"language":"Shell","last_updated":"2026-05-07","license":"MIT","name":"architecture-selection","publisher":"rsmdt","stars":305},"relations":{"categories":["system-architecture","devops","engineering-leadership"],"similar":[{"id":"vasilyu1983/AI-Agents-public/software-architecture-design"},{"id":"Pixel-Process-UG/superkit-agents/senior-architect"},{"id":"rsmdt/the-startup/specify-solution"},{"id":"rsmdt/the-startup/platform-operations"},{"id":"miles990/claude-software-skills/architecture-patterns"},{"id":"rsmdt/the-startup/performance-analysis"},{"id":"tech-leads-club/agent-skills/nestjs-modular-monolith"},{"id":"duck4nh/antigravity-kit/system-design-expert"},{"id":"athola/claude-night-market/architecture-paradigms"},{"id":"elophanto/EloPhanto/backend-architecture"}]},"slug":{"owner":"rsmdt","repo":"the-startup","skill":"architecture-selection"},"version":"2c4f4d8f"}