What problem does it solve? Netlify site configuration is scattered across netlify.toml, the dashboard UI, and CLI-managed environment variables, with subtle precedence rules and silent misconfiguration traps. This Skill provides a complete reference for writing correct netlify.toml files and managing environment variables without falling into common pitfalls. ## Core Features & Use Cases - Complete netlify.toml syntax: Covers build settings, redirects (splats, path parameters, conditions, force), headers, deploy contexts, functions, edge functions, plugins, Image CDN, and the [dev] block. - Precedence and gotcha guidance: Documents that netlify.toml overrides UI settings, that _redirects files are processed before toml rules, that redirects/headers cannot be scoped to deploy contexts, and that toml-declared variables are build-scoped only. - Environment variable management: Covers Netlify CLI commands (env:set, env:get, env:list, env:import, env:unset) with context scoping and secret handling. - Use Case: You set a custom command and targetPort in the [dev] block but netlify dev ignores your command — this Skill explains that framework must be "#custom" in that combination. ## Quick Start Ask the assistant to write a netlify.toml with a SPA catch-all redirect, security headers, and production-only environment variables for your site.
