read-docs
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
- Check for docs/ folder - Primary documentation location
- Search filenames - Glob for keyword matches in file names
- Search contents - Grep for keyword matches in file contents
- 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)
- Exact filename match (e.g., "auth" →
Locations Searched
In order of priority:
docs/**/*.md- Primary documentationCLAUDE.md- Project conventionsREADME.md- Project overview*.mdin 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:
-
Search filenames for keyword matches:
- Glob pattern:
docs/**/*{keyword}*
- Glob pattern:
-
Search file contents for keyword matches:
- Grep pattern:
{keyword}path:docs/and root*.mdfiles
- Grep pattern:
-
Rank matches by priority:
- Exact filename match (e.g., "auth" →
docs/auth.md) - Filename contains keyword (e.g., "auth" →
docs/authentication-guide.md) - Content match with keyword in a heading (e.g.,
## Authindocs/architecture.md) - Content match in body text
- Exact filename match (e.g., "auth" →
-
Read up to 5 top-ranked matches and summarize findings.
-
For multi-word queries (e.g., "database schema"), search each word separately AND as a phrase. Prioritize files that match all words over files matching only one.
-
If more than 5 files match, list the remaining filenames without reading them so the user knows what else is available.
Without keywords:
List available documentation:
- Glob pattern:
docs/**/*.md - Glob pattern:
*.md(root-level docs)
Present a structured overview of available documentation:
- Group files by directory (e.g.,
docs/api/,docs/guides/, root-level) - For each file, show the filename and its first heading (or first non-empty line if no heading exists)
- If more than 20 files exist, summarize by directory with file counts and list only the top-level structure instead of enumerating every file
Output
Summarize findings:
- Documents found - List with brief description of each
- Key information - Relevant excerpts for the query
- Related docs - Other documents that may be useful
Examples
Search internal docs before implementing auth feature:
/read-docs auth
Searches docs/ filenames and contents for auth-related documentation. Finds docs/auth.md and references in docs/architecture.md, then summarizes relevant patterns, token handling conventions, and any documented gotchas before you start coding.
Check for documented gotchas before refactor:
/read-docs database migration
Searches for migration-related docs and surfaces any documented pitfalls, required steps, or past issues logged in docs/log/. Presents key findings so you can avoid known problems during the refactor.
Troubleshooting
No docs/ folder found in project
Solution: Fall back to searching root-level .md files (README.md, CLAUDE.md, CONTRIBUTING.md). If the project has no documentation at all, use research-online for external references or check inline code comments via Grep for conventions.
Documentation is stale or contradicts code
Solution: Trust the code over the documentation when they conflict. Note the discrepancy in your response so the user can update the docs, and verify behavior by reading the actual source files rather than relying on the outdated documentation.
Notes
- This skill is for internal project docs, not external library docs
- For external library documentation, use
research-online - If no docs/ folder exists, search root .md files only
More from nielsmadan/agentic-coding
pdf
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
22review-comments
Review and clean up low-quality code comments. Use when you notice "what" comments that should be "why" comments, or want to clean up comment noise before a PR.
12frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, artifacts, posters, or applications (websites, landing pages, dashboards, React components, HTML/CSS layouts) or when styling/beautifying any web UI.
11optimize-seo
Audit and optimize web pages for SEO. Use when user asks to "optimize SEO", "check SEO", "add meta tags", "add structured data", "add schema markup", "improve search ranking", "SEO audit", or wants to generate Open Graph tags, JSON-LD, or fix SEO issues on HTML pages.
11skill-creator
Guide for creating effective skills. Use when users want to create a new skill, update an existing skill, or need help structuring a skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Triggers on "create a skill", "build a skill", "new skill", "improve this skill", or "skill for [use case]".
11review-security
Security audit for vulnerabilities, secrets, and unsafe patterns. Use before releases, after adding auth code, or when reviewing third-party integrations.
10