Download for macOS
Skill

uniform-forms

@uniformdev Updated 2026-10-08

Use when adding a form (like contact, signup, newsletter, lead-capture or survey) to a Uniform project, when creating form field component definitions or building a generic form submission endpoint. Do not use when embedding an iframe for an external form provider.

Install

With your agent

Install OMGSkills skill "uniformdev/agent-skills:skills/uniform-forms" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/uniformdev/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/uniform-forms ~/.claude/skills/uniform-forms

From README

Uniform forms A form in Uniform is not a special entity — it is a composition of components. A Form container component renders the element and owns the resulting submit action; each input is its own component placed in the container's slot. Authors assemble forms in Uniform's visual editor; developers own the markup, state, and submission. Architecture Field components self-register with that context on mount and read/write their own value through it. The container never inspects its slot contents. Author-set Field name and identifier Every field must have a stable, author-set identifier. The name parameter is required on every field component. Slugify it to get the identifier used for the HTML name/id, and the payload key. Never fall back to a generated identifier, warn in the Uniform's visual editor when a field is missing an identifier. Form Submit or Fields should self-register Do not introspect slots. Do not walk component.slots.formFields to build fields.