Audit advanced Works with: Any AI

Architecture and Module Boundary Review

Table output

Check for coupling and layering problems.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Review the architecture and boundaries of my codebase. Description of the system and its purpose: [SYSTEM_DESCRIPTION]. Directory or module structure: [PASTE_STRUCTURE]. Import or dependency information if I have it: [PASTE_DEPENDENCIES]. Pain points: [PAIN_POINTS].

Respond with tables:
1. Module map: Module | Responsibility (one sentence) | Depends on | Depended on by | Size/complexity note.
2. Boundary problems: Problem | Where | Evidence | Why it hurts (change ripple, testing difficulty, circular dependency, shared mutable state, business logic in the wrong layer) | Severity.
3. Proposed boundaries: current module | proposed home | reason.
4. Refactoring sequence: Step | Change | Risk | How to verify | Rollback.

Then explain the three most important architectural rules to enforce (for example "the domain layer imports nothing from the web layer") and how to enforce them automatically in a test or lint rule. Distinguish clearly between problems that are real and preferences. Do not propose a rewrite; propose steps that keep the system running.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

• architecture
• coupling