HTML Form Debugger skill for Claude and Codex
A targeted diagnosis of why an HTML form will not validate or submit: the exact markup or JavaScript flaw with its line, why it produces the symptom you see…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a form does nothing on submit, shows a validation bubble it should not, reloads the page, or sends the wrong data and the user has the markup and script. Do not use for a general accessibility or structure audit of a working form, or server-side handler bugs. Related topics: coding, html.
What it will ask you for
- HTML source (longer free text)
- JavaScript handling (longer free text)
- Observed error (free text, e.g. "Error message or what happens instead")
- Browser (choose one: Chrome, Firefox, Safari, Edge, Other)
- Form method (choose one: GET, POST)
- Expected behaviour (free text, e.g. "What should happen on submit")
- Server-side symptoms (free text, e.g. "request never arrives or arrives with empty fields or 415 error")
How it works
- Match the symptom to a failure class (no action, blocked by validation, unintended reload, wrong payload) so the search starts in the right layer.
- Check the markup in order: submit control association, name attributes, required and pattern attributes, hidden required fields.
- Check the script for preventDefault timing, listener attachment, stopped propagation, FormData source, and body versus content-type mismatch.
- Consult browser-specific behaviour for the selected browser only after the generic causes are ruled out.
- Name the root cause with its line, explain how it produces the observed symptom, and give the minimal corrected snippet.
What you get
A markdown report with sections Summary (one line), Identified issues (each with line reference and effect), and Suggested fixes (exact snippets), plus one line on how to confirm it works.
What it watches out for
- Overlooking a field without a name attribute, which is valid HTML and silently never reaches the server.
- Blaming the fetch code when a hidden required input is blocking native validation with no visible message.
- Rewriting the whole form instead of the one line at fault, which loses the user's styling and makes the fix hard to review.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.