bee:pre-dev-dependency-map

What problem does it solve?

This Skill prevents the use of vague or unverified technology dependencies, ensuring reproducible builds, avoiding hidden incompatibilities, and mitigating security risks by enforcing explicit, versioned, and justified technology selections.

Core Features & Use Cases

• Explicit Versioning: Mandates specific versions for all packages, libraries, and infrastructure components.
• Standards Compliance: Validates technology choices against organizational standards (Bee Standards) and project-specific rules.
• Security & License Verification: Ensures dependencies are scanned for vulnerabilities (CVEs) and have compatible licenses for commercial use.
• Use Case: Before starting development on a new feature, this Skill ensures that the chosen database, backend framework, and frontend libraries are all explicitly defined with their exact versions, checked for security vulnerabilities, and approved according to project guidelines.

Quick Start

Use the bee:pre-dev-dependency-map skill to generate the PROJECT_RULES.md file based on TRD technology decisions and Bee Standards.