form-ux
Skill12 starsChanged 11 days agoMITView on GitHub
Form UX and accessibility pass. Use for forms, inputs, checkout, signup/login, validation, labels, autocomplete, mobile keyboards, inline errors, required fields, disabled submits, and field-level accessibility.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- botirkhaltaev/botir-skillstheir own version, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- botirkhaltaev/botir-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- a11y-passSkill
- art-directionSkill
- cognitive-a11ySkill
- color-systemSkill
- component-statesSkill
- data-vizSkill
- design-system-interviewSkill
- deslop-uiSkill
- empty-statesSkill
- humanize-copySkill
- i18n-readySkill
- improve-existing-websiteSkill
- micro-motionSkill
- responsive-layoutSkill
- spacing-systemSkill
- tastecheck-passSkill
- tasterollSkill
- themingSkill
- web-typographySkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Start with outcome, risk, and data authority, not an inherited input array.
- Very specific: line 37
Put specific adjacent “what + fix” errors behind aria-invalid/aria-describedby.
- Distinctive: line 39
Never silently disable submit.
- Very specific: line 43
Use [what is wrong] + [how to fix it] (+ example), plainly and without blame.
- Very specific: line 66
Use references/patterns.md for markup/wiring.
- Distinctive: line 70
Ask only necessary fields.
- Distinctive: line 87
No silent disabled submit.
- Very specific: line 101
Stop / handoff: Stop when validation rules or data ownership are unknown.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Form UX
A form is a completion path: reduce effort, prevent predictable errors, and make failure truthful, repairable, and accessible.
Model task before styling
Start with outcome, risk, and data authority, not an inherited input array. Remove, defer, or explain each field through this contract:
| Field contract | What to decide |
| User value | What completing this field unlocks now, in the user's words |
| Data rule | Required/optional condition, source of truth, and whether the rule is client- or server-owned |
| Input affordance | Label, type, inputmode, autocomplete, format help, and a safe example |
| Validation moment | What can be checked while editing, on blur, on submit, or only after a server request |
| Recovery | Exact message, preserved value, focus destination, and next available action |
| Sensitivity | Whether the field is personal, financial, irreversible, or must never be persisted locally |
Unknown rule/ownership stays unresolved; never invent validation; group by task, not database/API shape.
Non-negotiables
- Persistent associated label; visible required/optional state; correct type, inputmode, autocomplete, and one-column task flow (short related pairs excepted).
- Validate on submit. Validate on blur only when the value is complete enough to judge; after an error, re-check while the person repairs it. Keep server truth server-owned.
- Put specific adjacent “what + fix” errors behind
aria-invalid/aria-describedby; announce and focus the first error on failed submit. - Never silently disable submit; retain visible focus and explain what is missing.
Error-message formula
Use [what is wrong] + [how to fix it] (+ example), plainly and without blame. Tie it
visually/programmatically to the field; long-form summaries link to inline errors.
Validation is a conversation
Give feedback at the earliest truthful moment; browser checks never impersonate server truth. On submit distinguish field errors (focus/retain), conflict (correct branch), transient failure (preserved draft/safe retry), authorization (boundary/route), and irreversible payment (duplicate lock plus receipt/status). Pending work has accessible label/status, rejects duplicates, and restores an explained route on failure. Ignore stale responses so older validation cannot overwrite current value.
Worked contract
| Field | Rule owner | When to check | Repair path |
| server owns account availability; client owns basic shape | submit; blur after a complete address; re-check while repairing | “Enter an address like name@example.com.” Preserve the value; announce an account conflict only after the server responds. |
The row separates local affordance from server authority. Apply it to cross-field rules, invitation codes, inventory, pricing, and payment status.
Quick-start
Use references/patterns.md for markup/wiring; retain this field contract.
Reduce effort
Ask only necessary fields; defer optional data. Use safe defaults/autofill, nonblocking formatting, password reveal/paste, inline help, preserved input, and saved progress.
Reference files
references/patterns.md— types, validation, mobile/autofill, and a11y wiring.references/decision-records.md— novel-case ADR rules.
Evidence
Establish task, fields, rule owner, success/risk/interruption before styling. Record each
field/state, validation owner, and recovery; n/a needs subject absence, not unknown rule.
Self-check
- Field contract, labels, required state, types/autofill, and keyboard/screen-reader wiring complete?
- Submit/blur/repair timing, stale async responses, specific adjacent errors, first-error focus, and retained input work?
- No silent disabled submit; pending, duplicate, conflict, authorization, and irreversible outcomes differ?
How to deliver
Deliver one field/state matrix with source rule, affordance, owner/timing, recovery, pending behavior, evidence, and risk; hand adjacent concerns to their skills.
<!-- contract:v1:start -->Contract (generated)
Canonical detail: contract.json.
- Route: A form has completion, validation, recovery, autofill, or interruption problems.; avoid: The issue is only a control's visual interaction state.
- Exclude: Do not hide errors or validate only on blur without a recovery path. (+1 in contract.json)
- Stop / handoff: Stop when validation rules or data ownership are unknown. (+1 in contract.json); receives [component-states, design-system-interview, deslop-ui, humanize-copy, responsive-layout, spacing-system, tasteroll] -> sends [a11y-pass, i18n-ready, tastecheck-pass, cognitive-a11y]
- Output: completion-oriented form flow and evidence table
- Evidence:
table_with_evidencewithstatus,reason,remediation,evidence,provenance.
<!-- contract:v1:end -->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
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.