Use when complex systems need visual documentation, mapping component relationships and dependencies, creating hierarchies or taxonomies, documenting process flows or decision trees, understanding system architectures, visualizing data lineage or knowledge structures, planning information architecture, or when user mentions concept maps, system diagrams, dependency mapping, relationship visualization, or architecture blueprints.
Creates visual maps to document complex systems, relationships, and processes. Use when user requests architecture diagrams, dependency mapping, concept maps, or needs to understand component relationships and hierarchies.
/plugin marketplace add lyndonkl/claude/plugin install lyndonkl-thinking-frameworks-skills@lyndonkl/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
resources/evaluators/rubric_mapping_visualization_scaffolds.jsonresources/methodology.mdresources/template.mdCreate visual maps that make implicit relationships, dependencies, and structures explicit through diagrams, concept maps, and architectural blueprints.
Use mapping-visualization-scaffolds when you need to:
System Understanding:
Knowledge Organization:
Process & Flow Documentation:
Strategic Visualization:
A mapping scaffold is a structured approach to creating visual representations that show:
Quick Example:
For a microservices architecture:
Nodes: API Gateway, Auth Service, User Service, Payment Service, Database
Relationships:
- API Gateway → calls → Auth Service
- Auth Service → validates → User Service
- Payment Service → reads/writes → Database
Groupings: Frontend Layer, Business Logic Layer, Data Layer
This creates a visual map showing how services connect and depend on each other.
Copy this checklist and track your progress:
Mapping Visualization Progress:
- [ ] Step 1: Clarify mapping purpose
- [ ] Step 2: Identify nodes and relationships
- [ ] Step 3: Choose visualization approach
- [ ] Step 4: Create the map
- [ ] Step 5: Validate and refine
Step 1: Clarify mapping purpose
Ask user about their goal: What system/concept needs mapping? Who's the audience? What decisions will this inform? What level of detail is needed? See Common Patterns for typical use cases.
Step 2: Identify nodes and relationships
List all key elements (nodes) and their connections (relationships). Identify hierarchy levels, dependency types, and grouping criteria. For simple cases (< 20 nodes), use resources/template.md. For complex systems (50+ nodes) or collaborative sessions, see resources/methodology.md for advanced strategies.
Step 3: Choose visualization approach
Select format based on complexity: Simple lists for < 10 nodes, tree diagrams for hierarchies, network graphs for complex relationships, or layered diagrams for systems. For large-scale systems or multi-map hierarchies, consult resources/methodology.md for mapping strategies and tool selection. See Common Patterns for guidance.
Step 4: Create the map
Build the visualization using markdown, ASCII diagrams, or structured text. Start with high-level structure, then add details. Include legend if needed. Use resources/template.md as your scaffold.
Step 5: Validate and refine
Check completeness, clarity, and accuracy using resources/evaluators/rubric_mapping_visualization_scaffolds.json. Ensure all critical nodes and relationships are present. Minimum standard: Score ≥ 3.5 average.
Architecture Diagrams:
Concept Maps:
Dependency Graphs:
Hierarchies & Taxonomies:
Flow Diagrams:
Scope Management:
Clarity Over Completeness:
Validation:
Common Pitfalls:
Resources:
resources/template.md - Structured scaffold for creating mapsresources/evaluators/rubric_mapping_visualization_scaffolds.json - Quality criteriaOutput:
mapping-visualization-scaffolds.md in current directorySuccess Criteria:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.