What problem does it solve? Non-technical users often let AI write business features first, resulting in inconsistent structure, wavering tech choices, and unmaintainable backends. This Skill enforces a rules-first approach: define engineering rules, write them into an architecture design document, then build a minimal runnable skeleton that enforces those rules. ## Core Features & Use Cases - Rules-First Pipeline: Confirms business boundaries, locks the language and framework, and merges language conventions, framework best practices, and project rules into a backend architecture design document. - Four-Line Skeleton: Builds startup (config, health check), API (unified responses, standard HTTP error codes), business (layered separation), and operations (logging, error handling, README) lines without writing business features. - Verification & Outputs: Verifies the skeleton actually starts and responds, then generates backend-architecture-spec.md, AI agent rules, and prompt templates. - Use Case: A vibe-coding user who finished API planning asks the AI to set up the backend; the Skill locks the stack, produces the architecture document, scaffolds the runnable skeleton, and checks it against a 25-item checklist. ## Quick Start Ask the AI to use backend-skeleton-builder to define backend rules and build the minimal runnable skeleton based on your existing backend-api-spec.md before writing any business features.
