> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/style-formularza-i-style-komponentu.md).
# Form styles and component styles
## Adding CSS styles to the application
After clicking the button in the left sidebar menu **Application style**  a side panel with the CSS stylesheet editor embedded in the application will slide out. The button **Application style** is visible only in the editor **Request**.
Figure 1. Application style editing panel
The CSS editor offers:
* CSS syntax highlighting and autocomplete,
* text search,
* basic CSS validation,
* automatic refresh of the application after every change to the CSS definition.
The created style is applied by entering its name in the field **Style names** available in the section **Styling** panel **Properties**.
## Component styling and platform styles
Base components can be assigned styles defined in the platform or styles created in the application. Their names should be added in the panel **Properties** → section **Styling** → **Style names** (add subsequent styles by pressing the Enter key).
Figure 2. Example style ex-textfield-without-left-padding added to the component
\
\
When adding a platform style, we get a list of style suggestions available for a given component.
Figure 3. Example list of suggestions for the Label component
{% hint style="warning" %}
Available platform styles may vary depending on the deployment
{% endhint %}
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/style-formularza-i-style-komponentu.md?ask=&goal=
```
`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.