unity-skill-package-setuplisted
Install: claude install-skill Xenoneqq/unity-ai-skills
# Unity skill package setup
Run once per project. Everything it writes lives in the user's Unity repo, so **nothing here
happens without asking** — you are creating tracked files and a folder layout the whole team
inherits.
Safe to re-run: every step checks what is already there and adds only what is missing.
| File | Read it when |
|---|---|
| `references/git-hygiene.md` | Checking `.gitignore` and scene merging (Step 3). |
| `references/folder-scaffold.md` | Creating the asset folders (Step 6). |
| `references/first-run-scan.md` | Reading what the project already is (Step 7). |
| `references/project-memory.md` | Writing `CLAUDE.md` and `AGENTS.md` (Step 9). |
## 1. Find the project and see what already exists
```bash
PV=$(find . -path '*/ProjectSettings/ProjectVersion.txt' -not -path '*/Library/*' -print -quit)
ROOT=$(dirname "$(dirname "$PV")") # the Unity project
REPO=$(git rev-parse --show-toplevel) # the repo — often one level up
echo "unity project: $ROOT"
echo "repo root : $REPO"
ls "$REPO/CLAUDE.md" "$REPO/AGENTS.md" "$REPO/STRUCTURE.md" "$REPO/.claude/settings.json" 2>/dev/null
ls -d "$ROOT/Assets"/*/ 2>/dev/null
```
`CLAUDE.md`, `AGENTS.md` and `STRUCTURE.md` go at the **repo root**, not the Unity project root,
because that is where Claude Code reads them. They often differ — a Unity project frequently sits
one directory down.
**If any of those files already exist, read them before writing anything.** Never overwrite a
file someone wrote