> For the complete documentation index, see [llms.txt](https://docs.vechainkit.vechain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vechainkit.vechain.org/vechain-kit-v1.x/vechain-kit/troubleshooting/styling-issues.md).

# Styling Issues

VeChain Kit uses Chakra UI internally, which can cause styling conflicts with other CSS frameworks and custom styles.

### Common Problems

* CSS framework styles being overridden by VeChain Kit
* VeChain Kit components not rendering correctly due to missing Chakra setup
* Theme conflicts when your app also uses Chakra UI
* Unexpected styling on images, buttons, or form elements

### Quick Fixes

* **Install Chakra UI** as a peer dependency even if you don't use it directly
* **Use CSS layers** to control style precedence
* **Wrap your app** in ChakraProvider with ColorModeScript

### Issues in This Section

#### [Chakra Conflicts](#chakra-conflicts)

Setting up Chakra UI properly and resolving conflicts when your app also uses Chakra.

#### [CSS Framework Conflicts](#css-framework-conflicts)

Using CSS layers to resolve conflicts with Tailwind, Bootstrap, and other CSS frameworks.

***

**Can't find your issue?** Search our [GitHub Issues](https://github.com/vechain/vechain-kit/issues) or ask on [Discord](https://discord.com/invite/vechain).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vechainkit.vechain.org/vechain-kit-v1.x/vechain-kit/troubleshooting/styling-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.