> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/overview/how-to.md).

# How to

Task-shaped guides for the control problems that drive pro creatives off pure prompt tools – consistent characters, controlled composition, brand-true renders.

Task-shaped guides for the control problems that surface most often when a pro creative tries to deliver finished work from an AI tool. Each page is one specific job, end to end, with steps you can follow on a real project.

These pages assume you already have a project open. If you don't, start with [Make your first render](/overview/get-started/first-render-in-20-minutes.md).

## Most-asked

* [Keep a character consistent across shots](/overview/how-to/consistent-character-ai.md) – the single highest-leverage technique for finished work.
* [Build a storyboard](/overview/how-to/ai-storyboard.md) – from a fresh project to a scene-grouped shot list.
* [Make an animatic](/overview/how-to/ai-animatic.md) – cut your shots into a playable edit.

## Related concepts

* [Controlling AI output](/overview/concepts/control-ai-output.md) – why the three modes solve the problems pure prompt tools can't.
* [Image reference](/overview/concepts/image-reference.md) – the concept under most of the consistency how-tos.
* [How the visualizer thinks](/overview/concepts/how-the-visualizer-thinks.md) – the technical why.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/overview/how-to.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 `build a script that syncs our docs to a CMS` 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.