Atlas Context Sources
Use this skill to avoid shallow context gathering. Start with executable truth, then layer architecture and external docs.
Source Priority
- •Executable truth in this repository.
- •Atlas design and developer docs.
- •Git history for behavior changes.
- •Official external docs matching pinned versions.
- •Community posts only when primary sources are insufficient.
Prefer code over prose when they disagree. Treat docs as intent, not ground truth.
Workflow
- •Classify the request domain using references/domain-map.md.
- •Open at least one executable source and one supporting doc from that domain.
- •Check pinned versions (
package.json, crateCargo.toml) before reading external docs. - •Reconcile inconsistencies and state what source won and why.
- •Summarize with exact file paths, unresolved questions, and confidence.
Minimum Evidence Bar
- •Bug fix: failing path in code + architecture/context doc + validation command or test.
- •Feature work: entrypoint + contract/schema + release/deployment touchpoint.
- •API changes: route handler + shared types/schema + at least one caller.
- •Data format changes: proto or migration + serializer/parser + user/dev doc impact.
Fast Lookup Commands
bash
rg -n "keyword" apps crates docs
rg --files docs/dev docs/user
rg -n "route.ts|GET\\(|POST\\(" apps/web/app/api
rg -n "proto|manifest|pack|channel|build" crates apps
References
- •Atlas domain routing and best local files: references/domain-map.md
- •External primary docs by stack: references/external-sources.md