Prepare and execute Unity project work with Claude Code-style coding flows. Use when working on Unity repositories that need safe file discovery, `.meta` preservation, scene/prefab caution, asmdef-aware edits, validation checklists, or when handing Unity implementation tasks to Claude Code / ACP sessions.
Use this skill for Unity repositories where coding speed matters but asset integrity matters more.
scripts/unity-preflight.sh <repo-root> before proposing edits.references/project-discovery.md for repo scan and change targetingreferences/safe-editing-rules.md for Unity-specific guardrailsreferences/claude-code-handoff.md when preparing a Claude Code / ACP task.meta files. Never mass-delete, regenerate, or rename them casually.*.unity, *.prefab, *.asset, *.mat, and ProjectSettings/* as high-risk files.Run:
bash scripts/unity-preflight.sh /path/to/repo
Prioritize these folders in order:
Assets/** for gameplay/runtime/editor codePackages/manifest.json for package dependenciesProjectSettings/** only when project configuration changes are requiredreferences/claude-code-handoff.mdUse whichever checks fit the repo:
bash -n for helper scriptsnode --check / node --test for JS tooling around the Unity repo.meta churn and scene/prefab YAML churnreferences/project-discovery.mdreferences/safe-editing-rules.mdreferences/claude-code-handoff.mdscripts/unity-preflight.sh