> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark/cues/adding-and-deleting-cues.md).
# Adding and Deleting Cues
## Cue Options Window
The **New Cue Options Window** will appear when a new **cue is added** or a **cue is duplicated**. From here you can assign a **Cue Number, Cue Description**, and a **Cue Color**.
## Change Default Cue Color
If you want to change the Default Cue Color, change it in the **Spikemark Defaults**
## Add New Cues
There are several ways to **create a new cue:**
* [Menu Bar](#add-a-cue-from-the-menu-bar)
* [Hot Keys: CTRL + U](#add-a-cue-hot-keys-ctrl-u)
* [Right Click in the open space](#add-a-cue-with-right-click)
* [Duplicate Cues](#duplicate-a-cue)
###
### Add A Cue From the Menu Bar
###
### Add A Cue Hot Keys - CTRL + U
###
### Add A Cue with Right Click
## Duplicate A Cue
A new cue can also be created by duplicating one. This will copy over all of the properties and movements within that cue.
### Duplicate A Cue with Right Click
###
### Duplicate A Cue with CTRL+D
## Delete A Cue
When a cue is no longer needed, it's simple to delete a cue from the show.
### Delete A Cue With Right Click
###
### Delete A Cue Hot Keys - CTRL + SHIFT + U
---
# 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.creativeconners.com/docs/spikemark/cues/adding-and-deleting-cues.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.
