> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/component-designer/how-to-work-with-component-designer.md).
# How to work with component designer
Discover Component Designer areas
**Component Designer** has six distinct areas:
1. **Toolbar** – find tools to switch between selection and hand, and also to create [frames](/classic-app-builder/component-designer/frames-and-groups.md), shapes, text, images and [action components](/classic-app-builder/component-designer/action-components.md). These will be the building blocks of your designs.
2. **Parameters** – allow you to pass dynamic variables from your app to the component ang change states
3. **Actions** – trigger actions on the page, outside of your component
4. **Layers sidebar** – gives you access to layers.
5. **Canvas** – is your working area where you’ll arrange layers to create your designs. You’ll find lots of room to explore and iterate on your ideas.
6. [**Right sidebar**](/classic-app-builder/component-designer/right-sidebar.md) – access more information about your layers. With a layer selected, you can explore the properties of your current selection.
---
# 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.jetadmin.io/classic-app-builder/component-designer/how-to-work-with-component-designer.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.
