> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/ui-primitives-and-theming/theming.md).

# Theming Guide

Limio supports theming so each customer can have their own visual identity while using the same component library.

[**View interactive theming guide in Storybook**](https://innovate42.github.io/innovate42-service-template/?path=/docs/theming-guide--docs)

## How it works

Every component's appearance is driven by CSS custom properties (design tokens). You inject a stylesheet that overrides the tokens you want to change — everything else inherits from the default theme.

You can inject custom CSS via your Limio settings (Developer → General Settings). See [how to inject custom code](https://docs.limio.com/product/analytics/how-to-configure-the-limio-data-layer-to-collect-user-events-for-analytics) for the general approach.

## Customising your theme

Inject a CSS stylesheet that overrides the [design tokens](https://docs.limio.com/components/ui-primitives-and-theming/design-tokens.md) you want to change:

```css
@layer base {
  :root {
    --tw-primary: 220 85% 45%;
    --tw-primary-foreground: 0 0% 100%;
    --tw-text-primary: 220 60% 15%;
    --tw-text-secondary: 220 30% 35%;
    --tw-surface-main: 220 15% 96%;
    --tw-radius: 0.75rem;
  }
}
```

Only override what differs from the default. All other tokens inherit automatically.

Colour values are **space-separated** HSL triplets **without** the `hsl()` wrapper (e.g. `220 85% 45%`, not `220, 85%, 45%` and not `hsl(220, 85%, 45%)`). Components compose the token as `hsl(var(--tw-primary) / <alpha-value>)`, so a comma-separated value produces invalid CSS and silently breaks every opacity utility (for example the Button's `hover:tw-bg-primary/80`).

## Testing your changes

Use your browser's developer tools to override token values and preview changes instantly in Storybook.

## Further reading

* [Design Tokens](https://docs.limio.com/components/ui-primitives-and-theming/design-tokens.md) — all available tokens and their defaults
* [Primitives](https://docs.limio.com/components/ui-primitives-and-theming/primitives.md) — the component catalogue
* [Compositions](https://docs.limio.com/components/ui-primitives-and-theming/compositions.md) — real-world patterns showing themed components in action


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/components/ui-primitives-and-theming/theming.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
