arc42-c4

Map C4 diagrams to appropriate arc42 sections in architecture documents.

Updated May 2, 2020
One-click install
npx skills add https://github.com/vankichi/dotfiles --skill arc42-c4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arc42-c4
Source: https://github.com/vankichi/dotfiles/tree/main/claude/ja/skills/arc42-c4
Command: npx skills add https://github.com/vankichi/dotfiles --skill arc42-c4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves ambiguity in mapping architecture diagrams (C4) to documentation (arc42), ensuring consistent design practices across projects.

Core Features & Use Cases

  • Arc42-C4 Mapping: Defines a standard for mapping C4 diagrams to arc42 sections.
  • Decision Support: Helps in determining where to place diagrams and ADRs within design documents.
  • Use Case: When designing an architecture, this Skill aids in deciding where to place C4 diagrams (e.g., System Context, Container, Component) in the arc42 documentation.

Quick Start

Use the arc42-c4 skill to determine the appropriate arc42 section for a C4 Component diagram.

Frequently Asked Questions about arc42-c4

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

FAQPage Schema
How do I map C4 diagrams to arc42 sections for architecture documentation?

Mapping C4 diagrams to arc42 sections requires standardizing the placement of System Context, Container, and Component diagrams within specific documentation sections. This ensures consistent design practices and resolves ambiguity in architecture documentation across projects.

What is the best way to structure architecture design documents using the C4 model and arc42?

Structuring architecture design documents with the C4 model and arc42 involves defining a clear mapping standard for diagrams and ADRs. This approach provides decision support for determining exact placement within design documents to achieve documentation consistency.

Do I need to understand both arc42 and C4 model principles to use this mapping approach?

Yes, understanding both arc42 and C4 model principles is required. This knowledge is necessary to correctly choose the appropriate arc42 section for each C4 diagram type and to ensure design clarity within the architecture documentation.

Where should I place a C4 Component diagram in an arc42 document?

A C4 Component diagram should be placed in the appropriate arc42 section based on standard mapping rules. This mapping determines the correct placement to maintain design clarity and documentation consistency across the architecture design.

Can this mapping standard help with deciding where to put ADRs in arc42 documentation?

Yes, this mapping standard provides decision support for determining where to place Architecture Decision Records (ADRs) within arc42 design documents. It helps project teams standardize architecture design and maintain consistent documentation practices.

Why use a standardized mapping for C4 diagrams and arc42 sections instead of custom placement?

Using a standardized mapping for C4 diagrams and arc42 sections resolves ambiguity in architecture documentation. It ensures consistent design practices across project teams, eliminating the confusion that arises from custom or ad-hoc diagram placement.