New skills: Cinemachine 3, build automation/CI, save systems, AI Navigation, UGS multiplayer, VFX Graph, localization, XR
還沒有人認領這個 Issue。
評估
研究方向
Start by reviewing the existing skill frontmatter, manifest, README, and docs navigation to see how skills are structured and registered. Then scope the first five topics listed in the issue and identify the corresponding files to update. Done means those five skills include compiling Unity 6 examples and the manifest, README, and docs navigation are updated.
由索引模型根據 Issue 內容生成。
描述
Why it matters
The 18 skills cover core scripting well, but several areas Unity developers ask about daily have no coverage. The roadmap already lists some (Cinemachine, VFX Graph, Localization, build automation). Filling them widens who the plugin is useful for.
Gaps found (only bare package mentions today)
- Cinemachine 3.x (API changed heavily from 2.x; models often produce 2.x code)
- AI Navigation / NavMesh (
NavMeshSurface, agents, links) - VFX Graph and particle systems
- Localization (
com.unity.localization, string tables, smart strings) - Save systems (versioned save data, atomic writes, cloud saves)
- Unity Gaming Services / Multiplayer Services (Authentication, Relay, Lobby, Sessions, Cloud Save)
- XR (XR Interaction Toolkit, OpenXR)
- Build automation and CI (Build Profiles,
BuildPipeline, batchmode, GameCI GitHub Actions) - Lighting and baking, Terrain
- 2D depth: Tilemap, Sprite Atlas, 2D Animation / IK
- Performance (Unity 6 tools): GPU Resident Drawer, Project Auditor, BatchRendererGroup, STP missing from
performance-optimization.
Suggested approach
Prioritize by demand: Cinemachine 3, build automation/CI, save systems, AI Navigation, UGS multiplayer, then the rest. Each new skill follows the existing frontmatter standard and includes compiling Unity 6 examples.
Done when
At least the first five skills ship, with manifest, README and docs nav updated.
- 主要語言
- C#
- 星號
- 4
- 分支
- 0
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Unity-Developer-Tools 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 35/100
-
ci priority: low skills
難度 3/5 1-2 天 新手友好度 55/100
-
good first issue skills testing
難度 3/5 1-2 天 新手友好度 58/100
-
ci priority: medium testing
難度 4/5 1-2 天 新手友好度 57/100
-
documentation marketing priority: medium
難度 5/5 一週以上 新手友好度 35/100
查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue
相似的 Issue
-
type:task ux
難度 2/5 1-3 小時 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
維護者通常 1 天內回覆