[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CC14WNAP1Y77ZMM4VD29A":3,"skill-same:01M78CC14WNAP1Y77ZMM4VD29A":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78CC14WNAP1Y77ZMM4VD29A","platform-detection",null,"Identifies a .NET project's test platform, framework, command mode, and SDK-style versus classic project system, resolving global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest, xUnit, NUnit, and TUnit. Use when asking \"which test platform or framework?\", \"VSTest or MTP?\", or \"what runner does this project use?\", including bridge settings, UseVSTest opt-outs, and conflicting VSTest\u002FMTP configuration. Not for running or filtering tests, commands, flags, TRX, dumps, or test-command errors (use run-tests), or for hot-reload or migration requests.","Cratis\u002FPrologue","Cratis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16456213?v=4","01M6BXRH290K4C8RS4PTKK3HXQ","01M78C1YXTSPZGP4G1K2ZM6J1N",0,"MIT","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: platform-detection\ndescription: 'Identifies a .NET project''s test platform, framework, command mode, and SDK-style versus classic project system, resolving global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest, xUnit, NUnit, and TUnit. Use when asking \"which test platform or framework?\", \"VSTest or MTP?\", or \"what runner does this project use?\", including bridge settings, UseVSTest opt-outs, and conflicting VSTest\u002FMTP configuration. Not for running or filtering tests, commands, flags, TRX, dumps, or test-command errors (use run-tests), or for hot-reload or migration requests.'\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Fplatform-detection\u002FSKILL.md -->\n\n\u003C!-- Modified by Cratis from dotnet's original (MIT): frontmatter, applicability, navigation and the changes listed in NOTICE. Upstream: https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills (plugins\u002Fdotnet-test\u002Fskills\u002Fplatform-detection\u002FSKILL.md; see NOTICE) -->\n\n# Test Platform and Framework Detection\n\nCratis rules in `.cratis\u002Fai\u002Frules\u002F` (including `csharp.md`, `specs.csharp.md`, and `orleans.md`) and the `cratis-*` skills win where they differ. Specification authoring belongs to **cratis-specifications-csharp**; Cratis core repositories run xUnit v2 on VSTest.\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","\u003C!-- cratis-ai-managed: skills\u002Fplatform-detection\u002FSKILL.md -->\n\n\u003C!-- Modified by Cratis from dotnet's original (MIT): frontmatter, applicability, navigation and the changes listed in NOTICE. Upstream: https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills (plugins\u002Fdotnet-test\u002Fskills\u002Fplatform-detection\u002FSKILL.md; see NOTICE) -->\n\n# Test Platform and Framework Detection\n\nCratis rules in `.cratis\u002Fai\u002Frules\u002F` (including `csharp.md`, `specs.csharp.md`, and `orleans.md`) and the `cratis-*` skills win where they differ. Specification authoring belongs to **cratis-specifications-csharp**; Cratis core repositories run xUnit v2 on VSTest.\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":14,"description":7},"main","feed400071bf3f9f4410a956d73413daa6e1b334",".cratis\u002Fai\u002Fskills\u002Fplatform-detection","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue","https:\u002F\u002Fwww.cratis.io\u002Fprologue\u002F","https:\u002F\u002Fgithub.com\u002FCratis","https:\u002F\u002Fwww.cratis.io","Open-source (MIT) event sourcing and CQRS for .NET and beyond: Chronicle, Arc, Components and Screenplay.","2026-11-14 06:37:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Cratis\u002FPrologue --skill platform-detection",{"tool":39,"command":40},"bunx","bunx skills add Cratis\u002FPrologue --skill platform-detection",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Cratis\u002FPrologue --skill platform-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FSKILL.md",true,[47,51,57],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":15},"LICENSE","许可证",1171,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"NOTICE","OTHER","其他",910,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FNOTICE",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcommand-mode.md","REFERENCE","参考文档",1033,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002Freferences\u002Fcommand-mode.md",[64,72,80,88,96,104],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M78CCRM9594FCYFMCY5W137G","vectorization","Designs, implements, optimizes, and reviews SIMD code in .NET: vectorizing scalar loops with TensorPrimitives, Vector64, Vector128, Vector256, Vector512, or hardware intrinsics, and reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. Use when a .NET loop or SIMD routine is being written or reviewed. Not for performance work unrelated to SIMD.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fvectorization\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78CCJKGDNSDNCMA92PV8GCR","target-authoring","Canonical patterns for writing custom MSBuild targets: DependsOnTargets versus BeforeTargets and AfterTargets, the Build-to-CoreBuild three-level pattern, and the XxxDependsOn chain-extension pattern. Use when diagnosing or fixing custom-target anti-patterns: Directory.Build.targets redefining SDK targets, targets that replace CompileDependsOn instead of extending it, Outputs versus Returns misuse that returns stale results, missing Inputs\u002FOutputs causing needless rebuilds, or missing FileWrites registration. Not for incremental build tuning or general anti-pattern review (use the msbuild skill), or non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Ftarget-authoring\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78CCCWS16JZA36AGB5YVMAN","run-tests","Chooses and runs the repository-compatible .NET test command: classic, VSTest, bridged MTP, or native MTP syntax for MSTest, xUnit, NUnit, and TUnit. Use before running .NET tests or answering with a test command or flags: run the tests, one test, class, category, trait or target framework, combined filters, --filter-query, --no-build, --diag, TRX, coverage collection, crash or hang dumps, filter errors, or unrecognized options. Not for platform identification alone (use platform-detection), writing or debugging test code, interpreting a coverage report (use coverage-analysis), CI investigation, migration, or a persistent hot-reload loop.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Frun-tests\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Frun-tests\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M78CC6VC08Y3WTN4T784DYDY","profiling","Uses the free official .NET diagnostics CLI tools for profiling and runtime investigation in a repository: CPU, GC pressure, allocation growth, exception storms, lock contention, and slow code. Use when a .NET application needs performance or runtime profiling. Not for replacing realistic performance or load tests with ad-hoc tracing, production heap collection without a pause-risk plan, crash dumps (use dump-collect), or benchmark design (use microbenchmarking).","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fprofiling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fprofiling\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M78CBVQKQZ6C9VZAD48GB8AC","orleans","Designs Microsoft Orleans systems from each primitive's purpose and failure model: grains, digital twins, state versus databases, transactions, messaging, streams, timers, reminders, Durable Jobs, stateless workers, grain services, startup, and hosting. Use when a task needs an Orleans design decision: inspect version and topology, choose the primitive, implement, and validate. Not for other actor stacks, batch processing, relational-only CRUD, or advice without an Orleans decision.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M78CBNPV76FVMDRFNS0CAKJZ","msbuild","Investigates MSBuild build failures, diagnoses build performance, and reviews build XML and extension contracts using binary logs. Use for failing dotnet build, restore, pack, or publish; .binlog capture and replay; project, props, and targets conditions; custom-target inputs\u002Foutputs; Import\u002FExists hooks and packed NuGet imports; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Not for legacy or non-SDK project migration, framework or package upgrades, SDK installation, C# refactoring, runtime profiling, assertions after a successful build, or non-MSBuild builds.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fmsbuild\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fmsbuild\u002FSKILL.md",[],[]]