read-docslisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Read Docs Search internal documentation for project-specific information. ## Usage ``` /read-docs auth # Search for auth-related docs /read-docs database schema # Search for database/schema docs /read-docs # List available documentation ``` ## Search Strategy 1. **Check for docs/ folder** - Primary documentation location 2. **Search filenames** - Glob for keyword matches in file names 3. **Search contents** - Grep for keyword matches in file contents 4. **Prioritize results**: - Exact filename match (e.g., "auth" → `docs/auth.md`) - Filename contains keyword (e.g., "auth" → `docs/authentication-guide.md`) - Content matches (e.g., "auth" mentioned in `docs/architecture.md`) ## Locations Searched In order of priority: 1. `docs/**/*.md` - Primary documentation 2. `CLAUDE.md` - Project conventions 3. `README.md` - Project overview 4. `*.md` in project root - Other documentation ## Gotchas - The search cap of 5 files means relevant docs can be silently skipped. If the most relevant doc ranks 6th, it will be listed but never read. - Trust code over docs when they conflict — docs may describe an intended design that was never implemented or was later changed. ## Workflow ### With keywords: 1. Search filenames for keyword matches: - Glob pattern: `docs/**/*{keyword}*` 2. Search file contents for keyword match