> ## 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.

# Creative Teams

> Ideate with an assistant, produce in Studio, and standardize output with skills

Creative teams juggle ideation, production, and brand consistency across many formats. Brainstorming happens in meetings; assets land in shared drives; every designer interprets the brief a little differently.

UtopikAI connects **chat ideation**, **Studio production**, and **skills** so the team shares one way of working — without collapsing assistants and agents into a single concept.

Use an **assistant** for interactive brainstorming and brief refinement. Generate files in **[Studio](/studio/overview)**. Use **[skills](/skills/overview)** to encode repeatable creative workflows. Use an **agent** when production or review 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.

## Ideation with an assistant

Create a custom [assistant](/guides/assistants) for the creative team (or start from the built-in **Art** assistant). Attach brand guidelines, past campaign decks, and product visuals via document sets.

People then ask in chat, for example:

* Three concept directions for this campaign theme.
* Refine this prompt for a product hero shot.
* What does our style guide say about typography on social?

The assistant is for conversation and briefs — not for generating the final media file.

## Production in Studio

Open **[Studio](/studio/overview)** to generate the asset. Studio is a generation workspace; it is not the same as workflows.

* **[Image](/studio/image)** — Concepts, retouching, and background removal
* **[Video](/studio/video)** — Motion from a prompt or a still
* **[Audio](/studio/audio)** — Voice and music for spots and explainers
* **[3D](/studio/3d)** — Characters, products, and scene objects as models

Use **Target space** so outputs land where **Workspace members** expect them.

## Skills for repeatable creative work

Publish [skills](/skills/overview) that encode how your team works — for example:

* A storyboard outline skill assigned to the ideation assistant
* A brand-safe image prompt skill shared across the Workspace
* A review checklist skill an agent runs before saving to a space

Create skills in the **Admin panel** or from **Create skill**. See [Create](/skills/create) and [Install](/skills/install).

## Agents and workflows for production pipelines

When creative work should run without someone in chat — batch variants, scheduled refreshes, or a multi-step approval chain — use an **agent** plus **tasks** or **workflows**:

* **[Tasks](/tasks/overview)** — Recurring runs, for example weekly social variants from a connected content calendar
* **[Workflows](/workflows/overview)** — Generate in one step, then [user approval](/workflows/logic#user-approval) before assets publish to a space

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)
* [Create](/skills/create)
* [Workflows Overview](/workflows/overview)
* [Tasks Overview](/tasks/overview)