forms
Skill9 starsChanged 2 months agoMITView on GitHub
Accessible forms, field/form errors, submit pending, wizards, progressive disclosure. Use when building or fixing forms, login, settings, checkout, filters, "validasi", "form error", or multi-step flows.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- AnyOrgName/php-skillstheir own version, first seen Nov 8, 2026
- Anglesite/anglesite-skillstheir own version, first seen Oct 27, 2026
- VectorLabAU/skillstheir own version, first seen Oct 11, 2026
- trycompai/comptheir own version, first seen Oct 8, 2026
- msrv-tech/skillstheir own version, first seen Oct 2, 2026
- mgifford/accessibility-skillstheir own version, first seen Jul 27, 2026
Used with
Projects with it also use navigation.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
igorescodroSkillnavigation
Use when adding a new screen or modifying navigation in the Alkaa project — triggers on tasks like "add a new screen", "navigate to X", "add destination", "wire up navigation", or "create a navigation event". Also triggers when connecting UI actions to routes in NavGraph.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- trycompai/comp★ 2.1ksame name
- msrv-tech/skills★ 60same name
- mgifford/accessibility-skills★ 48same name
- Anglesite/anglesite-skills★ 15same name
- YepAPI/skills★ 8same name
- AnyOrgName/php-skills★ 4same name
- moasq/ios-dev-agent★ 4same name
- miovrag/claude-skills★ 1same name
- VectorLabAU/skills★ 1same name
- anipy1/claude-flutter-kit★ 0same 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 repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/design-system-enforcer.mdcCursor rule
- frontend-expertSkill
- accessibilitySkill
- anti-slop-codeSkill
- anti-slop-designSkill
- app-shellSkill
- architectureSkill
- componentsSkill
- content-designSkill
- data-fetchingSkill
- design-colorSkill
- design-directionSkill
- design-foundationsSkill
- design-surfacesSkill
- design-typographySkill
- design-vocabularySkill
- devtoolsSkill
- engineering-vocabularySkill
- fidelitySkill
- frontend-expertSkill
- marketingSkill
- monitoringSkill
- motion-inspectionSkill
- motionSkill
- performanceSkill
- polishSkill
- prototypeSkill
- quality-loopSkill
- responsiveSkill
- seoSkill
- skill-authoringSkill
- testingSkill
- tokensSkill
- webglSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 22
Read-only detail with no inputs
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forms & Validation
Overview
Forms must be keyboard-accessible, show clear errors, and never lose user input on soft failures.
When to use
- Any form, wizard, filter bar with submit
- Auth, settings, checkout, create/edit dialogs
When to skip
- Read-only detail with no inputs
- Pure button that is not a form submit
MUST (ship)
| Rule | Detail |
| Labels | Every control has a visible label or aria-label; htmlFor/id associated |
| Errors | Text + association (aria-describedby / equivalent) — not border-only |
| Submit | Pending/disabled while in flight; values kept on 4xx/5xx |
| Focus | On submit failure, move focus to first invalid field |
| Mobile | Primary submit width: 100% below 768; inputs font-size ≥ 16px |
| No Lorem | Real hint/error copy |
| Selects | Product filters / status pickers: prefer custom select (see components) — not bare native OS chrome |
Workflow
- Labels — visible label (or
aria-label); associate withhtmlFor/id - Validation — prefer inline field errors after submit or on blur; don’t block typing with aggressive live errors
- Submit — disable or show pending on the primary button; keep values on error
- Errors — field-level + optional form-level summary with links to fields
- Progressive disclosure — hide advanced fields until needed
- Mobile — full-width primary submit; adequate tap targets (
responsive) - Async submit — pair with
data-fetchingfor retry/toast; never wipe the form on soft fail
Agent boundaries
- May decide: validation timing (submit vs blur), wizard step count, inline vs summary errors
- Must not: invent purple/error hex off-token; skip labels for “clean UI”; use
alert()for validation
Checklist
- Labels + focus order correct
- Error text linked to fields (
aria-describedby/ equivalent) - Pending + error + success submit states
- First invalid field focused after failed submit
- No Lorem placeholder as the only copy
- Full-width primary + ≥16px inputs at 320px
- Works at 320px width (no horizontal overflow)
Depth
references/forms.md. A11y: accessibility. Responsive: responsive.
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.