HTML Form Documenter skill for Claude and Codex
Reference documentation for an existing HTML form that developers, QA, and product can share: purpose, a field-by-field table with types, constraints, and…
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 an existing form needs a shared spec document with a field table, validation rules, and submission contract for developers, QA, and product to work from. Do not use for auditing the form for accessibility problems, or debugging why it fails to submit. Related topics: coding, html.
What it will ask you for
- Form markup (longer free text)
- Documentation style (choose one: Brief, Detailed, Technical, Friendly)
- Include validation notes (choose one: Yes, No)
- Target audience (choose any: Developers, QA, Designers, Product Managers)
- Output format (choose one: Markdown, HTML, Plain text)
- Where it submits (free text, e.g. "Endpoint and method if not visible in the markup")
How it works
- Write the Overview: what the form collects, where and how it submits, and what success looks like.
- Build the Fields table with label, name, type, required, default, constraints, and autocomplete token per control in source order.
- State each validation rule in plain language with its user-facing message and who enforces it, when validation notes are on.
- Add the audience-specific sections selected: submission contract, QA test matrix, UI states, or product summary.
- Write the Example usage section with a filled submission and the resulting payload, then trim to the chosen style.
What you get
A document in the chosen format with sections Overview, Fields (table), Validation when enabled, audience sections as selected, and Example usage, with no commentary outside the document.
What it watches out for
- Documenting the visible label but not the name attribute, which is the only identifier the backend and the tests use.
- Listing validation rules without the message the user sees, so QA cannot write the expected result.
- Describing the form as it should behave rather than as the markup actually behaves, which hides bugs in the spec.
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.