← ClaudeAtlas

setup-architecture-as-codelisted

Establish architecture-as-code practice using C4 modeling and Structurizr DSL. Use after bootstrap-project, when establishing architecture documentation, or when migrating from diagram-based to code-based architecture.
jrjsmrtn/project-orchestration-skills · ★ 15 · Data & Documents · score 81
Install: claude install-skill jrjsmrtn/project-orchestration-skills
# Setup Architecture-as-Code Establish architecture-as-code practice using C4 modeling and Structurizr DSL. ## When to Use - After running `bootstrap-project` skill - When establishing architecture documentation for a project - When migrating from diagram-based to code-based architecture documentation - When you need version-controlled, validated architecture models ## What is Architecture-as-Code? Architecture-as-Code treats architecture documentation like source code: | Traditional Diagrams | Architecture-as-Code | |---------------------|---------------------| | Draw in GUI tools | Define in text/DSL | | Manual updates | Automated validation | | Binary files (PNG, VSDX) | Text files (version control friendly) | | Diagrams diverge from reality | Single source of truth | | Hard to review changes | PR-reviewable changes | | No validation | Syntax + semantic validation | **Implementation Stack**: - **Modeling Approach**: C4 Model (Context, Container, Component, Code) - **Definition Language**: Structurizr DSL - **Validation & Inspection**: structurizr/structurizr (consolidated image, replaces deprecated `structurizr/cli` and `structurizr/lite`) - **Visualization**: structurizr/structurizr `local` subcommand or Structurizr Cloud ## Required Inputs 1. **Project/System name** 2. **System description** (1-2 sentences) 3. **Key users/personas** (who interacts with the system) 4. **External systems** (what the system integrates with) 5. **Main containers** (applications, dat