c4

Create and maintain a machine-checkable C4 architecture model in ARCHITECTURE.md and workspace.dsl.

9|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/paivot-ai/paivot-graph --skill c4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c4
Source: https://github.com/paivot-ai/paivot-graph/tree/main/skills/c4
Command: npx skills add https://github.com/paivot-ai/paivot-graph --skill c4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and maintenance of a machine-checkable C4 architecture model alongside narrative documentation, ensuring architectural intent stays aligned with the codebase.

Core Features & Use Cases

  • Maintains a canonical C4 model in workspace.dsl and ARCHITECTURE.md to reflect boundaries, containers, and relationships.
  • Generates and exports architecture diagrams using Structurizr DSL or Mermaid for system-context and container views.
  • Enforces architecture boundaries and supports automatic diagram updates when the codebase evolves.

Quick Start

Enable architecture.c4 in your project settings, then run this skill to generate and synchronize the machine-checkable C4 model with ARCHITECTURE.md and the codebase.

Frequently Asked Questions about c4

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

FAQPage Schema
How do I maintain a machine-checkable C4 architecture model for my codebase?

To maintain a machine-checkable C4 architecture model, this skill synchronizes your ARCHITECTURE.md and workspace.dsl files with the codebase, ensuring architectural intent stays aligned as the code evolves.

Can I generate architecture diagrams from Structurizr DSL and Mermaid?

Yes, you can generate and export architecture diagrams using Structurizr DSL or Mermaid to create system-context and container views based on your canonical C4 model.

Do I need ARCHITECTURE.md and workspace.dsl files to use C4 architecture automation?

Yes, the repository must contain existing ARCHITECTURE.md and workspace.dsl files before running this skill, as it requires them to synchronize boundaries, containers, and relationships with the code.

What is the best way to enforce architecture boundaries in a software engineering project?

The best way to enforce architecture boundaries is by maintaining a canonical C4 model in workspace.dsl and ARCHITECTURE.md, which acts as an architecture contract to reflect explicit system limits.

How do I automatically update architecture diagrams when my codebase evolves?

You can automatically update architecture diagrams when the codebase evolves by running this skill to synchronize the machine-checkable C4 model with your code and Structurizr DSL workspace.