How does it handle non-functional requirements?

It provides templates for quality attribute utility trees, allowing you to define measurable targets for performance, security, and availability.

Can I use the diagrams generated in my GitHub repository?

Absolutely. The skill encourages diagrams-as-code using Mermaid or Structurizr syntax, which can be rendered directly in most Git platforms.

What levels of the C4 model does this skill support?

The skill supports Level 1 (System Context), Level 2 (Container), and Level 3 (Component) diagrams to provide various depths of architectural insight.

Does this skill help track architectural changes over time?

Yes, it uses Architecture Decision Records (ADRs) to document the context, consequences, and status of significant design choices chronologically.

Architecture Documentation

Name: Architecture Documentation
Author: CUBETIQ

byCUBETIQ

•

Aprendizaje y Documentación

Generates comprehensive system architecture documentation, C4 model diagrams, and Architecture Decision Records (ADRs).

The architecture-doc skill provides a structured framework for documenting complex software systems, ensuring design decisions and system structures are clearly communicated to stakeholders. It guides the creation of hierarchical C4 model diagrams, captures the rationale behind design choices through standardized Architecture Decision Records (ADRs), and defines measurable quality attribute targets. By prioritizing diagrams-as-code and version-controlled documentation, this skill helps teams maintain an accurate, evolving architectural blueprint that stays synchronized with the codebase.

Características Principales

01Standardized Architecture Decision Record (ADR) lifecycle management

02Environment-specific deployment topology mapping

03Hierarchical C4 model diagramming (Context, Container, Component)

04Measurable quality attribute and utility tree specification

051 GitHub stars

06Diagrams-as-code support using Mermaid and Structurizr DSL

Casos de Uso

01Establishing a clear architectural baseline for new project onboarding

02Aligning development and operations teams through deployment view diagrams

03Documenting significant design trade-offs and constraints via ADRs

Características Principales

01Standardized Architecture Decision Record (ADR) lifecycle management

02Environment-specific deployment topology mapping

03Hierarchical C4 model diagramming (Context, Container, Component)

04Measurable quality attribute and utility tree specification

051 GitHub stars

06Diagrams-as-code support using Mermaid and Structurizr DSL

Casos de Uso

01Establishing a clear architectural baseline for new project onboarding

02Aligning development and operations teams through deployment view diagrams

03Documenting significant design trade-offs and constraints via ADRs