How do I install the C4 Architecture Documentation skill?

Run npx skillmds@latest add hack23/c4-architecture-documentation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is C4 Architecture Documentation safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with C4 Architecture Documentation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is C4 Architecture Documentation free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published C4 Architecture Documentation?

Hack23 (@hack23) published this skill. Their other Agent Skills are listed on their SkillMD profile.

C4 Architecture Documentation by hack23

Name: C4 Architecture Documentation
Rating: 4.2 (5 reviews)
Author: Hack23

File contents

C4 Architecture Documentation Skill

Purpose

Document MCP server architecture using C4 model for different abstraction levels with Mermaid diagrams.

When to Use

✅ Documenting system architecture (ARCHITECTURE.md)
✅ Security architecture documentation (SECURITY_ARCHITECTURE.md)
✅ Future architecture planning (FUTURE_ARCHITECTURE.md)
✅ Architecture decision records
✅ Onboarding new developers

Required Documentation Portfolio

Current State

Document	Purpose
ARCHITECTURE.md	Complete C4 models (Context, Container, Component)
DATA_MODEL.md	Data structures, entities, relationships
FLOWCHART.md	Business process and data flows
STATEDIAGRAM.md	System state transitions and lifecycles
MINDMAP.md	System conceptual relationships
SWOT.md	Strategic analysis and positioning
SECURITY_ARCHITECTURE.md	Current security design and controls

Future State

Document	Purpose
FUTURE_ARCHITECTURE.md	Architectural evolution roadmap
FUTURE_DATA_MODEL.md	Enhanced data architecture plans
FUTURE_FLOWCHART.md	Improved process workflows
FUTURE_STATEDIAGRAM.md	Advanced state management
FUTURE_MINDMAP.md	Capability expansion plans
FUTURE_SWOT.md	Future strategic opportunities
FUTURE_SECURITY_ARCHITECTURE.md	Planned security improvements

C4 Model Levels

Level 1: System Context

graph TB
    User[AI Assistant/Developer] -->|MCP Protocol| Server[European Parliament MCP Server]
    Server -->|REST API| EPAPI[European Parliament Open Data API]
    Server -->|JSON-LD| EPData[EP Data Portal]

Level 2: Container Diagram

graph TB
    Client[MCP Client] -->|stdio/SSE| MCPServer[MCP Server - Node.js/TypeScript]
    MCPServer -->|HTTP/JSON| EPClient[EP API Client]
    EPClient -->|REST| EPAPI[data.europarl.europa.eu]
    MCPServer -->|Zod| Schemas[Validation Schemas]

Level 3: Component Diagram

graph TB
    Tools[MCP Tools] --> Client[EP API Client]
    Resources[MCP Resources] --> Client
    Prompts[MCP Prompts] --> Client
    Client --> Cache[LRU Cache]
    Client --> RateLimiter[Rate Limiter]
    Client --> Validator[Zod Schemas]

Mermaid Diagram Standards

Use graph TB for top-bottom flow diagrams
Use sequenceDiagram for interaction flows
Use stateDiagram-v2 for state machines
Use mindmap for conceptual relationships
Include legends and descriptions

ISMS Policy References

Secure Development Policy - Architecture documentation requirements
Information Security Policy - Security architecture governance

---name: c4-architecture-documentationdescription: Document system architecture using C4 model with context, container, component views and Mermaid diagramslicense: Apache-2.0---# C4 Architecture Documentation Skill## PurposeDocument MCP server architecture using C4 model for different abstraction levels with Mermaid diagrams.## When to Use- ✅ Documenting system architecture (ARCHITECTURE.md)- ✅ Security architecture documentation (SECURITY_ARCHITECTURE.md)- ✅ Future architecture planning (FUTURE_ARCHITECTURE.md)- ✅ Architecture decision records- ✅ Onboarding new developers## Required Documentation Portfolio### Current State| Document | Purpose ||----------|---------|| ARCHITECTURE.md | Complete C4 models (Context, Container, Component) || DATA_MODEL.md | Data structures, entities, relationships || FLOWCHART.md | Business process and data flows || STATEDIAGRAM.md | System state transitions and lifecycles || MINDMAP.md | System conceptual relationships || SWOT.md | Strategic analysis and positioning || SECURITY_ARCHITECTURE.md | Current security design and controls |### Future State| Document | Purpose ||----------|---------|| FUTURE_ARCHITECTURE.md | Architectural evolution roadmap || FUTURE_DATA_MODEL.md | Enhanced data architecture plans || FUTURE_FLOWCHART.md | Improved process workflows || FUTURE_STATEDIAGRAM.md | Advanced state management || FUTURE_MINDMAP.md | Capability expansion plans || FUTURE_SWOT.md | Future strategic opportunities || FUTURE_SECURITY_ARCHITECTURE.md | Planned security improvements |## C4 Model Levels### Level 1: System Context```mermaidgraph TB User[AI Assistant/Developer] -->|MCP Protocol| Server[European Parliament MCP Server] Server -->|REST API| EPAPI[European Parliament Open Data API] Server -->|JSON-LD| EPData[EP Data Portal]```### Level 2: Container Diagram```mermaidgraph TB Client[MCP Client] -->|stdio/SSE| MCPServer[MCP Server - Node.js/TypeScript] MCPServer -->|HTTP/JSON| EPClient[EP API Client] EPClient -->|REST| EPAPI[data.europarl.europa.eu] MCPServer -->|Zod| Schemas[Validation Schemas]```### Level 3: Component Diagram```mermaidgraph TB Tools[MCP Tools] --> Client[EP API Client] Resources[MCP Resources] --> Client Prompts[MCP Prompts] --> Client Client --> Cache[LRU Cache] Client --> RateLimiter[Rate Limiter] Client --> Validator[Zod Schemas]```## Mermaid Diagram Standards- Use `graph TB` for top-bottom flow diagrams- Use `sequenceDiagram` for interaction flows- Use `stateDiagram-v2` for state machines- Use `mindmap` for conceptual relationships- Include legends and descriptions## ISMS Policy References- [Secure Development Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Secure_Development_Policy.md) - Architecture documentation requirements- [Information Security Policy](https://github.com/Hack23/ISMS-PUBLIC/blob/main/Information_Security_Policy.md) - Security architecture governance

Frequently asked questions

C4 Architecture Documentation