[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMMA8EEE3CZ7D57BTSWQWQ":3,"skill-same:01M7CMMA8EEE3CZ7D57BTSWQWQ":90},{"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},"01M7CMMA8EEE3CZ7D57BTSWQWQ","unity-render-urp",null,"URP rendering: post-processing that won't show, Volume profiles and grades, Render Graph features.","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-render-urp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-render-urp\ndescription: >-\n  URP rendering: post-processing that won't show, Volume profiles and grades, Render Graph features.\n---\n\n# unity-render-urp — make it appear, then make it affordable\n\n> **\"I set the value and nothing happened\" is almost never the value.** URP post-processing has\n> five independent switches between a Volume and a pixel, four of them default to off or to a\n> narrow default, and none of them warns. Run the pre-flight before touching a parameter.\n\n## Symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| Added bloom, tonemapping or vignette and nothing happened | §1 pre-flight, in order |\n| Want the pre-flight as one paste-in call against a live Editor | [`reference\u002Fpreflight-snippet.md`](reference\u002Fpreflight-snippet.md) |\n| Is URP actually active? A URP asset is right there, but editing it changes nothing | §1 step 1 — it may be a dormant asset |\n| Works in Scene view, not in Game view | §1 — Scene view has its own post-processing toggle |\n| Code compiles against `PostProcessVolume` \u002F `GetSetting\u003CT>` \u002F `ColorGrading`; \"ColorGrading or ColorAdjustments?\" | [`reference\u002Fapi-renames.md`](reference\u002Fapi-renames.md) — those are the old stack |\n| Need a Volume parameter's real default, type or range | [`reference\u002Feffect-reference.md`](reference\u002Feffect-reference.md) |\n| A value \"does not take\" on an override | [`reference\u002Fapi-renames.md`](reference\u002Fapi-renames.md), then the parameter's range — a `Clamped*Parameter` clamps silently |\n| Scripting a profile, a Global Volume or a runtime grade tween | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) |\n| Want a grade to start from rather than a blank profile | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) — four presets |\n| Effect appears, costs too much on device; which effects a mobile build can afford | §3 |\n| Effect is suspected of costing too much, and no number says so | §3, then a before\u002Fafter frame-time window — `unity-profiling` |\n| \"Review my renderer feature\" — a Render Graph `ScriptableRendererFeature` | §4 |\n| Turning an HLSL function into a Shader Graph node | §5 |\n| A script-made material changes again after it was saved; an emissive lost its glow; every rebuild leaves a `.mat` diff | [`reference\u002Fmaterial-validation.md`](reference\u002Fmaterial-validation.md) |\n| A see-through fence or mesh shimmers or vanishes at distance; fog missing only in the player | [`reference\u002Fmaterial-validation.md`](reference\u002Fmaterial-validation.md) §3–4 |\n| A grade per level or venue, and bloom only on the high tier | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) — per venue, per tier |\n| Moving a built-in project to URP; everything went magenta; converting an old `PostProcessVolume` to a URP Volume | `unity-urp-migration` |\n\n## 1. Pre-flight — five checks, in this order\n\nStop at the first failure; fix it before checking the next.\n\n1. **URP is the active render pipeline — resolve it, do not infer it from the files.** A URP\n   asset sitting in `Assets\u002FSettings\u002F` is not a pipeline in force; it is inert until\n   `ProjectSettings\u002FGraphicsSettings.asset` or a quality tier points at it. Read the guid out of\n   `m_CustomRenderPipeline`, find the `.meta` that declares that guid, and count\n   `renderPipeline: {fileID: 11400000` in `QualitySettings.asset` to see whether a tier\n   overrides it:\n\n   ```bash\n   grep -m1 'm_CustomRenderPipeline:' ProjectSettings\u002FGraphicsSettings.asset\n   grep -c 'renderPipeline: {fileID: 11400000' ProjectSettings\u002FQualitySettings.asset\n   ```\n\n   `{fileID: 0}` with zero tier overrides means **built-in renderer** and nothing below applies —\n   a project created from a URP template can render on built-in this way, its URP assets\n   dormant. Resolve this first: it turns \"I set it and nothing happened\" into a one-minute\n   answer. Full resolver, the per-platform quality-tier mapping and the renderer-asset indirection:\n   → `reference\u002Fresolve-active-pipeline.md`.\n\n2. **HDR is enabled on the URP Asset.** Tonemapping requires it. Bloom still functions in SDR but\n   its `threshold` must be below 1 or it has nothing to select.\n3. **The camera's `renderPostProcessing` is true — it defaults to `false`.** And the renderer's\n   **PostProcessData asset must not be null**: null means the post-process pass does not exist at\n   all. With camera stacking, only the Base camera (or the last Overlay in the stack) should have\n   it on.\n4. **The Volume's GameObject layer is inside the camera's `volumeLayerMask`.** That mask defaults\n   to layer 0 (`Default`) only — a Volume parked on any other layer is invisible to the camera.\n\n> **A freshly added `UniversalAdditionalCameraData` reports** `renderPostProcessing=False`,\n> `volumeLayerMask=1` (bitmask 1 = layer 0 only), `renderType=Base`, `antialiasing=None`.\n> Re-check on your version in one call:\n>\n> ```csharp\n> var d = go.AddComponent\u003CUnityEngine.Rendering.Universal.UniversalAdditionalCameraData>();\n> return d.renderPostProcessing + \" \" + d.volumeLayerMask.value + \" \" + d.renderType;\n> ```\n5. **The Volume is enabled, has a profile, and at least one override has\n   `overrideState = true`.**\n\n> **Forgetting `overrideState` is the number one scripting error here.** The Volume system skips\n> any parameter whose `overrideState` is false, so a correctly-configured component contributes\n> nothing. `profile.Add\u003CT>(true)` turns them all on for that component.\n\nThen: are you looking at the **Game view**? Scene view has an independent post-processing toggle,\nand the camera's `renderType` must be `Base`, not `Overlay`.\n\nAll five as **one read-only `eval` block** that returns a numbered report — the fastest way to\nturn \"nothing happened\" into a line you can act on:\n→ [`reference\u002Fpreflight-snippet.md`](reference\u002Fpreflight-snippet.md).\n\n## 2. The API renamed almost everything → `reference\u002Fapi-renames.md`\n\n`PostProcessVolume`, `GetSetting\u003CT>` and `ColorGrading` are the old stack; the URP Volume names,\n`TryGet\u003CT>`, `ColorAdjustments`, and the override flag that a set value needs.\n\n## 3. What a mobile frame can afford\n\nKeep: `Tonemapping` (`Neutral`), a small `ColorAdjustments` exposure\u002Fcontrast trim, and a\nrestrained `Bloom` (`threshold` 1.0, `intensity` ~0.3, `downscale = Quarter`,\n`highQualityFiltering = false`, `maxIterations` reduced from the default 6).\n\nThat keep-list assumes HDR is still on (§1 step 2): Tonemapping needs it, and a `threshold` of 1.0\nselects nothing in a clamped SDR buffer. A project that turns HDR off to save mobile bandwidth\ndrops Tonemapping and puts the Bloom threshold below 1 — otherwise both silently do nothing.\n\nAvoid on mobile: **FilmGrain, MotionBlur, DepthOfField.** Each is full-screen and each buys\natmosphere rather than legibility.\n\n**Read a parameter's legal range off the component, never from memory** — several are not what\nthey look like: `Vignette.smoothness` is **0.01–1**, so a zero reads back as 0.01;\n`MotionBlur.clamp` is **0–0.2** with a 0.05 default; `Bloom.maxIterations` is **2–8** with a\ndefault of 6, so \"reduced from 6\" has a floor of 2. The Volume inspector shows the range, `eval`\non the type shows it, and the full table is\n→ [`reference\u002Feffect-reference.md`](reference\u002Feffect-reference.md).\n\nA mobile grade written out as values, beside three other presets:\n→ [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md).\n\n## 4. Reviewing a Render Graph renderer feature\n\n→ [`reference\u002Frender-graph-review.md`](reference\u002Frender-graph-review.md) — an eight-point\nchecklist and a fixed output shape that keeps **confirmed defects separate from suspicions**,\nplus the two corrected snippets that carry most of the checklist: a descriptor derived from\n`resourceData.activeColorTexture.GetDescriptor(renderGraph)` with only the two fields that must\ndiffer touched, and a `PassData` whose every field is assigned on every recording.\n\n## 5. Reflected Shader Graph custom nodes\n\nAn HLSL function preceded by `UNITY_EXPORT_REFLECTION` and tagged with four `funchints` becomes a\nnode in the graph's search. It is metadata, not shader authoring, and **every way of getting the\nmetadata wrong is silent** — the file compiles and no node appears.\n\n> **The feature needs `com.unity.shadergraph` 17.5 or newer; on 17.4 it is absent.** Check the\n> installed version, and the package itself, before writing anything — both checks are the version\n> gate in `reference\u002Fshader-graph-custom-node.md`. Below the floor, say so and stop.\n\nThe four required function hints, every parameter hint, where the file goes and why an existing\n`ShaderInclude` needs agreement before you append to it:\n→ [`reference\u002Fshader-graph-custom-node.md`](reference\u002Fshader-graph-custom-node.md). Every legal\ntag combination in one compilable file:\n→ [`resources\u002FShaderGraphHints.hlsl`](resources\u002FShaderGraphHints.hlsl).\n\n## 6. Verify\n\nPost-processing is the area where \"I set it\" and \"it is on screen\" diverge most often, and every\nstep of §1 fails silently.\n\n- **Look at the Game view**, at a screenshot you actually read (`unity-debug`) — not at the\n  inspector, and not at the Scene view, which has its own post-processing toggle.\n- **Read the value back off the component**, not off the code you just ran. `overrideState` is\n  the specific one to re-read.\n- **Report before\u002Fafter** in the six-line shape at the end of\n  [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md): which pipeline asset resolved\n  as active, which Volume, profile and overrides, the camera's `renderPostProcessing`. \"Added\n  bloom\" is not a result.\n- On mobile, take a frame-time number before and after — the same situation, the same run mode,\n  windows either side of the change (`unity-profiling`). Post-processing is full-screen work and\n  the cost is not proportional to how much you can see.\n\n## Scope — what this skill does NOT do\n\n**Shader authoring stays out** — writing the lighting maths, hand-building a graph, debugging\nwhat a fragment computes. The one exception is §5: **reflected Shader Graph custom nodes are in\nscope**, because a reflected node is an HLSL function plus four metadata tags, and every failure\nmode is a metadata failure rather than a shading one. Ask this skill to *make a function into a\nnode*; do not ask it what the function should compute.\n\n**Migrating a built-in project to URP stays out** — the phased conversion of materials,\npost-processing, lighting and quality tiers, and diagnosing one that was half-moved (magenta\nmaterials, an old `PostProcessVolume` still wired up, a stale bake, `GrabPass` and\n`OnRenderImage` code) is `unity-urp-migration`. This skill assumes the project already renders\nwith URP and asks why an effect will not appear on it.\n\n**HDRP stays out.** It is a different pipeline with different Volume components, different\nrenderer plumbing and different numbers; nothing here transfers. **Lighting and GI set-up**\n— light modes, the bake, probes, shadows, sky and fog — is `unity-lighting`.\n\nWhether the pipeline in force is even URP is §1 and\n[`reference\u002Fresolve-active-pipeline.md`](reference\u002Fresolve-active-pipeline.md); a project that\ncame from a URP template can be rendering built-in. Confirming that a change is visible on screen\nis `unity-debug`. **Measuring what an effect costs stays out too** — counters, frame-time windows\nand the before\u002Fafter table are `unity-profiling`; §3 tells you what to suspect, that skill tells\nyou what it actually cost.\n","# unity-render-urp — make it appear, then make it affordable\n\n> **\"I set the value and nothing happened\" is almost never the value.** URP post-processing has\n> five independent switches between a Volume and a pixel, four of them default to off or to a\n> narrow default, and none of them warns. Run the pre-flight before touching a parameter.\n\n## Symptom → where to look\n\n| Symptom | Go to |\n|---|---|\n| Added bloom, tonemapping or vignette and nothing happened | §1 pre-flight, in order |\n| Want the pre-flight as one paste-in call against a live Editor | [`reference\u002Fpreflight-snippet.md`](reference\u002Fpreflight-snippet.md) |\n| Is URP actually active? A URP asset is right there, but editing it changes nothing | §1 step 1 — it may be a dormant asset |\n| Works in Scene view, not in Game view | §1 — Scene view has its own post-processing toggle |\n| Code compiles against `PostProcessVolume` \u002F `GetSetting\u003CT>` \u002F `ColorGrading`; \"ColorGrading or ColorAdjustments?\" | [`reference\u002Fapi-renames.md`](reference\u002Fapi-renames.md) — those are the old stack |\n| Need a Volume parameter's real default, type or range | [`reference\u002Feffect-reference.md`](reference\u002Feffect-reference.md) |\n| A value \"does not take\" on an override | [`reference\u002Fapi-renames.md`](reference\u002Fapi-renames.md), then the parameter's range — a `Clamped*Parameter` clamps silently |\n| Scripting a profile, a Global Volume or a runtime grade tween | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) |\n| Want a grade to start from rather than a blank profile | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) — four presets |\n| Effect appears, costs too much on device; which effects a mobile build can afford | §3 |\n| Effect is suspected of costing too much, and no number says so | §3, then a before\u002Fafter frame-time window — `unity-profiling` |\n| \"Review my renderer feature\" — a Render Graph `ScriptableRendererFeature` | §4 |\n| Turning an HLSL function into a Shader Graph node | §5 |\n| A script-made material changes again after it was saved; an emissive lost its glow; every rebuild leaves a `.mat` diff | [`reference\u002Fmaterial-validation.md`](reference\u002Fmaterial-validation.md) |\n| A see-through fence or mesh shimmers or vanishes at distance; fog missing only in the player | [`reference\u002Fmaterial-validation.md`](reference\u002Fmaterial-validation.md) §3–4 |\n| A grade per level or venue, and bloom only on the high tier | [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md) — per venue, per tier |\n| Moving a built-in project to URP; everything went magenta; converting an old `PostProcessVolume` to a URP Volume | `unity-urp-migration` |\n\n## 1. Pre-flight — five checks, in this order\n\nStop at the first failure; fix it before checking the next.\n\n1. **URP is the active render pipeline — resolve it, do not infer it from the files.** A URP\n   asset sitting in `Assets\u002FSettings\u002F` is not a pipeline in force; it is inert until\n   `ProjectSettings\u002FGraphicsSettings.asset` or a quality tier points at it. Read the guid out of\n   `m_CustomRenderPipeline`, find the `.meta` that declares that guid, and count\n   `renderPipeline: {fileID: 11400000` in `QualitySettings.asset` to see whether a tier\n   overrides it:\n\n   ```bash\n   grep -m1 'm_CustomRenderPipeline:' ProjectSettings\u002FGraphicsSettings.asset\n   grep -c 'renderPipeline: {fileID: 11400000' ProjectSettings\u002FQualitySettings.asset\n   ```\n\n   `{fileID: 0}` with zero tier overrides means **built-in renderer** and nothing below applies —\n   a project created from a URP template can render on built-in this way, its URP assets\n   dormant. Resolve this first: it turns \"I set it and nothing happened\" into a one-minute\n   answer. Full resolver, the per-platform quality-tier mapping and the renderer-asset indirection:\n   → `reference\u002Fresolve-active-pipeline.md`.\n\n2. **HDR is enabled on the URP Asset.** Tonemapping requires it. Bloom still functions in SDR but\n   its `threshold` must be below 1 or it has nothing to select.\n3. **The camera's `renderPostProcessing` is true — it defaults to `false`.** And the renderer's\n   **PostProcessData asset must not be null**: null means the post-process pass does not exist at\n   all. With camera stacking, only the Base camera (or the last Overlay in the stack) should have\n   it on.\n4. **The Volume's GameObject layer is inside the camera's `volumeLayerMask`.** That mask defaults\n   to layer 0 (`Default`) only — a Volume parked on any other layer is invisible to the camera.\n\n> **A freshly added `UniversalAdditionalCameraData` reports** `renderPostProcessing=False`,\n> `volumeLayerMask=1` (bitmask 1 = layer 0 only), `renderType=Base`, `antialiasing=None`.\n> Re-check on your version in one call:\n>\n> ```csharp\n> var d = go.AddComponent\u003CUnityEngine.Rendering.Universal.UniversalAdditionalCameraData>();\n> return d.renderPostProcessing + \" \" + d.volumeLayerMask.value + \" \" + d.renderType;\n> ```\n5. **The Volume is enabled, has a profile, and at least one override has\n   `overrideState = true`.**\n\n> **Forgetting `overrideState` is the number one scripting error here.** The Volume system skips\n> any parameter whose `overrideState` is false, so a correctly-configured component contributes\n> nothing. `profile.Add\u003CT>(true)` turns them all on for that component.\n\nThen: are you looking at the **Game view**? Scene view has an independent post-processing toggle,\nand the camera's `renderType` must be `Base`, not `Overlay`.\n\nAll five as **one read-only `eval` block** that returns a numbered report — the fastest way to\nturn \"nothing happened\" into a line you can act on:\n→ [`reference\u002Fpreflight-snippet.md`](reference\u002Fpreflight-snippet.md).\n\n## 2. The API renamed almost everything → `reference\u002Fapi-renames.md`\n\n`PostProcessVolume`, `GetSetting\u003CT>` and `ColorGrading` are the old stack; the URP Volume names,\n`TryGet\u003CT>`, `ColorAdjustments`, and the override flag that a set value needs.\n\n## 3. What a mobile frame can afford\n\nKeep: `Tonemapping` (`Neutral`), a small `ColorAdjustments` exposure\u002Fcontrast trim, and a\nrestrained `Bloom` (`threshold` 1.0, `intensity` ~0.3, `downscale = Quarter`,\n`highQualityFiltering = false`, `maxIterations` reduced from the default 6).\n\nThat keep-list assumes HDR is still on (§1 step 2): Tonemapping needs it, and a `threshold` of 1.0\nselects nothing in a clamped SDR buffer. A project that turns HDR off to save mobile bandwidth\ndrops Tonemapping and puts the Bloom threshold below 1 — otherwise both silently do nothing.\n\nAvoid on mobile: **FilmGrain, MotionBlur, DepthOfField.** Each is full-screen and each buys\natmosphere rather than legibility.\n\n**Read a parameter's legal range off the component, never from memory** — several are not what\nthey look like: `Vignette.smoothness` is **0.01–1**, so a zero reads back as 0.01;\n`MotionBlur.clamp` is **0–0.2** with a 0.05 default; `Bloom.maxIterations` is **2–8** with a\ndefault of 6, so \"reduced from 6\" has a floor of 2. The Volume inspector shows the range, `eval`\non the type shows it, and the full table is\n→ [`reference\u002Feffect-reference.md`](reference\u002Feffect-reference.md).\n\nA mobile grade written out as values, beside three other presets:\n→ [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md).\n\n## 4. Reviewing a Render Graph renderer feature\n\n→ [`reference\u002Frender-graph-review.md`](reference\u002Frender-graph-review.md) — an eight-point\nchecklist and a fixed output shape that keeps **confirmed defects separate from suspicions**,\nplus the two corrected snippets that carry most of the checklist: a descriptor derived from\n`resourceData.activeColorTexture.GetDescriptor(renderGraph)` with only the two fields that must\ndiffer touched, and a `PassData` whose every field is assigned on every recording.\n\n## 5. Reflected Shader Graph custom nodes\n\nAn HLSL function preceded by `UNITY_EXPORT_REFLECTION` and tagged with four `funchints` becomes a\nnode in the graph's search. It is metadata, not shader authoring, and **every way of getting the\nmetadata wrong is silent** — the file compiles and no node appears.\n\n> **The feature needs `com.unity.shadergraph` 17.5 or newer; on 17.4 it is absent.** Check the\n> installed version, and the package itself, before writing anything — both checks are the version\n> gate in `reference\u002Fshader-graph-custom-node.md`. Below the floor, say so and stop.\n\nThe four required function hints, every parameter hint, where the file goes and why an existing\n`ShaderInclude` needs agreement before you append to it:\n→ [`reference\u002Fshader-graph-custom-node.md`](reference\u002Fshader-graph-custom-node.md). Every legal\ntag combination in one compilable file:\n→ [`resources\u002FShaderGraphHints.hlsl`](resources\u002FShaderGraphHints.hlsl).\n\n## 6. Verify\n\nPost-processing is the area where \"I set it\" and \"it is on screen\" diverge most often, and every\nstep of §1 fails silently.\n\n- **Look at the Game view**, at a screenshot you actually read (`unity-debug`) — not at the\n  inspector, and not at the Scene view, which has its own post-processing toggle.\n- **Read the value back off the component**, not off the code you just ran. `overrideState` is\n  the specific one to re-read.\n- **Report before\u002Fafter** in the six-line shape at the end of\n  [`reference\u002Fvolume-templates.md`](reference\u002Fvolume-templates.md): which pipeline asset resolved\n  as active, which Volume, profile and overrides, the camera's `renderPostProcessing`. \"Added\n  bloom\" is not a result.\n- On mobile, take a frame-time number before and after — the same situation, the same run mode,\n  windows either side of the change (`unity-profiling`). Post-processing is full-screen work and\n  the cost is not proportional to how much you can see.\n\n## Scope — what this skill does NOT do\n\n**Shader authoring stays out** — writing the lighting maths, hand-building a graph, debugging\nwhat a fragment computes. The one exception is §5: **reflected Shader Graph custom nodes are in\nscope**, because a reflected node is an HLSL function plus four metadata tags, and every failure\nmode is a metadata failure rather than a shading one. Ask this skill to *make a function into a\nnode*; do not ask it what the function should compute.\n\n**Migrating a built-in project to URP stays out** — the phased conversion of materials,\npost-processing, lighting and quality tiers, and diagnosing one that was half-moved (magenta\nmaterials, an old `PostProcessVolume` still wired up, a stale bake, `GrabPass` and\n`OnRenderImage` code) is `unity-urp-migration`. This skill assumes the project already renders\nwith URP and asks why an effect will not appear on it.\n\n**HDRP stays out.** It is a different pipeline with different Volume components, different\nrenderer plumbing and different numbers; nothing here transfers. **Lighting and GI set-up**\n— light modes, the bake, probes, shadows, sky and fog — is `unity-lighting`.\n\nWhether the pipeline in force is even URP is §1 and\n[`reference\u002Fresolve-active-pipeline.md`](reference\u002Fresolve-active-pipeline.md); a project that\ncame from a URP template can be rendering built-in. Confirming that a change is visible on screen\nis `unity-debug`. **Measuring what an effect costs stays out too** — counters, frame-time windows\nand the before\u002Fafter table are `unity-profiling`; §3 tells you what to suspect, that skill tells\nyou what it actually cost.\n",{"name":5,"description":7},"main","b7459aa49fb881c5abb764223674ec8f397a02b1","skills\u002Funity-render-urp",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-render-urp",{"tool":38,"command":39},"bunx","bunx skills add tipoLi5890\u002Funity-dev-skills --skill unity-render-urp",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tipoLi5890\u002Funity-dev-skills --skill unity-render-urp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,86],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fapi-renames.md","REFERENCE","参考文档",2156,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fapi-renames.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Feffect-reference.md",11839,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Feffect-reference.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"reference\u002Fmaterial-validation.md",6408,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fmaterial-validation.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"reference\u002Fpreflight-snippet.md",6436,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fpreflight-snippet.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"reference\u002Frender-graph-review.md",10651,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Frender-graph-review.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"reference\u002Fresolve-active-pipeline.md",6949,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fresolve-active-pipeline.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"reference\u002Fshader-graph-custom-node.md",5894,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fshader-graph-custom-node.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"reference\u002Fvolume-templates.md",15150,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Freference\u002Fvolume-templates.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"resources\u002FEditor\u002FUrpMaterialValidation.cs","OTHER","其他",6557,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Fresources\u002FEditor\u002FUrpMaterialValidation.cs",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"resources\u002FShaderGraphHints.hlsl",7022,"https:\u002F\u002Fgithub.com\u002FtipoLi5890\u002Funity-dev-skills\u002Fblob\u002Fmain\u002Fskills\u002Funity-render-urp\u002Fresources\u002FShaderGraphHints.hlsl",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"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",[],[]]