> For the complete documentation index, see [llms.txt](https://docs.devlaunchers.org/dl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/contributing/creating-components/variables-+-properties.md). # Variables + Properties ## Overview In the Universal Design System (UDS), **property types** help define and control how components behave, look, and adapt across contexts. These properties are powered by **Figma variables**, which allow us to build flexible, responsive, and accessible components using reusable tokens. Property types allow us to define rules around appearance, behavior, content, and structure — keeping components consistent and scalable without hardcoding values. ### What are Variables in Figma? Variables are named values we can re-alias in layers that allow us to conditionally assign multiple potential values based on a series of conditional statements.

We can also use them to create consistency in more simple use cases such as presets like padding values. Variables are raw values — like colors, numbers, or text — that can be reused and adjusted depending on the design context (e.g. light vs. dark mode, mobile vs. desktop). When used in components, variables: * Ensure consistency across projects * Enable theme-aware styling (like dark mode) * Allow quick updates across files * Support localization, accessibility, and responsive behavior ### What are Properties in Figma? <...> ### How Do They Work Together? <...> --- # 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.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/contributing/creating-components/variables-+-properties.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.