Form Design Encyclopedia logo

Form Design Encyclopedia

Community
phazurlabs
form-design-encyclopedia

200+ form patterns covering every input type, layout, validation strategy, multi-step wizard, and error state, with production React and CSS, accessibility requirements, and mobile optimization. Use when building or fixing a form, choosing a validation approach, or reducing abandonment on signup and checkout.

Overview

Publisherphazurlabs
Repositorysumi
Skill nameform-design-encyclopedia
Stars
58
Forks
11
Bundled files
7
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by phazurlabs on GitHub. Read the source before you install it.

Installation

Install the Form Design Encyclopedia AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/phazurlabs/sumi/tree/main/skills/form-design-encyclopedia
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/phazurlabs/sumi.git /tmp/sumi
mkdir -p .claude/skills
cp -r /tmp/sumi/skills/form-design-encyclopedia .claude/skills/form-design-encyclopedia
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Form Design Encyclopedia in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Form Design Encyclopedia on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Form Design Encyclopedia is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Form Design Encyclopedia — Every Form Pattern

Mental model

Every field is a request for effort, and the user is deciding continuously whether the thing they came for is still worth it. So the discipline is subtraction: the best form change is almost always deleting a field.

  • One column. Multi-column forms cause skipped fields and mis-scanning. The exception is genuinely paired data — city and postcode, expiry and CVC.
  • Labels above inputs. Fastest to scan, survives translation, survives narrow screens. Placeholder-as-label is an accessibility failure and a memory burden the moment someone starts typing.
  • Validate on blur, not on keystroke. Validating while someone is still typing tells them they are wrong before they have finished being right. Re-validate on submit; show errors inline, next to the field, never only at the top.
  • An error message names the fix, not the failure. "Enter a date in the past" beats "Invalid date".
  • Every field earns its place. If nobody can name the decision a field informs, it is decoration with a compliance cost.

Constants

Every input in the catalog implements these six states. A field missing focus or error is not finished.

default · focus · filled · disabled · error · success

Touch target minimum 44x44px. Label-to-input gap 8px. Field-to-field gap 20-24px. Error text sits directly beneath its field, never floating.

Index

NeedReference
A specific input type — text, email, phone, date, file, OTP, rich textinput-field-catalog.md
Password strength meter, masked input, currency, percentageinput-field-catalog.md
The six field states as codeinput-field-catalog.md
Single column, two column, card-based, inline layoutsform-layout-patterns.md
Login, signup, contact, payment, address, settings, survey formsform-layout-patterns.md
When to validate and what to sayvalidation-error-patterns.md
100+ ready error message templatesvalidation-error-patterns.md
Splitting a long form into stepsmulti-step-form-patterns.md
Step indicators, back navigation, data persistencemulti-step-form-patterns.md
Labels, required marking, error association, group labelsform-accessibility-code.md
Why people abandon, and what to instrumentform-analytics.md

Reference architecture

FileCoversLines
references/form-layout-patterns.md19 layouts + specialized forms2344
references/input-field-catalog.md55 input types, all states1539
references/multi-step-form-patterns.mdwizards, steppers, persistence1151
references/form-accessibility-code.mdsemantic HTML, ARIA, errors1025
references/validation-error-patterns.mdtiming, anatomy, 100+ templates780
references/form-analytics.mdmeasuring form performance69

What every reference file contains

  1. When the pattern applies and when it does not
  2. Complete React plus CSS, with all six states rendered
  3. The ARIA wiring — label association, error announcement, group semantics
  4. Mobile behaviour: keyboard type, autocomplete token, target size
  5. The failure mode that pattern is known for

Routing

For a specific input — the field-state reference plus every input type from text and icon-prefixed through to password strength meters: read references/input-field-catalog.md.

For arranging a form — single column, two column, card-based and the rest of the nineteen layouts, plus the specialized login, signup, contact, payment, address, settings and survey forms: read references/form-layout-patterns.md.

For validation and errors — timing strategy, error message anatomy, 100+ message templates, and warning patterns: read references/validation-error-patterns.md.

For multi-step flows — when to split at all, step indicators, navigation between steps, and data persistence: read references/multi-step-form-patterns.md.

For accessibility — semantic HTML foundations, label association methods, required-field marking, error association and group labeling: read references/form-accessibility-code.md.

For odds and ends — the patterns that had no home in the files above when this skill was converted to a router: read references/form-supplementary.md.

Cross-References

  • component-patterns-code (React component implementations)
  • micro-copy-intelligence (error messages, helper text, button labels)
  • conversion-optimization-patterns (form conversion, CTA optimization)
  • accessibility-inclusive-design (WCAG compliance, screen reader testing)
  • mobile-ux-design (touch targets, mobile patterns)
  • interaction-motion-design (form transitions, validation animations)
  • performance-states-patterns (loading, empty, error states)
  • navigation-pattern-encyclopedia (form navigation, multi-step flows)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Form Design Encyclopedia AI skill do?

200+ form patterns covering every input type, layout, validation strategy, multi-step wizard, and error state, with production React and CSS, accessibility requirements, and mobile optimization. Use when building or fixing a form, choosing a validation approach, or reducing abandonment on signup and checkout.

Why use Form Design Encyclopedia on TypingMind?

Because you install it once and use it with any model. Form Design Encyclopedia is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Form Design Encyclopedia in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/phazurlabs/sumi/tree/main/skills/form-design-encyclopedia. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Form Design Encyclopedia?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Form Design Encyclopedia?

As many as you like. As long as a model supports skills, you can use Form Design Encyclopedia with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Form Design Encyclopedia AI skill free?

Yes. It is published on GitHub by phazurlabs under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇