Generate C4 diagrams as draw.io XML from system descriptions.
npx skills add https://github.com/cjennings/rulesets --skill c4-diagram-cjennings
Please help me install this Agent Skill. Skill: c4-diagram Source: https://github.com/cjennings/rulesets/tree/main/c4-diagram Command: npx skills add https://github.com/cjennings/rulesets --skill c4-diagram-cjennings
Transform plain-language descriptions of a software system into structured C4 architecture diagrams, enabling rapid planning, communication, and alignment with stakeholders.
Describe your software system in plain language and specify the diagram level you want (e.g., system context or container) to generate the initial diagrams.
High-intent search queries and answers about installing and using this skill.
To generate C4 architecture diagrams from a text description, provide a conversational narrative of your software system and an optional diagram level. The skill processes this input through phased modeling to output structured C4 diagrams.
Yes, you can create draw.io diagrams using the C4 model because the skill outputs draw.io compatible XML. This allows direct integration of generated System Context and Container diagrams into existing documentation workflows.
The best way to automate system context and container diagram creation is providing a plain-language system description to an automated modeling tool. This approach uses Simon Brown's C4 methodology to structure the diagrams and performs layout audits for readability.
Generating C4 diagrams with this approach does not require manual layout adjustments because the process includes an automated layout audit. This audit checks the generated draw.io XML to ensure the architecture diagrams remain readable for stakeholders.
To structure a software system description for C4 diagram generation, write a plain-language narrative explaining the system and specify the desired diagram level, such as system context or container. The skill guides you through understanding the system and building the model from this input.
You need a System Context diagram to show high-level interactions with external users and systems, while a Container diagram details the internal deployable components. You can specify either level as input to generate the appropriate draw.io XML output.
davidrrowleyAssess software architectures with C4 diagrams, STRIDE analysis, and WAF pillar evaluations.
NexusSemaGenerate C4 Context, Container, and Component diagrams as draw.io XML from architecture shard documents.
ExpeditoJValidate system architecture with documentation, diagrams, and stakeholder consensus.
VSF-QC-TTSStandardize architecture diagrams using C4 and UML models with Mermaid syntax.
