Back to Details

unity-gamedev-skill-pack

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Unity GameDev Skill Pack

Unity游戏开发技能包

Use this skill to turn an external Unity skill pack into a reviewed internal package.
使用此技能将外部Unity技能包转换为经过审核的内部包。

When to use this skill

使用场景

  • You discovered an external Unity skill repository during survey runs.
  • You want selective reuse (workflow ideas) rather than direct copy-paste.
  • You need PR-safe imports with risk notes, provenance, and rollback.
  • 在调研过程中发现了外部Unity技能仓库。
  • 希望选择性复用（工作流思路）而非直接复制粘贴。
  • 需要带有风险说明、来源信息和回滚方案的PR安全导入方式。

When not to use

不适用场景

  • You need to debug a concrete Unity runtime/build error right now.
  • You are writing gameplay code directly instead of curating skill docs.
  • 当前需要调试具体的Unity运行时/构建错误。
  • 正在直接编写游戏玩法代码而非整理技能文档。

Instructions

操作步骤

Step 1: Capture source provenance

步骤1：记录来源信息

Record at least one concrete source URL plus retrieval method (
indexed snippet
or 
direct page retrieval
).
至少记录一个具体的源URL以及获取方式（
indexed snippet
或
direct page retrieval
）。

Step 2: Extract reusable patterns only

步骤2：仅提取可重用模式

From the source pack, keep transferable workflow units (setup checks, guardrails, validation order). Drop tool-locked fluff and unverifiable claims.
从源技能包中保留可迁移的工作流单元（设置检查、防护措施、验证顺序）。舍弃工具专属的冗余内容和无法验证的声明。

Step 3: Run safety gates

步骤3：执行安全检查

Before adding any imported guidance:
  • verify license suitability
  • check recency/activity
  • check that instructions are deterministic and non-destructive
  • flag engine-version assumptions explicitly
在添加任何导入的指南之前：
  • 验证许可证适用性
  • 检查更新频率/活跃度
  • 确保说明是确定性且无破坏性的
  • 明确标记引擎版本假设

Step 4: Package into local skill structure

步骤4：打包为本地技能结构

Create/update:
  • SKILL.md
    (operator-facing workflow)
  • SKILL.toon
    (compact behavior contract)
  • evals/evals.json
    (prompt assertions that enforce boundaries)
创建/更新：
  • SKILL.md
    （面向操作者的工作流文档）
  • SKILL.toon
    （简洁的行为契约）
  • evals/evals.json
    （用于约束边界的提示断言）

Step 5: Add risk + rollback in PR

步骤5：在PR中添加风险与回滚方案

State what was imported, what was intentionally excluded, known risks, and exact rollback path (revert commit/PR).
说明导入内容、刻意排除的部分、已知风险以及精确的回滚路径（还原提交/PR）。

Step 6: Validate before merge

步骤6：合并前验证

Run JSON checks, diff hygiene (
git diff --check
), and skill validator scripts when available.
运行JSON检查、差异清洁度检查（
git diff --check
），以及可用的技能验证脚本。

Output format

输出格式

Return a short curation packet:
  • Source(s)
  • Imported patterns
  • Excluded patterns
  • Risks
  • Validation results
返回一份简短的整理包：
  • 来源信息
  • 导入的模式
  • 排除的模式
  • 风险点
  • 验证结果

Examples

示例

  • "Survey found 
    tjboudreaux/cc-plugin-unity-gamedev
    ; import only reusable setup/validation flow into local skill docs with risk notes."
  • "Source license unclear after metadata fallback" -> keep as discovery evidence but do not promote/import without explicit exception rationale.
  • "调研发现
    tjboudreaux/cc-plugin-unity-gamedev
    ；仅将可重用的设置/验证流程导入本地技能文档，并添加风险说明。"
  • "元数据回退后仍无法明确源许可证" -> 保留为发现证据，但在无明确例外理由的情况下不推广/导入。

Best practices

最佳实践

  1. Prefer adaptation over replication: rewrite external guidance in local conventions.
  2. Keep provenance labels near claims so reviewers can verify quickly.
  3. Always include rollback steps in PR body when importing external workflows.
  1. 优先适配而非复制：按照本地规范重写外部指南。
  2. 将来源标签放在声明附近，方便审核者快速验证。
  3. 导入外部工作流时，PR正文中务必包含回滚步骤。

References

参考资料