---
title: "Working with AI"
description: "Give AI coding assistants accurate NotForm knowledge using llms.txt, per-page Markdown, and the NotForm agent skill."
canonical_url: "https://notformdocs.vercel.app/docs/ai/working-with-ai"
---

> Index of every page on this site: [llms.txt](https://notformdocs.vercel.app/llms.txt)

AI assistants are fast at writing form code, and just as quick to invent APIs that do not exist. NotForm's API is small but specific, so an assistant working from memory will often reach for names from other libraries.

NotForm gives assistants three ways to work from the real documentation.

<table>
<thead>
  <tr>
    <th>
      Resource
    </th>
    
    <th>
      What it is
    </th>
    
    <th>
      Best for
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="/docs/ai/llms-txt">
        <code>
          llms.txt
        </code>
      </a>
    </td>
    
    <td>
      An index of every documentation page with a one-line description
    </td>
    
    <td>
      Letting an assistant discover which pages exist
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/ai/llms-txt#read-a-single-page">
        Page Markdown
      </a>
    </td>
    
    <td>
      Any documentation page as clean Markdown
    </td>
    
    <td>
      Loading exactly the pages a task needs
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/ai/llms-txt#the-full-documentation">
        <code>
          llms-full.txt
        </code>
      </a>
    </td>
    
    <td>
      The whole documentation in one file
    </td>
    
    <td>
      Broad tasks, or tools that cannot follow links
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/ai/agent-skill">
        The agent skill
      </a>
    </td>
    
    <td>
      A short set of instructions that routes an agent to the right pages
    </td>
    
    <td>
      Making the agent do all of the above on its own
    </td>
  </tr>
</tbody>
</table>

## Quick start

1. **Install the skill.** Copy the `notform` skill into your project so your assistant loads it automatically. See [Agent skill](https://notformdocs.vercel.app/docs/ai/agent-skill#install).
2. **Ask for what you need.** Describe the form in plain words. The skill makes the assistant read the matching pages before it writes code.
3. **Review against the docs.** Ask the assistant which pages it used. If something it wrote is not in those pages, it is a guess.

No skill support? Paste `https://notformdocs.vercel.app/llms.txt` into the conversation and ask the assistant to read the pages relevant to your task before writing code.

## What assistants get right and wrong

Assistants do well when the docs are in front of them. These are the mistakes the documentation and skill are designed to prevent:

- using `path` props or form context from NotForm v3 instead of explicit field instances;
- using `index` instead of `item.id` as an array key;
- mutating arrays directly instead of through `ArrayField` methods;
- expecting `form.setValue` or `field.model` writes to validate;
- passing field configuration on every render and expecting it to apply;
- mixing NotForm with another form library on the same form.

## Next steps

- [llms.txt and Markdown pages](https://notformdocs.vercel.app/docs/ai/llms-txt)
- [The NotForm agent skill](https://notformdocs.vercel.app/docs/ai/agent-skill)

## Sitemap

See the full [sitemap](https://notformdocs.vercel.app/sitemap.md) for all pages.