---
name: save-atlas
description: Save navigation knowledge from this session to the atlas.
---

Review the code areas explored or changed in this session and save any durable navigation knowledge to the atlas. Start with AtlasList so you can see the current maps and avoid duplicates. AtlasUpdate replaces every point on the map, so when a related map already exists, read it first with AtlasRead and pass back the full point set you want to keep along with the new ones.

Only record areas that revealed real structure: a bug fix that touched multiple files, feature work in a new subsystem, a refactor that moved or renamed important pieces, or an investigation that clarified how components fit together. Skip trivial single-file edits that do not add much navigation value.

For each area worth keeping, update an existing matching map when one already exists. When a new feature or subsystem spans multiple files, create a dedicated map for it instead of scattering points across existing maps. Use a short descriptive name and a clear scope. Mark the important files, directories, and symbols, and give each point a brief note that explains why it matters.

If this session deleted, renamed, or moved files that appear in any map, those maps should already have been fixed immediately after each change. Verify now that no stale points remain.
