architecture-c4-modeling
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.
Practitioner Heuristics
- Each relationship in diagrams must answer one operational question: ownership, protocol, failure impact, or data-classification.
- If two boxes cannot be owned by different teams or deployed/scaled independently, they are usually not separate containers.
- Component diagrams are useful only for high-change or high-risk containers; do not draw them by default.
- Keep names consistent with runtime artifacts and code modules to avoid translation loss.
Workflow
- Define the audience and the questions each C4 level must answer.
- Draw the context view around real external actors and systems.
- Draw container boundaries based on runtime and ownership constraints.
- Add component views only where behavior is too complex for container-level reasoning.
- Annotate critical interactions with trust, latency, and failure assumptions.
- Reconcile naming and dependencies with actual repositories and runtime topology.
Common Failure Modes
- Diagrams mirror org charts instead of runtime behavior.
- Container boundaries are chosen by technology preference rather than coupling/ownership.
- Component diagrams become full class diagrams and lose decision value.
Failure Conditions
- Stop when source system inventory is stale or contradictory.
- Stop when critical boundaries cannot be represented unambiguously.
- Escalate when diagram conclusions conflict with approved architectural decisions.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9