aria-nbv-context

name	aria-nbv-context
description	Use to localize unknown ARIA-NBV files, symbols, docs, or source families through deterministic local discovery before handoff.
metadata	{"mode":"router","not_when":["exact file and owner are already known","KG-backed authority, freshness, or claim checking is required","a concrete failure command or traceback owns the task"],"handoff_to":["aria-litkg-memory for KG-backed retrieval, routing, or claim checks","diagnose-aria for concrete failures","nearest AGENTS.md or narrow skill after localization"],"evidence_required":["localized owning files or source family","nearest applicable AGENTS.md","targeted rg or generated context evidence"],"applies_to":["**"],"triggers":["locate files","cross-surface context","where is this implemented","source family"],"must_read":["AGENTS.md",".agents/references/source_order.md"],"canonical_sources":["AGENTS.md",".agents/references/source_order.md#role-split",".agents/skills/aria-nbv-context/references/context_map.md"],"literature_refs":["docs/contents/literature/index.qmd","docs/literature/sources.jsonl","quality-driven-rri","finite-candidate-rl"],"tool_refs":["mcp__code_index.search_code_advanced","mcp__code_index.get_symbol_body"],"verification":["make context when generated context is stale or missing"]}

Aria NBV Context

Use this skill as the local discovery layer. It should identify the smallest relevant set of files, then hand off to a narrower implementation, docs, KG, or diagnostic workflow.

Workflow

1. Read AGENTS.md and .agents/references/source_order.md.
2. Use docs/_generated/context/source_index.md only when it already exists or source-family routing is unclear; refresh with make context only when needed.
3. Use source-specific outline tools before broad raw reads:
   • Quarto: scripts/nbv_qmd_outline.sh --compact
   • Typst: scripts/nbv_typst_includes.py --paper --mode outline
   • Literature: scripts/nbv_literature_index.sh
   • Code/contracts: scripts/nbv_get_context.sh modules|contracts|match <term>
4. Open the nearest nested AGENTS.md once the surface is known.
5. Use targeted rg inside the narrowed file set.

Zoom-Out Output

When asked to map a surface, return:

• domain term and glossary anchor when one exists
• owning package/module and nearest AGENTS.md
• main callers and data contracts
• relevant tests or render checks
• docs/memory surfaces likely to need updates
• open risks or missing context

References

• references/context_map.md for non-obvious concept-to-source routing.