Cognitive ux forms
Design and audit forms, applications, intake journeys, and high-stakes submission flows using evidence-informed UX. Use when people must enter correct information, save progress, correct errors, review, and submit; return field necessity review, task flow, labels/examples, validation/recovery behavior, accessibility requirements, and completion-quality testing.From its SKILL.md
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-formsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 480 tokens by cl100k_base, as published. Nobody here has run it
Cognitive UX: Forms & Applications
Scope
Use for any data-entry-heavy task. Use cognitive-ux-civic, cognitive-ux-jobs, cognitive-ux-health, or cognitive-ux-finance when its domain risk requires additional safeguards.
Intake
- Identify user, task, decision rules, documents, privacy sensitivity, and consequence of error.
- Identify required versus optional data, conditional logic, validation service, save/resume, review, and deadline.
- Identify device, language, assistive technology, support, and legal/program constraints.
State assumptions that could change the design. Define the primary task, its consequence of failure, and a measurable user outcome before proposing a layout.
Design procedure
- Ask only for information needed for the decision or immediate task; explain sensitive-data purpose.
- Group fields by the user’s mental task, keep labels visible, show format examples beside input, and reveal conditions at the appropriate decision point.
- Preserve entered values; validate specifically, do not rely on color alone, and say how to recover from every error.
- Support save/resume, review/edit, and a clear submitted/not-submitted confirmation for consequential forms.
- Test full completion with keyboard, zoom, error states, interruptions, and representative users.
Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.
Required outputs
- field necessity and data-minimization audit
- conditional form journey
- label/help/error/recovery specification
- save/resume/review/submission state model
- completion, correction, and accessibility study
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not erase data after errors, hide required fields or format rules, use placeholders as labels, ask for unnecessary personal data, or make submission state ambiguous.
Related skills
Use cognitive-ux-civic, cognitive-ux-jobs, cognitive-ux-health, and cognitive-ux-finance. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.
What ships with it: 2 files
1.3 KB alongside SKILL.md
agents/
- openai.yaml196 B
references/
- archetype-evidence.md1.1 KB