# For agents

This docs set is meant to be read by language models and coding agents as easily as by people. Owners should start at [What your site can do](./index.md).

HTML is at `/cms/docs`. Every page has a Markdown twin at `/cms/docs/{page}.md`. Start with [`llms.txt`](/cms/docs/llms.txt). Full dump: [`llms-full.txt`](/cms/docs/llms-full.txt). Feature catalog JSON: [`catalog.json`](/cms/docs/catalog.json).

## How to behave

- Speak in plain words to the owner. They run a gym or a trades business.
- Open a pull request. Do not push to `main`.
- Do not invent prices, bios, testimonials, or results.
- Do not print secrets.
- Do not dispatch `migrate.yml` or approve a production deploy unless the owner asked.
- Update `docs/public/` in the **same** PR when owner-facing behaviour changes.
- Run `pnpm docs:check` on xylo-cms changes.

## Placeholders

Never write angle-bracket placeholders. The public site treats those as HTML tags. Use `YOUR-DOMAIN` or `{slug}` in inline code.

## Heading anchors

Anchors are stable slugs from heading text: lowercase, punctuation to hyphens, duplicates get `-2`. Prefer not to rename H2s that other pages link to.

## Skills in a site repo

Shipped with `pnpm xylo sync`:

- `add-blog-post`
- `update-site-content`
- `edit-follow-ups`
- `link-a-file`
- `apply-site-update` (legacy git-merge updates; package bumps use [Updates](./sync.md))

## Screenshots

Owner docs may include a Markdown image pointing at `docs/public/assets/` (for example `admin-dashboard.webp`) from the seeded Brightside Studio demo only. No live customer data.