agentleFS
TrecekTrecek/useful-claude-skills/.claude/skills/arch-lens-c4-container/SKILL.md

arch-lens-c4-container

Skill1 starsChanged 8 months agoMITView on GitHub

Create C4 Container architecture diagram showing static structure, building blocks, and technology choices. Anatomical lens answering "How is it built?

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    BEFORE creating any diagram, LOAD the /mermaid skill using the Skill tool - this is MANDATORY

    line 37
  2. Distinctive:

    Look for: entry points, main files, CLI commands, app servers

    line 51
  3. Distinctive:

    Look for: services, core modules, domain logic, handlers

    line 56
  4. Distinctive:

    Look for: shared modules, utilities, common code, SDKs

    line 61
  5. Distinctive:

    Look for: database configs, ORM models, repositories, cache clients

    line 66
  6. Distinctive:

    Look for: HTTP clients, SDK imports, external API calls

    line 71
  7. Distinctive:

    Do NOT place write-only artifacts under "state tracking" or "source of truth" categories.

    line 99
  8. Distinctive:

    Use the mermaid skill conventions to create a diagram with:

    line 103
  9. Very specific:

    Write the diagram to: temp/arch-lens-c4-container/arch_diag_c4_container_{YYYY-MM-DD_HHMMSS}.md

    line 127
  10. Distinctive:

    Before creating the diagram, verify:

    line 228

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

C4 Container Architecture Lens

Cognitive Mode: Anatomical Primary Question: "How is it built?" Focus: Static Structure, Containers, Technology Choices, External Integrations

When to Use

  • Need to understand the high-level technical building blocks
  • Documenting container boundaries and communication
  • Onboarding new team members to system architecture
  • User invokes /arch-lens-c4-container or /make-arch-diag c4

Critical Constraints

NEVER:

  • Modify any source code files
  • Include internal implementation details (that's for other lenses)
  • Show runtime behavior or state transitions

ALWAYS:

  • Focus on CONTAINERS (deployable units, not classes)
  • Show technology choices for each container
  • Identify external systems and integrations
  • BEFORE creating any diagram, LOAD the /mermaid skill using the Skill tool - this is MANDATORY

Analysis Workflow

Step 1: Launch Parallel Exploration Subagents

Spawn Explore subagents to investigate:

Application Layer

  • Find CLI entry points and commands
  • Identify web applications and APIs
  • Determine frontend technologies
  • Look for: entry points, main files, CLI commands, app servers

Service/Business Logic Layer

  • Find core business logic containers
  • Identify processing engines or workflows
  • Look for: services, core modules, domain logic, handlers

Package/Library Layer

  • Find shared packages and utilities
  • Identify internal libraries
  • Look for: shared modules, utilities, common code, SDKs

Data Storage Layer

  • Find database connections and storage
  • Identify caching layers
  • Look for: database configs, ORM models, repositories, cache clients

External Integrations

  • Find API clients and external calls
  • Identify third-party services
  • Look for: HTTP clients, SDK imports, external API calls

Step 2: Identify Containers

For each container discovered, document:

  • Name: Short descriptive name
  • Technology: Primary technology/framework
  • Responsibility: 2-3 word description
  • Communication: How it talks to other containers

Step 3: Map Relationships

Identify connections between containers:

  • Which containers call which?
  • What protocols are used (HTTP, subprocess, import)?
  • Which are synchronous vs asynchronous?

CRITICAL - Analyze Read/Write Direction: For EVERY component and connection, determine:

  • Read sources: Where does this component READ data FROM?
  • Write destinations: Where does this component WRITE data TO?
  • Bidirectional: Does data flow both ways?

Label connections with direction:

  • --> with "reads" or "queries" for read operations
  • --> with "writes" or "saves" for write operations
  • <--> for bidirectional

Do NOT place write-only artifacts under "state tracking" or "source of truth" categories.

Step 4: Create the Diagram

Use the mermaid skill conventions to create a diagram with:

Direction: TB (top-to-bottom) for hierarchical container layout

Subgraphs for Layers:

  • Application Layer (user-facing)
  • Service Layer (business logic)
  • Package Layer (shared utilities)
  • Storage Layer (persistence)
  • External Systems (third-party)

Node Styling:

  • cli class: CLI, user interfaces, entry points
  • phase class: Services, core processing
  • handler class: Packages, shared utilities
  • stateNode class: Databases, storage
  • integration class: External APIs, third-party services

Connections:

  • Solid arrows for primary data flow
  • Label connections with action verbs

Step 5: Write Output

Write the diagram to: temp/arch-lens-c4-container/arch_diag_c4_container_{YYYY-MM-DD_HHMMSS}.md


Output Template

# C4 Container Diagram: {Project Name}

**Lens:** C4 Container (Anatomical)
**Question:** How is it built?
**Date:** {YYYY-MM-DD}
**Scope:** {What was analyzed}

## Container Overview

| Container | Technology | Responsibility |
|-----------|------------|----------------|
| {name} | {tech} | {responsibility} |

## Architecture Diagram

```mermaid
%%{init: {'flowchart': {'nodeSpacing': 50, 'rankSpacing': 60, 'curve': 'basis'}}}%%
graph TB
    %% CLASS DEFINITIONS %%
    classDef cli fill:#1a237e,stroke:#7986cb,stroke-width:2px,color:#fff;
    classDef stateNode fill:#004d40,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef handler fill:#e65100,stroke:#ffb74d,stroke-width:2px,color:#fff;
    classDef phase fill:#6a1b9a,stroke:#ba68c8,stroke-width:2px,color:#fff;
    classDef output fill:#00695c,stroke:#4db6ac,stroke-width:2px,color:#fff;
    classDef integration fill:#c62828,stroke:#ef9a9a,stroke-width:2px,color:#fff;

    %% USER %%
    USER(["User<br/>━━━━━━━━━━<br/>Role description"])

    subgraph Apps ["Application Layer"]
        direction TB
        APP1["Container Name<br/>━━━━━━━━━━<br/>Technology<br/>Responsibility"]
    end

    subgraph Services ["Service Layer"]
        direction TB
        SVC1["Container Name<br/>━━━━━━━━━━<br/>Technology<br/>Responsibility"]
    end

    subgraph Packages ["Shared Packages"]
        direction TB
        PKG1["Package Name<br/>━━━━━━━━━━<br/>Technology<br/>Responsibility"]
    end

    subgraph Storage ["Data Storage"]
        direction TB
        DB1[("Database<br/>━━━━━━━━━━<br/>Technology<br/>Purpose")]
    end

    subgraph External ["External Systems"]
        direction TB
        EXT1["External Service<br/>━━━━━━━━━━<br/>Protocol<br/>Purpose"]
    end

    %% CONNECTIONS %%
    USER --> APP1
    APP1 --> SVC1
    SVC1 --> PKG1
    SVC1 --> DB1
    SVC1 --> EXT1

    %% CLASS ASSIGNMENTS %%
    class USER cli;
    class APP1 cli;
    class SVC1 phase;
    class PKG1 handler;
    class DB1 stateNode;
    class EXT1 integration;

Color Legend:

ColorCategoryDescription
Dark BlueCLI/AppsUser-facing applications and entry points
PurpleServicesCore business logic and services
OrangePackagesShared utilities and libraries
TealStorageDatabase persistence layers
RedExternalExternal integrations and APIs

Key Architectural Insights

ContainerResponsibilityTechnology
{container}{what it does}{tech stack}

Communication Patterns

  • {Description of key communication patterns}

---

## Pre-Diagram Checklist

Before creating the diagram, verify:

- [ ] LOADED `/mermaid` skill using the Skill tool
- [ ] Using ONLY classDef styles from the mermaid skill (no invented colors)
- [ ] Diagram will include a color legend table

---

## Related Skills

- `/make-arch-diag` - Parent skill for lens selection
- `/mermaid` - MUST BE LOADED before creating diagram
- `/arch-lens-module-dependency` - For detailed coupling analysis
- `/arch-lens-deployment` - For physical deployment topology

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.