diagram-design Skill
Design and review guidance for software architecture diagrams (Mermaid, Draw.io). Use when creating, reviewing, or editing diagrams in any markdown documentation. Triggered by: diagram, flowchart, sequence diagram, mermaid, drawio, architecture diagram, data flow, state machine, ER diagram, class diagram, C4 model, sys Published by microsoft in devsquad-copilot.
What is diagram-design Skill?
Design and review guidance for software architecture diagrams (Mermaid, Draw.io). Use when creating, reviewing, or editing diagrams in any markdown documentation. Triggered by: diagram, flowchart, sequence diagram, mermaid, drawio, architecture diagram, data flow, state machine, ER diagram, class diagram, C4 model, sys Published by microsoft in devsquad-copilot. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Data analysis
- Design and media
- Documentation use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use diagram-design Skill
- Use it for documentation.
- Use it for data analysis.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/diagram-design/SKILL.md
What it does
Design and review guidance for software architecture diagrams (Mermaid, Draw.io). Use when creating, reviewing, or editing diagrams in any markdown documentation. Triggered by: diagram, flowchart, sequence diagram, mermaid, drawio, architecture diagram, data flow, state machine, ER diagram, class diagram, C4 model, sys
Skill instructions
Diagram Design Principles A diagram exists to help someone understand something. Before creating one, ask: who is the audience and what question does this diagram answer? - Business stakeholders need system context: what the system does, who uses it, what it connects to. Omit internals and technology. - Developers need technical clarity: components, data flows, technology choices. - A diagram that tries to serve both audiences usually serves neither. Zoom, don't cram. Each diagram should answer one question at one level of abstraction. Use separate diagrams for context, containers, components, and code, like zooming into a map. Keep it simple. When a diagram feels cluttered, split it. Avoid crossing arrows, limit to ~15 elements, and prefer clarity over completeness. Every element must be meaningful. Each box needs a name and a responsibility (one sentence). Add technology labels only for technical audiences. If you cannot describe what an element does, remove it. Diagrams complement t
Explore related resources
Frequently asked questions
What is diagram-design?
diagram-design is a open-source AI agent skill with Copy skill directory. Design and review guidance for software architecture diagrams (Mermaid, Draw.io). Use when creating, reviewing, or editing diagrams in any markdown documentation.
Who is diagram-design best for?
diagram-design is best for reusing agent instructions, scripts, and references, documentation workflows, data analysis workflows, design and media workflows.
How do I install diagram-design?
Install or run diagram-design using Copy skill directory. Check diagram-design for the latest setup command.
Is diagram-design actively maintained?
diagram-design may need a closer maintenance check before production use.
Auto-fetched from GitHub.
