メニュー
Review C4 architecture models for notation compliance, completeness, and common mistakes. Use when reviewing architecture PRs, auditing existing models, validating model quality, or before publishing architecture documentation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Model deployment environments using C4 deployment diagrams and Structurizr DSL. Use when adding deployment views, modeling infrastructure, documenting production/staging environments, or mapping containers to infrastructure.
Create and evolve C4 architecture models with proper abstractions, diagram types, and notation. Use when adding elements to a C4 model, choosing diagram types, modeling relationships, or making architecture modeling decisions.
Structurizr DSL syntax reference and patterns for writing C4 architecture models. Use when writing or editing workspace.dsl files, looking up DSL syntax, implementing specific patterns, or troubleshooting DSL errors.
| name | c4-review |
| description | Review C4 architecture models for notation compliance, completeness, and common mistakes. Use when reviewing architecture PRs, auditing existing models, validating model quality, or before publishing architecture documentation. |
| metadata | {"author":"Georges Martin <jrjsmrtn@gmail.com>","version":"0.1.7"} |
| license | MIT |
Review C4 architecture models for notation compliance, completeness, and common mistakes.
architecture/workspace.dslarchitecture/workspace.dsl)Run structurizr/structurizr to catch syntax errors before manual review:
podman run --rm \
-v "$(pwd):/work:z" \
structurizr/structurizr validate -w /work/architecture/workspace.dsl
Mount the project root (not just architecture/) so !adrs / !docs symlinks resolve.
If validation fails, fix syntax errors first. Do not proceed with review until the model parses cleanly.
Run the inspect subcommand to surface Checkstyle-style violations (missing descriptions, duplicate names, duplicate view keys, duplicate relationship descriptions, etc.):
podman run --rm \
-v "$(pwd):/work:z" \
structurizr/structurizr inspect -w /work/architecture/workspace.dsl -s error,warning
The exit code equals the number of violations. Severity levels can be tuned per element via structurizr.inspection.* workspace properties (ignore, info, warning, error).
Check every element in the model against these criteria:
Check every relationship:
Suggest specific alternatives for vague labels:
| Vague | Ask | Better Example |
|---|---|---|
| "Uses" | What does it use it for? | "queries order history from" |
| "Connects to" | What data flows? | "sends email notifications via" |
| "Interacts with" | What's the interaction? | "submits search queries to" |
| "Communicates with" | What's communicated? | "publishes order events to" |
Check each view:
include * or explicitly includes all relevant elementsshape Personshape Cylinder!identifiers hierarchical is used (recommended for non-trivial models)api, database, not c1, c2)!adrs directive points to ADR directory (if ADRs exist)!docs directive points to documentation (if applicable)Produce a review summary with:
validateinspectWhen reviewing a C4 model for an Elixir/OTP system, check these additional items:
The review is complete when:
validate passes (the model parses cleanly) and the inspect violation count has been triagedc4-model — C4 abstractions and diagram typesstructurizr-dsl — DSL syntax referencec4-deployment — Deployment modeling specifics