> 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/codecks-scene-notes/intro.md).

# Intro

<figure><picture><source srcset="/files/V8I015kAs7YikZjXEXu9" media="(prefers-color-scheme: dark)"><img src="/files/bHHSrvfdcq6mjmooxGU5" alt=""></picture><figcaption></figcaption></figure>

:link: Available on the [**Unity Asset Store**](https://bit.ly/codecksscenenotes_as)&#x20;

Codecks Scene Notes is a Unity integration of [**Codecks**](https://tools.continis.io/codecks-scene-notes/www.codecks.io), which brings added power to an already cool project management tool.

See what it is about in this quick trailer:

{% embed url="<https://youtu.be/xApCaowevM0?si=fuQOerWkQk8wa8na>" %}

### Requirements

To use Codecks Scene Notes you need to have an existing Codecks account (free tier is fine), and you need a working internet connection. You can create one at [**codecks.io**](https://tools.continis.io/codecks-scene-notes/www.codecks.io).

{% hint style="info" %}
If you are looking for a simple notes integration that is completely project-based (no server, no backend), you can consider my other asset [Scene Notes](https://tools.continis.io/scene-notes/)!
{% endhint %}

### Terminology

In Codecks, every note, bug, issue, etc. is represented by a card, and cards are grouped into decks. In this tool, once cards make it into Unity we refer to them as Scene Notes.

There is a one to one correspondence: (in Codecks) a **Card** < > a **Scene Note** (in Unity)

In essence, to create a Scene Note you take a Codecks card and you assign it a position in space, and a scene that it is associated with.

{% hint style="warning" %}
A Scene Note can't exist without having a Codecks card associated to it.
{% endhint %}


---

# 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/codecks-scene-notes/intro.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.