AGENTS.md
The in-repo manual coding agents read before touching the library.
The library documents itself in-repo, for agents working inside the package. If you are consuming it, the handbook you are reading now is the right document.
| Where | What it is |
|---|---|
packages/react-native-ui/AGENTS.md | The package manual — stack, rules, the three component patterns, sizing, theming, testing, and an index table of every component |
packages/react-native-ui/src/components/<name>/AGENTS.md | One file per component, covering its own design decisions in full |
packages/react-native-ui/README.md | The human-facing introduction |
What it covers that this site does not
- The reasoning behind each component's edge cases, in full — why
Spinner's arc caps arebutt, whyCheckbox's fill radius is computed from--radiusrather than written down, whyTabs' settle lives inonFinalizerather thanonEnd. - The compound-component file layout, and the five load-bearing properties of the closing
Object.assign. - The
displayNameconvention: every component carries aDelacourUI.-prefixed name matching its dotted path in the public API, enforced by a test that reads the source as text. - How to add a component, end to end.
src/docs.test.ts fails the build for a component folder with no AGENTS.md, for a doc that is
only a heading, and for a component missing from the package doc's index table. Documentation is a
build gate there, not a convention.
Pointing an agent at this site instead
For an agent writing app code, install the skill — one file the assistant reads on its own, teaching it to copy real components rather than write plausible ones.
bunx delacour@latest skillsFailing that, /llms.txt indexes every page here, and any page
can be fetched as Markdown by appending .md to its URL.