> For the complete documentation index, see [llms.txt](https://react-dsfr.codegouv.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://react-dsfr.codegouv.studio/colors.md). # Colors Most of the time, when using the provided components from the Design System for French Republic (DSFR), there is no need to explicitly manipulate colors. These components are designed with a set of default colors that aim to maintain consistency and harmony across your application or website. However, when you are crafting a new component or customizing existing ones, it becomes essential to select the appropriate color scheme that aligns with the DSFR guidelines for your specific use case. To assist you in effortlessly navigating through the DSFR color palette and selecting the perfect hues for your components, we provide you with a user-friendly color picker tool. This tool is designed to simplify the process of choosing colors that adhere to the DSFR’s design principles, ensuring that your custom components not only look visually appealing but also maintain a cohesive and unified design language. {% embed url="" %} Color picker tool {% endembed %} {% embed url="" %} Tutorial {% endembed %} --- # 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://react-dsfr.codegouv.studio/colors.md?ask=&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.