form-design

Design accessible web forms with correct input types, labels, and validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/andersoncollab/design-agent --skill form-design-andersoncollab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-design
Source: https://github.com/andersoncollab/design-agent/tree/main/skills/form-design
Command: npx skills add https://github.com/andersoncollab/design-agent --skill form-design-andersoncollab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you avoid low-conversion, inaccessible, and frustrating forms by providing production-ready UX patterns for inputs, validation, multi-step flows, and recovery from errors.

Core Features & Use Cases

  • Input type + autocomplete optimization: Use correct HTML input types and autocomplete values to reduce friction and improve autofill success.
  • Accessible labeling and validation: Implement visible labels and inline validation that connects errors to inputs via ARIA (aria-describedby, role="alert"), without clearing user input.
  • Multi-step wizard architecture: Add step indicators, per-step validation, back navigation, and progress saving so users can resume.
  • Error summary + submit states: Provide top-of-form error summaries with anchored links and prevent double submits with loading/success/error feedback patterns.
  • Mobile-first layout guidance: Prefer single-column layouts with touch-friendly sizing to improve completion on iOS/Android.

Quick Start

Use the form-design skill to generate an accessible, mobile-first multi-step sign-up form with inline validation, an error summary, and resilient submit loading states.

Frequently Asked Questions about form-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an accessible multi-step wizard with inline validation?

Design an accessible multi-step wizard by adding step indicators, per-step validation gating, back navigation, and ARIA-linked error messaging that connects inline validation errors to inputs without clearing user data. This approach ensures users can resume progress and recover from errors efficiently.

What is the best way to handle form error recovery and prevent double submits?

The best way to handle form error recovery is providing top-of-form error summaries with anchored links and implementing submit state handling with loading, success, and error feedback to prevent double submits. This ensures users recover without retyping their input.

Does mobile-first form layout require single-column inputs for iOS and Android?

Yes, mobile-first form layout requires single-column inputs with touch-friendly sizing to improve completion rates on iOS and Android. This layout constraint reduces friction and aligns with correct HTML input types and autocomplete values to enhance autofill success.

How do I connect inline validation errors to inputs using ARIA attributes?

Connect inline validation errors to inputs using ARIA attributes like `aria-describedby` and `role="alert"` to announce errors to assistive technologies. This accessible labeling ensures visible labels and validation messages are properly linked without clearing user input.

When do I need autocomplete optimization for high-conversion checkout forms?

You need autocomplete optimization for high-conversion checkout forms when reducing input friction and improving autofill success rates are critical. Using correct HTML input types and autocomplete values ensures browsers accurately populate signup and checkout fields.