development-guidelines
Development Guidelines
Working with Dependencies
- Always try to use latest versions for dependencies.
- If you are not sure, do not make assumptions about how external dependencies work. Always consult documentation.
- Before trying alternative methods, always try to use context7 MCP to lookup documentation for external dependencies like libraries, SDKs, APIs and other external frameworks, tools, etc.
- IMPORTANT! Always make sure that documentation version is the same as declared dependency version itself.
- Only revert to web-search or other alternative methods if you can't find documentation in context7.
More from serpro69/claude-toolbox
cove
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
1merge-docs
Semantically compare and merge two design docs for the same feature into one unified document. Use when you have two competing or complementary design/implementation docs (e.g., from separate analysis-process runs) and need to reconcile them into a single source of truth.
1analysis-process
Turn the idea for a feature into a fully-formed PRD/design/specification and implementation-plan. Use when you have a spec or requirements that needs implementation. Use in pre-implementation (idea-to-design) stages to make sure you understand the spec/requirements and ensure you have a correct implementation plan before writing actual code.
1testing-process
Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.
1documentation-process
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix
1solid-code-review
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
1