Architecture Review FAQs

Question 1

What is an ADR in the context of this skill?

Accepted Answer

ADR stands for Architectural Decision Record. This skill helps locate, verify, and document these records to ensure all major design decisions are tracked and followed.

Question 2

Can I perform a focused review instead of a full audit?

Accepted Answer

Yes, the skill supports progressive loading, allowing you to load specific modules like ADR audit, coupling analysis, or principle checks for a more targeted review scope.

Question 3

How does the coupling analysis help my codebase?

Accepted Answer

It maps module interactions to identify circular dependencies, ensures dependencies flow in the correct direction, and verifies that data ownership boundaries are respected.

Question 4

When is the best time to use the Architecture Review skill?

Accepted Answer

It is most effective before approving major reimplementations, during dependency restructuring, or when introducing entirely new services to a system.

Question 5

Does this skill help with performance and security?

Accepted Answer

Yes, the Principle Checks module specifically flags issues related to security (like input validation) and performance (like N+1 queries or missing caching).

Architecture Review

Key Features

Use Cases

Architecture Review

Key Features

Use Cases