What problem does it solve? Deploying a framework to Netlify involves framework-specific adapters, build commands, publish directories, SSR/edge routing, and env var rules that differ per framework — getting any of them wrong causes silent failures like SSR pages serving static HTML or env vars not updating. ## Core Features & Use Cases - Framework adapter setup: Step-by-step SSR/edge adapter configuration for Next.js, Astro, SvelteKit, Nuxt, Remix, React Router, TanStack Start, SolidStart, Gatsby, Angular, Hydrogen, and Express. - Build settings reference: A lookup table of build commands and publish directories for 20+ frameworks, plus SPA redirect rules and the SSR catch-all footgun. - Env var and local dev rules: Build-time env injection semantics, client-prefix secret warnings, and Vite-plugin-based local platform emulation without the Netlify CLI. - Use Case: Your Next.js site on Netlify serves stale pages after deploys — the skill tells you to enable skew protection via NETLIFY_NEXT_SKEW_PROTECTION and, for Next below 14.1.4, add experimental.useDeploymentId in next.config.js. ## Quick Start Ask the agent to configure your framework project for Netlify deployment, for example: set up my SvelteKit app with the Netlify adapter and correct build settings.