What problem does it solve?
This Skill prevents over-engineering and the introduction of unnecessary complexity or disallowed technologies in the project. It automatically enforces the project's Minimum Viable Product (MVP) principles and technical constraints, saving development time, reducing technical debt, and maintaining a lean codebase.
Core Features & Use Cases
- Technical Blacklist Enforcement: Automatically scans code for disallowed technologies (e.g., Redis, CQRS, MediatR, Docker, GraphQL), reporting violations with suggested MVP-compliant alternatives.
- Dependency Injection Validation: Detects and flags violations of dependency injection best practices, such as the use of Service Locator patterns or attribute injection, promoting clean and testable architecture.
- Over-Design Analysis: Uses
serena and sequential-thinking to identify potentially over-engineered solutions (e.g., complex patterns for simple CRUD), offering simplified alternatives and a cost-benefit analysis.
- Use Case: Before merging a Pull Request, this Skill automatically scans the new code. If it finds a developer has introduced a
MediatR dependency or an overly complex Event Sourcing pattern for a simple feature, it flags the violation and suggests a simpler, MVP-compliant approach, preventing unnecessary complexity.
Quick Start
Check the current code for MVP compliance and any over-designed patterns.
