Use when the task needs the right diagram type selected explicitly before architecture, integration, runtime, data-model, workflow, or UX reasoning.
Scanned 9/8/2026
Install to Claude Code
Skills Directorynpx -y skills add agisota/old-one --skill diagram-taxonomy --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Diagram Taxonomy?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/agisota-diagram-taxonomy)More formats (shields.io, HTML) on the badges page.
---
name: diagram-taxonomy
description: Use when the task needs the right diagram type selected explicitly before architecture, integration, runtime, data-model, workflow, or UX reasoning.
---
# Diagram Taxonomy
Choose the lightest diagram that answers the question:
- ASCII architecture -> boundaries, modules, ownership, blast radius
- sequence -> who calls whom and in what order
- data-flow -> where data moves and transforms
- ERD -> how data is shaped
- state machine -> how status/lifecycle changes over time
- component/screen map -> what the workflow surface looks like
Reference:
- `~/.ai-agent-hub/knowledge/rules/operator-pack-v3/DIAGRAM_TAXONOMY.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
