diagram-and-architecture-visualslisted

# Diagram and Architecture Visuals Use this skill when a diagram will communicate structure, flow, state, ownership, dependencies or quantitative relationships better than prose/table alone. Do not make a diagram merely because the task is technical. A good diagram reduces cognitive load; a bad one converts readable text into boxes and arrows. ## First decision: should this be a diagram? Prefer prose/table when: - the relationship is trivial; - a two-column or three-column table communicates the same thing; - there is only one meaningful node/action; - the artifact would need a paragraph of legend just to become understandable. Use a diagram when spatial relationship, order, branching, state, trust boundaries, topology, ownership or relative quantity is materially easier to understand visually. ## Route by job Agentit does not vendor every upstream diagram skill into core. Choose the smallest useful implementation family JIT. ### General/branded visual communication -> diagram-design Use or inspect `cathrynlavery/diagram-design` when the job is primarily **visual explanation** and benefits from a polished standalone diagram. The inspected upstream supports a broad type library including architecture, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar, loop/flywheel, trees, layers, Sankey, Wardley, deployment, dependency, UML, story maps and database schemas. It uses progressive disclosure: choose the visual/semantic type, then lo