form-design-encyclopedia
Skill58 starsChanged 23 days agoApache-2.0View on GitHub
200+ form patterns covering every input type, layout, validation strategy, multi-step wizard, and error state, with production React and CSS, accessibility requirements, and mobile optimization. Use when building or fixing a form, choosing a validation approach, or reducing abandonment on signup and checkout.
In this repository44 other files it gives its agents.
- accessibility-inclusive-designSkill
- agentic-ai-generative-uxSkill
- ai-design-generationSkill
- ai-spatial-voice-uxSkill
- ambient-calm-zero-uiSkill
- animation-recipe-librarySkill
- business-design-templatesSkill
- cognitive-psychology-uxSkill
- color-palette-librarySkill
- component-patterns-codeSkill
- conversion-optimization-patternsSkill
- cross-cultural-i18n-uxSkill
- data-visualization-masterySkill
- design-critique-case-studiesSkill
- design-memorySkill
- design-process-methodsSkill
- design-systems-architectureSkill
- design-token-presetsSkill
- desktop-app-designSkill
- figma-design-tool-workflowsSkill
- icon-illustration-systemsSkill
- image-media-patternsSkill
- interaction-motion-designSkill
- layout-block-intelligenceSkill
- micro-copy-intelligenceSkill
- mobile-ux-designSkill
- navigation-pattern-encyclopediaSkill
- nng-ux-heuristicsSkill
- page-composition-engineSkill
- performance-states-patternsSkill
- platform-visual-standardsSkill
- reference-intelligenceSkill
- responsive-block-patternsSkill
- screen-flow-patternsSkill
- sector-style-intelligenceSkill
- shadow-elevation-densitySkill
- sumi-orchestratorSkill
- typography-pairing-recipesSkill
- ui-pattern-intelligenceSkill
- ui-visual-design-systemSkill
- ux-ethics-content-strategySkill
- ux-metrics-measurementSkill
- ux-research-methodsSkill
- visual-design-masterySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Every field is a request for effort, and the user is deciding continuously whether the thing they came for is still worth it.
- Distinctive: line 25
Every field earns its place: If nobody can name the decision a field informs, it is decoration with a compliance cost.
- Distinctive: line 30
Every input in the catalog implements these six states.
- Distinctive: line 69
When the pattern applies and when it does not
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Design Encyclopedia — Every Form Pattern
Mental model
Every field is a request for effort, and the user is deciding continuously whether the thing they came for is still worth it. So the discipline is subtraction: the best form change is almost always deleting a field.
- One column. Multi-column forms cause skipped fields and mis-scanning. The exception is genuinely paired data — city and postcode, expiry and CVC.
- Labels above inputs. Fastest to scan, survives translation, survives narrow screens. Placeholder-as-label is an accessibility failure and a memory burden the moment someone starts typing.
- Validate on blur, not on keystroke. Validating while someone is still typing tells them they are wrong before they have finished being right. Re-validate on submit; show errors inline, next to the field, never only at the top.
- An error message names the fix, not the failure. "Enter a date in the past" beats "Invalid date".
- Every field earns its place. If nobody can name the decision a field informs, it is decoration with a compliance cost.
Constants
Every input in the catalog implements these six states. A field missing focus or error is not finished.
default · focus · filled · disabled · error · successTouch target minimum 44x44px. Label-to-input gap 8px. Field-to-field gap 20-24px. Error text sits directly beneath its field, never floating.
Index
| Need | Reference |
| A specific input type — text, email, phone, date, file, OTP, rich text | input-field-catalog.md |
| Password strength meter, masked input, currency, percentage | input-field-catalog.md |
| The six field states as code | input-field-catalog.md |
| Single column, two column, card-based, inline layouts | form-layout-patterns.md |
| Login, signup, contact, payment, address, settings, survey forms | form-layout-patterns.md |
| When to validate and what to say | validation-error-patterns.md |
| 100+ ready error message templates | validation-error-patterns.md |
| Splitting a long form into steps | multi-step-form-patterns.md |
| Step indicators, back navigation, data persistence | multi-step-form-patterns.md |
| Labels, required marking, error association, group labels | form-accessibility-code.md |
| Why people abandon, and what to instrument | form-analytics.md |
Reference architecture
| File | Covers | Lines |
references/form-layout-patterns.md | 19 layouts + specialized forms | 2344 |
references/input-field-catalog.md | 55 input types, all states | 1539 |
references/multi-step-form-patterns.md | wizards, steppers, persistence | 1151 |
references/form-accessibility-code.md | semantic HTML, ARIA, errors | 1025 |
references/validation-error-patterns.md | timing, anatomy, 100+ templates | 780 |
references/form-analytics.md | measuring form performance | 69 |
What every reference file contains
- When the pattern applies and when it does not
- Complete React plus CSS, with all six states rendered
- The ARIA wiring — label association, error announcement, group semantics
- Mobile behaviour: keyboard type, autocomplete token, target size
- The failure mode that pattern is known for
Routing
For a specific input — the field-state reference plus every input type from
text and icon-prefixed through to password strength meters: read
references/input-field-catalog.md.
For arranging a form — single column, two column, card-based and the rest of
the nineteen layouts, plus the specialized login, signup, contact, payment,
address, settings and survey forms: read references/form-layout-patterns.md.
For validation and errors — timing strategy, error message anatomy, 100+
message templates, and warning patterns: read
references/validation-error-patterns.md.
For multi-step flows — when to split at all, step indicators, navigation
between steps, and data persistence: read
references/multi-step-form-patterns.md.
For accessibility — semantic HTML foundations, label association methods,
required-field marking, error association and group labeling: read
references/form-accessibility-code.md.
For odds and ends — the patterns that had no home in the files above when this skill was converted to a router: read references/form-supplementary.md.
Cross-References
- component-patterns-code (React component implementations)
- micro-copy-intelligence (error messages, helper text, button labels)
- conversion-optimization-patterns (form conversion, CTA optimization)
- accessibility-inclusive-design (WCAG compliance, screen reader testing)
- mobile-ux-design (touch targets, mobile patterns)
- interaction-motion-design (form transitions, validation animations)
- performance-states-patterns (loading, empty, error states)
- navigation-pattern-encyclopedia (form navigation, multi-step flows)
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.

