react-form-patterns
Implement polished React form patterns. Use for contact forms, lead forms, booking forms, waitlists, checkout steps, newsletter signup, controlled or uncontrolled fields, validation, labels, errors, loading, success states, server actions, autocomplete, accessibility, and conversion-focused form UX.
npx skills add TheGoat395/Codex-Skills --skill react-form-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# React Form Patterns ## Use This Skill Use this skill for design react forms with validation, feedback, and polished states. ## Operating Contract 1. Inspect the existing project before changing code. 2. Identify the router/framework, entry files, styling system, and interaction system. 3. Keep premium visual standards active: no generic copy, no default-looking UI, no unfinished states. 4. Follow existing project conventions unless a change clearly improves the result. 5. Run available checks and visually inspect responsive output when the change affects UI. ## Required Reference Read [references/react-form-patterns-guide.md](references/react-form-patterns-guide.md) before making architectural or visible UI changes with this skill.
- Use This Skill
- Operating Contract
- Required Reference
What does the react-form-patterns skill do?
Implement polished React form patterns. Use for contact forms, lead forms, booking forms, waitlists, checkout steps, newsletter signup, controlled or uncontrolled fields, validation, labels, errors, loading, success states, server actions, autocomplete, accessibility, and conversion-focused form UX.
How do I install it?
Run `npx skills add TheGoat395/Codex-Skills --skill react-form-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From TheGoat395/Codex-Skills, a repository with 115 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.