fix: restrict Astro template selection to explicit requests + tsconfig mismatch guard

- Template selection now requires explicit 'Astro' mention (rule 6 narrowed)
- Added IMPORTANT default guidance: when in doubt use Vite Shadcn
- Rule 10 expanded: forms, contact pages, interactive UIs → Vite Shadcn
- Rule 11 expanded: calculators, todo apps, CRUD apps → Vite Shadcn
- Added TSCONFIG CONSISTENCY section to system prompt
- Prevents framework mismatch: React code + Astro tsconfig = build failure

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: zebbern

app/lib/common/prompts/new-prompt.ts

@@ -539,6 +539,11 @@ export const getFineTunedPrompt = (
     - Template package.json has critical peer deps (@radix-ui/*, class-variance-authority, clsx, tailwind-merge, etc.). Omitting any causes cascading build failures.
     - REVERSE CHECK: Also scan for imports that are NOT used in the file. If a package is imported but no exported name from it appears in the code, REMOVE that import. Clean code has zero unused imports.
 
+  TSCONFIG CONSISTENCY (CRITICAL — FRAMEWORK MISMATCH ERRORS):
+    - If you are writing React code, tsconfig.json MUST use "jsx": "react-jsx" and MUST NOT extend "astro/tsconfigs/strict" or any Astro config.
+    - If the template's tsconfig.json has "extends": "astro/tsconfigs/strict" but you are building a React project, you MUST rewrite tsconfig.json with a React-compatible config.
+    - SELF-CHECK: Does tsconfig.json match the framework you're using? React needs "react-jsx", Vue needs vue-tsc, Svelte needs @tsconfig/svelte.
+
   FOLLOW-UP RESPONSE DISCIPLINE (CRITICAL):
     - When the user asks to fix SPECIFIC files, ONLY modify those files — no unnecessary config rewrites.
     - Do NOT re-create package.json, tsconfig, vite.config, tailwind.config, utility files, or seed data unless asked.

app/utils/selectStarterTemplate.ts

@@ -256,18 +256,20 @@ const starterTemplateSelectionPrompt = (
   showcaseTemplates: PromptTemplate[] = [],
 ) => `You pick the best starter template for a user's project. Respond ONLY with the XML selection — no explanation.
 
+IMPORTANT: When in doubt, default to "Vite Shadcn". Most web projects (forms, apps, dashboards, UIs) should use React via Vite Shadcn. Only use Astro if the user EXPLICITLY says "Astro" or asks for a multi-page static content site with NO interactivity (pure blog, docs site with markdown).
+
 Decision rules (in priority order):
 1. If the user explicitly names a framework (Vue, Svelte, Angular, SolidJS, Qwik, Remix, Astro, Expo), use that framework's template — this overrides rules 2-13.
 2. Trivial tasks (scripts, algorithms, CLI tools, API-only, no UI) → blank
 3. Game, canvas, WebGL, 3D (three.js), or animation-heavy → Vite React (lighter, no UI overhead)
 4. Presentation or slides → Slidev
 5. Mobile app (iOS, Android, React Native, cross-platform) → Expo App
-6. Static site, blog, or documentation → Basic Astro
+6. Static content-only site (blog with markdown, documentation site, no interactive UI) AND user explicitly says "Astro" → Basic Astro
 7. Vanilla/plain JavaScript (no framework) → Vanilla Vite
 8. TypeScript-only project (no UI framework) → Vite Typescript
 9. Fullstack React with SSR or API routes → NextJS Shadcn
-10. Specific site type (portfolio, dashboard, SaaS, e-commerce, landing page) → matching showcase template if available, otherwise Vite Shadcn
-11. Any other web project → Vite Shadcn as default
+10. Specific site type (portfolio, dashboard, SaaS, e-commerce, landing page, form, contact page) → matching showcase template if available, otherwise Vite Shadcn
+11. Any other web project (including forms, calculators, todo apps, CRUD apps, interactive UIs) → Vite Shadcn as default
 
 Starter templates:
 <template><name>blank</name><description>Empty starter for simple scripts</description><tags>basic, script</tags></template>