c4

To generate C4 architecture diagrams from a codebase, you can use a skill that parses the repository structure and produces Mermaid-based C4 Context and Container diagrams. It writes the generated files directly to the project's documentation locations.

Yes, you can create Mermaid C4 Context and Container diagrams automatically by invoking the skill on a project. It reads the repository to produce L1 and L2 diagrams, removing manual diagram labor.

This skill works for both multi-repo and single-repo projects where architecture diagrams are needed on demand. It resolves target output paths via portfolio helpers and writes files to the appropriate framework locations.

You should regenerate C4 architecture diagrams during onboarding, architecture reviews, or documentation refresh workflows after structural changes. This ensures the C4 Context and Container diagrams remain up-to-date with the current codebase.

The best way to document software architecture without manual diagramming is to generate diagrams directly from the codebase. This approach produces Mermaid-based C4 diagrams and honors portfolio templates when present.

You do not need portfolio templates to generate C4 diagrams, but the skill honors them when they are present. It writes diagrams to the project's documentation locations or framework-wide paths based on the available templates.