netlify-frameworks

Translate framework server-side behavior into Netlify Functions and Edge Functions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MichaelFrieze/riffatlas --skill netlify-frameworks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: netlify-frameworks
Source: https://github.com/MichaelFrieze/riffatlas/tree/main/.agents/skills/netlify-frameworks
Command: npx skills add https://github.com/MichaelFrieze/riffatlas --skill netlify-frameworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Netlify deployments often break for modern frameworks because SSR, routing, and build outputs require framework-specific integration rather than plain static hosting.

Core Features & Use Cases

  • Framework detection: Identify whether a project is Astro, Next.js, Nuxt, Vite/React, TanStack Start, or SvelteKit by checking config files.
  • Adapter-based SSR translation: Configure how server-side routes, API endpoints, redirects, and middleware are converted into Netlify Functions and Edge Functions during the build.
  • Routing and 404 handling: Apply SPA catch-all redirects and appropriate 404 strategies for static versus SSR frameworks.
  • Environment variable compatibility: Map framework-specific client prefixes (VITE_, PUBLIC_, NEXT_PUBLIC_, NUXT_PUBLIC_) and clarify server-side access patterns.

Quick Start

Use the netlify-frameworks guide to set up the correct Netlify adapter/plugin for your framework (for example, Vite with @netlify/vite-plugin or Next.js runtime) and configure SPA redirects or SSR 404 handling accordingly.

Frequently Asked Questions about netlify-frameworks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js SSR app to Netlify?

Deploying Next.js SSR to Netlify requires applying the correct runtime adapter that translates server-side routes and API endpoints into Netlify Functions during the build process.

Why does my Astro or SvelteKit build break on Netlify?

Astro and SvelteKit builds break on Netlify because SSR, routing, and build outputs require framework-specific integration rather than plain static hosting configurations.

How do I handle SPA client routing and 404 redirects on Netlify?

To handle SPA client routing on Netlify, you must apply framework-specific catch-all redirects and appropriate 404 strategies for static versus SSR frameworks.

Do I need specific build settings for Vite and React on Netlify?

Vite and React deployments require applying the @netlify/vite-plugin to correctly configure build and publish settings alongside SPA redirects if needed.

How do environment variable prefixes work for Nuxt and Vite on Netlify?

Environment variable prefixes like VITE_ and NUXT_PUBLIC_ must be mapped correctly according to framework-specific client access patterns to ensure proper server-side availability.

Does Netlify support TanStack Start framework deployments?

Yes, Netlify supports TanStack Start by detecting its configuration files and applying the correct SSR adapters to convert server-side behavior into Netlify Functions.