> For the complete documentation index, see [llms.txt](https://speedtutoruk.gitbook.io/door-interaction-kit-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://speedtutoruk.gitbook.io/door-interaction-kit-doc/support/system-namespace.md).

# System Namespace

**What is a namespace?**

A namespace is almost like a folder that keeps scripts and classes from clashing with others that might have the same name. It's good practise to add them around classes which may have common names or specific use cases, so you can keep the code specific to your systems.

```csharp
Namespace DoorInteractionKit;
```

**How to reference namespaces to use in other scripts?**

If you need to access the chess puzzle scripts from another script that isn’t in relation to this asset you may need to use a namespace collection at the top of your script:

```csharp
Using DoorInteractionKit;
```


---

# 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://speedtutoruk.gitbook.io/door-interaction-kit-doc/support/system-namespace.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.