When should I create an ADR using this tool?

The skill triggers ADR creation when a decision involves multiple viable alternatives and is either hard to reverse or affects multiple domains.

How does this skill maintain C4 diagrams?

The skill manages Level 1, 2, and 3 C4 diagrams using Mermaid syntax, automatically updating them during the /design phase when structural boundaries or dependencies change.

What is an ADR in the context of this skill?

An Architecture Decision Record (ADR) is a specialized document that captures a significant technical choice, its context, and its consequences using the Michael Nygard pattern.

Can this skill detect if my code violates my architecture?

Yes, during /diagnose and /discern, the skill compares actual code import patterns against the declared dependencies in your C4 diagrams to flag boundary violations.

Does it support Level 4 (Code) diagrams?

No, Level 4 diagrams are not supported because the skill treats the source code itself as the definitive code-level diagram.

Architecture Awareness

Name: Architecture Awareness
Author: Elmmly

byElmmly

•

Aprendizaje y Documentación

Manages Architecture Decision Records (ADRs) and C4 diagrams to ensure technical decisions and system boundaries remain synchronized with code.

The Architecture Awareness skill integrates technical decision-making and structural visualization directly into the development workflow. By automating the creation of Nygard-pattern ADRs and maintaining Neon Dark-styled C4 Mermaid diagrams, it ensures that the 'Why' and 'How' of a system remain in sync with the 'What'. The skill proactively identifies architectural drift, boundary violations, and stale documentation during design, implementation, and diagnostic phases, making it essential for teams prioritizing long-term maintainability and clear system boundaries.

Características Principales

01Staleness detection for architectural artifacts that haven't been updated in 90 days.

02Automated ADR lifecycle management from proposed to accepted or superseded status.

033 GitHub stars

04Multi-level C4 diagramming including System Context, Container, and Component views.

05Automated coupling and cohesion analysis to detect architectural drift in source code.

06Smart context loading that surfaces relevant technical decisions during implementation.

Casos de Uso

01Conducting automated architectural audits and compliance checks during the development lifecycle.

02Documenting complex technical trade-offs between multiple viable architectural alternatives.

03Visualizing and enforcing domain boundaries to prevent tight coupling in microservices.

Características Principales

01Staleness detection for architectural artifacts that haven't been updated in 90 days.

02Automated ADR lifecycle management from proposed to accepted or superseded status.

033 GitHub stars

04Multi-level C4 diagramming including System Context, Container, and Component views.

05Automated coupling and cohesion analysis to detect architectural drift in source code.

06Smart context loading that surfaces relevant technical decisions during implementation.

Casos de Uso

01Conducting automated architectural audits and compliance checks during the development lifecycle.

02Documenting complex technical trade-offs between multiple viable architectural alternatives.

03Visualizing and enforcing domain boundaries to prevent tight coupling in microservices.