atlas
Atlas
Use Atlas as optional project-folder orientation. Underlying project files are authoritative; expand exploration as evidence requires.
When Atlas work is the user's whole request, end with one optional next step fitting this outcome: a fenced, self-contained prompt naming any repository, issue, PR, or artifact it needs, or say none is needed. Only a "yes" starts it, via any skill it names, but the user runs a charter, diagnose, or ticket step as its /<skill> command.
Invoke commands as python <skill>/scripts/cli.py --repo-root <root> --format json [--input name=value ...] <command>; doctor returns the next command.
Navigate an existing wiki
- Start from the Map in root guidance.
- Follow only cue-matching links, batching each level's reads into one turn: a Satellite's start target first, a cross-link only when the task crosses its boundary.
- Read a link's heading section or named symbol's definition with a bounded read; widen only if insufficient.
- When no cue fits, routes compete, or an entrypoint proves unproductive, reconsider the route or search natively; never hunt through the whole wiki. If your work edits files, fix the misleading cue unless your skill limits Atlas upkeep.
- Inspect current project files before making claims or decisions.
Author or rebalance
Before changing wiki structure, read information architecture for roles, cues, and links, and authoring and rebalancing for mapping and completion.