# Moves

> Named motion design techniques your agent understands, and how to use their prompts.

Moves are named motion design techniques: what each one looks like, when it works, and where it shows up in the gallery. Ask your agent for a move by name.

A move is one technique, such as squash and stretch: what it looks like, when it works, the mistakes to avoid, and videos in the gallery that use it. The name gives you and your agent one word for the motion you want.

## Families [#families]

Moves are grouped into families: Timing, Type, Transitions, UI, Vector, Generative, Camera, Texture, Data and Sound.

## Use a move [#use-a-move]

<Steps>
<Step>

### Find it [#find-it]

Find a move on the [Moves page](/moves). Filter by family.

</Step>
<Step>

### Read it [#read-it]

Open it to see what it looks like, when it works, the mistakes to avoid and gallery videos that use it.

</Step>
<Step>

### Copy its prompt [#copy-its-prompt]

With Pro, copy its prompt into your request to a coding agent that makes videos in code, next to what the video is about.

</Step>
<Step>

### Tune the parameters [#tune-the-parameters]

Adjust the parameters it names, such as timing or stagger, until the motion feels right.

</Step>
</Steps>

<Callout type="info" title="Prompts are in Pro">
  Move pages are free to read. The copy-ready prompt and the parameters to tune
  for every move are in [Pro](/pro).
</Callout>

## Public data [#public-data]

The public part of every move (name, family, summary, good-for tags, gallery examples and related moves, no prompts) is available as JSON at `/api/moves`. See the [Public API](/docs/api).