Netlify Forms Playbook

Guide for using Netlify Forms for HTML form handling. Use when adding contact forms, feedback forms, file upload forms, or any form that should be collecte

---
name: netlify-forms
description: Guide for using Netlify Forms for HTML form handling. Use when adding contact forms, feedback forms, file upload forms, or any form that should be collected by Netlify. Covers the data-netlify Use when working with Netlify Platform, Edge Functions, Netlify CLI.
triggers:
  - netlify forms
  - netlify platform
  - edge functions
---

# Netlify Forms Playbook

## 1. When to Use This Skill
Load `skill-netlify-forms` whenever an engineering, architecture, or operations task involves **Netlify Platform, Edge Functions, Netlify CLI**. Specifically:
- Guide for using Netlify Forms for HTML form handling. Use when adding contact forms, feedback forms, file upload forms, or any form that should be collected by Netlify. Covers the data-netlify
- Designing, reviewing, refactoring, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight validation and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Netlify Platform, Edge Functions, Netlify CLI
- **Permissions Boundary:** Read-only inspection by default; ask for explicit human confirmation before executing destructive mutations or production deployments.
- **Reference Specification:** `https://github.com/netlify/netlify-mcp`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `tsconfig.json`, `pyproject.toml`, `Cargo.toml`, `wrangler.jsonc`, or schema declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical production patterns for **Netlify Platform**:
   - Enforce strict schema and type validation at every external boundary.
   - Include explicit error handling, structured telemetry, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or managed secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
npx netlify status
npx netlify build --dry
npx netlify deploy --build
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a build, migration, test run, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide