domains / families / software-engineering / platform-detection

platform-detection

separate

Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration. Resolves global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest/xUnit/NUnit/TUnit. DO NOT USE when the user asks to run/filter tests or for commands, flags, TRX/dumps, or test-command/filter errors; use run-tests directly. Do not route hot-reload or migration requests here as the entry skill; mtp-hot-reload may use this skill internally for platform detection.

When to use

• Identify test platform
• Identify test framework
• Determine command mode
• Distinguish SDK-style vs classic project
• Resolve bridge settings
• Handle UseVSTest opt-outs
• Resolve configuration conflicts
• Determine runner usage

When not to use

• Run or filter tests
• Handle test commands or flags
• Process TRX or dumps
• Resolve test-command or filter errors
• Route hot-reload requests
• Route migration requests

Skill page

Source