> ## Documentation Index
> Fetch the complete documentation index at: https://docs.utopikai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Creation

> Draft briefs in chat with an assistant, then generate images, video, and audio in Studio

Content teams often split work between a writer who shapes the message and a designer who produces the asset. That handoff slows blog posts, social campaigns, and product explainers.

UtopikAI lets you **brainstorm and refine in chat**, then **generate the file in Studio** — without treating chat as a substitute for media generation.

Use an **assistant** for the interactive brief and copy. Generate images, video, audio, or 3D in **[Studio](/studio/overview)**. Use an **agent** only when content work should run on its own, on a schedule, or inside a **[workflow](/workflows/overview)**. Assistants and agents are two different entities; each has its own models, knowledge, skills, tools, and prompts.

## A content assistant

Create a custom [assistant](/guides/assistants) for your content team (or start from the built-in **Art** or **General** assistant). Instruct it on brand voice, audience, and what to cite from connected knowledge.

People then ask in chat, for example:

* Turn this product update into three social post variants.
* What tone fits this audience based on our style guide?
* Draft a shot list for a 30-second product demo.

The assistant can iterate on headlines, hooks, and structure before anyone opens Studio.

## Generate in Studio

**[Studio](/studio/overview)** is the generation workspace — not the same as workflows. Open the generator you need:

* **[Image](/studio/image)** — Hero stills, social graphics, and concept art from a text prompt or reference image
* **[Video](/studio/video)** — Short clips from a prompt or a still
* **[Audio](/studio/audio)** — Voiceovers and music beds for those clips
* **[3D](/studio/3d)** — Product or character models when the deliverable is a mesh, not a flat image

Save outputs to a **space** with **Target space** so **Workspace members** can find them.

## Knowledge worth connecting

Attach document sets so the assistant stays on brand and accurate. Typical sources, via [connectors](/connectors/overview):

* Brand guidelines and style guides
* Product docs and release notes
* Past campaign performance summaries
* Approved messaging and claims

Connectors are optional. Index them when you want answers grounded in those sources.

## Skills, tools, and scheduled work

* **[Skills](/skills/overview)** — Reusable instructions for recurring formats, for example a blog outline or social caption template
* **[Tools](/tools/overview)** — Publish or hand off assets to apps your team already uses. The live catalog is on the [UtopikAI tools page](https://www.utopikai.com/tools)
* **[Tasks](/tasks/overview)** — Recurring runs of one assistant or agent, for example a weekly content brief from recent product updates

Do not use a chat assistant as a substitute for unattended runs. Create an [agent](/guides/agents) for that.

## Related documentation

* [Use Cases Overview](/more/use_cases/overview)
* [Creating Assistants](/guides/assistants)
* [Creating Agents](/guides/agents)
* [Studio Overview](/studio/overview)
* [Skills Overview](/skills/overview)
* [Tasks Overview](/tasks/overview)