AI and agents | pixilui docs

pixilui is written to be read by coding agents as well as people. Everything an agent needs to pick an item, install it and use it correctly is published as plain text, generated from the same metadata as the pages you are reading.

llms.txt#

File	What it holds	When to use it
`/llms.txt`	An index: every item by category, one line each, with a link to its markdown page	Give it to an agent first, so it can choose
`/llms-small.txt`	Every item's description, when to use it, when not to, its props and its notes for AI, without source	Planning a screen, choosing between items
`/llms-full.txt`	Every item page in full, with source for free items	One-shot context for an agent that cannot browse

The files follow the llms.txt format and are rebuilt with the registry, so they never drift from the code.

Per-item markdown#

Every item page has a markdown twin with the whole page in the same order: install, preview knobs, code, usage, API, keyboard, accessibility, motion, responsive, performance, notes for AI and related items.

bash

curl https://pixilui.com/components/approval-card/markdown

Item pages link to it with <link rel="alternate" type="text/markdown">, so agents that look for an alternate format find it. Docs pages have the same twin at /docs/<page>/markdown.

Copy prompt and Copy page#

On each item page:

Copy prompt copies instructions for a coding agent (add the registry, run the install command, the import line, keep the semantic utilities) followed by the item's full markdown with every file. Paste it into Claude Code, Cursor or any chat and the agent has all it needs, even offline.
Copy page copies the page as markdown, for notes or for an agent you are already talking to.

Notes for AI#

Every item's metadata has a "Notes for AI" list: the mistakes an agent is likely to make with that item and how to avoid them (for example, that native input attributes go to the <input> while className goes to the wrapper). They appear on the page, in the markdown and in llms-small.txt.

The registry for tools#

The shadcn registry is plain JSON at /r/<name>.json, with the index at /r/registry.json. Any tool that speaks the shadcn registry format can list and install items.

MCP server (coming)#

An MCP server will let agents search the catalog, read an item and get its install command without leaving the editor. It will be open for free items and serve Pro items to licence holders with a token. Until then, point your agent at /llms.txt.

Writing prompts that work#

Name the item: "use the pixilui approval card for the refund confirmation" beats "add a confirmation".
Ask the agent to read the item's markdown page before writing code.
Ask it to keep the semantic utilities (bg-surface, text-secondary, rounded-control) and to restyle through className and data attributes, not by editing the item.