> 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/checkbox/checkbox-shape.md).

# Ω CheckboxShape

Base: The shape given to a checkbox and its status at the Primitive level.

[Styleguide Link](https://zpl.io/brAxME1)

Parent: [CheckboxCtrl](/core/overview/checkbox.md)

To start with we will have two shapes available, the default normal [squared off checkbox](https://zpl.io/brAxME1) (that you see most of the time) and a customized appearance of "[Circle Check](https://zpl.io/anBGkKv)". These "Shapes" are set in the child level area of "Base - Shape" for the parent Checkbox Primitive.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2Ff28WLyOAFrK0WlyoU7aH%2FStyle.png?alt=media&amp;token=2d424097-e85c-4678-95df-69601e6ef7ab" alt=""><figcaption></figcaption></figure>

The appearance of the shapes and status (checked, unchecked, indeterminate) are all supplied from an icon in the icon library (Icons-Base > Icons > Primatives). They are labeled in the icons file as Checkbox On/Off/Indeterminate for the squared off and Selection On/Off/Indeterminate for the circular checkbox.


---

# 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/checkbox/checkbox-shape.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.