mcpField
F
form-ux-review

form-ux-review

github.com/sylphxaiDesign & UI149 installsUpdated today
Repository

About form-ux-review

form-ux-review is a skill for reviewing and improving form experiences for design and product teams. It prioritizes fixes using risk, data sensitivity, and completion metrics while preserving safety, legal, and privacy safeguards.

Key features

  1. 01Assess form goals and risks
  2. 02Map fields, validation, and error recovery
  3. 03Separate necessary from internal friction
  4. 04Prioritize fixes with metrics
  5. 05Preserve safety and material-term safeguards

Use cases

  1. 01Review high-risk or sensitive-data forms
  2. 02Improve validation and error recovery
  3. 03Assess save/resume and accessibility

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill form-ux-review

After installing, type/form-ux-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/form-ux-systems.md

Details

From the project README

Form UX Review

Use this skill to make forms easier, safer, and more trustworthy without hiding important terms.

Workflow

  1. Identify form goal, user intent, risk level, platform, data sensitivity, and completion metric.
  2. Read references/form-ux-systems.md.
  3. Map fields, steps, validation, error recovery, save/resume, accessibility, security, and support evidence.
  4. Separate friction that protects users from friction that only reflects internal data needs.
  5. 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>

Comments

Markdown supported