architecture-checker

What problem does it solve?

Software projects accumulate hidden structural tech debt when architectural rules (dependency directions, module boundaries, layer separation) are violated, leading to brittle codebases that are hard to maintain, test, and scale as the team and product grow.

Core Features & Use Cases

• Multi-pattern enforcement: Supports layered, hexagonal, clean, modular monolith, and vertical slice architectural patterns, with configurable dependency direction rules stored in a project-level architecture rules file.
• Comprehensive violation detection: Identifies circular dependencies, leaky abstractions, god modules, forbidden imports, cross-module internal access, SQL schema boundary violations, and high blast radius changes.
• Use Case: For a team building a modular monolith SaaS, this skill catches when a billing module accidentally imports code from an iam module's internal directory, or when domain logic imports a database driver, preventing structural rot before it reaches production.

Quick Start

Use the architecture-checker skill to scan your codebase for dependency direction violations and circular imports after making structural changes to your project.