---
title: AI Agents
description: Integrate c15t with AI coding assistants using the docs bundled in each package and c15t agent skills. Give agents version-matched local docs for consent management, banners, script loading, callbacks, and integrations.
lastModified: 2026-03-24
---
## Bundled Docs

Every supported c15t package now ships docs inside the installed package itself.

### Where to find them

* `node_modules/c15t/docs/README.md`
* `node_modules/@c15t/react/docs/README.md`
* `node_modules/@c15t/nextjs/docs/README.md`
* `node_modules/@c15t/backend/docs/README.md`

Start with the package `README.md`, then follow its linked pages for the relevant workflow.

These docs are version-matched to the exact c15t package version in your project, including generated reference content like prop and type tables.

### Why use them

If your app uses multiple c15t packages, use the docs from each relevant installed package instead of relying on stale model knowledge.

### Agent philosophy

When an AI tool is helping with c15t behavior, it should read the installed c15t docs first and use model knowledge second. That keeps consent flows, script gating, banner behavior, and integrations aligned with the exact version you have installed.

### Customization ladder for agents

When an agent is working on consent UI, it should choose the lowest-power tool that solves the task:

1. Start with the pre-built component and its existing props or provider options
2. Use `theme` tokens for semantic visual changes
3. Use `theme.slots` for targeted styling of specific parts
4. Use CSS variables or className-level overrides only when integrating with external styles
5. Use compound components only when the markup order must change
6. Use `noStyle` only when c15t structure is still correct but all styling must be replaced
7. Use headless hooks only when markup and behavior both need to be rebuilt

For common tasks:

* Banner footer background -> `theme.colors.surfaceHover`
* Banner card background -> `theme.colors.surface`
* Banner card/footer/title tweaks -> banner slots
* Stock action styling -> `theme.consentActions`
* Copy changes -> `ConsentManagerProvider.options.i18n`

If a token appears not to work, the agent should verify the token-to-component mapping before suggesting CSS overrides, `!important`, `noStyle`, or headless mode.

***

## Agent Skills

c15t publishes agent skills that give AI coding assistants deep knowledge of c15t's APIs, components, and configuration. Skills are reusable workflows and tool-specific guidance, not version-matched local docs.

### Installation

Via the c15t CLI:

| Package manager | Command                             |
| :-------------- | :---------------------------------- |
| npm             | `npx @c15t/cli install-skills`      |
| pnpm            | `pnpm dlx @c15t/cli install-skills` |
| yarn            | `yarn dlx @c15t/cli install-skills` |
| bun             | `bunx @c15t/cli install-skills`     |

Or directly:

| Package manager | Command                           |
| :-------------- | :-------------------------------- |
| npm             | `npx skills add c15t/skills`      |
| pnpm            | `pnpm dlx skills add c15t/skills` |
| yarn            | `yarn dlx skills add c15t/skills` |
| bun             | `bunx skills add c15t/skills`     |

### What skills provide

* **Styling customization** — strict escalation guidance across props, tokens, slots, CSS variables, compound components, `noStyle`, and headless
* **Internationalization** — translation setup, locale routing integration
* **Script management** — configuring third-party scripts with consent categories
* **Component setup** — ConsentBanner, ConsentDialog, provider configuration

### Supported tools

* Claude Code
* Cursor
* GitHub Copilot (via `.github/skills`)
* Any agent that supports the skills format

***

## When to use which

Use bundled docs when:

* Your agent can read files in the local project
* You want version-matched docs from the installed c15t packages
* You want a package-local README that tells the agent which detailed docs to read first
* You want concrete guidance for consent management, cookie banners, consent dialogs, preference centers, script loading, callbacks, and integrations

Use agent skills when:

* Your tool supports the skills ecosystem
* You want reusable workflows and tool-specific guidance that can point back to the installed package README files

Use both when:

* Your tool supports both local file context and skills
* You want local package docs plus reusable setup and configuration help
* You want the bundled package docs as the source of truth plus a reusable decision tree for customization