Architecture Monolith

Overview

Use this skill to design modular monoliths that preserve internal autonomy without introducing distributed-system overhead.

Scope Boundaries

• Product scope or team size favors a single deployable unit.
• Cross-domain workflows require strong transactional consistency.
• Operational simplicity is a top constraint.

Core Judgments

• Module boundaries: domain cohesion and dependency direction inside one codebase.
• Internal contracts: which module APIs are allowed and how enforced.
• Data ownership in shared database: logical ownership and write access discipline.
• Future extraction seams: where boundaries should support later service splits.