c4-architecture-c4-architecture

Generate C4 architecture documentation from existing codebases.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill c4-architecture-c4-architecture-chicanoandres702
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c4-architecture-c4-architecture
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/c4-architecture-c4-architecture
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill c4-architecture-c4-architecture-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates comprehensive C4 architecture documentation for an existing codebase, saving time and ensuring consistent architectural records across multiple levels.

Core Features & Use Cases

  • Bottom-up Code-Level Documentation: Documents every subdirectory starting from the deepest paths to capture all code elements.
  • Component Synthesis: Aggregates code-level docs into logical components to show responsibilities and boundaries.
  • Container & Context Mapping: Maps components to deployment containers and system context diagrams for stakeholders.
  • Linkable Artifacts: Outputs are organized under C4-Documentation with references to source files and APIs when applicable.

Quick Start

Run the c4-architecture-c4-architecture workflow against a repository to generate the full C4 documentation set in C4-Documentation/.

Frequently Asked Questions about c4-architecture-c4-architecture

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

FAQPage Schema
How do I generate C4 architecture documentation from an existing codebase?

You can generate C4 architecture documentation by running a bottom-up workflow that analyzes your deepest code directories first, synthesizing code, component, container, and context diagrams automatically into a structured output directory.

What is the best way to automate context and container diagram creation for software projects?

Automating context and container diagram creation involves aggregating code-level documentation into logical components, then mapping those components to deployment containers and system contexts to provide clear architectural boundaries for stakeholders.

Can I include API specifications and source file links in my C4 model diagrams?

Yes, generating C4 architecture diagrams can optionally include API specifications and linkable artifacts, organizing outputs with direct references to the analyzed source files for comprehensive architecture documentation.

Does bottom-up code analysis work for large software repositories?

Bottom-up code analysis applies to software projects of varying sizes by systematically documenting every subdirectory starting from the deepest paths to capture all code elements before synthesizing higher-level views.

How to map code components to deployment containers automatically?

Mapping code components to deployment containers is done through component synthesis, which aggregates code-level documentation into logical components to show responsibilities and boundaries before mapping them to the container level.

Why should I use a multi-phase workflow for architecture documentation?

A multi-phase workflow ensures comprehensive architecture documentation by sequentially performing code, component, container, and context synthesis, which captures structural details bottom-up while producing consistent stakeholder-facing diagrams.