Form audit skill

# Form Check Inspect forms on a Framer page before launch. Report problems visible in the project, and separate configured settings from behavior that requires a published-site test. ## Scope - Review every form on the selected or named page unless the user specifies one. - If the page has no forms, report that and stop. Do not create a form. - If no page is selected or named, use the current page. If that cannot be identified, ask which page to review. - Identify each form as native Framer, a code component, or a third-party embed. Mark settings controlled elsewhere as unverified. ## Checks 1. Confirm that each submit button is linked to the intended form and has a clear label. Its position outside the form container is not an issue if the link is correctly configured. 2. Check each field’s input type, submission name, required setting, and visible label. Placeholder text alone is not a visible label. For checkbox and radio groups, check group and option labels. 3. Inspect Send To. Report a missing destination as a launch blocker. Check configured email, Google Sheets, or webhook settings. Check email verification only if its status is visible. A configured destination does not prove delivery. 4. Inspect the button’s available loading, success, error, and incomplete states. Report unclear or misleading feedback, but do not require every optional visual state. Describe states as configured, not tested. 5. Check desktop and phone layouts for clipped fields, unreadable labels, overlapping messages, or an unreachable button. ## Output Start with a one-sentence readiness assessment that names the page path and form. Report findings under two headings: ## Launch blockers Number each blocker separately. Under each number, give: - Issue: What is wrong. - Evidence: The exact setting or content inspected. - Fix: One specific action. ## Improvements Use the same numbered Issue / Evidence / Fix format for changes that would improve the form but do not block launch. Then add: - Passed inspection: A brief summary, without listing every field. - Unverified: Settings or behavior the Agent could not inspect. - Manual test: The steps needed on the published site to verify validation, feedback, and delivery. Do not use a Markdown table. Do not explain why a finding belongs in its category when the evidence already makes that clear. Do not call an improvement a launch blocker unless it prevents submission or creates a serious accessibility problem. ## Rules - Do not infer runtime behavior from a configured state or link. - Do not suggest changing required fields without evidence that the requirement is wrong. - Do not invent a fallback email address or destination. - Do not submit a real entry or change the form unless the user asks. - Do not claim the form works end to end until delivery is confirmed.