> 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/developers/store/submission-requirements/component-checklist.md).

# Component Checklist

If you are building components for Elements, they must meet the following criteria:

* [ ] **Do no modify the look of the Editor:**
  * [ ] Do not change the look of other components in the editor.
* [ ] **Component is WYSIWYG in the Editor:**
  * [ ] The Editor looks the same (or as close as technically possible) to Preview.
  * [ ] Settings and Admin options are not visible in the Editor. Place these in the Inspector, or include a toggle to hide in the Editor.
* [ ] **Component MUST use Tailwind CSS:**
  * [ ] Component styling should always use Tailwind classes found in the Theme Studio
  * [ ] Component should always use Theme based UI Controls where possible
  * [ ] Avoid generating custom CSS, always prefer Tailwind CSS
  * [ ] Do not use !important statements for generated CSS
* [ ] **Component should be Performant:**
  * [ ] Component should not parse @text or @typography data in their hooks.js files
  * [ ] Component UI should not slow down Editor
* [ ] Do not include HTML comments in code output


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/elements-docs/developers/store/submission-requirements/component-checklist.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 `build a script that syncs our docs to a CMS` 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.