> For the complete documentation index, see [llms.txt](https://morphic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morphic.com/docs/es/guias-practicas/storyboarding.md).

# Storyboard

El storyboard en Morphic te ayuda a convertir ideas en cuadros visuales claros antes de la generación final. Te permite planificar escenas, la intención de cámara y el flujo visual desde las primeras etapas del proceso creativo.

Hay tres formas de crear storyboards en Morphic:

1. [Crear storyboards usando un guion](/docs/es/guias-practicas/storyboarding/storyboarding-using-a-script.md)
2. [Crear storyboards usando referencias visuales](/docs/es/guias-practicas/storyboarding/storyboarding-using-visual-references.md)
3. [Crear storyboards usando una cuadrícula](/docs/es/guias-practicas/storyboarding/storyboarding-using-a-grid.md)

***

Si tienes algún problema o alguna pregunta, no dudes en ponerte en contacto. Estaremos encantados de ayudarte. Escríbenos a [**support@morphic.com**](mailto:support@morphic.com)**.**


---

# 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://morphic.com/docs/es/guias-practicas/storyboarding.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.