[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMKMH23JZXB2CV1WS0EH4T":3,"skill-same:01M7CMKMH23JZXB2CV1WS0EH4T":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CMKMH23JZXB2CV1WS0EH4T","unity-new-project",null,"Start a new Unity 6 project: pin the editor, git and LFS, pinned UPM packages, asmdef layout.","tipoLi5890\u002Funity-dev-skills","tipoLi5890","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177803612?v=4","01M7CMD7DHGZ09CB53CRFHAA34","Li, ching yu","01M7CMD7E70K5RAHWWZVYX9YMG",2,"MIT","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-new-project\ndescription: >-\n  Start a new Unity 6 project: pin the editor, git and LFS, pinned UPM packages, asmdef layout.\n---\n\n# unity-new-project — day-one decisions for a Unity 6 project\n\n> **Everything here is cheap now and expensive later.** None of it is urgent on day one, which\n> is exactly why it gets skipped — and every item is something that, once a team and a history\n> exist, costs a migration rather than a setting.\n\n## Request → where to look\n\n| Request or symptom | Go to |\n|---|---|\n| Starting a Unity project; which editor version; render pipeline at creation | §1 |\n| A freshly created template project does not compile | §1, then [`reference\u002Fpackage-bootstrap.md`](reference\u002Fpackage-bootstrap.md) |\n| Onboarding a repo to version control: `.meta`, ignores, LFS from day one | §2, [`reference\u002Fversion-control-setup.md`](reference\u002Fversion-control-setup.md) |\n| Publishing an existing project to a git remote | [`reference\u002Fversion-control-setup.md`](reference\u002Fversion-control-setup.md) §4 |\n| Adding a UPM git dependency; pinning it to an annotated tag | §3 |\n| Mobile is even \"maybe\": IL2CPP \u002F Android baseline | §4 |\n| Installing packages; which packages a starting project needs | §4b, [`reference\u002Fpackage-selection.md`](reference\u002Fpackage-selection.md) |\n| Reviewing early project structure: asmdef module boundaries, the single input funnel, Boot scene | [`reference\u002Fproject-structure.md`](reference\u002Fproject-structure.md) |\n| Tests for pure assemblies without opening the Editor | [`reference\u002Fpure-test-lane.md`](reference\u002Fpure-test-lane.md) |\n| A scaffolder that wipes Inspector values; generated ScriptableObjects | [`reference\u002Fgenerated-assets.md`](reference\u002Fgenerated-assets.md) |\n\n## 1. Pin the editor, first commit\n\n- Record the exact editor version (e.g. `6000.0.47f1`) and install via Unity\n  Hub; `ProjectSettings\u002FProjectVersion.txt` is the SoT and is committed.\n  A teammate (or CI) on a different patch version silently reserializes\n  assets — diffs become noise and prefabs drift.\n- Decide the render pipeline (URP for mobile\u002F2.5D) at creation — swapping\n  pipelines later touches every material.\n- **Once the target platforms are known, put the editor install in the background and keep asking**\n  — `unity install \u003Cversion> --module \u003Cmodules> --yes --accept-eula` runs for minutes, none of the\n  remaining decisions depend on it, and `unity editors --installed` is the confirmation that it\n  landed before you create the project. An install that died halfway looks exactly like one still\n  running. **Both flags are what makes it backgroundable**: without them the install stops on a\n  prompt nobody is watching, and a job blocked on stdin is indistinguishable from a slow download.\n- **A template is not a working configuration.** Creating from `universal-2d` on Unity 6000.4\n  gives project-wide compile errors from the template's own stale package locks. When a *fresh*\n  project will not compile, suspect `Packages\u002Fmanifest.json` before the code —\n  `reference\u002Fpackage-bootstrap.md`.\n\n## 2. Version control (Unity's own layout fights git)\n\n- **`.meta` files ARE committed** (they carry GUIDs — a missing .meta = broken\n  references for everyone else); enable `Visible Meta Files` +\n  `Asset Serialization: Force Text`; caches (`Library\u002F` etc.) stay ignored.\n- Large binaries → **git LFS from day one** — retrofitting LFS rewrites history. Write\n  `.gitattributes` in the *first* commit, then **prove the first binary commit used it**:\n  `git lfs ls-files | wc -l` and `git show HEAD:\u003Cpath> | head -c 60` (an LFS blob starts\n  `version https:\u002F\u002Fgit-lfs.github.com\u002Fspec\u002Fv1`). `git lfs ls-files --cached` does not exist — it\n  exits with `Error: unknown flag: --cached`, which is easy to miss inside a chained command. Full\n  file, the text-YAML exception that grows (a dynamic CJK TMP font asset can grow from ~202 KB to\n  1.3–1.6 MB over a day of Editor sessions), and publishing an already-large repo to a remote:\n  `reference\u002Fversion-control-setup.md`.\n- **Keep an LFS ledger**: each binary commit states what it adds against the plan's quota, a\n  push of several hundred MB or of purchased assets waits for the person, and when agents share\n  a checkout, check `git log origin\u002Fmain..HEAD` before pushing → `reference\u002Fversion-control-setup.md` §5–§7.\n- Three hosting shapes, and the choice is the user's, not a default: **GitHub\u002FGitLab + LFS**;\n  **UVCS**, which handles large binaries natively and needs no LFS at all; or plain local `git`.\n- Push the first commit **after** packages are installed and the Editor has generated `.meta`\n  files — an initial commit of an empty project is a commit you will have to amend. If you are\n  scripting creation, that is what `--no-initial-commit` is for. **If creation already committed**\n  — a `--vcs` run without that flag publishes the bare project as commit one — add a follow-up\n  commit for the packages and `.meta` files rather than amending or re-committing the same tree\n  twice; the history is already public by then, and two initial commits are worse than one empty\n  one.\n- **Credentials go in on stdin, never in `argv`** (`--git-token-stdin`). A token expanded from an\n  environment variable is still visible in the process list and in shell history; CI must mask it\n  in logs too.\n\n## 3. UPM git dependencies — the pinning iron law\n\nAdd private packages by git URL **pinned to an annotated tag**, never a\nbranch:\n\n```\n\"com.\u003Cvendor>.\u003Cpkg>\": \"https:\u002F\u002Fgithub.com\u002F\u003Corg>\u002F\u003Crepo>.git?path=unity-package#vX.Y.Z\"\n```\n\nTracking `master` means builds change under you; a pinned tag makes every\nupgrade a deliberate ref bump. Keep NDK\u002FAGP versions aligned with what the\nnative packages were built against — don't bump blindly, and expect a native\nSDK to pin those deliberately rather than take automated dependency bumps.\nNote the `?path=` form when the package lives in a subfolder — the usual\nshape for a native SDK, whose Unity package sits one folder inside the repo\nthat also carries the native sources.\n\nThree consequences of it being a *git* URL:\n\n- **Credentials, not Unity, decide whether it resolves.** A machine can reach a private dependency\n  non-interactively over https (an osxkeychain helper, say) and **not over SSH**. Run\n  `git ls-remote \u003Cthat exact URL>` before the installer on any new machine or CI box; without it\n  the project simply fails to compile, and the symptom you actually see is \"no test results file\",\n  not a package error.\n- **`manifest.json` is the request; `packages-lock.json` is what you compiled.** The lockfile\n  carries the resolved commit `hash` — check it against the tag, and check\n  `Library\u002FPackageCache` for the directory that was really unpacked.\n- **A tag bump touches three places together**: the version constant in your installer script,\n  `manifest.json`, and `packages-lock.json`.\n\n## 4. Android\u002FIL2CPP baseline (if mobile is even \"maybe\")\n\nSet in Player Settings on day one: **IL2CPP + ARM64**, minSdk to what your\nplugins demand now, and a real package name (`com.\u003Corg>.\u003Capp>` — renaming\nlater touches keystore\u002Fstore identity, same trap as Flutter's `--org`).\nBuild\u002Frelease mechanics: `unity-android-release`.\n\n> **The minSdk you ask for is not necessarily the minSdk you ship.** Unity\n> 6000.4 clamps minSdk up to its own floor of 25: ask for 23 and you get `AndroidApiLevel25`\n> back, so the build ships **minSdk 25** whatever the plugin's documented floor says. Treat a\n> plugin's number as a lower bound, not the answer: set it in the setup method below, read\n> `PlayerSettings.Android.minSdkVersion` back, and ship *that* value — it is the one for the\n> release notes. Check the floor on your own editor version (26 from 6000.5).\n\nPut these in a re-runnable `[MenuItem]` + `-executeMethod` method rather than clicking them,\nand set `EditorSettings.serializationMode = ForceText` and\n`VersionControlSettings.mode = \"Visible Meta Files\"` in the same method — §2 depends on both,\nand both vanish when someone recreates the project from a template.\n→ `reference\u002Fgenerated-assets.md`\n\n## 4b. Packages: install them through the API, never by hand\n\nInstall only what the concept actually needs, prefer what the template already ships (a URP\ntemplate already has the render pipeline and Input System), and **do not pin a version** unless\nthere is a stated minimum. Concept → need → id, and the subtraction step that shrinks the list:\n[`reference\u002Fpackage-selection.md`](reference\u002Fpackage-selection.md). Two rules that decide whether\nit works at all:\n\n- **Never edit `Packages\u002Fmanifest.json` by hand**, and never guess an id. List it with\n  `Client.SearchAll()` — one call is cheaper than one wrong guess. The single exception is the\n  template whose own locks do not compile (§1): there you replace the manifest wholesale with a\n  set known good on *this* editor version, reopen the Editor, and let UPM rewrite the lockfile.\n- A headless install that returns exit 0 and installs nothing is the normal failure mode, not an\n  unusual one. → `reference\u002Fpackage-bootstrap.md`\n\nIf you are driving this as a guided flow, **start the editor install in the background while you\nare still asking the concept questions**, then join on `unity editors --installed --format json`\nbefore doing anything downstream. Parallelism only pays when there is conversation to overlap it\nwith — with nothing left to ask, just wait.\n\n> **Ask one step at a time, and the concept interview is not this skill's.** What the game is\n> belongs to `unity-game-brief`; what arrives here is a settled proposal. Even for the questions\n> this skill does own — target platforms, hosting shape, editor version — put one on the table,\n> wait for the answer, then move: platform and monetisation answers change which modules install\n> and which packages go in the list, so a batch of questions collected up front produces a setup\n> that has to be redone. Nothing is scaffolded before those answers exist.\n\n## 5. Structure that survives growth → `reference\u002Fproject-structure.md`\n\nasmdef per module, a `noEngineReferences` assembly and its pure test lane, injected clock and\nseed, one input funnel, a Boot scene, the art pipeline, generated assets as build output.\n\n## Scope — what this skill does NOT do\n\nThis skill owns the **decisions**; the `unity` commands that execute them are `unity-cli`.\n\n**No gameplay scaffolding.** A generic genre skeleton produces throwaway mock primitives that\nhave to be deleted before real work starts, so this skill stops at a clean, correctly-configured\nproject. Building the actual game is every other skill in this plugin.\n\nWhat the game *is* — the brief, the constraints, the architecture proposal, the first interaction —\nis `unity-game-brief`; this skill starts when that proposal names the assemblies.\n\nAlso not here: which packages a given genre needs beyond the starting point in §4b and\n`reference\u002Fpackage-selection.md` — that table is something to subtract from once the concept is\nknown, never a list to install whole. Nor anything about shipping — `unity-android-release`,\n`unity-web-release`.\n\nNor the font pipeline: this skill owns only the version-control consequence that TMP font assets\nlive in the text (non-LFS) half of the repo and grow there. Atlases, fallback chains and\nlocales are `unity-localization`.\n\n## Related skills\n\nThe terminal: `unity-cli`. Verifying a change: `unity-debug`.\n\nGameplay: `unity-gameplay` (routes by perspective).\n3C: `unity-input` · `unity-camera` · `unity-animation`.\n2D runtime: `unity-2d-controller` · `unity-physics-2d` · `unity-2d-rendering` ·\n`unity-2d-level` · `unity-2d-grid` · `unity-2d-animation`.\nUI: `unity-game-ui` (routes) → `unity-ui-ugui` · `unity-ui-toolkit`.\nAssets: `unity-3d-models` · `unity-2d-sprites` · `unity-rigged-character`.\nRuntime domains: `unity-physics-3d` · `unity-navigation` · `unity-render-urp` ·\n`unity-audio` · `unity-localization`.\nShipping: `unity-android-release` · `unity-web-release`.\nBackend & commerce: `unity-live-services` (routes) → `unity-ugs` ·\n`unity-multiplayer-services` · `unity-vivox` · `unity-iap` · `unity-ads-levelplay`.\n\nConsistent AI art: `codex-visual`.\n","# unity-new-project — day-one decisions for a Unity 6 project\n\n> **Everything here is cheap now and expensive later.** None of it is urgent on day one, which\n> is exactly why it gets skipped — and every item is something that, once a team and a history\n> exist, costs a migration rather than a setting.\n\n## Request → where to look\n\n| Request or symptom | Go to |\n|---|---|\n| Starting a Unity project; which editor version; render pipeline at creation | §1 |\n| A freshly created template project does not compile | §1, then [`reference\u002Fpackage-bootstrap.md`](reference\u002Fpackage-bootstrap.md) |\n| Onboarding a repo to version control: `.meta`, ignores, LFS from day one | §2, [`reference\u002Fversion-control-setup.md`](reference\u002Fversion-control-setup.md) |\n| Publishing an existing project to a git remote | [`reference\u002Fversion-control-setup.md`](reference\u002Fversion-control-setup.md) §4 |\n| Adding a UPM git dependency; pinning it to an annotated tag | §3 |\n| Mobile is even \"maybe\": IL2CPP \u002F Android baseline | §4 |\n| Installing packages; which packages a starting project needs | §4b, [`reference\u002Fpackage-selection.md`](reference\u002Fpackage-selection.md) |\n| Reviewing early project structure: asmdef module boundaries, the single input funnel, Boot scene | [`reference\u002Fproject-structure.md`](reference\u002Fproject-structure.md) |\n| Tests for pure assemblies without opening the Editor | [`reference\u002Fpure-test-lane.md`](reference\u002Fpure-test-lane.md) |\n| A scaffolder that wipes Inspector values; generated ScriptableObjects | [`reference\u002Fgenerated-assets.md`](reference\u002Fgenerated-assets.md) |\n\n## 1. Pin the editor, first commit\n\n- Record the exact editor version (e.g. `6000.0.47f1`) and install via Unity\n  Hub; `ProjectSettings\u002FProjectVersion.txt` is the SoT and is committed.\n  A teammate (or CI) on a different patch version silently reserializes\n  assets — diffs become noise and prefabs drift.\n- Decide the render pipeline (URP for mobile\u002F2.5D) at creation — swapping\n  pipelines later touches every material.\n- **Once the target platforms are known, put the editor install in the background and keep asking**\n  — `unity install \u003Cversion> --module \u003Cmodules> --yes --accept-eula` runs for minutes, none of the\n  remaining decisions depend on it, and `unity editors --installed` is the confirmation that it\n  landed before you create the project. An install that died halfway looks exactly like one still\n  running. **Both flags are what makes it backgroundable**: without them the install stops on a\n  prompt nobody is watching, and a job blocked on stdin is indistinguishable from a slow download.\n- **A template is not a working configuration.** Creating from `universal-2d` on Unity 6000.4\n  gives project-wide compile errors from the template's own stale package locks. When a *fresh*\n  project will not compile, suspect `Packages\u002Fmanifest.json` before the code —\n  `reference\u002Fpackage-bootstrap.md`.\n\n## 2. Version control (Unity's own layout fights git)\n\n- **`.meta` files ARE committed** (they carry GUIDs — a missing .meta = broken\n  references for everyone else); enable `Visible Meta Files` +\n  `Asset Serialization: Force Text`; caches (`Library\u002F` etc.) stay ignored.\n- Large binaries → **git LFS from day one** — retrofitting LFS rewrites history. Write\n  `.gitattributes` in the *first* commit, then **prove the first binary commit used it**:\n  `git lfs ls-files | wc -l` and `git show HEAD:\u003Cpath> | head -c 60` (an LFS blob starts\n  `version https:\u002F\u002Fgit-lfs.github.com\u002Fspec\u002Fv1`). `git lfs ls-files --cached` does not exist — it\n  exits with `Error: unknown flag: --cached`, which is easy to miss inside a chained command. Full\n  file, the text-YAML exception that grows (a dynamic CJK TMP font asset can grow from ~202 KB to\n  1.3–1.6 MB over a day of Editor sessions), and publishing an already-large repo to a remote:\n  `reference\u002Fversion-control-setup.md`.\n- **Keep an LFS ledger**: each binary commit states what it adds against the plan's quota, a\n  push of several hundred MB or of purchased assets waits for the person, and when agents share\n  a checkout, check `git log origin\u002Fmain..HEAD` before pushing → `reference\u002Fversion-control-setup.md` §5–§7.\n- Three hosting shapes, and the choice is the user's, not a default: **GitHub\u002FGitLab + LFS**;\n  **UVCS**, which handles large binaries natively and needs no LFS at all; or plain local `git`.\n- Push the first commit **after** packages are installed and the Editor has generated `.meta`\n  files — an initial commit of an empty project is a commit you will have to amend. If you are\n  scripting creation, that is what `--no-initial-commit` is for. **If creation already committed**\n  — a `--vcs` run without that flag publishes the bare project as commit one — add a follow-up\n  commit for the packages and `.meta` files rather than amending or re-committing the same tree\n  twice; the history is already public by then, and two initial commits are worse than one empty\n  one.\n- **Credentials go in on stdin, never in `argv`** (`--git-token-stdin`). A token expanded from an\n  environment variable is still visible in the process list and in shell history; CI must mask it\n  in logs too.\n\n## 3. UPM git dependencies — the pinning iron law\n\nAdd private packages by git URL **pinned to an annotated tag**, never a\nbranch:\n\n```\n\"com.\u003Cvendor>.\u003Cpkg>\": \"https:\u002F\u002Fgithub.com\u002F\u003Corg>\u002F\u003Crepo>.git?path=unity-package#vX.Y.Z\"\n```\n\nTracking `master` means builds change under you; a pinned tag makes every\nupgrade a deliberate ref bump. Keep NDK\u002FAGP versions aligned with what the\nnative packages were built against — don't bump blindly, and expect a native\nSDK to pin those deliberately rather than take automated dependency bumps.\nNote the `?path=` form when the package lives in a subfolder — the usual\nshape for a native SDK, whose Unity package sits one folder inside the repo\nthat also carries the native sources.\n\nThree consequences of it being a *git* URL:\n\n- **Credentials, not Unity, decide whether it resolves.** A machine can reach a private dependency\n  non-interactively over https (an osxkeychain helper, say) and **not over SSH**. Run\n  `git ls-remote \u003Cthat exact URL>` before the installer on any new machine or CI box; without it\n  the project simply fails to compile, and the symptom you actually see is \"no test results file\",\n  not a package error.\n- **`manifest.json` is the request; `packages-lock.json` is what you compiled.** The lockfile\n  carries the resolved commit `hash` — check it against the tag, and check\n  `Library\u002FPackageCache` for the directory that was really unpacked.\n- **A tag bump touches three places together**: the version constant in your installer script,\n  `manifest.json`, and `packages-lock.json`.\n\n## 4. Android\u002FIL2CPP baseline (if mobile is even \"maybe\")\n\nSet in Player Settings on day one: **IL2CPP + ARM64**, minSdk to what your\nplugins demand now, and a real package name (`com.\u003Corg>.\u003Capp>` — renaming\nlater touches keystore\u002Fstore identity, same trap as Flutter's `--org`).\nBuild\u002Frelease mechanics: `unity-android-release`.\n\n> **The minSdk you ask for is not necessarily the minSdk you ship.** Unity\n> 6000.4 clamps minSdk up to its own floor of 25: ask for 23 and you get `AndroidApiLevel25`\n> back, so the build ships **minSdk 25** whatever the plugin's documented floor says. Treat a\n> plugin's number as a lower bound, not the answer: set it in the setup method below, read\n> `PlayerSettings.Android.minSdkVersion` back, and ship *that* value — it is the one for the\n> release notes. Check the floor on your own editor version (26 from 6000.5).\n\nPut these in a re-runnable `[MenuItem]` + `-executeMethod` method rather than clicking them,\nand set `EditorSettings.serializationMode = ForceText` and\n`VersionControlSettings.mode = \"Visible Meta Files\"` in the same method — §2 depends on both,\nand both vanish when someone recreates the project from a template.\n→ `reference\u002Fgenerated-assets.md`\n\n## 4b. Packages: install them through the API, never by hand\n\nInstall only what the concept actually needs, prefer what the template already ships (a URP\ntemplate already has the render pipeline and Input System), and **do not pin a version** unless\nthere is a stated minimum. Concept → need → id, and the subtraction step that shrinks the list:\n[`reference\u002Fpackage-selection.md`](reference\u002Fpackage-selection.md). Two rules that decide whether\nit works at all:\n\n- **Never edit `Packages\u002Fmanifest.json` by hand**, and never guess an id. List it with\n  `Client.SearchAll()` — one call is cheaper than one wrong guess. The single exception is the\n  template whose own locks do not compile (§1): there you replace the manifest wholesale with a\n  set known good on *this* editor version, reopen the Editor, and let UPM rewrite the lockfile.\n- A headless install that returns exit 0 and installs nothing is the normal failure mode, not an\n  unusual one. → `reference\u002Fpackage-bootstrap.md`\n\nIf you are driving this as a guided flow, **start the editor install in the background while you\nare still asking the concept questions**, then join on `unity editors --installed --format json`\nbefore doing anything downstream. Parallelism only pays when there is conversation to overlap it\nwith — with nothing left to ask, just wait.\n\n> **Ask one step at a time, and the concept interview is not this skill's.** What the game is\n> belongs to `unity-game-brief`; what arrives here is a settled proposal. Even for the questions\n> this skill does own — target platforms, hosting shape, editor version — put one on the table,\n> wait for the answer, then move: platform and monetisation answers change which modules install\n> and which packages go in the list, so a batch of questions collected up front produces a setup\n> that has to be redone. Nothing is scaffolded before those answers exist.\n\n## 5. Structure that survives growth → `reference\u002Fproject-structure.md`\n\nasmdef per module, a `noEngineReferences` assembly and its pure test lane, injected clock and\nseed, one input funnel, a Boot scene, the art pipeline, generated assets as build output.\n\n## Scope — what this skill does NOT do\n\nThis skill owns the **decisions**; the `unity` commands that execute them are `unity-cli`.\n\n**No gameplay scaffolding.** A generic genre skeleton produces throwaway mock primitives that\nhave to be deleted before real work starts, so this skill stops at a clean, correctly-configured\nproject. Building the actual game is every other skill in this plugin.\n\nWhat the game *is* — the brief, the constraints, the architecture proposal, the first interaction —\nis `unity-game-brief`; this skill starts when that proposal names the assemblies.\n\nAlso not here: which packages a given genre needs beyond the starting point in §4b and\n`reference\u002Fpackage-selection.md` — that table is something to subtract from once the concept is\nknown, never a list to install whole. Nor anything about shipping — `unity-android-release`,\n`unity-web-release`.\n\nNor the font pipeline: this skill owns only the version-control consequence that TMP font assets\nlive in the text (non-LFS) half of the repo and grow there. Atlases, fallback chains and\nlocales are `unity-localization`.\n\n## Related skills\n\nThe terminal: `unity-cli`. Verifying a change: `unity-debug`.\n\nGameplay: `unity-gameplay` (routes by perspective).\n3C: `unity-input` · `unity-camera` · `unity-animation`.\n2D runtime: `unity-2d-controller` · `unity-physics-2d` · `unity-2d-rendering` ·\n`unity-2d-level` · `unity-2d-grid` · `unity-2d-animation`.\nUI: `unity-game-ui` (routes) → `unity-ui-ugui` · `unity-ui-toolkit`.\nAssets: `unity-3d-models` · `unity-2d-sprites` · `unity-rigged-character`.\nRuntime domains: `unity-physics-3d` · `unity-navigation` · `unity-render-urp` ·\n`unity-audio` · `unity-localization`.\nShipping: `unity-android-release` · `unity-web-release`.\nBackend & commerce: `unity-live-services` (routes) → `unity-ugs` ·\n`unity-multiplayer-services` · `unity-vivox` · `unity-iap` · `unity-ads-levelplay`.\n\nConsistent AI art: `codex-visual`.\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-new-project",0,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills","https:\u002F\u002Fgithub.com\u002FtipoLi5890","https:\u002F\u002Ftipoli5890.github.io\u002F","2026-11-10 09:16:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tipoLi5890\u002Funity-dev-skills --skill unity-new-project",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-new-project",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-new-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002FSKILL.md",true,[46,52,56,60,64,68,72],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fgenerated-assets.md","REFERENCE","参考文档",5080,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fgenerated-assets.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fpackage-bootstrap.md",12669,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fpackage-bootstrap.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fpackage-selection.md",8750,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fpackage-selection.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fproject-structure.md",3292,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fproject-structure.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"reference\u002Fpure-test-lane.md",4416,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fpure-test-lane.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"reference\u002Fversion-control-setup.md",8539,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Freference\u002Fversion-control-setup.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fpure_tests.py","SCRIPT","脚本",27173,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-new-project\u002Fscripts\u002Fpure_tests.py",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CMNYXQNW14ST64EYEEZ5V5","unity-web-release","Ship a WebGL\u002FWebGPU build: shrink the download, Brotli server headers, Safari and iPhone memory.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-web-release\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CMNTHD1EA70CCJ2F9FN3HT","unity-vivox","Vivox voice and text chat: channels, positional voice, mute and push-to-talk, mic permission.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-vivox\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CMNPHPRQZ7K1FES2953DRQ","unity-urp-migration","Migrate a Built-in project to URP, or fix a half-moved one: pink materials, PPv2, old shaders.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-urp-migration\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CMNJ756DK4V0D50HMAZYQW","unity-ui-ugui","Canvas UI (uGUI): CanvasScaler, RectTransform anchors, Layout Groups, ScrollView, UI built from C#.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-ugui\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CMNDESZN79EK5FRDXCA2WA","unity-ui-toolkit","UI Toolkit (UXML, USS, UIDocument): flex layout, binding, custom elements, editor windows.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ui-toolkit\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7CMN8GBV07K0YCY07BJ6A1W","unity-ugs","Unity Gaming Services API: which package, init and sign-in order, Cloud Save, Cloud Code, Remote Config.","https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-ugs\u002FSKILL.md",[],[]]