[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CASRAF5AG6467V0PPB1CK":3,"skill-same:01M78CASRAF5AG6467V0PPB1CK":57},{"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},"01M78CASRAF5AG6467V0PPB1CK","eliminate-redundant-restores",null,"Removes repeated NuGet restores from multi-step .NET builds safely, including Directory.Build.rsp with -restore and safe restore suppression. Use when separate build, test, or publish steps each restore, or when NETSDK1004 or NETSDK1047 appears after --no-restore. Not for a slow first restore, a build with only one restore, version or lock-file errors, or general build slowness without a measured baseline (use the msbuild skill).","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\u002Feliminate-redundant-restores\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Feliminate-redundant-restores\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eliminate-redundant-restores\ndescription: 'Removes repeated NuGet restores from multi-step .NET builds safely, including Directory.Build.rsp with -restore and safe restore suppression. Use when separate build, test, or publish steps each restore, or when NETSDK1004 or NETSDK1047 appears after --no-restore. Not for a slow first restore, a build with only one restore, version or lock-file errors, or general build slowness without a measured baseline (use the msbuild skill).'\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Feliminate-redundant-restores\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-msbuild\u002Fskills\u002Feliminate-redundant-restores\u002FSKILL.md; see NOTICE) -->\n\n# Eliminate Redundant Restores\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.\n\nA no-op restore still evaluates every project and checks restore state, so each extra restore in a multi-step build costs seconds to tens of seconds in a large repo. The cure is easy to get wrong: `--no-restore` on a step that no earlier restore actually covered turns a slow build into a failed one. This skill finds which invocations restore, proves which are already covered, and changes only those.\n\n## When to Use\n\n- A pipeline or script runs several `dotnet`\u002F`msbuild` steps and the log shows restore output in more than one of them\n- A restore step exists, yet later steps still print `Determining projects to restore...`\n- A repository `Directory.Build.rsp` or the active MSBuild installation's `MSBuild.rsp` contains `-restore`\n- Someone asks where `--no-restore` or `-restore:false` can safely be added\n- `NETSDK1004` or `NETSDK1047` appeared after `--no-restore` was added\n\n## When Not to Use\n\n- The first restore is slow (feed latency, missing package cache): that is caching, not redundancy\n- There is only one restore across all invocations: nothing to deduplicate\n- Restore errors about versions, lock files or auditing: fix the restore itself\n- Unranked \"why is my build slow\": start with build perf baseline, then build perf diagnostics\n\n## Inputs\n\nDiscover repository inputs in the working directory; do not ask the user for paths.\n\n- CI definitions (`*.yml`, `.github\u002Fworkflows`, `azure-pipelines*.yml`, `Jenkinsfile`) and build scripts (`build.cmd`, `build.sh`, `build.ps1`, `eng\u002F`)\n- `Directory.Build.rsp`, `Directory.Build.props`\u002F`.targets`, `NuGet.config`\n- Auto-loaded `MSBuild.rsp` beside the active MSBuild executable, or response files passed explicitly with `@file`. A repository-local `MSBuild.rsp` is not auto-loaded\n- Restore evidence if present: step logs or a binlog\n\n## Workflow\n\n### Step 1: Confirm restore is repeated and worth removing\n\n- Log evidence: `Determining projects to restore...` or `All projects are up-to-date for restore.` once per invocation.\n- Binlog evidence: restore evaluations carry the global properties `MSBuildRestoreSessionId` and `ExcludeRestorePackageImports=true`; the Target Performance Summary lists `Restore` with N calls.\n- Quantify each no-op restore. If there is one restore, or the repeated ones total about a second, report \"nothing worth removing\" and stop without editing.\n\n### Step 2: Inventory every invocation in execution order\n\n| Invocation | Restores? |\n|---|---|\n| `dotnet build`, `test`, `publish`, `pack` | Implicitly, unless `--no-restore`; also check inherited rsp flags |\n| `dotnet run` | Implicitly before building; `--no-restore` can still inherit rsp restore on older SDKs. With `--no-build`, no build or restore runs |\n| `dotnet test`, `publish`, `pack` with `--no-build` | No implicit restore, but an rsp `-restore` can still enable restore; add `--no-restore -restore:false` |\n| `dotnet msbuild`, `msbuild.exe`, CI MSBuild tasks | With `-restore` or `-t:Restore`, including flags inherited from repository `Directory.Build.rsp` or installation-level `MSBuild.rsp`, even when a step looks build-only |\n| `dotnet restore`, `nuget restore`, `msbuild -t:Restore` | Explicit restore |\n| CI build task with a \"restore packages\" option | Check its default |\n\nStarting with .NET SDK 9.0.1xx, `--no-restore` forwards `-restore:false` to override rsp flags; older SDKs can still inherit `-restore` despite skipping the CLI's implicit restore. Whenever an rsp enables restore, use the version-independent `--no-restore -restore:false` with `dotnet build`, `test`, `publish` or `pack`, even with `--no-build`. `dotnet msbuild` and `msbuild.exe` take `-restore:false`, not `--no-restore`.\n\n`dotnet run` does not expose the MSBuild `-restore:false` override. With an rsp on older SDKs, first build using `dotnet build --no-restore -restore:false`, then run using `dotnet run --no-build` with the same project, configuration, framework and runtime inputs (or execute the built DLL directly). Passing `-restore:false` to `dotnet run` is not a restore-suppression strategy.\n\n### Step 3: Decide per invocation\n\nKeep the first restore. Skip a later one only when all four checks pass:\n\n| Check | If it fails |\n|---|---|\n| **Same project set.** A restore covers its entry project or solution and that project's ProjectReference closure. It does not cover a project in another solution or `.slnf`, a tool built from another path, or a project an orchestrating `.proj` builds through the `MSBuild` task (`-restore` on the orchestrator leaves those unrestored and they fail with NETSDK1004) | Keep restore on that step, or add the project to the explicit restore step |\n| **Same restore inputs.** `-r`\u002F`--runtime`, RID-producing `-a`\u002F`--arch`, `--os`, `--ucr`\u002F`--use-current-runtime`, `TargetFramework(s)`, `RuntimeIdentifier(s)`, `PublishAot`, package sources (`--source`, `--configfile`, `RestoreSources`), `RestorePackagesPath`, and any `-p:` value a PackageReference condition reads. Architecture\u002FOS options combine with the SDK's current RID; `--use-current-runtime` selects it. Missing RID targets fail with NETSDK1047 (`Assets file ... doesn't have a target for 'net10.0\u002Flinux-x64'`) | Match the effective RID in the explicit restore (for example `publish --os linux --arch x64` requires `restore -r linux-x64`), or keep restore on the later step. A generic restore does not cover these aliases merely because there is no `-r`. Do not require `SelfContained=true` on restore solely because publish is self-contained: RID-only restore covers ordinary SDK projects. Match `Configuration` or `SelfContained` only if repository conditions change package inputs |\n| **Same available restore state.** Earlier `project.assets.json` files must exist where the later invocation looks for them. Match `--artifacts-path`, `UseArtifactsOutput`\u002F`ArtifactsPath`, and `MSBuildProjectExtensionsPath`\u002F`BaseIntermediateOutputPath`; another job or workspace does not automatically share these files | Align the explicit restore's output layout with build\u002Ftest, or retain restore in the later workspace. For `build --artifacts-path artifacts --no-restore`, use `restore --artifacts-path artifacts` first; ordinary `obj\u002F` assets do not cover that layout |\n| **Nothing changes packages in between.** A step that generates or edits a project, runs `dotnet add package`, rewrites `Directory.Packages.props` or `NuGet.config` invalidates the earlier restore | Move the explicit restore after that step |\n\n### Step 4: Apply the smallest change\n\n- One explicit restore carrying every restore input, then `--no-restore`, `-restore:false` or `--no-build` on later steps.\n- Several `dotnet test` steps over one solution: build once, then `dotnet test --no-build` on each. Add `--no-restore -restore:false` if an rsp enables restore, including on .NET 8 and earlier. `--no-restore` alone still rebuilds.\n- Keep self-contained publish settings. A `publish --no-build` still needs a prior build with matching configuration, framework, RID and self-contained output; restore compatibility does not prove that build outputs exist.\n- Scope the change to CI and scripts. Leave `-restore` in `Directory.Build.rsp`, because developers rely on it; pass `-restore:false` per invocation instead.\n- Never remove the first restore. If it is a `--locked-mode` gate, keep it there.\n- Do not bundle static graph restore or package caching into this change.\n\n```bash\n# One restore carries every input later steps use\ndotnet restore MyApp.sln -r linux-x64\n# Explicit overrides also work when an rsp enables restore on older SDKs\ndotnet build MyApp.sln -c Release --no-restore -restore:false\ndotnet test MyApp.sln -c Release --no-build --no-restore -restore:false\ndotnet publish src\u002FApi -c Release -r linux-x64 --no-restore -restore:false\n# msbuild invocations need the explicit switch if an rsp file adds -restore\ndotnet msbuild Packaging.proj -t:Pack -restore:false\n```\n\n### Step 5: Validate and report truthfully\n\n1. Run the changed pipeline or script end to end in a clean temporary copy (no `obj\u002F`, no `project.assets.json`). A project that was never restored only fails there. YAML syntax or flag-presence checks do not validate restore coverage or test execution. If you cannot run it, say \"not validated\" and list the steps and projects to confirm.\n2. Success evidence: every later step passed; `Restore` calls (binlog) or `Determining projects to restore` lines fell from N to the expected count; for a time claim, before\u002Fafter medians of at least three runs.\n3. Report a restore failure (NETSDK1004, NETSDK1047) separately from a build failure, and never claim success after either.\n\n## Output\n\nExplain which steps restored, which earlier restore covers them, what changed, and what remains unvalidated. State whether redundant restores were removed or no change was needed, keeping the required first restore. Use prose or a findings table as appropriate; no fixed table headings or verdict syntax are required.\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---|---|\n| Adding `--no-restore` to every command | Apply the Step 3 checks per step |\n| Missing that an rsp adds `-restore` to \"build-only\" msbuild steps | Search for `*.rsp` before concluding a step does not restore |\n| Deleting `-restore` from `Directory.Build.rsp` | Override per CI invocation; the rsp serves developers |\n| Orchestrator `.proj` restored, children not | Restore each child explicitly, or keep restore on the step that builds it |\n| Publishing with `-r`, architecture\u002FOS options, or `--use-current-runtime` after a generic restore | Restore with the same effective runtime identifier, including SDK-host defaults used by the aliases |\n| A generator step edits PackageReferences after restore | Restore after the generator |\n","\u003C!-- cratis-ai-managed: skills\u002Feliminate-redundant-restores\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-msbuild\u002Fskills\u002Feliminate-redundant-restores\u002FSKILL.md; see NOTICE) -->\n\n# Eliminate Redundant Restores\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.\n\nA no-op restore still evaluates every project and checks restore state, so each extra restore in a multi-step build costs seconds to tens of seconds in a large repo. The cure is easy to get wrong: `--no-restore` on a step that no earlier restore actually covered turns a slow build into a failed one. This skill finds which invocations restore, proves which are already covered, and changes only those.\n\n## When to Use\n\n- A pipeline or script runs several `dotnet`\u002F`msbuild` steps and the log shows restore output in more than one of them\n- A restore step exists, yet later steps still print `Determining projects to restore...`\n- A repository `Directory.Build.rsp` or the active MSBuild installation's `MSBuild.rsp` contains `-restore`\n- Someone asks where `--no-restore` or `-restore:false` can safely be added\n- `NETSDK1004` or `NETSDK1047` appeared after `--no-restore` was added\n\n## When Not to Use\n\n- The first restore is slow (feed latency, missing package cache): that is caching, not redundancy\n- There is only one restore across all invocations: nothing to deduplicate\n- Restore errors about versions, lock files or auditing: fix the restore itself\n- Unranked \"why is my build slow\": start with build perf baseline, then build perf diagnostics\n\n## Inputs\n\nDiscover repository inputs in the working directory; do not ask the user for paths.\n\n- CI definitions (`*.yml`, `.github\u002Fworkflows`, `azure-pipelines*.yml`, `Jenkinsfile`) and build scripts (`build.cmd`, `build.sh`, `build.ps1`, `eng\u002F`)\n- `Directory.Build.rsp`, `Directory.Build.props`\u002F`.targets`, `NuGet.config`\n- Auto-loaded `MSBuild.rsp` beside the active MSBuild executable, or response files passed explicitly with `@file`. A repository-local `MSBuild.rsp` is not auto-loaded\n- Restore evidence if present: step logs or a binlog\n\n## Workflow\n\n### Step 1: Confirm restore is repeated and worth removing\n\n- Log evidence: `Determining projects to restore...` or `All projects are up-to-date for restore.` once per invocation.\n- Binlog evidence: restore evaluations carry the global properties `MSBuildRestoreSessionId` and `ExcludeRestorePackageImports=true`; the Target Performance Summary lists `Restore` with N calls.\n- Quantify each no-op restore. If there is one restore, or the repeated ones total about a second, report \"nothing worth removing\" and stop without editing.\n\n### Step 2: Inventory every invocation in execution order\n\n| Invocation | Restores? |\n|---|---|\n| `dotnet build`, `test`, `publish`, `pack` | Implicitly, unless `--no-restore`; also check inherited rsp flags |\n| `dotnet run` | Implicitly before building; `--no-restore` can still inherit rsp restore on older SDKs. With `--no-build`, no build or restore runs |\n| `dotnet test`, `publish`, `pack` with `--no-build` | No implicit restore, but an rsp `-restore` can still enable restore; add `--no-restore -restore:false` |\n| `dotnet msbuild`, `msbuild.exe`, CI MSBuild tasks | With `-restore` or `-t:Restore`, including flags inherited from repository `Directory.Build.rsp` or installation-level `MSBuild.rsp`, even when a step looks build-only |\n| `dotnet restore`, `nuget restore`, `msbuild -t:Restore` | Explicit restore |\n| CI build task with a \"restore packages\" option | Check its default |\n\nStarting with .NET SDK 9.0.1xx, `--no-restore` forwards `-restore:false` to override rsp flags; older SDKs can still inherit `-restore` despite skipping the CLI's implicit restore. Whenever an rsp enables restore, use the version-independent `--no-restore -restore:false` with `dotnet build`, `test`, `publish` or `pack`, even with `--no-build`. `dotnet msbuild` and `msbuild.exe` take `-restore:false`, not `--no-restore`.\n\n`dotnet run` does not expose the MSBuild `-restore:false` override. With an rsp on older SDKs, first build using `dotnet build --no-restore -restore:false`, then run using `dotnet run --no-build` with the same project, configuration, framework and runtime inputs (or execute the built DLL directly). Passing `-restore:false` to `dotnet run` is not a restore-suppression strategy.\n\n### Step 3: Decide per invocation\n\nKeep the first restore. Skip a later one only when all four checks pass:\n\n| Check | If it fails |\n|---|---|\n| **Same project set.** A restore covers its entry project or solution and that project's ProjectReference closure. It does not cover a project in another solution or `.slnf`, a tool built from another path, or a project an orchestrating `.proj` builds through the `MSBuild` task (`-restore` on the orchestrator leaves those unrestored and they fail with NETSDK1004) | Keep restore on that step, or add the project to the explicit restore step |\n| **Same restore inputs.** `-r`\u002F`--runtime`, RID-producing `-a`\u002F`--arch`, `--os`, `--ucr`\u002F`--use-current-runtime`, `TargetFramework(s)`, `RuntimeIdentifier(s)`, `PublishAot`, package sources (`--source`, `--configfile`, `RestoreSources`), `RestorePackagesPath`, and any `-p:` value a PackageReference condition reads. Architecture\u002FOS options combine with the SDK's current RID; `--use-current-runtime` selects it. Missing RID targets fail with NETSDK1047 (`Assets file ... doesn't have a target for 'net10.0\u002Flinux-x64'`) | Match the effective RID in the explicit restore (for example `publish --os linux --arch x64` requires `restore -r linux-x64`), or keep restore on the later step. A generic restore does not cover these aliases merely because there is no `-r`. Do not require `SelfContained=true` on restore solely because publish is self-contained: RID-only restore covers ordinary SDK projects. Match `Configuration` or `SelfContained` only if repository conditions change package inputs |\n| **Same available restore state.** Earlier `project.assets.json` files must exist where the later invocation looks for them. Match `--artifacts-path`, `UseArtifactsOutput`\u002F`ArtifactsPath`, and `MSBuildProjectExtensionsPath`\u002F`BaseIntermediateOutputPath`; another job or workspace does not automatically share these files | Align the explicit restore's output layout with build\u002Ftest, or retain restore in the later workspace. For `build --artifacts-path artifacts --no-restore`, use `restore --artifacts-path artifacts` first; ordinary `obj\u002F` assets do not cover that layout |\n| **Nothing changes packages in between.** A step that generates or edits a project, runs `dotnet add package`, rewrites `Directory.Packages.props` or `NuGet.config` invalidates the earlier restore | Move the explicit restore after that step |\n\n### Step 4: Apply the smallest change\n\n- One explicit restore carrying every restore input, then `--no-restore`, `-restore:false` or `--no-build` on later steps.\n- Several `dotnet test` steps over one solution: build once, then `dotnet test --no-build` on each. Add `--no-restore -restore:false` if an rsp enables restore, including on .NET 8 and earlier. `--no-restore` alone still rebuilds.\n- Keep self-contained publish settings. A `publish --no-build` still needs a prior build with matching configuration, framework, RID and self-contained output; restore compatibility does not prove that build outputs exist.\n- Scope the change to CI and scripts. Leave `-restore` in `Directory.Build.rsp`, because developers rely on it; pass `-restore:false` per invocation instead.\n- Never remove the first restore. If it is a `--locked-mode` gate, keep it there.\n- Do not bundle static graph restore or package caching into this change.\n\n```bash\n# One restore carries every input later steps use\ndotnet restore MyApp.sln -r linux-x64\n# Explicit overrides also work when an rsp enables restore on older SDKs\ndotnet build MyApp.sln -c Release --no-restore -restore:false\ndotnet test MyApp.sln -c Release --no-build --no-restore -restore:false\ndotnet publish src\u002FApi -c Release -r linux-x64 --no-restore -restore:false\n# msbuild invocations need the explicit switch if an rsp file adds -restore\ndotnet msbuild Packaging.proj -t:Pack -restore:false\n```\n\n### Step 5: Validate and report truthfully\n\n1. Run the changed pipeline or script end to end in a clean temporary copy (no `obj\u002F`, no `project.assets.json`). A project that was never restored only fails there. YAML syntax or flag-presence checks do not validate restore coverage or test execution. If you cannot run it, say \"not validated\" and list the steps and projects to confirm.\n2. Success evidence: every later step passed; `Restore` calls (binlog) or `Determining projects to restore` lines fell from N to the expected count; for a time claim, before\u002Fafter medians of at least three runs.\n3. Report a restore failure (NETSDK1004, NETSDK1047) separately from a build failure, and never claim success after either.\n\n## Output\n\nExplain which steps restored, which earlier restore covers them, what changed, and what remains unvalidated. State whether redundant restores were removed or no change was needed, keeping the required first restore. Use prose or a findings table as appropriate; no fixed table headings or verdict syntax are required.\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---|---|\n| Adding `--no-restore` to every command | Apply the Step 3 checks per step |\n| Missing that an rsp adds `-restore` to \"build-only\" msbuild steps | Search for `*.rsp` before concluding a step does not restore |\n| Deleting `-restore` from `Directory.Build.rsp` | Override per CI invocation; the rsp serves developers |\n| Orchestrator `.proj` restored, children not | Restore each child explicitly, or keep restore on the step that builds it |\n| Publishing with `-r`, architecture\u002FOS options, or `--use-current-runtime` after a generic restore | Restore with the same effective runtime identifier, including SDK-host defaults used by the aliases |\n| A generator step edits PackageReferences after restore | Restore after the generator |\n",{"name":5,"license":14,"description":7},"main","feed400071bf3f9f4410a956d73413daa6e1b334",".cratis\u002Fai\u002Fskills\u002Feliminate-redundant-restores","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 eliminate-redundant-restores",{"tool":39,"command":40},"bunx","bunx skills add Cratis\u002FPrologue --skill eliminate-redundant-restores",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Cratis\u002FPrologue --skill eliminate-redundant-restores","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Feliminate-redundant-restores\u002FSKILL.md",true,[47,51],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":15},"LICENSE","许可证",1181,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"NOTICE","OTHER","其他",1019,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Feliminate-redundant-restores\u002FNOTICE",[58,66,74,82,90,98],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M78CC14WNAP1Y77ZMM4VD29A","platform-detection","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.","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",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]