LLMs.txt

The documentation site serves CDS documentation in a machine-readable format following the llmstxt.org convention. It is a way to plug the design system into an agent that doesn't support AI Skills — Cursor, Copilot, Windsurf and others.

Documentation sets

The documentation is sliced by topic: an agent with a limited context takes the slice it needs instead of the whole catalog.

File	What's inside	When to take it
/llms.txt	Index: the list of sets and what every component is for	The entry point, start here
/llms-components.txt	Components: purpose, examples and API contract	Building an interface — the main slice
/llms-tokens.txt	Tokens and themes	Working with color and theming
/llms-guides.txt	Installation, conventions, forms, theming, Tailwind, tree-shaking, responsiveness	Setting up a project
/llms-migration.txt	CDS 3 → CDS 4 migration	Converting existing code
/llms-full.txt	Everything at once	Only if the context window allows

The same files ship in the npm package — node_modules/@central-design-system/components/llms/. The offline option is handier when the agent works without network access.

What's inside

The llms.txt index lists the sets and gives the purpose of every component, grouped by category — the agent picks a component from it without reading the full catalog:

### Controls (17)

- **CdsSelect** — Селект открывает выпадающий список и позволяет выбрать одно
  или несколько значений из заранее известного набора: страну, статус, категорию
- **CdsCombobox** — Комбобокс — поле с выпадающим списком и свободным вводом

In the other files every component gets a section: purpose, a "See also" hint, the documentation prose with live examples and the API contract.

# CdsButton

_Категория: Content · появился в 4.0.0_

Кнопка — основной способ запустить действие: отправить форму, открыть модальное
окно, подтвердить выбор.

**Смотрите также:** Для перехода, оформленного как текст в абзаце, подойдёт
CdsLink, а для выбора одного из вариантов — CdsButtonToggle.

## Вариации
...

## Рекомендации

| ✅ Хорошо | ❌ Плохо |
| --- | --- |
| Одно главное действие на экране — primary, остальные менее контрастны. | Несколько primary-кнопок соревнуются за внимание. |

## API

### CdsButton

**Props**

| Prop | Type | Default | Required | Description |
| --- | --- | --- | --- | --- |
| `appearance` | `"primary" \| "secondary" \| "tertiary" \| "inverse"` | `'primary'` | no | Внешний вид компонента |

How to plug it in

Add a pointer to the file you need in your product's instructions (AGENTS.md, .cursorrules, .github/copilot-instructions.md):

CDS components: https://<documentation-address>/llms-components.txt
Tokens and themes: https://<documentation-address>/llms-tokens.txt

In Cursor the files are plugged in through @Docs, in Windsurf — through @ or .windsurfrules.

There is a more precise option for Claude Code

AI Skills load reference files as needed and carry a working procedure, not just data. The flat catalog is for places where skills aren't supported.

How it is generated

The files are assembled from the design system sources and are never edited by hand:

cd packages/components
bun run generate:meta   # component contracts → meta.json
bun run generate:llms   # meta.json + documentation pages → llms/

The source is the same content model as AI Skills use: contracts come from meta.json, purpose and prose come from component documentation pages, examples come from the demos shared with the site and Storybook. That is why the catalog never drifts from what you read here.