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

# Design and Theming

Build a consistent responsive design system with themes, breakpoints and dark mode

Elements uses a project-wide design system to keep colours, typography, spacing, borders, shadows, and responsive behaviour consistent.

### Theme Studio

[Theme Studio](/elements-docs/using-elements/design-and-theming/theme-studio.md) is where you choose a theme and configure the shared values used by components throughout the project.

Its sections cover:

* Theme selection and creation.
* Responsive screens and container widths.
* Page colours.
* Colour palettes.
* Font families and sizes.
* Spacing, shadows, border widths, and border radii.
* Typography rules for paragraphs, headings, code, quotations, lists, and links.

### Breakpoints

[Breakpoints](/elements-docs/using-elements/design-and-theming/responsive-breakpoints.md) control where responsive property overrides begin. Elements follows a mobile-first system, so a value continues into larger breakpoints until it is overridden.

### Dark Mode

[Dark Mode](/elements-docs/using-elements/design-and-theming/dark-mode.md) lets the design respond to the visitor’s system or browser appearance. Theme colours provide paired light and dark values so components can switch consistently.

### Recommended Workflow

1. Choose or create a Theme.
2. Set the responsive Screens and container widths.
3. Define the primary colour roles and dark-mode values.
4. Choose fonts, type sizes, and Typography rules.
5. Establish spacing, borders, radii, and shadows.
6. Build pages with theme values before adding local overrides.


---

# 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.realmacsoftware.com/elements-docs/using-elements/design-and-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.