Reference for netlify.toml configuration. Use when configuring build settings, redirects, rewrites, headers, deploy contexts, environment variables, or any site-level configuration. Covers the complete netlify.toml syntax including redirects with splats/conditions, headers, deploy contexts, functions config, and edge functions config.
98
100%
Does it follow best practices?
Impact
92%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
SPA routing, headers, and deploy contexts
SPA catch-all redirect
100%
100%
Catch-all is last redirect
100%
100%
Build publish directory
100%
100%
Production build context
0%
100%
Deploy-preview build context
100%
100%
Production API env var
100%
100%
Deploy-preview API env var
100%
100%
Security headers present
100%
100%
Headers TOML structure
100%
100%
Asset cache headers
100%
100%
No secrets in toml
100%
100%
TOML file at root
100%
100%
Proxy, geo-routing, force override, scheduled function
Permanent redirect for /shop
100%
100%
Splat syntax used
100%
100%
Country/language condition
80%
100%
Conditional redirect to /fr
100%
100%
API proxy redirect
100%
100%
Proxy custom header
100%
100%
Admin force override
100%
100%
Specific rules before catch-all
100%
100%
Functions node_bundler
0%
0%
Scheduled function syntax
100%
100%
Functions directory configured
0%
0%
No path parameters confused with splat
100%
100%
Edge functions, image CDN, dev server, plugins
Edge function path mapping
100%
100%
Edge function TOML syntax
100%
100%
Deno import map configured
100%
100%
Remote images pattern
100%
100%
Remote images as list
100%
100%
Dev targetPort set
100%
100%
Dev framework auto
100%
100%
Dev port configured
0%
0%
Plugin package name
100%
100%
Plugin inputs section
100%
100%
netlify.toml at root
100%
100%
cffaf74
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.