design-a-form
Design an accessible form around a real task and data need. Use when fields, sequencing, validation, consent, errors, saving, submission, and recovery must work together.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- design-a-form
- category
- design
- description
- Design an accessible form around a real task and data need. Use when fields, sequencing, validation, consent, errors, saving, submission, and recovery must work together.
# design-a-form
## Procedure
1. Define user task, authority, eligibility, decision, data purpose, and completion evidence.
2. Remove fields that are unnecessary or obtainable safely elsewhere.
3. Group questions in a logical sequence and reveal complexity only when relevant.
4. Write persistent labels, help, examples, required status, formats, and inclusive choices.
5. Choose native controls and correct autocomplete, input, and keyboard behavior.
6. Define client and server validation with field errors, summary, focus, and preserved input.
7. Design save, resume, review, submit, confirmation, duplicate, timeout, and failure states.
8. Explain consent, retention, sharing, consequences, and alternative channels.
9. Test with keyboard, screen reader, zoom, mobile, slow connection, errors, and representative users.
10. Reconcile submitted data with the authoritative system and support path.
## Guardrails
- Do not collect sensitive data without purpose and authority.
- Never erase input after a recoverable error.
- Avoid placeholder-only labels or color-only errors.
## Done
- A form specification covers fields, logic, validation, consent, states, and evidence
- End-to-end submission and failure tests pass
- Accessibility and data-minimization review are recorded
在 GitHub 查看