agentsclimarketplace

C4 modeling

Skill aiskillstore/marketplace/skills/consiliency/c4-modeling

C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.From its SKILL.md

Install
npx -y skills add aiskillstore/marketplace --skill c4-modeling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

3.2 KB, 723 tokens by cl100k_base, as published. Nobody here has run it

C4 Modeling Skill

Create hierarchical architecture diagrams at four abstraction levels using the C4 model and Mermaid syntax.

Variables

VariableDefaultDescription
DEFAULT_LEVELcontextStart with context, container, component, or code
OUTPUT_FORMATmermaidmermaid, structurizr, plantuml
INCLUDE_LEGENDtrueAdd legend to diagrams

Instructions

MANDATORY - Follow the Workflow steps below when creating C4 diagrams.

  • Always start at Level 1 (Context) and zoom in as needed
  • Never mix abstraction levels in a single diagram
  • Include descriptions for all elements

Red Flags - STOP and Reconsider

If you're about to:

  • Create a container diagram without first creating a context diagram
  • Mix containers and components in the same diagram
  • Show implementation details at the context level
  • Create a code-level diagram for non-critical code

STOP -> Check the appropriate level guidelines in reference/level-guidelines.md -> Then proceed

Workflow

  1. Determine the audience and purpose
  2. CHECKPOINT: Start at Level 1 (Context) unless you have higher-level diagrams
  3. Identify all actors and systems at current level
  4. Define relationships with labeled arrows
  5. Add technology choices (for Level 2+)
  6. CHECKPOINT: Verify you haven't mixed abstraction levels
  7. Include descriptions for clarity

C4 Levels

LevelNamePurposeAudience
1ContextSystem in environmentEveryone
2ContainerMajor componentsTechnical stakeholders
3ComponentInternal structureDevelopers
4CodeImplementationDevelopers (sparingly)

Quick Reference

Level 1: Context

Show: System, users, external systems Hide: Internal details, databases, technology

Level 2: Container

Show: Applications, APIs, databases, queues Hide: Internal structure, classes

Level 3: Component

Show: Modules, services, repositories Hide: Individual classes, functions

Level 4: Code

Show: Classes, interfaces, key abstractions Use: Only for complex/critical areas

See reference/level-guidelines.md for detailed guidance. See reference/mermaid-syntax.md for Mermaid C4 syntax.

Mermaid Quick Syntax

C4Context
    title System Context Diagram
    Person(user, "User", "Description")
    System(system, "System", "Description")
    System_Ext(ext, "External", "Description")
    Rel(user, system, "Uses")
C4Container
    title Container Diagram
    Container(web, "Web App", "React", "UI")
    Container(api, "API", "Node.js", "Backend")
    ContainerDb(db, "Database", "PostgreSQL", "Storage")
    Rel(web, api, "Calls", "REST")

See reference/mermaid-syntax.md for complete syntax reference.

Output

Diagrams should include:

  1. Title indicating level and system
  2. All relevant elements with descriptions
  3. Labeled relationships
  4. Technology choices (Level 2+)
  5. Clear boundaries for grouping

What ships with it: 3 files

40.1 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.