agentleFS
Sign inStart free
botirkhaltaevbotirkhaltaev/botir-skills/skills/form-ux/SKILL.md

form-ux

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Form design UX: labels, structure, validation timing, error placement, progressive disclosure, and accessibility of forms. Use when designing or reviewing forms, multi-step wizards, checkout/settings inputs, or fixing validation and input-error UX. Triggers on: "form design", "validation UX", "input errors", "form labels", "inline validation", "multi-step form", "wizard UX", "accessible forms".

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Labels: always visible (above input by default).

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Form UX

Collect required data with minimal friction. Pattern overview also in interaction-design-patterns; this skill is the deep dive.

Essentials

  • Labels always visible (above input by default); never placeholder-as-label
  • One column for most forms; group with headings/fieldsets
  • Validate on blur (and on submit); not on every keystroke unless formatting aids (phone)
  • Errors next to fields: what / why / how; preserve input
  • Required marked; optional unmarked
  • Progressive disclosure — show advanced/rare fields only when needed
  • Accessible — <label for>, errors announced, keyboard complete

Structure sketch

[ Step 2 of 3 ●●○ ]
Shipping
  Full name *
  Address *
  Apt / suite        ← optional, unmarked
              [Continue]

Reference Map

  • references/labels-and-structure.md — labels, layout, grouping, disclosure
  • references/validation-and-errors.md — timing, placement, messaging
  • references/form-accessibility.md — names, errors, keyboard, WCAG map

Related Skills

  • For pattern context / navigation / loading → use interaction-design-patterns
  • For empty/error recovery surfaces → use error-empty-states
  • For a11y POUR / contrast → use a11y-accessibility-design
  • For mobile keyboards / targets → use mobile-touch-design
  • For microcopy tone → use ux-writing-content-design

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free