Enforces documentation research before implementation. Auto-loads when implementing features to ensure current best practices are followed. Researches official docs first.
Installs into .claude/skills of the current project.
Are you the author of Documentation Research?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/diegosouzapw-documentation-research)
---
name: documentation-research
description: Enforces documentation research before implementation. Auto-loads when implementing features to ensure current best practices are followed. Researches official docs first.
user-invocable: false
---
# Documentation Research Skill
This skill enforces documentation research before any technical implementation to ensure code follows current best practices.
## Core Principle
**NO IMPLEMENTATION WITHOUT DOCUMENTATION RESEARCH**
Before writing ANY code:
1. Search official documentation online
2. Verify current best practices
3. Check for deprecated patterns
4. Report findings to user
5. Only then proceed
## Documentation Sources
| Technology | Primary Documentation |
|------------|----------------------|
| Django | docs.djangoproject.com |
| FastAPI | fastapi.tiangolo.com |
| React | react.dev |
| Python | docs.python.org |
| TypeScript | typescriptlang.org/docs |
## Research Protocol
1. **Search Official Docs** - Use WebSearch/WebFetch
2. **Verify Version** - Check latest stable release
3. **Review Best Practices** - Note recommended patterns
4. **Check Deprecations** - Avoid outdated APIs
5. **Document Findings** - Summarize before implementing
## Report Format
```
π Documentation Research Summary
ββββββββββββββββββββββββββββββββββ
π Technology: [Framework]
π¦ Version: [Version]
β CURRENT BEST PRACTICES
β’ [Practice 1]
β’ [Practice 2]
β οΈ DEPRECATED PATTERNS (Avoid)
β’ [Pattern] - Use [alternative] instead
π SOURCES
β’ [URL]
Ready to proceed? (yes/no)
```
## Enforcement Rules
1. Documentation research is non-negotiable
2. Always verify which version is being used
3. Check for deprecated APIs before using
4. Follow security best practices from docs