Prompt To App Generation

User opens bolt.new and types: 'Build a marketing site with a blog and SSR; I want it deployed to Netlify.' Bolt must pick a starter framework that fits SSR + Netlify-friendly output.

Pick a framework whose default build output is Netlify-deployable without extra config (e.g., Next.js, Astro, SvelteKit, Remix). State the choice in chat with one sentence of rationale before scaffolding so the user can correct on turn 1 without burning more tokens. Do not pick a CSR-only Vite + Re…

First-turn scaffold for a Next.js app. The chat declares it will create app/, components/, lib/, package.json, next.config.js, but the diff only contains app/ and package.json.

Every file the chat declares it will create must appear in the applied diff. The WebContainer preview must boot — missing next.config.js or tailwind.config.js when the prompt asked for Tailwind is a scaffold failure. If a file is intentionally deferred, say so explicitly in chat.

Initial scaffold writes package.json with 'react': '*' and 'next': 'latest' for the user's Next.js app.

Pin to exact or caret-pinned versions known to work together in WebContainer (e.g., 'next': '^14.2.0', 'react': '^18.3.0'). '*' and 'latest' are reproducibility hazards — every fresh install may resolve to a different working tree. Surface the pinned versions in chat so the user knows what was chos…