sc-build

# /sc-build — idea to working web app Use this for a new app, a vague business idea, or requests such as: > `/sc-build I need a website for my laundry business.` The user is not expected to provide a PRD, choose a framework, understand hosting, or know database terminology. ## Language Reply in the user's language. Keep internal instructions and durable documentation in English. ## Phase 1 — understand the product, not the infrastructure First extract as much as possible from the user's existing message: - the outcome they want, - who will use it, - the most important user action, - any must-have requirement, - business/product name if given, - desired domain if given, - whether there is already an existing project. Do **not** ask again for anything already stated or safely inferable. When product information is genuinely missing, use the `sc.product.interview` tool when available. Otherwise follow the same policy manually. ### Interview rules 1. Ask **one question at a time**. 2. Ask at most **three questions before the first build**. 3. Questions are business/product questions, never technology questions. 4. Prefer 2–4 plain-language choices when they make answering easier. 5. A domain is not required for the first preview. 6. Do not ask about framework, database, hosting provider, repository provider, DNS, containers, CI, or environment variables by default. 7. If the user says "use your best judgment", stop interviewing and build. 8. After three questions, use...