doc-navigatorlisted

# Doc Navigator Navigate codebase documentation efficiently by checking known doc locations first, before resorting to grep/glob searches. ## When to Use - Finding architectural decisions (ADRs) - Locating feature specs or API docs - Researching codebase before implementation - Suggesting documentation structure for new projects - Alternative to grep/glob for doc discovery ## Quick Start 1. Check for docs directory at project root 2. Scan for common doc file patterns 3. If docs exist → map topics to locations 4. If no docs → suggest documentation structure (see `references/doc-patterns.md`) ## Common Documentation Locations Check these locations in order: ``` project-root/ ├── docs/ # Primary documentation │ ├── architecture/ # System design, ADRs │ ├── features/ # Feature specs │ ├── api/ # API documentation │ └── guides/ # How-to guides ├── .github/ # GitHub-specific docs │ └── docs/ ├── README.md # Project overview ├── ARCHITECTURE.md # High-level architecture ├── CONTRIBUTING.md # Contribution guidelines └── doc/ or documentation/ # Alternative doc folders ``` ## Topic-to-Location Mapping | Looking for... | Check first | |----------------|-------------| | Project overview | `README.md` | | Architecture/design | `docs/architecture/`, `ARCHITECTURE.md`, `docs/adr/` | | Feature specs | `docs/features/`, `docs/specs/` | | API reference | `do