Form Error States

What it does

Designs accessible, recoverable validation and submission errors that never discard what the visitor typed.

When to use it

Use for inline validation, error summaries, server failures, or auditing vague and inaccessible errors.

Problems it prevents

Stops a form clearing itself and showing a vague error after a failed submission.

Typical workflow

1. Define the error model (inline vs summary)
2. Preserve entered values on failure
3. Manage focus to the first error
4. Write specific, actionable error copy

Example output

A form that keeps every typed value after a failed submit, with focus sent straight to the first real problem.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• FocusedForm Success States

  Designs truthful, accessible success states that confirm completion only once the server has actually accepted it.

• SystemAccessibility

  Checks keyboard navigation, screen-reader semantics, colour contrast and focus handling across any interface.

• FocusedPassword Visibility

  Implements accessible password show/hide controls without weakening authentication safety.