dotfiles

Use when interacting with a running Unity Editor instance — sending commands, checking editor connection status, installing the Pipeline package, or evaluating C# expressions in the editor.

Use when installing, uninstalling, or upgrading Unity editors, adding or listing modules, or browsing available Unity releases.

Use for general Unity CLI operations — list or open projects, list installed editors, read CLI logs, or any other Unity CLI task not covered by a more specific skill (unity-cli-install, unity-cli-build, unity-cli-pipeline).

Use when creating or editing Unity Shader Graph assets programmatically (Unity 6.5+) — authoring custom nodes from HLSL via the Shader Function Reflection API, generating .shadergraph files, or wiring nodes by editing the graph JSON.

Use when reading the Unity Editor Console (log/warning/error entries) or detecting compile errors (C#/Burst, shader, compute shader) from a connected editor via the Pipeline package.

Use when creating a new minimal Unity project.

Operational style guide for Jujutsu (jj) VCS. Use when working with version control in a project that has a .jj directory.

Shader coding style for Unity projects. Use when writing or editing Unity shader (.shader, .hlsl) files.

Use when building, running headless, or running tests for a Unity project from the command line.

Capture a specific Unity Editor window (including floating windows) as an image, resize it for token efficiency, and visually evaluate it. Use when asked to check, verify, or diagnose the visual state of any Unity Editor window.

C# coding style for Unity projects. Use when writing or editing C# (.cs) files in a Unity project.

Migrate an existing Unity UPM package repository to the newer release workflow used for Unity 6.3 signing support. Use when a repository lacks the new root/package `CHANGELOG.md` copies, needs `package.json` field cleanup such as `changelogUrl` and `_upm.changelog`, or still contains obsolete GitHub Actions release automation.

Maintain and release a Unity UPM package repository that follows the `Packages/jp.keijiro.*` layout. Use when updating the `Unreleased` section in `CHANGELOG.md`, preparing a new package release, generating `package.json` `_upm.changelog` metadata, syncing root/package documentation files, packing a signed tarball with `upm`, creating a GitHub release, or checking release readiness. Keep npm publishing as a manual user step.