About unity-implement
A workflow skill for implementing user-requested changes in Unity projects. It sets boundaries for tools and edits, requires validation through the Unity pipeline, and specifies cleanup and reporting steps.
Key features
- 01Establishes project and tool boundaries
- 02Uses Unity tools for code and UI edits
- 03Runs typechecks and tests
- 04Keeps temporary artifacts in .scratch/
- 05Defers human playtesting and Player Build
Use cases
- 01Implement a Unity feature from a task spec
- 02Validate changes with targeted and full tests
- 03Make UI edits without directly editing Unity YAML
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ icarealot/ dotfiles --skill unity-implementAfter installing, type/unity-implementin Claude Code to confirm it loaded.
Details
From the project READMEImplement the work described by the user in the spec or tasks.
1. Establish the boundary
unity-cliandunity-pipeline.ui-uguifor Runtime/Canvas UI orui-imguifor Editor IMGUI.- No new external package,
Packages/manifest.jsonchange, or editor-resource import such as TMP Essentials. - An opened Editor.
On a failed gate, stop and report with the required user action.
2. Implement and validate
- Call the Skill tool with
unity-tddwhere possible, at pre-agreed seams. - Run typechecking regularly, single test files regularly, and the full test suite once at the end by using
unity-pipeline. - Use
unity-clifor every non-code edit; never edit Unity YAML directly. - Use
ui-uguifor Runtime/Canvas UI andui-imguifor Editor IMGUI. - Use repository-root
.scratch/for all temporary scripts, files, logs, exports, screenshots, and command output. Remove every artifact created for this work item before reporting. - Report human playtesting, Player Build, as deferred rather than running it.
3. Report
Once done, report the results or any issues encountered.
Comments
Markdown supported