33 lines
2.1 KiB
Markdown
33 lines
2.1 KiB
Markdown
## Brief overview
|
|
These rules establish the mandatory use of Context7 MCP server for all development operations, ensuring access to the most current practices and information. This is a global requirement that applies to all projects and development tasks.
|
|
|
|
## Context7 MCP dependency
|
|
- All library research, documentation lookup, and best practice validation MUST use Context7 MCP server
|
|
- Before implementing any new technology, framework, or library, validate current patterns through Context7
|
|
- When encountering errors or implementation issues, consult Context7 for updated solutions and patterns
|
|
- Never assume knowledge of libraries or frameworks without Context7 validation
|
|
|
|
## Development workflow with Context7
|
|
- Start any new feature or library integration by resolving the library ID through Context7
|
|
- Use Context7 to get current documentation and implementation patterns before coding
|
|
- When debugging or troubleshooting, reference Context7 for updated solutions
|
|
- Validate testing patterns and mocking strategies through Context7 before implementation
|
|
|
|
## Information validation process
|
|
- Context7 serves as the authoritative source for current development practices
|
|
- All technical decisions should be informed by Context7 documentation and patterns
|
|
- When user requests revalidation of approaches, immediately consult Context7
|
|
- Prioritize Context7 guidance over assumed knowledge or outdated practices
|
|
|
|
## Implementation standards
|
|
- Follow Context7-validated patterns for testing, mocking, and development workflows
|
|
- Use Context7 to verify compatibility and current best practices for all dependencies
|
|
- Ensure all code patterns align with Context7-provided examples and documentation
|
|
- Reference Context7 for proper configuration and setup procedures
|
|
|
|
## Error handling and troubleshooting
|
|
- When tests fail or implementations don't work as expected, consult Context7 for current solutions
|
|
- Use Context7 to validate mocking patterns and testing strategies
|
|
- Reference Context7 for proper error handling and debugging approaches
|
|
- Always check Context7 for updated patterns when encountering technical issues
|