latest-docs
Fetch and verify latest official documentation before implementation. Use when implementing features with any library, framework, or technology. Prevents outdated patterns and deprecated API usage.
When & Why to Use This Skill
The Latest Documentation Check skill ensures that software implementations are always aligned with the most current official documentation. By proactively fetching real-time data on libraries, frameworks, and APIs, it bridges the gap created by AI knowledge cutoffs, preventing the adoption of outdated patterns, deprecated APIs, and breaking changes in modern development workflows.
Use Cases
- Version Upgrades & Migrations: Automatically identify breaking changes and required code adjustments when upgrading dependencies like React, Next.js, or Node.js.
- New Technology Adoption: Fetch the latest best practices and syntax for unfamiliar libraries to ensure the implementation follows current industry standards.
- API Reliability: Verify the most recent endpoint structures and parameter requirements to prevent runtime errors caused by using deprecated or modified API methods.
- Environment Compatibility: Check for version-specific behaviors across different runtimes (e.g., Node.js vs. Bun) or language versions (e.g., Python 3.10 vs. 3.12).
| name | latest-docs |
|---|---|
| description | | |
| context | implementation, development, library, framework, api |
| auto-trigger | true |
Latest Documentation Check
Purpose
Ensure implementations follow the latest official documentation. Prevent usage of deprecated APIs, outdated patterns, or breaking changes.
When to Use
Automatic Triggers
- Before implementing features using external libraries/frameworks
- Before using APIs that may have version-specific behavior
- When upgrading or migrating dependencies
- When user mentions specific library/framework versions
Manual Check
- When uncertain about current best practices
- When documentation may have changed since knowledge cutoff
Process
Step 1: Identify Technologies
List all technologies/libraries involved in the implementation:
- Framework (React, Vue, Next.js, etc.)
- Libraries (axios, lodash, etc.)
- Runtime (Node.js, Deno, Bun, etc.)
- Language features (TypeScript, Go, Python version)
Step 2: Fetch Latest Documentation
Use WebSearch to find current official documentation:
WebSearch: "[library name] official documentation [current year]"
WebSearch: "[library name] latest version changelog"
WebSearch: "[library name] migration guide"
Step 3: Verify Version Compatibility
Check:
- Current stable version
- Breaking changes from previous versions
- Deprecated APIs to avoid
- New recommended patterns
Step 4: Document References
In your implementation response, include:
- Documentation URL referenced
- Version number verified
- Any deprecation warnings noted
Quick Reference
| Check | Search Query |
|---|---|
| Latest version | [lib] latest version [year] |
| Best practices | [lib] best practices [year] |
| Deprecations | [lib] deprecated api |
| Migration | [lib] migration guide v[X] to v[Y] |
Important Reminders
- Always verify version - Project may use different version than latest
- Check package.json/go.mod - Confirm actual version in use
- Note breaking changes - Inform user of any migration needs
- Cite sources - Include documentation URLs in response
Output Format
When referencing documentation, include:
Documentation verified:
- [Library]: v[X.Y.Z] (https://...)
- Last checked: [date]
- Notes: [any deprecations or important changes]