What problem does it solve? Technical diagrams often become decorative boxes and arrows that fail to communicate anything specific. This Skill guides the design of architecture, process, flow, hierarchy, relationship, and explanatory diagrams as visual models that answer a defined question for a defined audience, with consistent node, connector, grouping, and label semantics. ## Core Features & Use Cases - Question-driven diagram design: Fix the question, audience, and purpose first, then select the right abstraction level and diagram type instead of cramming everything into one image. - Semantic consistency rules: Map each visual difference (shape, line style, color, grouping) to exactly one meaning, with explicit direction on connectors and progressive disclosure from overview to detail diagrams. - Accessibility and verification checks: Avoid color-only encoding, audit edge crossings and ambiguous arrows, and provide text alternatives for complex diagrams based on W3C WAI guidance. - Use Case: When documenting a Cloudflare Workers system for onboarding, use this Skill to split a tangled single diagram into a context overview plus focused detail diagrams with a clear legend and labeled trust boundaries. ## Quick Start Use the diagram-design skill to plan an architecture diagram for my system that answers a specific question for new team members.
