[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS54TFRCS9FPW19S8G7PRR":3,"skill-same:01M7CS54TFRCS9FPW19S8G7PRR":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CS54TFRCS9FPW19S8G7PRR","unity-testing",null,"Use when writing or running Unity tests - Unity Test Framework EditMode vs PlayMode, test assembly definitions, testing plain C# and ScriptableObjects, PlayMode scene\u002Fphysics\u002Finput tests, batchmode CLI with result XML, coverage, and the dotnet test fallback when no editor is installed.","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Funity-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: unity-testing\ncategory: testing\ndescription: Use when writing or running Unity tests - Unity Test Framework EditMode vs PlayMode, test assembly definitions, testing plain C# and ScriptableObjects, PlayMode scene\u002Fphysics\u002Finput tests, batchmode CLI with result XML, coverage, and the dotnet test fallback when no editor is installed.\ntech_stack: Unity\nsource: informed by the Unity Test Framework, Input System testing and Code Coverage package docs; own wording\n---\n# Unity Testing\n\n## Overview\n\nThe Unity Test Framework (NUnit 3 underneath) runs tests in two modes. EditMode tests run in the editor without entering Play mode — fast, ideal for plain C# rules, ScriptableObjects and editor tooling. PlayMode tests run the player loop — needed for scenes, physics, coroutines and input, and slower. Most tests should be EditMode tests against plain classes (testable-game-logic).\n\n**Core principle:** EditMode first; PlayMode only for behaviour that needs the player loop. Read the result XML, not the log tail.\n\n## Which mode\n\n| Question | Mode | Typical setup |\n|---|---|---|\n| Does the damage\u002Fcooldown\u002Finventory rule compute correctly? | EditMode | `new` the plain class |\n| Is every shipped definition valid? | EditMode | `AssetDatabase.FindAssets` |\n| Does a ScriptableObject-driven system behave? | EditMode | `ScriptableObject.CreateInstance\u003CT>()` |\n| Does the character land on the floor \u002F trigger fire? | PlayMode | load a test scene, `WaitForFixedUpdate` |\n| Does pressing Jump jump? | PlayMode | `InputTestFixture` |\n| Does the coroutine\u002FAwaitable sequence finish? | PlayMode | `[UnityTest]` yielding frames |\n\n## Test assemblies\n\n```json\n{\n  \"name\": \"Tests.EditMode\",\n  \"references\": [\"Game.Core\", \"Game.Runtime\", \"UnityEngine.TestRunner\", \"UnityEditor.TestRunner\"],\n  \"includePlatforms\": [\"Editor\"],\n  \"overrideReferences\": true,\n  \"precompiledReferences\": [\"nunit.framework.dll\"],\n  \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n  \"autoReferenced\": false\n}\n```\n\nPlayMode assemblies leave `includePlatforms` empty (any platform) and drop `UnityEditor.TestRunner` unless they need editor APIs. Tests live where the repository keeps them (often `Assets\u002FTests\u002FEditMode` and `Assets\u002FTests\u002FPlayMode`); follow its naming — `Method_Scenario_Expected` when there is none.\n\n## EditMode examples\n\n```csharp\npublic class InventoryTests {\n    [Test] public void Add_BeyondStackLimit_OverflowsToNewSlot() {\n        var potion = ScriptableObject.CreateInstance\u003CItemDefinition>();\n        potion.Configure(id: \"potion\", maxStack: 5);\n        var inv = new Inventory(slots: 4);\n\n        inv.Add(potion, 7);\n\n        Assert.That(inv.Slots[0].Count, Is.EqualTo(5));\n        Assert.That(inv.Slots[1].Count, Is.EqualTo(2));\n        Object.DestroyImmediate(potion);\n    }\n\n    [TestCase(0f, 100)] [TestCase(0.5f, 50)] [TestCase(1f, 0)]\n    public void Damage_ByArmorFraction_ReducesLinearly(float armor, int expected) =>\n        Assert.That(DamageMath.Apply(100, armor), Is.EqualTo(expected));\n}\n```\n\nDestroy every object a test creates (`DestroyImmediate` in EditMode, `Destroy` in PlayMode, or in `[TearDown]`) — leaked objects leak into the next test.\n\n## PlayMode examples\n\n```csharp\npublic class PlayerPhysicsTests {\n    [UnitySetUp] public IEnumerator Load() { yield return SceneManager.LoadSceneAsync(\"Test_FlatFloor\"); }\n\n    [UnityTest] public IEnumerator Player_DroppedAboveFloor_BecomesGrounded() {\n        var player = Object.Instantiate(TestPrefabs.Player, new Vector3(0, 3, 0), Quaternion.identity);\n        for (int i = 0; i \u003C 100; i++) yield return new WaitForFixedUpdate();\n        Assert.That(player.GetComponent\u003CGroundCheck>().IsGrounded, Is.True);\n    }\n}\n\npublic class JumpInputTests : InputTestFixture {\n    [UnityTest] public IEnumerator PressingSpace_MakesPlayerJump() {\n        var keyboard = InputSystem.AddDevice\u003CKeyboard>();\n        var player = Object.Instantiate(TestPrefabs.Player);\n        yield return null;\n        Press(keyboard.spaceKey);\n        yield return new WaitForFixedUpdate();\n        Assert.That(player.GetComponent\u003CRigidbody>().linearVelocity.y, Is.GreaterThan(0f));\n    }\n}\n```\n\n- Use dedicated small test scenes (`Test_*.unity`) added to the test build, not production levels.\n- Wait on conditions with a cap (`for` up to N fixed updates) instead of `WaitForSeconds` guesses.\n- `Time.timeScale` can speed slow sequences, but physics results change with the step — assert outcomes, not exact positions.\n\n## Running headless\n\n```sh\nUNITY=\"\u002FApplications\u002FUnity\u002FHub\u002FEditor\u002F$(sed -n 's\u002Fm_EditorVersion: \u002F\u002Fp' ProjectSettings\u002FProjectVersion.txt)\u002FUnity.app\u002FContents\u002FMacOS\u002FUnity\"\nmkdir -p \u002Ftmp\u002Ftt-\u003Ctask key>\n\"$UNITY\" -batchmode -nographics -projectPath . -runTests -testPlatform EditMode \\\n  -testResults \u002Ftmp\u002Ftt-\u003Ctask key>\u002Feditmode.xml -logFile \u002Ftmp\u002Ftt-\u003Ctask key>\u002Feditmode.log\n\"$UNITY\" -batchmode -projectPath . -runTests -testPlatform PlayMode \\\n  -testResults \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fplaymode.xml -logFile \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fplaymode.log\n```\n\n- Do not add `-quit` with `-runTests`; the editor quits when the run ends.\n- Drop `-nographics` for PlayMode tests that render or capture (game-visual-self-review).\n- `-testFilter \"Game.Tests.InventoryTests\"` or `-testCategory` narrows a run while iterating.\n- The project must not be open in another editor instance (the lock fails the run).\n- Read the result: `grep -o 'result=\"[A-Za-z]*\" total=\"[0-9]*\" passed=\"[0-9]*\" failed=\"[0-9]*\"' editmode.xml | head -1`, and `grep 'error CS' editmode.log` for compile errors (a compile error means zero tests ran, which is not a pass). A non-zero exit code is a failure.\n- Licence errors in the log (\"No valid Unity Editor license\") mean the run never started — report it as not run.\n\nCoverage, when the Code Coverage package is installed: add `-enableCodeCoverage -coverageResultsPath \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcoverage -coverageOptions \"generateAdditionalMetrics;assemblyFilters:+Game.*\"`.\n\n## No editor on this machine\n\n1. Keep the rules in `Game.Core` (`noEngineReferences: true`).\n2. Build a throwaway test project outside the repo:\n\n```xml\n\u003C!-- \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcore-tests\u002FCoreTests.csproj -->\n\u003CProject Sdk=\"Microsoft.NET.Sdk\">\n  \u003CPropertyGroup>\u003CTargetFramework>net8.0\u003C\u002FTargetFramework>\u003CNullable>disable\u003C\u002FNullable>\u003C\u002FPropertyGroup>\n  \u003CItemGroup>\n    \u003CCompile Include=\"\u003Crepo>\u002FAssets\u002FScripts\u002FCore\u002F**\u002F*.cs\" \u002F>\n    \u003CCompile Include=\"\u003Crepo>\u002FAssets\u002FTests\u002FEditMode\u002FCore\u002F**\u002F*.cs\" \u002F>\n    \u003CPackageReference Include=\"Microsoft.NET.Test.Sdk\" Version=\"17.*\" \u002F>\n    \u003CPackageReference Include=\"NUnit\" Version=\"3.*\" \u002F>\n    \u003CPackageReference Include=\"NUnit3TestAdapter\" Version=\"4.*\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FProject>\n```\n\n3. `dotnet test \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcore-tests` — Unity's C# language version is older than .NET 8's default, so set `\u003CLangVersion>9.0\u003C\u002FLangVersion>` if the repo targets it, to avoid using features Unity cannot compile.\n4. Report both: `RAN: dotnet test (Core) 18\u002F18` and `NOT RUN: EditMode\u002FPlayMode — Unity \u003Cversion> not installed`.\n\n## Common Mistakes\n\n- PlayMode tests for pure rules — slow and flaky for no gain.\n- Tests that depend on production scenes or on execution order between tests.\n- Objects created in a test and never destroyed.\n- Reading \"Exiting batchmode successfully\" as \"tests passed\" while the XML says failed or the log shows `error CS`.\n\n## Red Flags\n\n- A new gameplay rule with only a PlayMode test.\n- `WaitForSeconds(2)` as the synchronisation in a test.\n- A test assembly that references `Game.UI` to test gameplay.\n","# Unity Testing\n\n## Overview\n\nThe Unity Test Framework (NUnit 3 underneath) runs tests in two modes. EditMode tests run in the editor without entering Play mode — fast, ideal for plain C# rules, ScriptableObjects and editor tooling. PlayMode tests run the player loop — needed for scenes, physics, coroutines and input, and slower. Most tests should be EditMode tests against plain classes (testable-game-logic).\n\n**Core principle:** EditMode first; PlayMode only for behaviour that needs the player loop. Read the result XML, not the log tail.\n\n## Which mode\n\n| Question | Mode | Typical setup |\n|---|---|---|\n| Does the damage\u002Fcooldown\u002Finventory rule compute correctly? | EditMode | `new` the plain class |\n| Is every shipped definition valid? | EditMode | `AssetDatabase.FindAssets` |\n| Does a ScriptableObject-driven system behave? | EditMode | `ScriptableObject.CreateInstance\u003CT>()` |\n| Does the character land on the floor \u002F trigger fire? | PlayMode | load a test scene, `WaitForFixedUpdate` |\n| Does pressing Jump jump? | PlayMode | `InputTestFixture` |\n| Does the coroutine\u002FAwaitable sequence finish? | PlayMode | `[UnityTest]` yielding frames |\n\n## Test assemblies\n\n```json\n{\n  \"name\": \"Tests.EditMode\",\n  \"references\": [\"Game.Core\", \"Game.Runtime\", \"UnityEngine.TestRunner\", \"UnityEditor.TestRunner\"],\n  \"includePlatforms\": [\"Editor\"],\n  \"overrideReferences\": true,\n  \"precompiledReferences\": [\"nunit.framework.dll\"],\n  \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n  \"autoReferenced\": false\n}\n```\n\nPlayMode assemblies leave `includePlatforms` empty (any platform) and drop `UnityEditor.TestRunner` unless they need editor APIs. Tests live where the repository keeps them (often `Assets\u002FTests\u002FEditMode` and `Assets\u002FTests\u002FPlayMode`); follow its naming — `Method_Scenario_Expected` when there is none.\n\n## EditMode examples\n\n```csharp\npublic class InventoryTests {\n    [Test] public void Add_BeyondStackLimit_OverflowsToNewSlot() {\n        var potion = ScriptableObject.CreateInstance\u003CItemDefinition>();\n        potion.Configure(id: \"potion\", maxStack: 5);\n        var inv = new Inventory(slots: 4);\n\n        inv.Add(potion, 7);\n\n        Assert.That(inv.Slots[0].Count, Is.EqualTo(5));\n        Assert.That(inv.Slots[1].Count, Is.EqualTo(2));\n        Object.DestroyImmediate(potion);\n    }\n\n    [TestCase(0f, 100)] [TestCase(0.5f, 50)] [TestCase(1f, 0)]\n    public void Damage_ByArmorFraction_ReducesLinearly(float armor, int expected) =>\n        Assert.That(DamageMath.Apply(100, armor), Is.EqualTo(expected));\n}\n```\n\nDestroy every object a test creates (`DestroyImmediate` in EditMode, `Destroy` in PlayMode, or in `[TearDown]`) — leaked objects leak into the next test.\n\n## PlayMode examples\n\n```csharp\npublic class PlayerPhysicsTests {\n    [UnitySetUp] public IEnumerator Load() { yield return SceneManager.LoadSceneAsync(\"Test_FlatFloor\"); }\n\n    [UnityTest] public IEnumerator Player_DroppedAboveFloor_BecomesGrounded() {\n        var player = Object.Instantiate(TestPrefabs.Player, new Vector3(0, 3, 0), Quaternion.identity);\n        for (int i = 0; i \u003C 100; i++) yield return new WaitForFixedUpdate();\n        Assert.That(player.GetComponent\u003CGroundCheck>().IsGrounded, Is.True);\n    }\n}\n\npublic class JumpInputTests : InputTestFixture {\n    [UnityTest] public IEnumerator PressingSpace_MakesPlayerJump() {\n        var keyboard = InputSystem.AddDevice\u003CKeyboard>();\n        var player = Object.Instantiate(TestPrefabs.Player);\n        yield return null;\n        Press(keyboard.spaceKey);\n        yield return new WaitForFixedUpdate();\n        Assert.That(player.GetComponent\u003CRigidbody>().linearVelocity.y, Is.GreaterThan(0f));\n    }\n}\n```\n\n- Use dedicated small test scenes (`Test_*.unity`) added to the test build, not production levels.\n- Wait on conditions with a cap (`for` up to N fixed updates) instead of `WaitForSeconds` guesses.\n- `Time.timeScale` can speed slow sequences, but physics results change with the step — assert outcomes, not exact positions.\n\n## Running headless\n\n```sh\nUNITY=\"\u002FApplications\u002FUnity\u002FHub\u002FEditor\u002F$(sed -n 's\u002Fm_EditorVersion: \u002F\u002Fp' ProjectSettings\u002FProjectVersion.txt)\u002FUnity.app\u002FContents\u002FMacOS\u002FUnity\"\nmkdir -p \u002Ftmp\u002Ftt-\u003Ctask key>\n\"$UNITY\" -batchmode -nographics -projectPath . -runTests -testPlatform EditMode \\\n  -testResults \u002Ftmp\u002Ftt-\u003Ctask key>\u002Feditmode.xml -logFile \u002Ftmp\u002Ftt-\u003Ctask key>\u002Feditmode.log\n\"$UNITY\" -batchmode -projectPath . -runTests -testPlatform PlayMode \\\n  -testResults \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fplaymode.xml -logFile \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fplaymode.log\n```\n\n- Do not add `-quit` with `-runTests`; the editor quits when the run ends.\n- Drop `-nographics` for PlayMode tests that render or capture (game-visual-self-review).\n- `-testFilter \"Game.Tests.InventoryTests\"` or `-testCategory` narrows a run while iterating.\n- The project must not be open in another editor instance (the lock fails the run).\n- Read the result: `grep -o 'result=\"[A-Za-z]*\" total=\"[0-9]*\" passed=\"[0-9]*\" failed=\"[0-9]*\"' editmode.xml | head -1`, and `grep 'error CS' editmode.log` for compile errors (a compile error means zero tests ran, which is not a pass). A non-zero exit code is a failure.\n- Licence errors in the log (\"No valid Unity Editor license\") mean the run never started — report it as not run.\n\nCoverage, when the Code Coverage package is installed: add `-enableCodeCoverage -coverageResultsPath \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcoverage -coverageOptions \"generateAdditionalMetrics;assemblyFilters:+Game.*\"`.\n\n## No editor on this machine\n\n1. Keep the rules in `Game.Core` (`noEngineReferences: true`).\n2. Build a throwaway test project outside the repo:\n\n```xml\n\u003C!-- \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcore-tests\u002FCoreTests.csproj -->\n\u003CProject Sdk=\"Microsoft.NET.Sdk\">\n  \u003CPropertyGroup>\u003CTargetFramework>net8.0\u003C\u002FTargetFramework>\u003CNullable>disable\u003C\u002FNullable>\u003C\u002FPropertyGroup>\n  \u003CItemGroup>\n    \u003CCompile Include=\"\u003Crepo>\u002FAssets\u002FScripts\u002FCore\u002F**\u002F*.cs\" \u002F>\n    \u003CCompile Include=\"\u003Crepo>\u002FAssets\u002FTests\u002FEditMode\u002FCore\u002F**\u002F*.cs\" \u002F>\n    \u003CPackageReference Include=\"Microsoft.NET.Test.Sdk\" Version=\"17.*\" \u002F>\n    \u003CPackageReference Include=\"NUnit\" Version=\"3.*\" \u002F>\n    \u003CPackageReference Include=\"NUnit3TestAdapter\" Version=\"4.*\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FProject>\n```\n\n3. `dotnet test \u002Ftmp\u002Ftt-\u003Ctask key>\u002Fcore-tests` — Unity's C# language version is older than .NET 8's default, so set `\u003CLangVersion>9.0\u003C\u002FLangVersion>` if the repo targets it, to avoid using features Unity cannot compile.\n4. Report both: `RAN: dotnet test (Core) 18\u002F18` and `NOT RUN: EditMode\u002FPlayMode — Unity \u003Cversion> not installed`.\n\n## Common Mistakes\n\n- PlayMode tests for pure rules — slow and flaky for no gain.\n- Tests that depend on production scenes or on execution order between tests.\n- Objects created in a test and never destroyed.\n- Reading \"Exiting batchmode successfully\" as \"tests passed\" while the XML says failed or the log shows `error CS`.\n\n## Red Flags\n\n- A new gameplay rule with only a PlayMode test.\n- `WaitForSeconds(2)` as the synchronisation in a test.\n- A test assembly that references `Game.UI` to test gameplay.\n",{"name":5,"source":24,"category":25,"tech_stack":26,"description":7},"informed by the Unity Test Framework, Input System testing and Code Coverage package docs; own wording","testing","Unity","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Funity-testing",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill unity-testing",{"tool":42,"command":43},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill unity-testing",{"tool":45,"command":46},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill unity-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fgame-developer\u002Fskills\u002Funity-testing\u002FSKILL.md",true,[],[51,57,64,71,78,85],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]