[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DYZTQV681EPVD6PBYY023A":3,"skill-same:01M6DYZTQV681EPVD6PBYY023A":100},{"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":23,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6DYZTQV681EPVD6PBYY023A","xunit",null,"Write, run, or repair .NET tests that use xUnit with the right package, CLI, and runner guidance. USE FOR: xUnit v2 or xUnit v3 projects; adding, running, debugging, or repairing xUnit tests; choosing between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: TUnit projects; MSTest projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","managedcode\u002Fdotnet-skills","managedcode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78253589?v=4","01M6DYDJR3EG8KB5G4PC65XCTT","Managed Code","01M6DYDJX0ZT432N04NYJW89DN",511,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"files","running","when","inspect","relevant","tunit","tests","platform","commands","project","repair","runner","do","testing","context","edit","write","repo","projects","repository","run","packages","debugging","cli","2026-11-10 10:12:30",false,"---\nname: xunit\ndescription: \"Write, run, or repair .NET tests that use xUnit with the right package, CLI, and runner guidance. USE FOR: xUnit v2 or xUnit v3 projects; adding, running, debugging, or repairing xUnit tests; choosing between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: TUnit projects; MSTest projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.\"\ncompatibility: \"Requires a .NET solution or project with xUnit packages; respects the repo's `AGENTS.md` commands first.\"\n---\n\n# xUnit.net\n\n## Diagnostic Output Budget\n\nKeep native test progress and ANSI visible; use the detected runner's supported flags (`--progress on --ansi on` for MTP\u002FTUnit), not MTP switches on VSTest. Keep console logs at `Warning` or higher and one concise final summary. Do not replay progress redraws, successful-test output, or Information\u002FDebug\u002FTrace logs into model context. On failure\u002Fcrash, show only the failing test\u002Fresource, root error, and relevant stack frames; deduplicate and cap each diagnostic response at 80 lines \u002F 8 KiB. Never dump entire console\u002Fhost\u002Fbrowser logs, HTML, TRX, or crash artifacts. Keep necessary artifacts size-bounded outside context, link them, and inspect exact bounded excerpts. Preserve the runner exit code through capture\u002Ffiltering; disclose truncation. Silence alone does not establish a hang.\n\n## Trigger On\n\n- the repo uses xUnit v2 or xUnit v3\n- you need to add, run, debug, or repair xUnit tests\n- the team is unsure whether a project is using VSTest or Microsoft.Testing.Platform\n\n## Value\n\n- produce a concrete project delta: code, docs, config, tests, CI, or review artifact\n- reduce ambiguity through explicit planning, verification, and final validation skills\n- leave reusable project context so future tasks are faster and safer\n\n## Do Not Use For\n\n- TUnit projects\n- MSTest projects\n- generic test strategy with no xUnit-specific mechanics\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- the test project file and package references\n- the active runner model for the test project\n\n## Quick Start\n\n1. Read the nearest `AGENTS.md` and confirm scope and constraints.\n2. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable.\n3. Return the `Required Result Format` with concrete artifacts and verification evidence.\n\n## Workflow\n\n1. Detect the active xUnit model before changing commands:\n   - `xunit` usually means v2\n   - `xunit.v3` means v3\n   - `xunit.runner.visualstudio` plus `Microsoft.NET.Test.Sdk` usually means VSTest compatibility is enabled\n   - `TestingPlatformDotnetTestSupport` or `UseMicrosoftTestingPlatformRunner` means Microsoft.Testing.Platform is in play\n2. Read the repo's real `test` command from `AGENTS.md`. If the repo has no explicit command yet, start with `dotnet test PROJECT_OR_SOLUTION`.\n3. Keep the runner model consistent:\n   - xUnit v2 usually runs through VSTest\n   - xUnit v3 can run as a standalone executable with `dotnet run`\n   - xUnit v3 can also integrate with Microsoft.Testing.Platform\n   - do not mix VSTest-only switches into Microsoft.Testing.Platform runs\n4. Run the narrowest useful scope first:\n   - one project\n   - one class\n   - one trait\n   - one method\n5. Prefer `[Theory]` for stable data-driven coverage and `[Fact]` for single-path invariant checks.\n6. Keep `xunit.analyzers` enabled when present. Fix analyzer findings instead of muting them casually.\n\n## Bootstrap When Missing\n\nIf xUnit is requested but not configured:\n\n1. Detect current framework first:\n   - `rg -n \"xunit(\\\\.v3)?|xunit\\\\.runner\\\\.visualstudio|TestingPlatformDotnetTestSupport|UseMicrosoftTestingPlatformRunner|TUnit|MSTest\" -g '*.csproj' .`\n2. If the repo currently uses `TUnit` or `MSTest`, do not auto-migrate. Return `status: not_applicable` unless migration is explicitly requested.\n3. For explicit xUnit adoption, add packages to the target test project:\n   - `dotnet add TEST_PROJECT.csproj package xunit.v3`\n   - optional VSTest bridge: `dotnet add TEST_PROJECT.csproj package xunit.runner.visualstudio`\n4. Add repo test commands and runner notes to `AGENTS.md`.\n5. Run `dotnet test TEST_PROJECT.csproj` or repo-defined xUnit command and return `status: configured` or `status: improved`.\n\n\n## Deliver\n\n- xUnit tests that match the repo's active xUnit version and runner\n- commands that work in local and CI runs\n- focused verification before broader suite execution\n\n## Validate\n\n- the chosen CLI matches the active runner model\n- test filters or focused runs are valid for that runner\n- tests use deterministic inputs and assertions\n- xUnit-specific analyzers remain active unless the repo documents an exception\n\n## Ralph Loop\n\nUse the Ralph Loop for every task, including docs, architecture, testing, and tooling work.\n\n1. Plan first (mandatory):\n   - analyze current state\n   - define target outcome, constraints, and risks\n   - write a detailed execution plan\n   - list final validation skills to run at the end, with order and reason\n2. Execute one planned step and produce a concrete delta.\n3. Review the result and capture findings with actionable next fixes.\n4. Apply fixes in small batches and rerun the relevant checks or review steps.\n5. Update the plan after each iteration.\n6. Repeat until outcomes are acceptable or only explicit exceptions remain.\n7. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path.\n\n### Required Result Format\n\n- `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked`\n- `plan`: concise plan and current iteration step\n- `actions_taken`: concrete changes made\n- `validation_skills`: final skills run, or skipped with reasons\n- `verification`: commands, checks, or review evidence summary\n- `remaining`: top unresolved items or `none`\n\nFor setup-only requests with no execution, return `status: configured` and exact next commands.\n\n## Load References\n\n- [references\u002Fxunit.md](references\u002Fxunit.md)\n- [references\u002Fpatterns.md](references\u002Fpatterns.md)\n- [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md)\n\n## Example Requests\n\n- \"Run this xUnit suite correctly.\"\n- \"Fix our xUnit v3 test command.\"\n- \"Add an xUnit regression test and keep CI compatible.\"\n","# xUnit.net\n\n## Diagnostic Output Budget\n\nKeep native test progress and ANSI visible; use the detected runner's supported flags (`--progress on --ansi on` for MTP\u002FTUnit), not MTP switches on VSTest. Keep console logs at `Warning` or higher and one concise final summary. Do not replay progress redraws, successful-test output, or Information\u002FDebug\u002FTrace logs into model context. On failure\u002Fcrash, show only the failing test\u002Fresource, root error, and relevant stack frames; deduplicate and cap each diagnostic response at 80 lines \u002F 8 KiB. Never dump entire console\u002Fhost\u002Fbrowser logs, HTML, TRX, or crash artifacts. Keep necessary artifacts size-bounded outside context, link them, and inspect exact bounded excerpts. Preserve the runner exit code through capture\u002Ffiltering; disclose truncation. Silence alone does not establish a hang.\n\n## Trigger On\n\n- the repo uses xUnit v2 or xUnit v3\n- you need to add, run, debug, or repair xUnit tests\n- the team is unsure whether a project is using VSTest or Microsoft.Testing.Platform\n\n## Value\n\n- produce a concrete project delta: code, docs, config, tests, CI, or review artifact\n- reduce ambiguity through explicit planning, verification, and final validation skills\n- leave reusable project context so future tasks are faster and safer\n\n## Do Not Use For\n\n- TUnit projects\n- MSTest projects\n- generic test strategy with no xUnit-specific mechanics\n\n## Inputs\n\n- the nearest `AGENTS.md`\n- the test project file and package references\n- the active runner model for the test project\n\n## Quick Start\n\n1. Read the nearest `AGENTS.md` and confirm scope and constraints.\n2. Run this skill's `Workflow` through the `Ralph Loop` until outcomes are acceptable.\n3. Return the `Required Result Format` with concrete artifacts and verification evidence.\n\n## Workflow\n\n1. Detect the active xUnit model before changing commands:\n   - `xunit` usually means v2\n   - `xunit.v3` means v3\n   - `xunit.runner.visualstudio` plus `Microsoft.NET.Test.Sdk` usually means VSTest compatibility is enabled\n   - `TestingPlatformDotnetTestSupport` or `UseMicrosoftTestingPlatformRunner` means Microsoft.Testing.Platform is in play\n2. Read the repo's real `test` command from `AGENTS.md`. If the repo has no explicit command yet, start with `dotnet test PROJECT_OR_SOLUTION`.\n3. Keep the runner model consistent:\n   - xUnit v2 usually runs through VSTest\n   - xUnit v3 can run as a standalone executable with `dotnet run`\n   - xUnit v3 can also integrate with Microsoft.Testing.Platform\n   - do not mix VSTest-only switches into Microsoft.Testing.Platform runs\n4. Run the narrowest useful scope first:\n   - one project\n   - one class\n   - one trait\n   - one method\n5. Prefer `[Theory]` for stable data-driven coverage and `[Fact]` for single-path invariant checks.\n6. Keep `xunit.analyzers` enabled when present. Fix analyzer findings instead of muting them casually.\n\n## Bootstrap When Missing\n\nIf xUnit is requested but not configured:\n\n1. Detect current framework first:\n   - `rg -n \"xunit(\\\\.v3)?|xunit\\\\.runner\\\\.visualstudio|TestingPlatformDotnetTestSupport|UseMicrosoftTestingPlatformRunner|TUnit|MSTest\" -g '*.csproj' .`\n2. If the repo currently uses `TUnit` or `MSTest`, do not auto-migrate. Return `status: not_applicable` unless migration is explicitly requested.\n3. For explicit xUnit adoption, add packages to the target test project:\n   - `dotnet add TEST_PROJECT.csproj package xunit.v3`\n   - optional VSTest bridge: `dotnet add TEST_PROJECT.csproj package xunit.runner.visualstudio`\n4. Add repo test commands and runner notes to `AGENTS.md`.\n5. Run `dotnet test TEST_PROJECT.csproj` or repo-defined xUnit command and return `status: configured` or `status: improved`.\n\n\n## Deliver\n\n- xUnit tests that match the repo's active xUnit version and runner\n- commands that work in local and CI runs\n- focused verification before broader suite execution\n\n## Validate\n\n- the chosen CLI matches the active runner model\n- test filters or focused runs are valid for that runner\n- tests use deterministic inputs and assertions\n- xUnit-specific analyzers remain active unless the repo documents an exception\n\n## Ralph Loop\n\nUse the Ralph Loop for every task, including docs, architecture, testing, and tooling work.\n\n1. Plan first (mandatory):\n   - analyze current state\n   - define target outcome, constraints, and risks\n   - write a detailed execution plan\n   - list final validation skills to run at the end, with order and reason\n2. Execute one planned step and produce a concrete delta.\n3. Review the result and capture findings with actionable next fixes.\n4. Apply fixes in small batches and rerun the relevant checks or review steps.\n5. Update the plan after each iteration.\n6. Repeat until outcomes are acceptable or only explicit exceptions remain.\n7. If a dependency is missing, bootstrap it or return `status: not_applicable` with explicit reason and fallback path.\n\n### Required Result Format\n\n- `status`: `complete` | `clean` | `improved` | `configured` | `not_applicable` | `blocked`\n- `plan`: concise plan and current iteration step\n- `actions_taken`: concrete changes made\n- `validation_skills`: final skills run, or skipped with reasons\n- `verification`: commands, checks, or review evidence summary\n- `remaining`: top unresolved items or `none`\n\nFor setup-only requests with no execution, return `status: configured` and exact next commands.\n\n## Load References\n\n- [references\u002Fxunit.md](references\u002Fxunit.md)\n- [references\u002Fpatterns.md](references\u002Fpatterns.md)\n- [references\u002Fanti-patterns.md](references\u002Fanti-patterns.md)\n\n## Example Requests\n\n- \"Run this xUnit suite correctly.\"\n- \"Fix our xUnit v3 test command.\"\n- \"Add an xUnit regression test and keep CI compatible.\"\n",{"name":5,"description":7,"compatibility":53},"Requires a .NET solution or project with xUnit packages; respects the repo's `AGENTS.md` commands first.","main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit",41,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills","https:\u002F\u002Fskills.managed-code.com","https:\u002F\u002Fgithub.com\u002Fmanagedcode","https:\u002F\u002Fwww.managed-code.com","Open Source Community for .NET Developers: Reliable, Actively Maintained, and Community-Driven. Made in Ukraine 🇺🇦 with ❤️","2026-11-10 19:58:06",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add managedcode\u002Fdotnet-skills --skill xunit",{"tool":70,"command":71},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill xunit",{"tool":73,"command":74},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill xunit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002FSKILL.md",true,[78,84,88,92,96],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"index.json","REFERENCE","参考文档",621,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fsoc\u002Fhunting\u002Fmimikatz\u002Fextract\u002Findex.json",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"manifest.json",99,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002Fmanifest.json",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fanti-patterns.md",16197,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002Freferences\u002Fanti-patterns.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpatterns.md",9999,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002Freferences\u002Fpatterns.md",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fxunit.md",3217,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTesting\u002FxUnit\u002Fskills\u002Fxunit\u002Freferences\u002Fxunit.md",[101,131,153,184,194,221],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":115,"publishedAt":48},"01M6DYQE1Y9FHAQHEDTVFQ3447","xtwitter-scraper","Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key configuration, pagination, binary exports, raw responses, retries, and webhook\u002Fevent flows in .NET. DO NOT USE FOR: unrelated stacks; direct browser automation; generic social-media strategy; or code that does not call Xquik. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FXTwitterScraper\u002Fskills\u002Fxtwitter-scraper\u002FSKILL.md",[107,110],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[116,117,118,44,119,120,121,43,122,123,124,125,39,126,127,24,128,32,129,130],"xtwitter scraper","browser automation","workflows","code","browser","search","api","Media","api client","access","unrelated","webhooks","social","modeling","webhook",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":143,"publishedAt":48},"01M6DYQ9S4PE1H6G8MCH9T21HR","sep","Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser\u002Fwriter options, and low-allocation row\u002Fcolumn workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FSep\u002Fskills\u002Fsep\u002FSKILL.md",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":141,"categoryName":142,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000036","内容创作者",[133,144,145,118,146,44,43,147,148,149,39,38,126,24,36,150,151,33,32,152],"writing","performance","tasks","data","parsing","parser","writer","options","high-performance",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":48},"01M6DZS2DNEPXCGGF6SSCW6G5V","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fwebgpu-claude-skill\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,26],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","applications","js","node","syntax","guide","use","language","three","compute","post","processing","with","renderer","for","materials","wgsl","effects",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":48},"01M6DZS0BQXW2B56A289XF1X76","roslynk","Use Roslynk for semantic inspection and edits of *.cs, *.razor and *.cshtml solution files.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Froslynk\u002Fskills\u002Froslynk\u002FSKILL.md",[],[186,172,24,191,192,180,193],"semantic","razor","inspection",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":48},"01M6DZRW6MEJCVW80K3S4XV60K","system-text-json-net11","Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[201,202,203,204,144,205,206,207,208,209,210,172,211,212,213,214,36,215,216,217,218,180,219,220,26],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","only","probe","guidance","later","type","dictionary","naming","targeting","custom","generic",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"publishedAt":48},"01M6DZRRJP3S662NFSG1RSPQQ7","process-api-net11","Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText\u002FBytes\u002FLines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fprocess-api-net11\u002FSKILL.md",[227,228],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[122,230,231,232,44,233,167,201,172,213,214,36,234,235,236,237,218,180,238],"process","process api net11","diagnostics","start","basic","processes","output","usage","new"]