generate-structurizr-c4-diagram
Skill16 starsChanged 4 months agoGPL-3.0View on GitHub
Generate C4 software-architecture diagrams in Structurizr DSL from a codebase, folder(s), a description, docs, or an existing diagram, then render them in the Structurizr playground and save PNG(s). Use whenever the user wants to visualize or document software architecture — any C4 view (System Context, Container, Component, Deployment, System Landscape, or a Dynamic view of runtime/request/message flow between services or containers); how services/microservices communicate or how a system is deployed; producing Structurizr DSL; or converting/reverse-engineering an existing diagram (Mermaid, PlantUML, UML, ad-hoc) into the C4 model. Triggers include "C4 diagram", "architecture diagram", "Structurizr", "diagram/visualize this codebase or system", and sequence/flow diagrams of how services interact. Not for — UML class diagrams, entity-relationship/DB-schema diagrams, network/infra topology, flowcharts or code sequence diagrams inside one function, Gantt charts, or merely explaining C4 without a diagram.
In this repository27 other files it gives its agents.
- evaluate-skill-with-copilot-sdkSkill
- skill-creatorSkill
- writing-great-skillsSkill
- data-cleanerSkill
- ds-report-writerSkill
- eda-autopilotSkill
- experiment-trackerSkill
- feature-forgeSkill
- fine-tuning-guideSkill
- hyperparameter-tunerSkill
- llm-app-builderSkill
- model-deployerSkill
- model-trainerSkill
- nn-architectSkill
- pipeline-builderSkill
- stats-advisorSkill
- viz-craftsmanSkill
- code-reviewSkill
- grill-meSkill
- implementSkill
- shipSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- project-pitchSkill
- arxiv-submissionSkill
- insight-extractorSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

