> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/docs/product-wiki-es/herramientas-de-ia/add-a-layer.md).
# Agregar una capa
Genera nuevas capas musicales en ACE Studio eligiendo un tipo de capa y describiendo el estilo que deseas.
## Qué es Agregar una capa
Agregar una capa es una herramienta de IA que genera nuevas capas de audio directamente en el Lienzo. Te permite describir el estilo y crear una capa musical que se ajusta perfectamente a tu Proyecto.
## Cómo agregar una capa
### Selecciona un Rango
1. Haz clic y arrastra sobre el Lienzo para crear una selección de tiempo.
2. La selección define la hora de inicio y la duración de la nueva capa.
3. Abrir **Agregar una capa** desde la barra de herramientas.
### Generar una capa
1. Elige el tipo de capa que deseas generar.
2. En **estilos musicales**, introduce una breve descripción del sonido que deseas.
3. Si eliges **Pista de canción**, **Vocal**, o **Coros**, también puedes introducir letras.
4. Si eliges **Personalizado**, puedes introducir el instrumento que deseas.
5. Haz clic en Generar para iniciar el proceso. La IA analizará tu Proyecto y generará una nueva capa musical que encaje perfectamente.
---
# 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.acestudio.ai/docs/product-wiki-es/herramientas-de-ia/add-a-layer.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.
