Model and document existing or planned software architectures with the C4 model across System Context, Container, and Component levels plus deployment diagrams, then emit diagrams through a selected renderer. Use when an architect needs audience-appropriate software architecture documentation; use the 'architecture-diagrams' skill for infrastructure topology.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Produce audience-appropriate C4 diagrams for existing systems from code or planned systems from requirements. Create new diagrams with the selected renderer, or update existing diagrams when their renderer is supported.
These defaults apply when creating new diagrams. Updates change only what the request targets.
| Diagram | Generated by default | User selection | Answers |
|---|---|---|---|
| Level 1: System Context | Yes | Which system when several qualify | Who uses the system and what does it interact with |
| Level 2: Container | Yes | None | What separately deployable or runnable units make up a system |
| Level 3: Component | Yes | Which containers when several qualify | What major building blocks sit inside one container |
| Level 4: Code | On request only | Which component to detail | How one component maps to code structures |
| Deployment | Offered when evidenced | Opt-in and which environment | Where container instances run in one named environment |
Read the selected renderer reference in full before generating or modifying diagrams. Apply every relevant rule.
| Renderer | Reference | Status |
|---|---|---|
mermaid | references/renderer-mermaid.md | Default |
Follow these steps when activating this skill:
Complete the run when the agreed diagrams are produced or updated, their content is supported by the available evidence, and each diagram passes rule-by-rule source validation against the selected renderer reference. Report renderer-specific validation using the statuses defined by that reference, including the reason when validation was not run.
Preserve the agreed system boundary, diagram levels, and renderer. Do not infer architecture, deployment topology, ownership, or relationship technology that the provided evidence does not support. Follow the selected renderer reference in full.
Stop and ask for clarification when unresolved modelling uncertainty materially affects the diagrams. Stop and report the limitation when required evidence is missing or the requested renderer is unsupported or unavailable. Do not substitute an unrequested renderer or fabricate unsupported elements to complete a diagram.
When diagrams are produced or updated, report the diagrams, selected renderer, source-validation result, renderer-specific validation status, assumptions or limitations, and unresolved decisions.
For a clarification stop, state the evidence found, each specific modelling decision blocking the diagrams, the plausible options for each decision, and that no diagrams were produced. Do not report validation status during a clarification stop because no diagram source has been produced yet.
Each source is paraphrased with attribution; none is reproduced verbatim.
Derived and original material share files here, so the boundary is marked inline in each file rather than split by file. The frontmatter expression is the conjunction of every license present in the package.
| Path | License | Origin |
|---|---|---|
references/renderer-mermaid.md | CC-BY-4.0 AND MIT | Repository renderer rules, paraphrased C4 concepts, and MIT-derived Mermaid syntax conventions |
references/c4-modelling-instructions.md | CC-BY-4.0 | Repository modelling rules with paraphrased C4 concepts |
SKILL.md and remaining package content | CC-BY-4.0 | Repository-original with paraphrased C4 concepts |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
The English summary is being prepared. Showing the original description.
Build, refresh, report, or probe an accessibility coverage matrix across criteria, surfaces, and evidence methods. Use when assessing coverage with the accessibility runtime harness and generated evidence bundle.
The English summary is being prepared. Showing the original description.
Authoring skill for Architecture Decision Records (ADRs) supporting capture, from-planner-handoff, and adopt-template entry modes with selectable Y-Statement or MADR v4.0.0 output templates, supersession lineage, and ASR trigger evaluation.
The English summary is being prepared. Showing the original description.
Authoring conventions for exploratory data analysis notebooks and analytical dashboards, covering section sequence, visualization selection, scale thresholds, caching and state, and dashboard validation budgets. Use when composing or reviewing an EDA notebook, an analytical dashboard, or a dashboard test pass.
The English summary is being prepared. Showing the original description.
Architecture diagram authoring for cloud infrastructure and declared data catalogs. Use when rendering Azure IaC or DS_CATALOG_V1 relationships as caller-selected ASCII or Mermaid diagrams.
The English summary is being prepared. Showing the original description.
Create a durable Architecture Review Record from a confirmed System Architecture Reviewer scope, evidence, pillar analysis, trade-offs, and dispositions
The English summary is being prepared. Showing the original description.