mapping-visualization-scaffolds
Creates visual maps that make implicit relationships, dependencies, and structures explicit through diagrams, concept maps, and architectural blueprints. Guides through identifying nodes and relationships, choosing visualization approaches, and validating completeness. 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, or when user mentions concept maps, system diagrams, dependency mapping, relationship visualization, or architecture blueprints.
What this skill does
# Mapping & Visualization Scaffolds ## Table of Contents - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Workflow 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](#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](resources/template.md). For complex systems (50+ nodes) or collaborative sessions, see [resources/methodology.md](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](resources/methodology.md) for mapping strategies and tool selection. See [Common Patterns](#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](resources/template.md) as your scaffold. **Step 5: Validate and refine** Check completeness, clarity, and accuracy using [resources/evaluators/rubric_mapping_visualization_scaffolds.json](resources/evaluators/rubric_mapping_visualization_scaffolds.json). Ensure all critical nodes and relationships are present. Minimum standard: Score ≥ 3.5 average. ## Common Patterns **Architecture Diagrams:** - System components as nodes - Service calls/data flows as relationships - Layers as groupings (frontend, backend, data) - Use for: Technical documentation, system design reviews **Concept Maps:** - Concepts/ideas as nodes - "is-a", "has-a", "leads-to" as relationships - Themes as groupings - Use for: Learning, knowledge organization, research synthesis **Dependency Graphs:** - Tasks/features/modules as nodes - "depends-on", "blocks", "requires" as relationships - Phases/sprints as groupings - Use for: Project planning, risk assessment, parallel work identification **Hierarchies & Taxonomies:** - Categories/classes as nodes - Parent-child relationships - Levels as groupings (L1, L2, L3) - Use for: Information architecture, org charts, skill trees **Flow Diagrams:** - Steps/states as nodes - Transitions/decisions as relationships - Swim lanes as groupings (roles, systems) - Use for: Process documentation, user journeys, decision trees ## Guardrails **Scope Management:** - Focus on relationships that matter for the specific purpose - Don't map everything—map what's decision-relevant - Stop at appropriate detail level (usually 3-4 layers deep) - For systems with > 50 nodes, create multiple focused maps **Clarity Over Completeness:** - Prioritize understandability over exhaustiveness - Use consistent notation and naming - Add legend if > 3 relationship types - Group related nodes to reduce visual complexity **Validation:** - Verify accuracy with subject matter experts - Test if someone unfamiliar can understand the map - Check for missing critical relationships - Ensure directionality is clear (A → B vs A ← B) **Common Pitfalls:** - ❌ Creating "hairball" diagrams with too many connections - ❌ Mixing abstraction levels (strategic + implementation details) - ❌ Using inconsistent node/relationship representations - ❌ Forgetting to state the map's purpose and scope ## Quick Reference **Resources:** - `resources/template.md` - Structured scaffold for creating maps - `resources/evaluators/rubric_mapping_visualization_scaffolds.json` - Quality criteria **Output:** - File: `mapping-visualization-scaffolds.md` in current directory - Contains: Nodes, relationships, groupings, legend (if needed) - Format: Markdown with ASCII diagrams or structured lists **Success Criteria:** - All critical nodes identified - Relationships clearly labeled with directionality - Appropriate grouping/layering applied - Understandable by target audience without explanation - Validated against quality rubric (score ≥ 3.5)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.