setup-architecture-as-code

Solid

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.

Data & Documents 15 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
40
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
jrjsmrtn
Repository
jrjsmrtn/project-orchestration-skills
Created
8 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

c4-model

Create or review C4 model architecture documentation (official c4model.com notation) as diagrams-as-code in Markdown — C4-PlantUML where the target renders it (GitLab.com does; verify Self-Managed instances), Mermaid flowchart/sequence conventions otherwise. Use whenever the user wants to visualize or document the architecture of a system or codebase — even if they never say "C4" — for requests like "diagram this service", "document the architecture", "how do the pieces of this repo fit together", "draw the system/containers/components", or when reviewing existing C4/Mermaid architecture diagrams for correctness. Covers system context, system landscape, container, component, dynamic, and deployment views. Do not use for generic flowcharts, ER diagrams, standalone Kubernetes topology, API contract documentation (OpenAPI/AsyncAPI), or architecture prose without diagrams.

4 Updated 1 weeks ago
mryll
AI & Automation Listed

architecture-diagrams

Draw architecture diagrams at consistent C4-style levels, as code, kept honest and fit to the audience. Use when documenting a system's structure or when existing diagrams mislead more than they help.

7 Updated 5 days ago
Amey-Thakur
Code & Development Listed

architecture-governance

Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.

0 Updated 2 weeks ago
Cartograf666