Best Practices

Atom keeps you moving fast. These quick habits make sure the results stay dependable.

Protect your work

• Save before big automations so Undo always has a safe place to land.
• Duplicating a comp for experiments lets you compare versions without stress.
• Keep a simple backup naming rhythm (Project_v01.aep, Project_v02.aep).

Stay clear and organised

• Use descriptive layer names. Atom can only hit what it can identify.
• Stick to a consistent stack (controls on top, hero layers in the middle, utilities below) to keep prompts predictable.
• Tighten the scope of each request (“selected layers”, “Scene 03 only”) for faster, cleaner runs.

Iterate with intent

• Build complex ideas in small steps and confirm after each reply.
• When working with expressions, ask Atom to outline dependencies before renaming or deleting layers.
• Check History to reuse great prompts and evolve them into a personal library.

Watch the meters

• Trial chats count down in the top bar. Upgrade before you run out mid-session.
• Monitor OpenRouter usage in your dashboard and set spending limits so you never hit a surprise cap.

Share the playbook

• Note repeatable prompts for teammates and keep conventions documented.