Agent skill

Install and use the NotForm agent skill, which routes AI coding assistants to the right documentation instead of answering from memory.

The NotForm agent skill is a small instruction file for AI coding assistants. It does not contain API documentation. Its job is to make the assistant look things up: identify your setup, find the relevant pages, read them, and only then write code.

Why a skill instead of more docs

A copy of the API inside the skill would go stale and compete with these docs. The skill instead holds the part that does not change: where to look, in what order, and the few rules that assistants break most often. The documentation stays the single source of truth.

Install

The skill lives in the NotForm repository at .agents/skills/notform/SKILL.md. To use it in your project, copy the notform folder into the skills directory your tool reads.

your-project/
└── .agents/
    └── skills/
        └── notform/
            └── SKILL.md

Some tools use a different folder. For example, Claude Code reads project skills from .claude/skills/. Check your tool's documentation for the location it expects, and place the notform folder there.

Commit the folder so everyone working on the project gets the same behavior.

You can also use the skills CLI to install it. It supports more than 35 agents, including Cursor, Claude Code, Codex, Windsurf, and Cline.

Use it

The skill activates when you ask an assistant to build, debug, or migrate a NotForm form. It is also user-invocable, so in tools that support slash commands you can run it by name:

/notform

Then describe the task:

Build a registration form with username, email, and a repeatable list of phone numbers. Show server errors under each field.

What the skill makes the assistant do

Identify your stack and version. It checks whether the project uses notform (Vue) or @notform/nuxt (Nuxt), and which version.
Handle v3 first. If the project is on NotForm 3.x, it reads the migration guide before anything else.
Read the index. It loads llms.txt to see which pages exist.
Load only what the task needs. It maps the task to pages, for example "validation or errors" to the Validation and Errors guides, and fetches those as Markdown.
Write from the pages. If something is not documented, it says so instead of inventing options.

Rules the skill reinforces

These are the mistakes assistants make most, and each is explained in the docs.

Create fields with form.field(path) and form.arrayField(path), and pass the instance to Field or ArrayField. See Field.
Bind field.model and spread field.events, with v-model first. See Binding inputs.
Schema input is what users edit. Schema output is what onSubmit receives. See Schema input and output.
Give initialValues for every bound field.
Use item.id as an array key, and change arrays only through their methods. See Array fields.
Writes through field.model and form.setValue do not validate.
Field configuration is read once, when the field is created. See Validation.
NotForm should be the only owner of a form's state. Do not combine it with another form library on the same form.

Example prompts

Goal	Prompt
New form	"Create a checkout form with NotForm and Zod. Validate on blur and show errors with accessible markup."
Integration	"Wire this form to our ShadcnVue inputs. Handle the `Field` name conflict."
Debugging	"My error message never clears after I fix the input. Find out why using the NotForm docs."
Migration	"Migrate this component from NotForm v3 to v4."
Review	"Review this form against the NotForm docs and list anything that is guessed."

Limits

The skill needs the assistant to be able to fetch URLs. Without network access, it asks you for the relevant pages instead of guessing.
The skill is a router. If the docs and your installed package disagree, trust the package's public exports and tell the maintainers.

llms.txt and Markdown pages

What the NotForm llms.txt, llms-full.txt, and per-page Markdown endpoints contain, and how to use each with an AI tool.