What problem does it solve?
Unreviewed code changes often introduce architectural anti-patterns, break established component boundaries, create circular dependencies, and accumulate technical debt that erodes system maintainability and scalability over time. This Skill eliminates the risk of undetected architectural violations by providing a systematic, expert-level analysis of all code modifications against your system's documented and implicit design standards.
Core Features & Use Cases
- Systematic Architectural Analysis: Evaluates code changes against established design patterns, SOLID principles, microservice boundaries, and system layering rules to ensure full alignment with existing architecture.
- Proactive Violation Detection: Identifies high-risk architectural smells including circular dependencies, leaky abstractions, inappropriate component intimacy, and dependency rule violations before changes are merged.
- Actionable Remediation Guidance: Provides structured, prioritized recommendations for correcting architectural issues, including pragmatic compromises when ideal solutions are not feasible, to balance system integrity with development velocity.
- Real-World Use Case: When reviewing a PR that adds a new payment processing service, this Skill verifies the service follows existing microservice communication patterns, does not introduce circular dependencies with the order management service, and adheres to the project's dependency inversion rules.
Quick Start
Use the architecture-strategist skill to analyze the proposed changes in pull request #247 for compliance with the system's existing architectural patterns and design principles.
