What problem does it solve? Netlify projects are configured through netlify.toml and the _headers/_redirects files, but the rules are full of footguns — env vars set in netlify.toml never reach functions at runtime, redirects and headers cannot be scoped per branch, and secrets in client-prefixed vars leak into bundles. This Skill gives an agent the exact syntax, precedence rules, and constraints needed to write correct configuration the first time. ## Core Features & Use Cases - Build and context configuration: Set build commands, publish directories, Node/tool versions, and per-context overrides for production, deploy previews, branch deploys, and local dev. - Redirects, rewrites, and headers: Write redirect/rewrite/proxy rules with splats, query params, country/language conditions, signed proxy redirects, custom headers, and SPA fallbacks. - Environment variables and secrets: Scope variables correctly across Builds, Functions, Runtime, and Post processing, mark secrets with the Secrets Controller, and avoid committing .env snapshots. - Use Case: A user asks why their env var is undefined inside a Netlify Function — the Skill explains that netlify.toml vars only get Builds and Post processing scopes and shows the fix using netlify env:set. ## Quick Start Ask the agent to add an SPA fallback redirect and a production-scoped environment variable to your Netlify site configuration.
