architecture-strategist

Architectural review evaluates pull requests and code modifications against established system patterns, component boundaries, and design principles. This Skill analyzes diffs to validate that changes preserve architectural intent, identify coupling risks, and ensure SOLID principles are maintained throughout refactors and feature additions.

SOLID principles and design patterns are foundational concepts for building maintainable systems. They define rules for component interaction, dependency management, and code organization. This Skill applies these principles during reviews to catch anti-patterns, enforce modularity, and prevent architectural degradation as codebases evolve.

Coupling risks and boundary violations occur when components depend too tightly on implementation details or when responsibilities cross module lines. This Skill detects these issues by analyzing code structure, dependency flows, and component interactions, then documents the architectural implications and recommends refactoring strategies.

Run architectural reviews during pull requests, refactors of core services, or when adding significant features to ensure changes align with established patterns. This Skill is most valuable when system boundaries, design decisions, or SOLID adherence could be affected by the proposed code modifications.

Yes. Architectural review scales to complex systems by validating component boundaries, dependency inversion patterns, and design decisions across distributed services. This Skill documents architectural implications for stakeholders and provides concrete recommendations to maintain integrity as systems grow.

When violations are detected—such as circular dependencies, boundary breaches, or SOLID principle violations—this Skill documents the risks, explains the architectural implications, and recommends corrective actions. This enables teams to make informed decisions about accepting or refactoring problematic changes.