Working with AI
Most AI coding assistants were trained before NotForm existed, so left to their own knowledge, they're likely to guess at an API that doesn't match this library — inventing prop names, mixing up which component owns which slot prop, or reaching for patterns from other form libraries entirely. The fix is to point the assistant at NotForm's actual documentation before it writes any code, rather than letting it rely on memory.
This documentation site is built with nuxt-llms, which automatically generates plain-text versions of these docs, stripped of navigation, styling, and page chrome, following the emerging llms.txt convention that AI tools are increasingly able to consume directly.
Usage
For most requests, point the assistant at llms.txt. It's an index of every page in this documentation, organized the same way as the sidebar — Getting Started, Components, Composables — with a link to each page's raw content:
https://notformdocs.vercel.app/llms.txt
An assistant that can follow links will read the index, pick out the pages relevant to the task (for example, not-array-field.md for a dynamic list of fields), and fetch only those — rather than needing the entire documentation set in context for every request.
Full Documentation
Some assistants and workflows can't follow links from a fetched file, or the task genuinely spans enough of NotForm that fetching pages one at a time is slower than just providing everything up front. For those cases, use the full documentation file instead — every page's content, already concatenated into one file:
https://notformdocs.vercel.app/llms-full.txt
llms-full.txt is a large file. It's the right choice when the assistant can't follow links, or when a task genuinely spans multiple components or composables — but for a single straightforward field or form, llms.txt plus a link-following assistant is usually enough, and keeps its context focused.Example Prompt
You can use a prompt like this in your AI editor:
"I need to build a user settings form with a dynamic array of email addresses. Please read the documentation at
https://notformdocs.vercel.app/llms.txtto understand how to use NotForm's<NotArrayField>anduseNotFormAPI before writing the Vue component."
Naming the specific components you expect to need — here, <NotArrayField> and useNotForm — helps the assistant focus on the relevant parts of the documentation rather than summarizing the whole library back to you.
Next steps
This is the last stop in Getting Started. From here, the Components guide covers the full API of every component referenced throughout these guides, and Composables covers everything the form instance from useNotForm exposes.