atlas_brief
Orient yourself in an unfamiliar project with a pre-computed, ranked briefing covering identity, layers, entrypoints, and key connected files.
Instructions
Get a pre-computed, token-bounded briefing that orients you in an unfamiliar project.
Call this FIRST, once, when you start working on a project you do not already know. It replaces the usual orientation ritual (listing directories, reading the README, opening several files just to get your bearings) with a single small response.
Returns a ranked summary: identity (repo, language distribution, size),
layers (the main directories, what role each plays, and their most important files),
entrypoints (how the project is actually started), and hubs (the most connected
files — the ones whose change propagates furthest). Every list is ranked and capped,
so the response size does NOT grow with the size of the repository.
Do NOT call this to enumerate symbols or files: by design it reports at most a handful
of layers and a few files per layer. Use atlas_search (optionally with path_prefix)
to find a specific implementation, and atlas_graph to explore connectivity.
Do NOT call it more than once per session — the briefing only changes after
atlas_index re-runs.
Facts are derived deterministically from the index; nothing is guessed. Entries carry
confidence (declared when read from a manifest such as pyproject/package.json,
inferred when detected in code) and warnings reports known gaps, e.g.
graph_unavailable, no_import_edges, low_symbol_coverage, index_stale.
Staleness is detected by comparing the indexed git HEAD with the current one, so
uncommitted edits are not detected (same limitation as atlas_status).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | Detail level. `0` is a minimal orientation (identity plus directory roles); `1` (default) adds per-layer top files, entrypoints and hubs. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |