architecture-governance Skill

Goal

Architecture is not a document; it's a constraint system checked by CI/CD.

Steps

1. Fitness Functions (Automated Tests)

Write tests that verify your architecture, not just your logic.

• Layering: "Classes in Domain should not depend on Infrastructure."
• Cycles: "No circular dependencies between slices."
• Naming: "All Interfaces should start with I" (if that's your rule).
• Inheritance: "All Domain Events must implement IDomainEvent."

2. Tools

• Java/Kotlin: ArchUnit.
• .NET: NetArchTest.
• TypeScript: dependency-cruiser or custom ESLint rules (see agentic-linter).
• PHP: PHPArkitect or Deptrac.