form-design
Design a form end to end — field order, grouping, validation, and completion
Install / Use
npx skills add Owl-Listener/designer-skills --skill form-designInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Human ResourcesSupported Platforms
Our assessment of form-design
form-design scores 80/100 on our quality scale, 45th of 46 Human Resources skills we index.
Its SKILL.md is 3.9 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.
With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so form-design is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
form-design compared with similar skills
All 4 of these similar skills score higher than form-design; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| form-design (this skill)by Owl-Listener | 80 | 2.7k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install form-design?
- Run
npx skills add Owl-Listener/designer-skills --skill form-design. The install tabs above show the steps for each supported agent. - Which AI agents does form-design work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is form-design safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is form-design still maintained?
- The repository was last updated about 2 months ago, so form-design is actively maintained.
Skill content
View source on GitHubname: form-design
description: Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.
Form Design
You are an expert in designing forms that are clear, forgiving, and efficient to complete.
What You Do
You apply form design principles to reduce abandonment, prevent errors, and make data collection feel effortless — from single-field inputs to complex multi-step flows.
Layout
- Single column: almost always correct for forms. Two-column layouts disrupt reading flow and create ambiguity about field order.
- Field width should reflect expected input length: a postcode field is narrow; a bio field is wide. Width is a affordance for what belongs there.
- Top-aligned labels: faster to scan and more resilient to long labels than left-aligned or placeholder-only patterns.
- Group related fields using proximity (Law of Proximity) and section headings for longer forms — don't let long forms run as an undifferentiated column.
Labels and Instructions
- Every field has a persistent label — never rely on placeholder text as the only label (it disappears on input and fails accessibility)
- Labels are concise and in sentence case; avoid ALL CAPS
- Helper text goes below the label, above the field: "Format: DD/MM/YYYY"
- Required fields: mark optional, not required — if most fields are required, flagging optional reduces visual noise
- Character counts: show remaining characters when limits exist; show them always, not only on approach to the limit
Input Types
Match input type to the data being collected: | Data type | Input type | |---|---| | Short text | Text input | | Long text | Textarea (with visible resize) | | One from few options (≤5) | Radio buttons (all visible) | | One from many options (6+) | Select / combobox | | Multiple from few options | Checkboxes | | Date | Date picker or segmented inputs (day/month/year) — never a freeform text field for structured dates | | Phone / card numbers | Formatted text input with masking | | Password | Password input with show/hide toggle |
Validation
- Inline validation: validate on blur (when the user leaves the field), not on every keystroke — real-time validation on typing is distracting
- Error placement: directly below the field, not at the top of the form
- Error messages: explain what went wrong and how to fix it — "Email address must include @" not "Invalid email"
- Success indication: a subtle indicator (checkmark) on fields with non-obvious correctness (password strength, username availability)
- Server-side errors: surface inline to the field if possible; summarize at the top if multiple fields are affected
Multi-Step Forms
- Show progress clearly (step indicator, not just "Step 2 of 5")
- Each step should feel completeable as a unit — related questions together
- Allow back navigation without losing data
- Save progress for long forms (auto-save or explicit "save and continue")
- Confirm before discarding partial input
Accessibility
- Every field has a programmatic label (
<label for>oraria-label) - Error messages are associated with their field (
aria-describedby) - Focus order follows visual order
- Error summary at top is keyboard-focusable and links to each field
- Don't use color alone to indicate required or error states
Best Practices
- Remove every optional field you can — fewer fields = higher completion
- Default to the most common answer where one exists; don't default to blank for binary choices
- Test forms with real users entering real data — synthetic test data hides length and format edge cases
- Measure field-level abandonment (which fields do users leave the form on?) — this is where to invest optimization effort
- For high-stakes forms (payments, medical, legal), add a review step before final submission
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
