system-architecture

Designs software architectures using C4 diagrams, ADRs, and quality attribute trade-off analysis.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill system-architecture-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-architecture
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/system-architecture
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill system-architecture-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams starting new systems or evaluating existing ones often lack a shared, documented understanding of system structure, leading to undocumented decisions, inconsistent diagrams, and technology choices made by default rather than by explicit evaluation. ## Core Features & Use Cases - C4 Model Diagrams: Produces Context, Container, Component, and Code-level diagrams that stay consistent across abstraction levels. - Architecture Decision Records: Documents significant decisions with status, context, decision, and consequences so rationale is never lost. - Quality Attribute Analysis: Evaluates trade-offs (e.g., consistency vs. availability) with measurable stimulus-response scenarios. - Use Case: When designing a new order-management system, use this Skill to discover architectural drivers, produce C4 diagrams, write ADRs for each significant decision, and validate the design with the development team. ## Quick Start Ask the assistant to design the architecture for your system using C4 diagrams, measurable quality attributes, and ADRs.

Frequently Asked Questions about system-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create C4 diagrams for a software system?▼

C4 diagrams are created in levels: start with a Context diagram showing the system and its users, then a Container diagram of deployable units, then Component diagrams, and Code-level only when needed. This Skill generates each level and checks consistency so no phantom systems appear.

What is an Architecture Decision Record and how do I write one?▼

An Architecture Decision Record (ADR) documents a significant architectural choice using four parts: status, context, decision, and consequences. This Skill writes ADRs for each significant decision and rejects records that omit context or consequences.

How do I evaluate quality attributes like scalability and availability?▼

Quality attributes are evaluated with measurable scenarios containing a stimulus, a response, and a concrete measure. The Skill maps trade-offs, such as consistency versus availability, and uses them to drive architecture style selection rather than choosing technology by default.

When should I use system architecture design instead of enterprise architecture?▼

Use system architecture when designing or evaluating a specific software system with C4 diagrams and ADRs. Enterprise capability mapping, investment portfolios, and business-unit governance belong to enterprise architecture and are explicitly routed elsewhere by this Skill.

What happens if architectural drivers or project artifacts are missing?▼

The Skill requests the blocking inputs—business goals, constraints, code, integrations, and quality attributes—before proceeding. It avoids inventing phantom systems or unsupported technology decisions and discloses any review gaps before finalizing.