What problem does it solve? Deploying frameworks with server-side rendering, API routes, or middleware to Netlify requires the correct adapter or plugin, and misconfiguration causes silent failures like shadowed SSR routes, missing runtime files, or undetected forms. This Skill provides per-framework guidance for Vite/React, Astro, TanStack Start, Next.js, Nuxt, and SvelteKit so deployments work the first time. ## Core Features & Use Cases - Framework Detection: Identify the framework from config files like astro.config.*, next.config.*, or svelte.config.* and route to the right reference guide. - Adapter & Plugin Setup: Configure @astrojs/netlify, @sveltejs/adapter-netlify, @netlify/vite-plugin, @netlify/vite-plugin-tanstack-start, or the automatic Next.js runtime and Nuxt Nitro preset. - Local Development Options: Choose between netlify dev and the Netlify Vite plugin family for local access to Functions, Blobs, DB, and environment variables. - Pitfall Prevention: Avoid SPA catch-all redirects shadowing SSR routes, ENOENT errors from untraced runtime file reads, and forms that Netlify never detects. - Use Case: A developer migrating a client-rendered React SPA to SvelteKit with SSR uses this Skill to install the adapter, remove the stale /* → /index.html redirect, and set up local dev with Netlify platform primitives. ## Quick Start Ask the assistant to set up your framework project for Netlify deployment, naming your framework such as SvelteKit or Astro.
