For AI tools
llms.txt, the registry and meta.json.
Start here
The repository is set up so an AI coding tool can use Monoline without guessing. Point it at these files, in this order.
AGENTS.md- Layout, commands, the component recipe, API conventions, CSS rules and the accessibility bar.
DESIGN.md- The look, the tokens and the copy rules.
llms.txt- Short index: what the kit is, links to the docs, and one line per component.
llms-full.txt- Every component in one file: description, import line, primitive, status, accessibility notes and its file list.
registry/- One JSON file per component or hook, plus
index.jsonlisting them all.
llms.txt, llms-full.txt and registry/ are generated by npm run registry. Do not edit them by hand.
registry/*.json
registry/index.json lists every entry with name, title, category, description, status, primitive, css, a11y, keywords, kind, import, path and files. Each registry/<name>.json adds dependencies and source, an array of {path, content} with the full file text. This is what the CLI reads.
bash
curl -s https://raw.githubusercontent.com/dasariprashant0/monoline/master/registry/button.json
meta.json fields
Every component folder has a meta.json, validated by npm run registry. This site is built from it, so a new component needs no docs change.
name- Equals the folder name.
title- Display name.
category- layout, typography, buttons, forms, data-display, feedback, overlays, navigation, effects, blocks or hooks.
description- One sentence.
status- Maturity, such as stable.
primitive- Optional. The Radix primitive underneath, if any.
css- Stylesheets in
packages/css/src/components/the component needs. a11y- Plain-language accessibility notes.
keywords- Alternative names, used for search.
Prompt tip
prompt
Read AGENTS.md and DESIGN.md. Build a settings page with @monoline/react.
Use only tokens for colour and spacing. Component list: llms.txt.