Before introducing any new dependency, package, helper, utility, or external tool, you MUST follow the Dependency Evaluation Skill.
- Evaluate whether the requirement can be implemented reliably with no more than 200 lines of production code, excluding tests.
- Identify relevant edge cases and write tests before integrating a new internal implementation.
- Prefer existing project capabilities or a small internal implementation over unnecessary dependencies.
- Evaluate security, maintenance status, compatibility, licensing, and supply-chain risks before installing any external package.
- Verify and select the latest stable release compatible with the project.
- Document every newly introduced external dependency or tool in
DECISIONS.mdusing the established Architecture Decision Record (ADR) format.