> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/integrations/integration-guides/sdk/react/yo-kit-provider.md).

# YO Kit Provider

`YoKitProvider` is an optional theming provider for the pre-built UI components in `@yo-protocol/react` (VaultCard, DepositModal, RedeemModal).

## Usage

```tsx
import { YoKitProvider } from '@yo-protocol/react'

// Use a preset theme
<YoKitProvider theme="dark">
  <App />
</YoKitProvider>

// Or customize the theme
<YoKitProvider theme={{
  colors: {
    primary: '#6366f1',
    background: '#0f0f0f',
  },
}}>
  <App />
</YoKitProvider>
```

## Props

| Prop       | Type                                       | Default  | Description                      |
| ---------- | ------------------------------------------ | -------- | -------------------------------- |
| `children` | `ReactNode`                                | —        | Required                         |
| `theme`    | `'light' \| 'dark' \| Partial<YoKitTheme>` | `'dark'` | Theme preset or custom overrides |

## Theme Object

When providing a custom theme, you can override any subset of:

```ts
interface YoKitTheme {
  colors: Record<string, string>
  radii: Record<string, string>
  fonts: Record<string, string>
  shadows: Record<string, string>
}
```

Custom themes are merged on top of the dark theme defaults.

## How It Works

`YoKitProvider` injects a `<style>` tag with CSS custom properties into the document head. The pre-built components reference these variables for styling.

This is separate from the docs-site theme (managed by `next-themes`). You only need `YoKitProvider` if you use the pre-built UI components.


---

# 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.yo.xyz/integrations/integration-guides/sdk/react/yo-kit-provider.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.