> For the complete documentation index, see [llms.txt](https://tools.continis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tools.continis.io/superscenes/using-superscenes/adding-removing-components.md).

# Adding/Removing components

Once you have at least one Scene Component type in your project, you can start adding components to scenes.

## Adding a component

To do so, simply select a Scene asset in the Project view, and look at its Inspector:

<figure><img src="/files/aBIPWIw6wjIadl2XJaQ7" alt="" width="375"><figcaption><p>Adding a scene component</p></figcaption></figure>

When you click the Add Scene Component button, all types available in the project will show up as a dropdown. Select the one you want to add.

Once added, Scene Component will appear just like Game Object components:

<figure><img src="/files/FeETRgCIAL53W2X2lKXE" alt="" width="375"><figcaption><p>The Inspector of a scene file, displaying 2 scene components</p></figcaption></figure>

## Removing a component

To remove a component, right-click on its header (or left-click on the three dots menu) and choose Remove Component.

<figure><img src="/files/zM7zaTgLGZygVYCFJjyM" alt="" width="359"><figcaption><p>Right-click to remove a component</p></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tools.continis.io/superscenes/using-superscenes/adding-removing-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
