> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/features/components.md).

# Components

You can reuse components across different projects, and you can also save them to a style guide.

***

{% embed url="<https://vimeo.com/1145946645?fe=ci&fl=sv&share=copy>" %}

### **Save a component to a style guide**

1. Open the project.
2. Click **Project options** (the dropdown next to the project name in the top-left).
3. Select **View components**.
4. In the left sidebar, choose a component, then click **Save to style guide** (top-right).
5. Pick the style guide to save it to.

Next time you create a project from that style guide, it will automatically include all components saved to it.

***

### **Reuse components**

1. In your project, click the **+** next to the prompt field and select **“Insert component.”**
2. Choose the source for the component:
   * **Current project**
   * **Another project**
   * **Current style guide** (if the project uses one)
3. Browse the available components, select the one you want, and click **“Insert into project.”**
4. Optionally, refine the prompt to specify where to insert the component or any changes you’d like to make.

***

### **Adding a component that exists in a project but isn’t available to insert**

1. Open the project.
2. Click **Project options** (next to the project name in the top-left).
3. Click **View components**.
4. Review the list. If a component is missing, click **Select element from project** (top-right).
5. In the preview, click the element you want to extract.


---

# 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.maker.co/features/components.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.
