# Using Nebula with AI

Work with Nebula through Claude and other AI tools.

Section: get-started
Docs: https://nebula.kaluza.com/get-started/using-nebula-with-ai

---

Nebula publishes itself in a form AI tools can read, so Claude can work from what the components actually do rather than from what it remembers about them.

## The plain-text docs

Every page on this site has a plain-text version, linked from the `LLMs` button under its title. Paste that URL into any AI tool and it reads the page as the tool sees it, with nothing to install.

For a component, the plain-text version carries more than the page shows at a glance: its props with types and defaults, its rules with their strength, its accessibility notes and its styles, all in one file.

Two entry points cover the whole site:

| URL | What it is |
| --- | --- |
| [`llms.txt`](pathname:///llms.txt) | The index. A quick reference, then every page grouped by section, each linking to its plain-text version. |
| [`llms-full.txt`](pathname:///llms-full.txt) | Every page in one file, around 100,000 tokens. Only worth fetching when you genuinely need all of it. |

Start an AI tool at the index rather than at a single page. It tells the tool how the docs are organised and what each section holds, so it can fetch the component it needs instead of guessing from one page it was handed.

## Skills

A skill teaches Claude how to use the docs for a particular job, so you don't have to point it at the right pages yourself.

| What you're doing | Skill |
| --- | --- |
| Writing or reviewing UI copy: labels, errors, notifications, empty states | `nebula-content` |
| Choosing a component, or building with one | `nebula` |
| Designing in Figma | See [Figma Setup](/get-started/figma) |

Both skills live in the Kaluza skills registry and neither is installed by default, so you add the one you need. Ask in `#ask-ai` if you're not sure how to add a skill on your setup, since it differs between Claude Code, the desktop app and claude.ai.

Neither skill replaces reading the docs yourself. They make Claude read them, which is a different thing.

## Checking the answer

Ask for the rule behind each point, and you can check it. Component rules have ids like `notification.title.no-terminal-punctuation`, printed next to each rule on the plain-text version of that component's page. A point with an id can be looked up. A point without one is Claude's opinion, which may still be right, but you should know which you're reading.

Rule strength matters as much as the rule. `MUST NOT` is a prohibition and `SHOULD NOT` isn't, and the two are easy to flatten into each other.

If you're writing code, check anything surprising against the version you have installed. Your app may be on an older `@kaluza-platform/nebula` than the one documented here, in which case a prop described on a component page won't exist in your build. The JSDoc comments shipped with the package's type definitions are what your app actually runs, so they settle it. See [Dev Setup](/get-started/setup).

## Contributing to Nebula

Two more skills live in the Nebula repository rather than the registry. They're for people changing Nebula, not for building with it:

- `nebula-docs` writes and reviews pages for this site.
- `nebula-a11y-docs` writes the Accessibility tab.

Nebula is moving to a federated model, where product teams contribute components rather than only requesting them. Fuller guidance on contributing will follow.

## Support

For the skills, or anything about using Nebula with AI, contact the design system team on Slack at `#ug-design-system`.