[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D0NBWN3263RN3RTNTXGE68":3,"skill-same:01M7D0NBWN3263RN3RTNTXGE68":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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D0NBWN3263RN3RTNTXGE68","platform-detection",null,"Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for \"which test platform\u002Fframework?\", \"VSTest or MTP?\", or \"what runner does this project use?\", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest\u002FMTP configuration. Resolves global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest\u002FxUnit\u002FNUnit\u002FTUnit. DO NOT USE when the user asks to run\u002Ffilter tests or for commands, flags, TRX\u002Fdumps, or test-command\u002Ffilter errors; use run-tests directly. Do not use for hot reload or migration.","itsmejay18\u002FAI-Skills-for-My-Development-Stack","itsmejay18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167779943?v=4","01M7CZRFC6DDZA5V2CX8WDSZED","Jay Jemino Ababon ","01M7CZRFCVRNW1SFHSQXEJ3CQN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fplatform-detection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: platform-detection\ndescription: >-\n  Identify a .NET project's test platform, framework, command mode, and\n  SDK-style vs classic project system. Use only for \"which test\n  platform\u002Fframework?\", \"VSTest or MTP?\", or \"what runner does this project\n  use?\", including bridge settings, UseVSTest opt-outs, and incompatible or\n  conflicting VSTest\u002FMTP configuration. Resolves global.json, project,\n  packages.config, Directory.Build.props, and Directory.Packages.props\n  precedence for MSTest\u002FxUnit\u002FNUnit\u002FTUnit. DO NOT USE when the user asks to\n  run\u002Ffilter tests or for commands, flags, TRX\u002Fdumps, or test-command\u002Ffilter\n  errors; use run-tests directly.\n  Do not use for hot reload or migration.\nlicense: MIT\n---\n\n# Test Platform and Framework Detection\n\nDetermine **which test platform** (VSTest or Microsoft.Testing.Platform) and **which test framework** (MSTest, xUnit, NUnit, TUnit) a project uses.\n\n## Response contract\n\nHonor the user's requested labels and order exactly, substituting the actual\nclassification for every placeholder. Start with the verdict: never put a\nheading, scratch analysis, tool syntax, or an echoed template before it. Follow\nwith one concise evidence sentence naming the repository facts needed to justify\nevery requested classification. When `Framework` is requested, name the package\nor project SDK that identifies it. Use a second sentence only for a conflict, an\nincomplete configuration, or target-framework-specific differences.\n\n`Platform` means the platform that actually executes tests: **VSTest** or\n**MTP**. If conflicting or incomplete configuration prevents execution, report\nit as unavailable rather than inventing a successful platform.\n\nNever classify the executed platform from `global.json` `test.runner` alone.\nThat setting selects `dotnet test` command mode; even an explicit `VSTest`\nvalue can bridge to an executable MTP application. Continue through the project\nrunner, bridge, and output-shape signals before writing `Platform:`.\n\nApply this scope gate before drafting the evidence:\n\n| User asks for | Evidence to include | Omit |\n|---------------|---------------------|------|\n| Platform and framework | Final runner selector and its winning source; package or project SDK identifying the framework; when needed, the property that makes it executable | Command mode; common SDK facts; `OutputType` unless it is missing or conflicting |\n| The single deciding signal | That runner-selection property, why its source wins, and why a competing package does not select or imply VSTest; still name the package or project SDK identifying a requested framework | Bridge, `OutputType`, SDK mode, and unrelated prerequisites when the configuration is complete |\n| Platforms per target framework | Only the conditional final values that differ by target | Common properties and project-wide SDK commentary |\n| Explicit opt-out | Final `UseVSTest` value and its winning source | Superseded defaults unless they create a conflict |\n| `dotnet test` mode | The separate command-mode and executed-platform classifications | None of the requested axes |\n\nIf the requested labels omit `dotnet test mode`, do not state or explain command\nmode anywhere in the response. An exact bridge property may still be decisive\nplatform evidence, but do not turn it into SDK or CLI-mode commentary.\nWhen the user asks which single signal decides between an explicit runner\nproperty and `Microsoft.NET.Test.Sdk`, the evidence sentence must say both that\nthe runner property selects MTP and that `Microsoft.NET.Test.Sdk` does not\nselect or imply VSTest.\n\nWhen import precedence decides a property, state why the winning source wins\n(for example, it is imported later or its condition applies), not merely that it\ncontains the final value or overrides another assignment.\n\nKeep the explanation on the requested axis:\n\n- An SDK version pin in `global.json` is context, not a platform selector. Claim\n  that `global.json` selects VSTest or native MTP only when its `test.runner`\n  setting actually does so.\n- If `UseVSTest=true` is decisive, say that directly. Do not speculate about an\n  absent `test.runner` or describe SDK pinning as an additional platform choice.\n- If command mode was not requested, do not add it, even when it was needed\n  internally to determine the executed platform.\n\nWhen a classic-project request also asks for the command family, add a direct\nline such as `Command family: MSBuild + vstest.console.exe`; do not turn it into\nan optional alternative or add an unnecessary build qualifier.\n\nFor a file-backed request, enumerate the following configuration names once,\nthen read every relevant file that is present in one batched operation:\n`global.json`, `.csproj`, `packages.config`, `Directory.Build.props`,\n`Directory.Build.targets`, `Directory.Packages.props`, and explicit imported\n`.props` \u002F `.targets`. A setting absent from the project file may be defined by\nan import, so never infer its final value from the `.csproj` alone. Do not search\nthe web or inspect unrelated files when repository configuration is sufficient.\n\nResolve properties in the actual MSBuild import order, not with a fixed\n\"project beats props\" rule. For every applicable target framework:\n\n1. Follow the import graph and conditions. A later applicable assignment wins.\n   `Directory.Build.props` is normally imported before the project body, so an\n   unconditional project assignment normally overrides it; later `.targets`\n   can override the project again.\n2. Record the final value and its winning source for `UseVSTest`, the framework\n   runner selector, `TestingPlatformDotnetTestSupport`, and `OutputType`.\n3. Treat `Directory.Packages.props` as version evidence unless it also contains\n   relevant properties. Resolve package\u002FSDK versions before applying\n   version-dependent defaults.\n4. Never infer a property from package presence. A package or SDK default counts\n   only when that resolved version actually supplies it and no later assignment\n   overrides it.\n\n## Detecting the project system\n\nClassify the project before selecting a CLI:\n\n- Root `Sdk` attribute or `\u003CSdk>` declaration: SDK-style.\n- `ToolsVersion`, `Microsoft.Common.props` \u002F `Microsoft.CSharp.targets` imports,\n  explicit `\u003CReference>` and `\u003CCompile Include>` items: classic non-SDK.\n- `packages.config`: classic NuGet dependency management.\n\nClassic projects can still use VSTest-compatible adapters, but `dotnet test` is\nnot automatically a valid invocation. Preserve repository scripts\u002FCI commands,\ncommonly MSBuild followed by `vstest.console.exe`. Mention `MSTest.exe` only\nwhen repository configuration or documentation establishes that legacy runner.\n\n## Detecting the test framework\n\nRead the `.csproj`, adjacent `packages.config`, and\n`Directory.Build.props` \u002F `Directory.Packages.props` and look for:\n\n| Package or SDK reference | Framework |\n|--------------------------|-----------|\n| `MSTest` metapackage, `\u003CProject Sdk=\"MSTest.Sdk[\u002Fversion]\">`, or `\u003CSdk Name=\"MSTest.Sdk\">` | MSTest |\n| `MSTest.TestFramework` + `MSTest.TestAdapter` | MSTest (also valid for v3\u002Fv4) |\n| `xunit`, `xunit.v3`, `xunit.v3.mtp-v1`, `xunit.v3.mtp-v2`, `xunit.v3.core.mtp-v1`, `xunit.v3.core.mtp-v2` | xUnit |\n| `NUnit` + `NUnit3TestAdapter` | NUnit |\n| `TUnit` | TUnit (MTP only) |\n\nIn classic projects, package IDs and versions may appear only in\n`packages.config`, while the project contains assembly `\u003CReference>` elements\nwith `HintPath` values. Use both sources.\n\n## Detecting the executed test platform\n\nIf the user explicitly requests `dotnet test` mode, read\n[`references\u002Fcommand-mode.md`](references\u002Fcommand-mode.md) before answering.\nDo not load that reference or mention command mode for a\nplatform\u002Fframework-only request.\n\nFor an SDK 8\u002F9 request that explicitly asks about command mode and has no\neffective bridge, state all three facts in one causal sentence: the runner makes\nthe project MTP-capable, `dotnet test` remains in VSTest mode, and the missing\nbridge means VSTest actually executes the tests. Mention that native MTP command\nmode starts with SDK 10 only when it helps explain that result.\n\nWhen execution is permitted and neither the prompt nor `global.json` identifies\nthe SDK, run `dotnet --version` once. For read-only identification requests that\nprohibit execution, do not probe the installed SDK; use repository facts and\nstate any necessary SDK assumption.\n\nAfter resolving final property values, classify in this order:\n\n1. Final `UseVSTest=true` selects VSTest. If `global.json` simultaneously\n   selects native MTP command mode, report `Platform: unavailable` because the\n   command mode and project opt-out conflict.\n2. A native-MTP selection in `global.json` executes a compatible MTP\n   application with final `OutputType=Exe` on MTP. A VSTest-only,\n   library-output, or opted-out project is unavailable.\n3. On SDK 8\u002F9, an enabled MTP runner plus final\n   `TestingPlatformDotnetTestSupport=true` plus final `OutputType=Exe` executes\n   on MTP.\n4. If the runner is enabled but the bridge is absent or false, a dual-capable\n   MSTest, NUnit, or xUnit project remains on VSTest: the runner establishes MTP\n   capability, but SDK 8\u002F9 `dotnet test` cannot reach it and the VSTest adapter\n   executes the tests instead. If the bridge is true but no runner is enabled,\n   the project also remains on VSTest.\n5. A runner and bridge with non-executable output is incomplete and unavailable.\n   An MTP-only framework that cannot be reached by the selected SDK path is also\n   unavailable, not VSTest.\n\nKeep each signal's role exact:\n\n- The runner property selects the test application.\n- `TestingPlatformDotnetTestSupport=true` lets SDK 8\u002F9 `dotnet test` reach that\n  application.\n- `OutputType=Exe` supplies the executable host shape. It does **not** select or\n  enable MTP.\n\nDo not confuse the `MSTest` metapackage with the `MSTest.Sdk` project SDK.\n`PackageReference Include=\"MSTest\"` plus `EnableMSTestRunner=true` enables the\nMSTest MTP runner, but it does **not** implicitly set\n`TestingPlatformDotnetTestSupport`.\n\nMSTest.Sdk enables the MTP runner by default. Check its resolved version and\nevaluated properties for bridge behavior: version 3.8 supplies\n`TestingPlatformDotnetTestSupport` unless a later assignment overrides it,\nwhile newer SDKs on .NET 10 may expect native MTP mode instead.\n`\u003CUseVSTest>true\u003C\u002FUseVSTest>` opts back into VSTest.\n\n| Signal | Meaning |\n|--------|---------|\n| `\u003CProject Sdk=\"MSTest.Sdk...\">` with no `UseVSTest` | MTP application; inspect the resolved SDK version and evaluated bridge property |\n| `MSTest` metapackage + `\u003CEnableMSTestRunner>true>` | MTP runner enabled; does not imply the VSTest-to-MTP bridge |\n| `\u003CUseMicrosoftTestingPlatformRunner>true` | Deciding xUnit runner-selection signal |\n| `\u003CEnableMSTestRunner>true>` \u002F `\u003CEnableNUnitRunner>true>` | Deciding MSTest\u002FNUnit runner-selection signal |\n| `TestingPlatformDotnetTestSupport=true` | Execution prerequisite for a VSTest-to-MTP bridge, not the runner-selection signal |\n| `Microsoft.Testing.Platform` package | MTP-capable application; not decisive by itself |\n| `TUnit` | MTP-only framework |\n| Final evaluated `\u003COutputType>Exe\u003C\u002FOutputType>` | Required executable host shape for package-based MTP applications |\n\n`Microsoft.NET.Test.Sdk` alone is not decisive; it can remain for compatibility\nin an MTP-enabled project. When an explicit override decides the result, name\nthe final override and its source, not the superseded default.\nWhen a runner-selection property competes with `Microsoft.NET.Test.Sdk`, say\nthat the runner property selects MTP and `Microsoft.NET.Test.Sdk` does **not**\nselect or imply VSTest. It may remain as compatibility support, but that is\nsecondary. `TestingPlatformDotnetTestSupport=true` is a bridge prerequisite, not\nthe runner-selection signal; never say that this property alone enables the\nbridge. For a request asking which single signal decides, stop there. Omit\nbridge or host-shape prerequisites when the configuration is complete, and add\nthem only when needed to explain why the selected runner cannot execute.\nLikewise, when an enabled runner is overridden or unreachable, state both axes\ncausally: the runner property makes the project MTP-capable, but the final\n`UseVSTest`\u002Fbridge\u002Foutput setting determines which platform actually executes.\nName the runner selector before using a package reference only to identify the\nframework.\n\nUse causal evidence, not a bag of signals. For example:\n\n```text\nPlatform: MTP\nFramework: NUnit\n\nDirectory.Build.props supplies final EnableNUnitRunner=true and\nTestingPlatformDotnetTestSupport=true, so NUnit executes on MTP.\n```\n\nFor an incompatible configuration, give one minimal alignment choice after the\nverdict without modifying files: either select the project's configured\nplatform globally or remove the project opt-out to use the globally selected\nplatform.\n\n### Conditional and per-target-framework properties\n\nEvaluate runner and bridge properties for each target framework. If conditions\nproduce different executed platforms, report each target explicitly (for\nexample, `net8.0: VSTest`, `net9.0: MTP`) rather than collapsing the project to\none global platform.\n","# Test Platform and Framework Detection\n\nDetermine **which test platform** (VSTest or Microsoft.Testing.Platform) and **which test framework** (MSTest, xUnit, NUnit, TUnit) a project uses.\n\n## Response contract\n\nHonor the user's requested labels and order exactly, substituting the actual\nclassification for every placeholder. Start with the verdict: never put a\nheading, scratch analysis, tool syntax, or an echoed template before it. Follow\nwith one concise evidence sentence naming the repository facts needed to justify\nevery requested classification. When `Framework` is requested, name the package\nor project SDK that identifies it. Use a second sentence only for a conflict, an\nincomplete configuration, or target-framework-specific differences.\n\n`Platform` means the platform that actually executes tests: **VSTest** or\n**MTP**. If conflicting or incomplete configuration prevents execution, report\nit as unavailable rather than inventing a successful platform.\n\nNever classify the executed platform from `global.json` `test.runner` alone.\nThat setting selects `dotnet test` command mode; even an explicit `VSTest`\nvalue can bridge to an executable MTP application. Continue through the project\nrunner, bridge, and output-shape signals before writing `Platform:`.\n\nApply this scope gate before drafting the evidence:\n\n| User asks for | Evidence to include | Omit |\n|---------------|---------------------|------|\n| Platform and framework | Final runner selector and its winning source; package or project SDK identifying the framework; when needed, the property that makes it executable | Command mode; common SDK facts; `OutputType` unless it is missing or conflicting |\n| The single deciding signal | That runner-selection property, why its source wins, and why a competing package does not select or imply VSTest; still name the package or project SDK identifying a requested framework | Bridge, `OutputType`, SDK mode, and unrelated prerequisites when the configuration is complete |\n| Platforms per target framework | Only the conditional final values that differ by target | Common properties and project-wide SDK commentary |\n| Explicit opt-out | Final `UseVSTest` value and its winning source | Superseded defaults unless they create a conflict |\n| `dotnet test` mode | The separate command-mode and executed-platform classifications | None of the requested axes |\n\nIf the requested labels omit `dotnet test mode`, do not state or explain command\nmode anywhere in the response. An exact bridge property may still be decisive\nplatform evidence, but do not turn it into SDK or CLI-mode commentary.\nWhen the user asks which single signal decides between an explicit runner\nproperty and `Microsoft.NET.Test.Sdk`, the evidence sentence must say both that\nthe runner property selects MTP and that `Microsoft.NET.Test.Sdk` does not\nselect or imply VSTest.\n\nWhen import precedence decides a property, state why the winning source wins\n(for example, it is imported later or its condition applies), not merely that it\ncontains the final value or overrides another assignment.\n\nKeep the explanation on the requested axis:\n\n- An SDK version pin in `global.json` is context, not a platform selector. Claim\n  that `global.json` selects VSTest or native MTP only when its `test.runner`\n  setting actually does so.\n- If `UseVSTest=true` is decisive, say that directly. Do not speculate about an\n  absent `test.runner` or describe SDK pinning as an additional platform choice.\n- If command mode was not requested, do not add it, even when it was needed\n  internally to determine the executed platform.\n\nWhen a classic-project request also asks for the command family, add a direct\nline such as `Command family: MSBuild + vstest.console.exe`; do not turn it into\nan optional alternative or add an unnecessary build qualifier.\n\nFor a file-backed request, enumerate the following configuration names once,\nthen read every relevant file that is present in one batched operation:\n`global.json`, `.csproj`, `packages.config`, `Directory.Build.props`,\n`Directory.Build.targets`, `Directory.Packages.props`, and explicit imported\n`.props` \u002F `.targets`. A setting absent from the project file may be defined by\nan import, so never infer its final value from the `.csproj` alone. Do not search\nthe web or inspect unrelated files when repository configuration is sufficient.\n\nResolve properties in the actual MSBuild import order, not with a fixed\n\"project beats props\" rule. For every applicable target framework:\n\n1. Follow the import graph and conditions. A later applicable assignment wins.\n   `Directory.Build.props` is normally imported before the project body, so an\n   unconditional project assignment normally overrides it; later `.targets`\n   can override the project again.\n2. Record the final value and its winning source for `UseVSTest`, the framework\n   runner selector, `TestingPlatformDotnetTestSupport`, and `OutputType`.\n3. Treat `Directory.Packages.props` as version evidence unless it also contains\n   relevant properties. Resolve package\u002FSDK versions before applying\n   version-dependent defaults.\n4. Never infer a property from package presence. A package or SDK default counts\n   only when that resolved version actually supplies it and no later assignment\n   overrides it.\n\n## Detecting the project system\n\nClassify the project before selecting a CLI:\n\n- Root `Sdk` attribute or `\u003CSdk>` declaration: SDK-style.\n- `ToolsVersion`, `Microsoft.Common.props` \u002F `Microsoft.CSharp.targets` imports,\n  explicit `\u003CReference>` and `\u003CCompile Include>` items: classic non-SDK.\n- `packages.config`: classic NuGet dependency management.\n\nClassic projects can still use VSTest-compatible adapters, but `dotnet test` is\nnot automatically a valid invocation. Preserve repository scripts\u002FCI commands,\ncommonly MSBuild followed by `vstest.console.exe`. Mention `MSTest.exe` only\nwhen repository configuration or documentation establishes that legacy runner.\n\n## Detecting the test framework\n\nRead the `.csproj`, adjacent `packages.config`, and\n`Directory.Build.props` \u002F `Directory.Packages.props` and look for:\n\n| Package or SDK reference | Framework |\n|--------------------------|-----------|\n| `MSTest` metapackage, `\u003CProject Sdk=\"MSTest.Sdk[\u002Fversion]\">`, or `\u003CSdk Name=\"MSTest.Sdk\">` | MSTest |\n| `MSTest.TestFramework` + `MSTest.TestAdapter` | MSTest (also valid for v3\u002Fv4) |\n| `xunit`, `xunit.v3`, `xunit.v3.mtp-v1`, `xunit.v3.mtp-v2`, `xunit.v3.core.mtp-v1`, `xunit.v3.core.mtp-v2` | xUnit |\n| `NUnit` + `NUnit3TestAdapter` | NUnit |\n| `TUnit` | TUnit (MTP only) |\n\nIn classic projects, package IDs and versions may appear only in\n`packages.config`, while the project contains assembly `\u003CReference>` elements\nwith `HintPath` values. Use both sources.\n\n## Detecting the executed test platform\n\nIf the user explicitly requests `dotnet test` mode, read\n[`references\u002Fcommand-mode.md`](references\u002Fcommand-mode.md) before answering.\nDo not load that reference or mention command mode for a\nplatform\u002Fframework-only request.\n\nFor an SDK 8\u002F9 request that explicitly asks about command mode and has no\neffective bridge, state all three facts in one causal sentence: the runner makes\nthe project MTP-capable, `dotnet test` remains in VSTest mode, and the missing\nbridge means VSTest actually executes the tests. Mention that native MTP command\nmode starts with SDK 10 only when it helps explain that result.\n\nWhen execution is permitted and neither the prompt nor `global.json` identifies\nthe SDK, run `dotnet --version` once. For read-only identification requests that\nprohibit execution, do not probe the installed SDK; use repository facts and\nstate any necessary SDK assumption.\n\nAfter resolving final property values, classify in this order:\n\n1. Final `UseVSTest=true` selects VSTest. If `global.json` simultaneously\n   selects native MTP command mode, report `Platform: unavailable` because the\n   command mode and project opt-out conflict.\n2. A native-MTP selection in `global.json` executes a compatible MTP\n   application with final `OutputType=Exe` on MTP. A VSTest-only,\n   library-output, or opted-out project is unavailable.\n3. On SDK 8\u002F9, an enabled MTP runner plus final\n   `TestingPlatformDotnetTestSupport=true` plus final `OutputType=Exe` executes\n   on MTP.\n4. If the runner is enabled but the bridge is absent or false, a dual-capable\n   MSTest, NUnit, or xUnit project remains on VSTest: the runner establishes MTP\n   capability, but SDK 8\u002F9 `dotnet test` cannot reach it and the VSTest adapter\n   executes the tests instead. If the bridge is true but no runner is enabled,\n   the project also remains on VSTest.\n5. A runner and bridge with non-executable output is incomplete and unavailable.\n   An MTP-only framework that cannot be reached by the selected SDK path is also\n   unavailable, not VSTest.\n\nKeep each signal's role exact:\n\n- The runner property selects the test application.\n- `TestingPlatformDotnetTestSupport=true` lets SDK 8\u002F9 `dotnet test` reach that\n  application.\n- `OutputType=Exe` supplies the executable host shape. It does **not** select or\n  enable MTP.\n\nDo not confuse the `MSTest` metapackage with the `MSTest.Sdk` project SDK.\n`PackageReference Include=\"MSTest\"` plus `EnableMSTestRunner=true` enables the\nMSTest MTP runner, but it does **not** implicitly set\n`TestingPlatformDotnetTestSupport`.\n\nMSTest.Sdk enables the MTP runner by default. Check its resolved version and\nevaluated properties for bridge behavior: version 3.8 supplies\n`TestingPlatformDotnetTestSupport` unless a later assignment overrides it,\nwhile newer SDKs on .NET 10 may expect native MTP mode instead.\n`\u003CUseVSTest>true\u003C\u002FUseVSTest>` opts back into VSTest.\n\n| Signal | Meaning |\n|--------|---------|\n| `\u003CProject Sdk=\"MSTest.Sdk...\">` with no `UseVSTest` | MTP application; inspect the resolved SDK version and evaluated bridge property |\n| `MSTest` metapackage + `\u003CEnableMSTestRunner>true>` | MTP runner enabled; does not imply the VSTest-to-MTP bridge |\n| `\u003CUseMicrosoftTestingPlatformRunner>true` | Deciding xUnit runner-selection signal |\n| `\u003CEnableMSTestRunner>true>` \u002F `\u003CEnableNUnitRunner>true>` | Deciding MSTest\u002FNUnit runner-selection signal |\n| `TestingPlatformDotnetTestSupport=true` | Execution prerequisite for a VSTest-to-MTP bridge, not the runner-selection signal |\n| `Microsoft.Testing.Platform` package | MTP-capable application; not decisive by itself |\n| `TUnit` | MTP-only framework |\n| Final evaluated `\u003COutputType>Exe\u003C\u002FOutputType>` | Required executable host shape for package-based MTP applications |\n\n`Microsoft.NET.Test.Sdk` alone is not decisive; it can remain for compatibility\nin an MTP-enabled project. When an explicit override decides the result, name\nthe final override and its source, not the superseded default.\nWhen a runner-selection property competes with `Microsoft.NET.Test.Sdk`, say\nthat the runner property selects MTP and `Microsoft.NET.Test.Sdk` does **not**\nselect or imply VSTest. It may remain as compatibility support, but that is\nsecondary. `TestingPlatformDotnetTestSupport=true` is a bridge prerequisite, not\nthe runner-selection signal; never say that this property alone enables the\nbridge. For a request asking which single signal decides, stop there. Omit\nbridge or host-shape prerequisites when the configuration is complete, and add\nthem only when needed to explain why the selected runner cannot execute.\nLikewise, when an enabled runner is overridden or unreachable, state both axes\ncausally: the runner property makes the project MTP-capable, but the final\n`UseVSTest`\u002Fbridge\u002Foutput setting determines which platform actually executes.\nName the runner selector before using a package reference only to identify the\nframework.\n\nUse causal evidence, not a bag of signals. For example:\n\n```text\nPlatform: MTP\nFramework: NUnit\n\nDirectory.Build.props supplies final EnableNUnitRunner=true and\nTestingPlatformDotnetTestSupport=true, so NUnit executes on MTP.\n```\n\nFor an incompatible configuration, give one minimal alignment choice after the\nverdict without modifying files: either select the project's configured\nplatform globally or remove the project opt-out to use the globally selected\nplatform.\n\n### Conditional and per-target-framework properties\n\nEvaluate runner and bridge properties for each target framework. If conditions\nproduce different executed platforms, report each target explicitly (for\nexample, `net8.0: VSTest`, `net9.0: MTP`) rather than collapsing the project to\none global platform.\n",{"name":5,"license":15,"description":7},"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","02-CSharp-WPF-Desktop-Development\u002Fplatform-detection","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack","https:\u002F\u002Fgithub.com\u002Fitsmejay18","2026-09-18 16:06:36",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill platform-detection",{"tool":36,"command":37},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill platform-detection",{"tool":39,"command":40},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill platform-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fplatform-detection\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fcommand-mode.md","REFERENCE","参考文档",952,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fplatform-detection\u002Freferences\u002Fcommand-mode.md",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7D2RKBHPZ3E1RNN5DWHT550","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector\u003CT>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D2RDJ7RN3QK8GJR0QTER1D","resolve-project-references","Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fresolve-project-references\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7D2R1H2GTNZYHG9YRX3JDQW","optimizing-ef-core-queries","Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database schema. For EF Core, not Dapper or raw ADO.NET.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Foptimizing-ef-core-queries\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D2QREG04W1YT0NEBHEW5C9","microbenchmarking","Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling\u002Ftracing .NET code (dotnet-trace, PerfView), production telemetry, or load\u002Fstress testing (Crank, k6).","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fmicrobenchmarking\u002FSKILL.md",[],[],{"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},"01M7D2QGE175XWPZVACVH2868Z","incremental-build","Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs\u002FOutputs on custom targets, volatile properties in output paths (timestamps\u002FGUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fincremental-build\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},"01M7D2Q1DQTC6K49R73WQTTPSB","eval-performance","Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Feval-performance\u002FSKILL.md",[],[]]