Back to Details

zoom-out

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Zoom Out

宏观视角（Zoom Out）

Get a higher-level architectural perspective on unfamiliar code sections.
获取不熟悉代码片段的更高层次架构视角。

When to use this skill

使用场景

  • Navigating unfamiliar code and needing to understand how it connects to the larger system
  • Before making changes to understand the blast radius
  • When you need a module map before diving into implementation
  • 浏览不熟悉的代码，需要了解其与更大系统的关联方式
  • 在进行修改前，了解影响范围（blast radius）
  • 在深入实现细节前，需要一份模块映射图

When not to use this skill

不适用场景

  • Finding specific symbols or patterns → use 
    codebase-search
  • Architectural improvement opportunities → use 
    improve-codebase-architecture
  • Debugging a specific failure → use 
    debugging
  • 查找特定符号或模式 → 使用
    codebase-search
  • 寻找架构改进机会 → 使用
    improve-codebase-architecture
  • 调试特定故障 → 使用
    debugging

What zoom-out produces

宏观视角技能的输出内容

A structural map showing:
  • All relevant modules in the area of interest
  • Caller relationships (what calls what)
  • Key dependencies (what depends on what)
  • Domain vocabulary from CONTEXT.md applied to module names
一份结构映射图，包含：
  • 感兴趣区域内的所有相关模块
  • 调用关系（谁调用谁）
  • 关键依赖项（谁依赖谁）
  • 应用到模块名称的CONTEXT.md中的领域词汇

How to use

使用方法

When you encounter unfamiliar code, ask for a zoom-out before diving in:
"Zoom out and give me a broader view of how [module/component] fits into the system."
The response will map the relevant modules using the project's domain glossary, not internal implementation names.
当遇到不熟悉的代码时，在深入细节前请求宏观视角：
"Zoom out and give me a broader view of how [module/component] fits into the system."
响应会使用项目的领域词汇表来映射相关模块，而非内部实现名称。

Output format

输出格式

[Module A] → calls → [Module B], [Module C]
[Module B] ← called by → [Module A], [Module D]

Key seams:
- [Interface X] separates [Domain Concept 1] from [Domain Concept 2]
- [Interface Y] is where [Domain Concept 3] behavior can be swapped

Domain terms in use here:
- "Order" = [what it means in this context]
- "Customer" = [what it means in this context]
[Module A] → calls → [Module B], [Module C]
[Module B] ← called by → [Module A], [Module D]

Key seams:
- [Interface X] separates [Domain Concept 1] from [Domain Concept 2]
- [Interface Y] is where [Domain Concept 3] behavior can be swapped

Domain terms in use here:
- "Order" = [what it means in this context]
- "Customer" = [what it means in this context]

Note on invocation

调用说明

This skill sets 
disable-model-invocation: true
— it is a directive framework that instructs the agent how to respond, not an independent processing unit. Invoke it as a behavioral directive when exploring code.
此技能设置了
disable-model-invocation: true
——它是一个指令框架，用于指导Agent如何响应，而非独立处理单元。在探索代码时，将其作为行为指令调用。

Instructions

操作步骤

  1. Identify the task trigger and expected output.
  2. Follow the workflow steps in this skill from top to bottom.
  3. Validate outputs before moving to the next step.
  4. Capture blockers and fallback path if any step fails.
  1. 识别任务触发条件和预期输出。
  2. 从上到下遵循此技能中的工作流程步骤。
  3. 进入下一步前验证输出内容。
  4. 记录任何步骤失败时的障碍和回退路径。

Examples

示例

  • Example: Apply this skill to a small scope first, then scale to full scope after validation passes.
  • 示例：先在小范围内应用此技能，验证通过后再扩展到完整范围。

Best practices

最佳实践

  • Keep outputs deterministic and auditable.
  • Prefer small reversible changes over broad risky edits.
  • Record assumptions explicitly.
  • 保持输出可确定且可审计。
  • 优先选择小的可逆变更，而非广泛的高风险编辑。
  • 明确记录假设。

References

参考资料

  • Project standards: 
    .agent-skills/skill-standardization/SKILL.md
  • Validator script: 
    .agent-skills/skill-standardization/scripts/validate_skill.sh
  • 项目标准：
    .agent-skills/skill-standardization/SKILL.md
  • 验证脚本：
    .agent-skills/skill-standardization/scripts/validate_skill.sh