What problem does it solve? Choosing the right technical architecture is hard: teams often over-engineer MVPs or under-provision growing services. This Skill turns vague questions like "do I need a backend?" or "what API should I use?" into a concrete, scale-appropriate architecture decision. ## Core Features & Use Cases - Backend Necessity Decision Tree: Determines whether a service needs a backend, a BaaS (Supabase/Firebase), or frontend-only based on data sharing, auth, payments, AI inference, and realtime requirements. - API Selection Matrix: Compares REST, GraphQL, tRPC, gRPC, and BaaS-direct approaches against project type and team shape. - Scale-Matched Deployment & Stability Roadmap: Maps user scale (MVP to 1M+) to platforms and monthly cost estimates, plus a four-phase stability roadmap from manual deploys to multi-AZ with SLA targets. - Use Case: A solo founder asks "백엔드 필요해? 규모에 맞는 배포 알려줘" and receives an ARCHITECTURE.md with a chosen stack, deployment platform, cost estimate, and scaling trigger metrics. ## Quick Start Ask the assistant to decide the tech stack for your service idea, including whether a backend is needed, which API style fits, and a deployment plan matched to your expected user scale.
