Skip to content

Grid Notes

Short, checked notes on using a library with an AI agent: what to install, how to wire it up, what goes wrong and how to keep it accessible.

DocsUpdated 2026-11-12
Browse docs

What they are

An agent that has never seen the current version of a library will write code for an older one. A Grid Note is a one-page brief, written by ExonUI from the library's own documentation, that gives the agent what it needs to get this right the first time.

There are notes for 16 libraries and registries, each on its own page:

What's in a note

  • Install: the command, the packages it adds and anything you need first.
  • Setup: one to three code blocks with the wiring for React, Next.js and Tailwind CSS v4.
  • Gotchas: three to five concrete traps, such as version mismatches, licence limits and code that stalls the page.
  • Accessibility: how to respect reduced motion, and how keyboard and screen reader users are served.
  • Version and date: which version we checked and when, shown on every note.

Give a note to your agent

Open a library's note and press Copy note for your agent. It copies the whole note as Markdown. Paste it into the conversation, or save it as a rules file your agent reads for the project, and ask for what you want:

Prompt
Here is a Grid Note for Lenis. Follow it exactly.

[paste the note]

Add smooth scrolling to the layout, and turn it off when the visitor prefers reduced motion.

Grid can return the same note itself: grid_describe on pack:<id> includes it, with a Markdown version. Grid isn't published yet, so for now copying is the way.

How far to trust them

Libraries change faster than notes. Each note says which version we checked and the date; when yours is newer, read the library's changelog before trusting a note's code. The catalog links every library's own documentation.

Tip

Notes are written in our own words and link to the sources. They're an agent's starting brief, not a replacement for the library's documentation.