Architecture C4 Modeling

Overview

Use this skill to produce C4 views that remove architectural ambiguity and help teams reason about scope, ownership, and risk.

Scope Boundaries

• System boundaries are unclear across teams or services.
• People disagree on where responsibilities belong.
• A large change requires shared architecture context before coding.

Core Judgments

• System boundary: what is inside the system and what is external dependency.
• Container split: what deserves a runtime boundary versus a module boundary.
• Component granularity: where decomposition clarifies behavior versus adds noise.
• Trust boundaries and data sensitivity: where stronger controls are required.