Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Design a form end to end — field order, grouping, validation, and completion.
Install Form Design
$ npx skills add Owl-Listener/designer-skills --skill form-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills form-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/interaction-design/skills/form-design .claude/skills/form-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .claude/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill form-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills form-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/interaction-design/skills/form-design .agents/skills/form-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .agents/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill form-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills form-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/interaction-design/skills/form-design .cursor/skills/form-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .cursor/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path interaction-design/skills/form-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill form-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills form-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/interaction-design/skills/form-design .gemini/skills/form-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .gemini/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills form-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill form-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/interaction-design/skills/form-design .github/skills/form-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .github/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill form-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills form-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/interaction-design/skills/form-design .opencode/skills/form-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "form-design" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/form-design into .opencode/skills/form-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
form-design- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~992 tokens
- SKILL.md length
- 533 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a form end to end — field order, grouping, validation, and completion.
- The artifact is a form
- SKILL.md covers What You Do, Layout, Labels and Instructions and Input Types, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Form Design is an agent skill from Owl-Listener/designer-skills. 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.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- The artifact is a form
Example prompts
- “/form-design”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Form Design loads about 992 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 533 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 533 words, ~992 tokens.
Download SKILL.mdSave it as
.claude/skills/form-design/SKILL.md (or your agent's skills folder).- name
- 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 |
Show full SKILL.md (253 more words)Show less
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
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in interaction-design/skills/form-design of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Form Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Form Design this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~992 | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Form Design
What does Form Design do?
Design a form end to end — field order, grouping, validation, and completion. Form Design is an agent skill from Owl-Listener/designer-skills. Design a form end to end — field order, grouping, validation, and completion.
When should I use Form Design?
Form Design fits situations like: the artifact is a form.
How do I install Form Design in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill form-design -a claude-code`. Or copy the skill folder (interaction-design/skills/form-design in Owl-Listener/designer-skills) into .claude/skills/form-design in your project. Claude Code loads it when a task matches its description.
How do I install Form Design in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill form-design -a codex`. Or copy the skill folder (interaction-design/skills/form-design in Owl-Listener/designer-skills) into .agents/skills/form-design in your project. Codex loads it when a task matches its description.
Can I use Form Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill form-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/form-design, .gemini/skills/form-design, .github/skills/form-design and .opencode/skills/form-design in your project.
What does Form Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Form Design is instructions for the agent only.
Does Form Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Form Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Form Design use?
Form Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Form Design use?
About 992 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Form Design?
Skills that share tags, products or a category with Form Design: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Form Design?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.