What to give it
- llms.txt is the index: what Tray UI is, the three lines that install it, and a link to every page. It is short enough to paste into a prompt.
- llms-full.txt holds the whole system in one file: the rules of the brand book, the guides (grounds, behaviour, accessibility, page layouts), theming, React, the index of components and the guidelines of every component with its markup.
- Every page of this site is also Markdown at its own address with
.mdadded: the page of the button is at/components/button, its Markdown at/components/button.md. A block's Markdown holds its whole page of HTML, and a chart's holds its React file. Each page names its Markdown in its head, as<link rel="alternate" type="text/markdown">.
An agent that can fetch pages needs only the address of llms.txt. One that cannot needs llms-full.txt, or the Markdown of the pages the task touches, pasted in.
Connect it to a tool
- In a chat, attach llms-full.txt, or paste llms.txt and let the agent fetch the pages it lists.
- In an editor with an agent (Cursor, Windsurf, Claude Code, Copilot), add the address of llms.txt as a documentation source where the tool allows one, or save llms-full.txt into the project and point the agent at it from its rules file (
AGENTS.md,CLAUDE.md,.cursor/rules). - In a project of your own, copy the three files in and tell the agent where they are, so it links them instead of a CDN.
What to tell the agent
- Link the three files; write plain HTML with
tray-classes; attach behaviour withdata-tray. - Start a screen from the nearest block, not from an empty page.
- Follow the brand book: one yellow per view, depth by fill, selected is solid ink, sentence case, buttons that start with a verb.
- Use only classes that exist. If a layout needs a value that no class gives, use a token (
var(--space-6)), never a literal colour or size. - Check the result at 1280, 768 and 390 pixels in a light and a dark theme.
- From npm, the files are
trayuiand React istrayui-react; an agent that installs them needs nothing else from the system.
A prompt to start from
Text
Build the order history page of a shop with Tray UI.
Read https://trayui.com/llms.txt first, then the pages it lists for the
components you use. Start from the closest block (a table page), link
tokens.css, components/bundle.css and components/bundle.js, and use only
tray- classes and tokens that exist. One yellow button per view.
Give me one HTML file, then check it at 1280, 768 and 390 px wide.What it gets right, and what to check
An agent that has read the guidelines writes the right markup for a component: the classes, the attributes and the ARIA. What it gets wrong most often is the page around the components: two yellow buttons in one view, a colour or a size typed by hand, a heading level skipped. Ask it to check its page against the brand book before it hands it over, and look at it in a dark theme.