Overview

Helps ensure development work follows established best practices from dependency management to documentation verification. It emphasizes using the latest dependency versions, avoiding assumptions about external tools, and using context7 MCP to align docs with declared versions.

How This Skill Works

During tasks, it prompts you to always use the latest dependency versions and to consult official docs rather than guessing. It relies on context7 MCP to fetch documentation and verify that the docs match the declared dependency version. If documentation isn't found in context7, you may resort to web-search only after trying context7.

When to Use It

• When updating dependencies or adding new libraries
• When integrating external SDKs or APIs
• When verifying compatibility with documentation
• During code reviews to validate dependency usage
• When unsure about how a dependency behaves

Quick Start

1. Step 1: Check and lock the latest compatible dependency versions
2. Step 2: Use context7 MCP to fetch and verify official docs match the declared versions
3. Step 3: If docs are missing in context7, perform a targeted web-search only after Context7 check, then test thoroughly

Best Practices

• Always aim for the latest compatible dependency version
• Never assume external libraries’ behavior; consult official docs
• Use context7 MCP to lookup documentation and verify version parity
• Only use web-search if context7 MCP docs are unavailable
• Document dependency decisions and version references in PRs

Example Use Cases

• Upgrading a library to a newer patch while confirming docs match the change
• Replacing a deprecated API after checking official guidance
• Verifying API changes against the library’s published docs
• Resisting quick-fix hacks when dependency behavior is unclear and consulting docs first
• Ensuring all dependencies’ docs and versions are aligned before release

Frequently Asked Questions