Back to Details

mapping-visualization-scaffolds

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Mapping & Visualization Scaffolds

映射与可视化脚手架

Table of Contents

目录

Purpose

目的

Create visual maps that make implicit relationships, dependencies, and structures explicit through diagrams, concept maps, and architectural blueprints.
创建可视化图谱，通过图表、概念图和架构蓝图将隐性的关系、依赖和结构显性化。

When to Use

适用场景

Use mapping-visualization-scaffolds when you need to:
System Understanding:
  • Document complex system architectures (microservices, infrastructure, data flows)
  • Map component dependencies and relationships
  • Visualize API endpoints and integration points
  • Understand legacy system structure
Knowledge Organization:
  • Create concept maps for learning or teaching
  • Build taxonomies and hierarchies
  • Organize research literature or domain knowledge
  • Structure information architecture
Process & Flow Documentation:
  • Map user journeys and workflows
  • Create decision trees and flowcharts
  • Document approval chains or escalation paths
  • Visualize project dependencies and timelines
Strategic Visualization:
  • Map stakeholder relationships and influence
  • Visualize organizational structures
  • Create competitive landscape maps
  • Document value chains or business models
在以下场景中使用映射与可视化脚手架：
系统理解：
  • 记录复杂系统架构（微服务、基础设施、数据流）
  • 映射组件依赖与关系
  • 可视化API端点和集成点
  • 理解遗留系统结构
知识组织：
  • 创建用于学习或教学的概念图
  • 构建分类体系和层级结构
  • 整理研究文献或领域知识
  • 规划信息架构
流程与工作流文档：
  • 绘制用户旅程和工作流
  • 创建决策树和流程图
  • 记录审批链或升级路径
  • 可视化项目依赖和时间线
战略可视化：
  • 映射利益相关者关系与影响力
  • 可视化组织结构
  • 创建竞争格局图谱
  • 记录价值链或商业模式

What Is It

什么是映射脚手架

A mapping scaffold is a structured approach to creating visual representations that show:
  • Nodes (components, concepts, people, steps)
  • Relationships (connections, dependencies, hierarchies, flows)
  • Attributes (properties, states, metadata)
  • Groupings (clusters, categories, layers)
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.
映射脚手架是一种创建可视化表示的结构化方法，用于展示：
  • 节点（组件、概念、人员、步骤）
  • 关系（连接、依赖、层级、流转）
  • 属性（特性、状态、元数据）
  • 分组（集群、类别、层级）
快速示例：
对于微服务架构：
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
此示例创建了一个可视化图谱，展示服务之间的连接和依赖关系。

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 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.
复制以下清单并跟踪进度：
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
步骤1：明确映射目的
询问用户目标：需要映射什么系统/概念？受众是谁？这份图谱将用于支撑哪些决策？需要达到什么细节程度？查看常见模式了解典型用例。
步骤2：识别节点与关系
列出所有关键元素（节点）及其连接（关系）。确定层级、依赖类型和分组标准。对于简单场景（少于20个节点），使用resources/template.md。对于复杂系统（50个以上节点）或协作场景，查看resources/methodology.md获取进阶策略。
步骤3：选择可视化方法
根据复杂度选择格式：少于10个节点用简单列表，层级结构用树形图，复杂关系用网络图，系统用分层图。对于大规模系统或多图谱层级结构，参考resources/methodology.md获取映射策略和工具选择建议。查看常见模式获取指导。
步骤4：创建图谱
使用Markdown、ASCII图表或结构化文本构建可视化。先从高层结构开始，再添加细节。必要时添加图例。使用resources/template.md作为脚手架。
步骤5：验证与优化
使用resources/evaluators/rubric_mapping_visualization_scaffolds.json检查完整性、清晰度和准确性。确保所有关键节点和关系都已包含。最低标准：平均得分≥3.5。

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
架构图：
  • 系统组件作为节点
  • 服务调用/数据流作为关系
  • 层级作为分组（前端、后端、数据层）
  • 用途：技术文档、系统设计评审
概念图：
  • 概念/想法作为节点
  • "是一种"、"包含"、"导致"作为关系
  • 主题作为分组
  • 用途：学习、知识组织、研究综合
依赖图谱：
  • 任务/功能/模块作为节点
  • "依赖于"、"阻塞"、"需要"作为关系
  • 阶段/迭代作为分组
  • 用途：项目规划、风险评估、并行工作识别
层级与分类体系：
  • 类别/类作为节点
  • 父子关系
  • 层级作为分组（L1、L2、L3）
  • 用途：信息架构、组织架构图、技能树
流程图：
  • 步骤/状态作为节点
  • 转换/决策作为关系
  • 泳道作为分组（角色、系统）
  • 用途：流程文档、用户旅程、决策树

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
范围管理：
  • 聚焦于与特定目的相关的关系
  • 不要映射所有内容——只映射与决策相关的部分
  • 在合适的细节层级停止（通常3-4层深）
  • 对于超过50个节点的系统，创建多个聚焦的图谱
清晰优先于完整：
  • 优先考虑可理解性而非详尽性
  • 使用一致的符号和命名
  • 若关系类型超过3种，添加图例
  • 对相关节点进行分组以降低视觉复杂度
验证：
  • 与主题专家核实准确性
  • 测试不熟悉内容的人是否能理解图谱
  • 检查是否遗漏关键关系
  • 确保方向性清晰（A→B vs A←B）
常见陷阱：
  • ❌ 创建连接过多的"毛球"图
  • ❌ 混合抽象层级（战略+实现细节）
  • ❌ 使用不一致的节点/关系表示
  • ❌ 忘记说明图谱的目的和范围

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)
资源：
  • resources/template.md
    - 创建图谱的结构化脚手架
  • resources/evaluators/rubric_mapping_visualization_scaffolds.json
    - 质量标准
输出：
  • 文件：当前目录下的
    mapping-visualization-scaffolds.md
  • 包含：节点、关系、分组、图例（如有需要）
  • 格式：带有ASCII图表或结构化列表的Markdown
成功标准：
  • 识别所有关键节点
  • 关系清晰标注方向
  • 应用了合适的分组/分层
  • 目标受众无需解释即可理解
  • 符合质量标准（得分≥3.5）