Best Practices
Atom keeps you moving fast. These quick habits make sure the results stay dependable.
Protect your work
- Save before big automations so checkpoints and recovery copies have a stable project file.
- Duplicate important sequences before structural edits.
- Keep a simple backup naming rhythm (
Project_v01.prproj,Project_v02.prproj).
Stay clear and organised
- Use descriptive names for bins, sequences, clips, and tracks. Atom can only target what it can identify.
- Keep source media organized in stable bins so searches and edits stay predictable.
- Tighten the scope of each request (“selected clips”, “active sequence only”) for faster, cleaner runs.
Iterate with intent
- Build complex ideas in small steps and confirm after each reply.
- Ask Atom to inspect linked media, track placement, and timing before a large ripple edit or sequence rebuild.
- Check History to reuse great prompts and evolve them into a personal library.
Tune the chat
- Enable Settings → Features → Auto-scroll chat to keep long responses pinned to the latest update.
- Turn on Notification sound and choose a completion sound if you want an alert after longer tasks.
- Use Clear chat history when you want to remove all saved conversations.
Watch the meters
- Trial days count down in the top bar. Upgrade before the trial ends.
- Monitor your AI usage through your provider dashboard.
Capture what works
- Turn proven patterns into [skills](/docs/reference/skills) so Atom can reapply them across projects.
- Note repeatable prompts for teammates and keep conventions documented.
- Ask Atom to create a skill after you’ve built something worth reusing: “Create a skill from this caption style and export setup.”