What problem does it solve? When working in the Viru Air monorepo, re-onboarding after a break means re-reading a large documentation tree and risking confusion between live docs and archived history. This Skill provides a compact, reusable operating context so you can quickly identify which documents are canonical, which are historical, and what the current working rules are before editing, verifying, or publishing changes. ## Core Features & Use Cases - Fast Re-onboarding: A prioritized reading path through AGENTS.md, README.md, docs/overview, and the Codex operating contract so you regain context without scanning the full docs tree. - Source-of-Truth Discipline: Clear rules distinguishing live documentation (docs/overview, docs/reference, docs/specs, docs/runbooks, docs/qa) from historical material (docs/plans, docs/archive). - Operating Rules Reference: Bundled references summarize the project map, stack (FastAPI, Next.js, Postgres, Redis), main routes, and the adapted review-and-publication workflow. - Use Case: You return to the Viru Air repo after two weeks and need to modify a backend contract. Use this Skill to reload the canonical doc map, confirm the operating rules, and know exactly which reference files to open before editing. ## Quick Start Use the viru-air-context skill to reload the project context and tell me which docs are canonical before I start editing the backend.
