C4 Container Level: System Deployment
Use this skill when
- Working on c4 container level: system deployment tasks or workflows
- Needing guidance, best practices, or checklists for c4 container level: system deployment
Do not use this skill when
- The task is unrelated to c4 container level: system deployment
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Containers
[Container Name]
- Name: [Container name]
- Description: [Short description of container purpose and deployment]
- Type: [Web Application, API, Database, Message Queue, etc.]
- Technology: [Primary technologies: Node.js, Python, PostgreSQL, Redis, etc.]
- Deployment: [Docker, Kubernetes, Cloud Service, etc.]
Purpose
[Detailed description of what this container does and how it's deployed]
Components
This container deploys the following components:
Interfaces
[API/Interface Name]
- Protocol: [REST/GraphQL/gRPC/Events/etc.]
- Description: [What this interface provides]
- Specification: [Link to OpenAPI/Swagger/API Spec file]
- Endpoints:
GET /api/resource - [Description]
POST /api/resource - [Description]
Dependencies
Containers Used
- [Container Name]: [How it's used, communication protocol]
External Systems
- [External System]: [How it's used, integration type]
Infrastructure
- Deployment Config: [Link to Dockerfile, K8s manifest, etc.]
- Scaling: [Horizontal/vertical scaling strategy]
- Resources: [CPU, memory, storage requirements]
Container Diagram
Use proper Mermaid C4Container syntax:
C4Container
title Container Diagram for [System Name]
Person(user, "User", "Uses the system")
System_Boundary(system, "System Name") {
Container(webApp, "Web Application", "Spring Boot, Java", "Provides web interface")
Container(api, "API Application", "Node.js, Express", "Provides REST API")
ContainerDb(database, "Database", "PostgreSQL", "Stores data")
Container_Queue(messageQueue, "Message Queue", "RabbitMQ", "Handles async messaging")
}
System_Ext(external, "External System", "Third-party service")
Rel(user, webApp, "Uses", "HTTPS")
Rel(webApp, api, "Makes API calls to", "JSON/HTTPS")
Rel(api, database, "Reads from and writes to", "SQL")
Rel(api, messageQueue, "Publishes messages to")
Rel(api, external, "Uses", "API")
**Key Principles** (from [c4model.com](https://c4model.com/diagrams/container)):
- Show **high-level technology choices** (this is where technology details belong)
- Show how **responsibilities are distributed** across containers
- Include **container types**: Applications, Databases, Message Queues, File Systems, etc.
- Show **communication protocols** between containers
- Include **external systems** that containers interact with
API Specification Template
For each container API, create an OpenAPI/Swagger specification:
openapi: 3.1.0
info:
title: [Container Name] API
description: [API description]
version: 1.0.0
servers:
- url: https://api.example.com
description: Production server
paths:
/api/resource:
get:
summary: [Operation summary]
description: [Operation description]
parameters:
- name: param1
in: query
schema:
type: string
responses:
'200':
description: [Response description]
content:
application/json:
schema:
type: object
Example Interactions
- "Synthesize all components into containers based on deployment definitions"
- "Map the API components to containers and document their APIs as OpenAPI specs"
- "Create container-level documentation for the microservices architecture"
- "Document container interfaces as Swagger/OpenAPI specifications"
- "Analyze Kubernetes manifests and create container documentation"
Key Distinctions
- vs C4-Component agent: Maps components to deployment units; Component agent focuses on logical grouping
- vs C4-Context agent: Provides container-level detail; Context agent creates high-level system diagrams
- vs C4-Code agent: Focuses on deployment architecture; Code agent documents individual code elements
Output Examples
When synthesizing containers, provide:
- Clear container boundaries with deployment rationale
- Descriptive container names and deployment characteristics
- Complete API documentation with OpenAPI/Swagger specifications
- Links to all contained components
- Mermaid container diagrams showing deployment architecture
- Links to deployment configurations (Dockerfiles, K8s manifests, etc.)
- Infrastructure requirements and scaling considerations
- Consistent documentation format across all containers
1---2name: c4-container-53description: Expert C4 Container-level documentation specialist. Synthesizes4 Component-level documentation into Container-level architecture, mapping5 components to deployment units, documenting container interfaces as APIs, and6 creating container diagrams. Use when synthesizing components into deployment7 containers and documenting system deployment architecture.8metadata:9 source: https://skillmd.com/skills/diegosouzapw/c4-container-510 model: sonnet11---1213# C4 Container Level: System Deployment1415## Use this skill when1617- Working on c4 container level: system deployment tasks or workflows18- Needing guidance, best practices, or checklists for c4 container level: system deployment1920## Do not use this skill when2122- The task is unrelated to c4 container level: system deployment23- You need a different domain or tool outside this scope2425## Instructions2627- Clarify goals, constraints, and required inputs.28- Apply relevant best practices and validate outcomes.29- Provide actionable steps and verification.30- If detailed examples are required, open `resources/implementation-playbook.md`.3132## Containers3334### [Container Name]3536- **Name**: [Container name]37- **Description**: [Short description of container purpose and deployment]38- **Type**: [Web Application, API, Database, Message Queue, etc.]39- **Technology**: [Primary technologies: Node.js, Python, PostgreSQL, Redis, etc.]40- **Deployment**: [Docker, Kubernetes, Cloud Service, etc.]4142## Purpose4344[Detailed description of what this container does and how it's deployed]4546## Components4748This container deploys the following components:4950- Documentation: [c4-component-name.md](./c4-component-name.md)5152## Interfaces5354### [API/Interface Name]5556- **Protocol**: [REST/GraphQL/gRPC/Events/etc.]57- **Description**: [What this interface provides]58- **Specification**: [Link to OpenAPI/Swagger/API Spec file]59- **Endpoints**:60 - `GET /api/resource` - [Description]61 - `POST /api/resource` - [Description]6263## Dependencies6465### Containers Used6667- [Container Name]: [How it's used, communication protocol]6869### External Systems7071- [External System]: [How it's used, integration type]7273## Infrastructure7475- **Deployment Config**: [Link to Dockerfile, K8s manifest, etc.]76- **Scaling**: [Horizontal/vertical scaling strategy]77- **Resources**: [CPU, memory, storage requirements]7879## Container Diagram8081Use proper Mermaid C4Container syntax:8283```mermaid84C4Container85 title Container Diagram for [System Name]8687 Person(user, "User", "Uses the system")88 System_Boundary(system, "System Name") {89 Container(webApp, "Web Application", "Spring Boot, Java", "Provides web interface")90 Container(api, "API Application", "Node.js, Express", "Provides REST API")91 ContainerDb(database, "Database", "PostgreSQL", "Stores data")92 Container_Queue(messageQueue, "Message Queue", "RabbitMQ", "Handles async messaging")93 }94 System_Ext(external, "External System", "Third-party service")9596 Rel(user, webApp, "Uses", "HTTPS")97 Rel(webApp, api, "Makes API calls to", "JSON/HTTPS")98 Rel(api, database, "Reads from and writes to", "SQL")99 Rel(api, messageQueue, "Publishes messages to")100 Rel(api, external, "Uses", "API")101```102````103104**Key Principles** (from [c4model.com](https://c4model.com/diagrams/container)):105106- Show **high-level technology choices** (this is where technology details belong)107- Show how **responsibilities are distributed** across containers108- Include **container types**: Applications, Databases, Message Queues, File Systems, etc.109- Show **communication protocols** between containers110- Include **external systems** that containers interact with111112````113114## API Specification Template115116For each container API, create an OpenAPI/Swagger specification:117118```yaml119openapi: 3.1.0120info:121 title: [Container Name] API122 description: [API description]123 version: 1.0.0124servers:125 - url: https://api.example.com126 description: Production server127paths:128 /api/resource:129 get:130 summary: [Operation summary]131 description: [Operation description]132 parameters:133 - name: param1134 in: query135 schema:136 type: string137 responses:138 '200':139 description: [Response description]140 content:141 application/json:142 schema:143 type: object144````145146## Example Interactions147148- "Synthesize all components into containers based on deployment definitions"149- "Map the API components to containers and document their APIs as OpenAPI specs"150- "Create container-level documentation for the microservices architecture"151- "Document container interfaces as Swagger/OpenAPI specifications"152- "Analyze Kubernetes manifests and create container documentation"153154## Key Distinctions155156- **vs C4-Component agent**: Maps components to deployment units; Component agent focuses on logical grouping157- **vs C4-Context agent**: Provides container-level detail; Context agent creates high-level system diagrams158- **vs C4-Code agent**: Focuses on deployment architecture; Code agent documents individual code elements159160## Output Examples161162When synthesizing containers, provide:163164- Clear container boundaries with deployment rationale165- Descriptive container names and deployment characteristics166- Complete API documentation with OpenAPI/Swagger specifications167- Links to all contained components168- Mermaid container diagrams showing deployment architecture169- Links to deployment configurations (Dockerfiles, K8s manifests, etc.)170- Infrastructure requirements and scaling considerations171- Consistent documentation format across all containers