FO
form-ux-review
Review and design form UX for signup, checkout, onboarding, settings, support, enterprise lead forms, creator submission, marketplace listing, payment, cancellation, data export, and admin workflows across web, mobile, and desktop. Use when improving form completion, clarity, accessibility, validati
Install
mkdir -p .claude/skills/form-ux-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17246" && unzip -o skill.zip -d .claude/skills/form-ux-review && rm skill.zipInstalls to .claude/skills/form-ux-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review and design form UX for signup, checkout, onboarding, settings, support, enterprise lead forms, creator submission, marketplace listing, payment, cancellation, data export, and admin workflows across web, mobile, and desktop. Use when improving form completion, clarity, accessibility, validation, errors, field order, progressive disclosure, autosave, trust, fraud controls, and support evidence.403 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
Form UX Review
Use this skill to make forms easier, safer, and more trustworthy without hiding important terms.
Workflow
- Identify form goal, user intent, risk level, platform, data sensitivity, and completion metric.
- Read
references/form-ux-systems.md. - Map fields, steps, validation, error recovery, save/resume, accessibility, security, and support evidence.
- Separate friction that protects users from friction that only reflects internal data needs.
- Produce prioritized fixes with metrics and validation checks.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not remove fields needed for safety, legal, payment, privacy, or support without another control.
- Do not hide material terms behind prechecked boxes or vague copy.
- Do not optimize completion if it increases bad-fit leads, refunds, fraud, or support burden.
Output format
Form context:
Primary task:
Findings:
- P0 <issue> -> fix, validation, metric
- P1 <issue> -> fix, validation, metric
Field/step map:
- <field> -> why needed, validation, recovery
Instrumentation:
- <event/property>