> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview.md). # ε Elements Elements are the graphical user interface (GUI) elements used by operating systems to offer a consistent visual language to interact with software and technology. These elements use a visual convention to represent information based on the OS it's on. These individual interface building blocks are used to build the components in the design system. Each element has their unique properties, such as typeface, color, size, and spacing, which make up the styles used in the design system. ## Φ Primitives Simple interface objects that are used to construct elements are considered primitives. These are objects that can't be broken down further. On their own primitives don't really accomplish much, but when combines with other primitives and elements they become functional pieces of our design system. As an example, a single radio button acts as primitive element in the design, as it can’t be broken down further. It can toggle on and off, carries a few properties, but being such a simple object, it doesn't accomplish much on its own. But, when combined with other primitives and elements like a Label it then starts to gain value as a functional part of the design system. We've set up a Kitchen Sink application that isolates all elements and components into their own screens to show the different variations of each. **Note:** The difference between an element and a component is that elements do not handle the spacing between elements, where components account for spacing, scaling, and breakpoint. --- # 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://able.bucca.com/core/overview.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.