Enterprise DDD Architecture

Use this skill for large systems where domain boundaries, ownership, and cross-team scaling matter more than local feature speed.

Use This Skill When

• Multiple domains must be isolated (billing, auth, catalog, attendance, etc.).
• You need explicit module contracts across frontend and backend.
• Event-driven integration is preferred over direct cross-module coupling.
• Monorepo governance and release boundaries are required.

Do Not Use When

• Project is small or single-team with low domain complexity.
• A simple layered architecture is sufficient.

Architecture Contract