Skill
4
Agent
All Skills
Search
Tools
中文
|
EN
Explore
Loading...
Back to Details
level-design
Compare original and translation side by side
🇺🇸
Original
English
🇨🇳
Translation
Chinese
Level Design
关卡设计（Level Design）
Purpose
目的
Shape level flow, pacing, navigation, encounter staging, and spatial teaching.
塑造关卡流程（level flow）、节奏把控（pacing）、导航设计（navigation）、遭遇战编排（encounter staging）以及空间引导（spatial teaching）。
Use When
适用场景
building levels, missions, dungeons, arenas, or traversal spaces
players get lost or overwhelmed
encounters need better pacing
构建关卡、任务、地下城、竞技场或探索空间时
玩家出现迷路或信息过载情况时
遭遇战需要优化节奏时
Inputs
输入要素
core loop
combat or traversal rules
narrative beats
content constraints
core loop（核心循环）
战斗或探索规则
叙事节点（narrative beats）
内容约束条件
Process
实施流程
define the player path, beats, and teaching moments
place pressure, relief, discovery, and decision points intentionally
support readability, landmarks, and recovery from mistakes
coordinate with UI, narrative, and combat timing
review the space with playtest and traversal metrics
明确玩家路径、节点以及引导环节
合理设置压力点、舒缓点、探索点和决策点
提升可读性，设置地标，支持玩家从失误中恢复
与UI、叙事和战斗节奏协同配合
通过 playtest（游戏测试）和探索数据复盘空间设计
Outputs
输出成果
level beat map
encounter flow notes
spatial teaching plan
revision targets
level beat map（关卡节点图）
encounter flow notes（遭遇战流程说明）
spatial teaching plan（空间引导方案）
优化目标
Quality Bar
质量标准
supports the core fantasy and player goals
defines readable rules, edge cases, and feedback
creates concrete hooks for tuning, telemetry, and QA
契合核心玩法体验与玩家目标
明确清晰的规则、边界场景及反馈机制
为调优、数据监控（telemetry）和QA（质量保障）提供明确切入点
Common Failure Modes
常见失误模式
adding systems that do not serve the core loop
shipping vague rules that QA and engineering must guess at
tuning without instrumentation or hypotheses
添加与core loop无关的系统
交付模糊规则，导致QA和开发团队需要自行揣测
未借助监控工具或假设前提进行调优
Related Agents
关联Agent
level-designer
combat-designer
narrative-designer
level-designer（关卡设计师）
combat-designer（战斗设计师）
narrative-designer（叙事设计师）
Related Commands
关联命令
level-beat
playtest-report
verify
level-beat
playtest-report
verify
Notes
注意事项
Keep this skill aligned with the relevant rules layer and current project documentation.
If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
确保本skill与相关规则层及当前项目文档保持一致
若引擎特定约束对工作流程产生实质性影响，转交至对应引擎skill或引擎专属审核人员处理