本文へ移動
cccskills
無料GitHub で公開

c4-architecture

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.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md6.7 KB
  • references/c4-modelling-instructions.md7.2 KB
  • references/renderer-mermaid.md29.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

C4 Architecture Skill

Goal

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.

Supported Diagrams

These defaults apply when creating new diagrams. Updates change only what the request targets.

DiagramGenerated by defaultUser selectionAnswers
Level 1: System ContextYesWhich system when several qualifyWho uses the system and what does it interact with
Level 2: ContainerYesNoneWhat separately deployable or runnable units make up a system
Level 3: ComponentYesWhich containers when several qualifyWhat major building blocks sit inside one container
Level 4: CodeOn request onlyWhich component to detailHow one component maps to code structures
DeploymentOffered when evidencedOpt-in and which environmentWhere container instances run in one named environment

Supported Renderers

Read the selected renderer reference in full before generating or modifying diagrams. Apply every relevant rule.

RendererReferenceStatus
mermaidreferences/renderer-mermaid.mdDefault

Process

Follow these steps when activating this skill:

  1. Ensure the renderer required by the user is available.
  2. Inspect the relevant code and documentation to identify architecture elements, boundaries, relationships, and deployment evidence.
  3. Read and apply the C4 modelling instructions, including its modelling-uncertainty decision.
  4. When creating new diagrams, identify which diagrams, systems, and levels are required. Ask the user to clarify if unclear from context.
  5. When updating an existing diagram document, read the complete document first and apply only the requested model delta. Preserve existing nodes, relationships, comments, layout controls, and stable identifiers unless the requested change affects them. Ask the user before removing content whose relevance is uncertain.
  6. Before responding, validate each created/edited diagram rule by rule against the selected renderer reference and correct every violation.

Success Criteria

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.

Constraints

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 Rules

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.

Final Response

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.

Attribution and licensing

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.

PathLicenseOrigin
references/renderer-mermaid.mdCC-BY-4.0 AND MITRepository renderer rules, paraphrased C4 concepts, and MIT-derived Mermaid syntax conventions
references/c4-modelling-instructions.mdCC-BY-4.0Repository modelling rules with paraphrased C4 concepts
SKILL.md and remaining package contentCC-BY-4.0Repository-original with paraphrased C4 concepts

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

Create a durable Architecture Review Record from a confirmed System Architecture Reviewer scope, evidence, pillar analysis, trade-offs, and dispositions

日本語の概要は準備中です。原文の説明を表示しています。

microsoft/hve-core1,5182026年10月11日 更新

microsoft のスキルをすべて見る

このスキルの問題を報告する