Engine Agnostic Patterns
Implement design patterns independent of specific engine
Risk Level
MEDIUM
Core Rules
- Use generic patterns
- test portability
- validate independence
Response Pattern
When Using This Skill
- Implement patterns
- test compatibility
- validate reusability
- Ensure performance meets requirements
Usage Contexts
- Code reuse
- engine independence
What NOT to Do
- Engine-specific patterns
- tight coupling
- poor reusability
Key Requirements
- Understand the use cases before application
- Follow the documented response pattern
- Validate results in the target environment
- Monitor for performance impact
Further Learning
Review related skills and documentation for deeper understanding of related systems and best practices.