[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CV0TYF2FHWQP0GE960P5HN":3,"skill-same:01M7CV0TYF2FHWQP0GE960P5HN":45},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CV0TYF2FHWQP0GE960P5HN","build-parallelism",null,"Analyze MSBuild scheduling across at least two distinct projects in a solution\u002Ffilter\u002FBuild.proj. USE FOR: measured idle workers, -m not scaling, serial ProjectReference critical paths, graph builds, MSBuild Projects-list scheduling. DO NOT USE FOR: duplicate executions or invariant-generation races (find-repeated-work-within-one-build), non-MSBuild systems.","deadmade\u002Fdead-agent-skills","deadmade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130925709?v=4","01M7CTQ65AGYR4J9K9TX0YR9V3","01M7CTQ66B4VMJFEDZP4EKKE6K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fbuild-parallelism\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: build-parallelism\ndescription: \"Analyze MSBuild scheduling across at least two distinct projects in a solution\u002Ffilter\u002FBuild.proj. USE FOR: measured idle workers, -m not scaling, serial ProjectReference critical paths, graph builds, MSBuild Projects-list scheduling. DO NOT USE FOR: duplicate executions or invariant-generation races (find-repeated-work-within-one-build), non-MSBuild systems.\"\nlicense: MIT\n---\n\n## Diagnose a slow parallel build (start here)\n\nWork this checklist in order — it targets the usual root cause (a serial\ndependency chain that no number of cores can parallelize):\n\n1. **Check how many worker nodes actually built the solution.** Capture a\n   binlog with `dotnet build \u002Fbl:{}` (PowerShell: `dotnet build '-bl:{}'`) and\n   inspect the node timeline to see whether more than one node ran. Every\n   `dotnet` CLI command built on the SDK's MSBuild-forwarding path (`build`,\n   `msbuild`, `test`, `pack`, `publish`, etc.) enables `\u002Fmaxcpucount` (multiple\n   nodes) by default; `-m:1` forces a single node. A direct `MSBuild.exe`\n   invocation is sequential by default, so pass `-m` explicitly to enable\n   parallel worker nodes there.\n2. **Find the critical path.** From the binlog, read per-project timings and the\n   node timeline. If total build time ≈ the sum of the projects on one\n   dependency chain, that chain — not CPU count — is the bottleneck.\n3. **Name the chain explicitly**, e.g. `Core → Api → Web → Tests`. A long serial\n   chain stays serial no matter how large `-m` is, because each project waits on\n   its predecessor.\n4. **Look for unnecessary `ProjectReference` edges** that lengthen the chain — a\n   reference that only needs build order (not the output assembly), or one that\n   could be a `PackageReference`, forces serialization it doesn't need.\n5. **Recommend flattening**: break false dependencies so independent projects\n   build concurrently, and consider `\u002Fgraph` for better scheduling.\n\n## MSBuild Parallelism Model\n\n- `\u002Fmaxcpucount` (or `-m`): number of worker nodes (processes)\n- Every `dotnet` CLI command (`build`, `msbuild`, `test`, `pack`, `publish`,\n  etc.) passes `\u002Fmaxcpucount` by default via the SDK's shared MSBuild-forwarding\n  path; `-m:1` overrides it with one node\n- A direct `MSBuild.exe` invocation is sequential by default and requires an\n  explicit `-m`\n- Recommended: `-m` without a number = use all logical processors\n- Each node builds one project at a time\n- Projects are scheduled based on dependency graph\n\n## Project Dependency Graph\n\n- MSBuild builds projects in dependency order (topological sort)\n- Critical path: longest chain of dependent projects determines minimum build time\n- Bottleneck: if project A depends on B, C, D and B takes 60s while C and D take 5s, B is the bottleneck\n- Diagnosis: replay binlog to diagnostic log with `performancesummary` and check Project Performance Summary — shows per-project time; grep for `node.*assigned` to check scheduling\n- Wide graphs (many independent projects) parallelize well; deep graphs (long chains) don't\n\n## Graph Build Mode (`\u002Fgraph`)\n\n- `dotnet build \u002Fgraph` or `msbuild \u002Fgraph`\n- What it changes: MSBuild constructs the full project dependency graph BEFORE building\n- Benefits: better scheduling, avoids redundant evaluations, enables isolated builds\n- Limitations: all projects must use `\u003CProjectReference>` (no programmatic MSBuild task references)\n- When to use: large solutions with many projects, CI builds\n- When NOT to use: projects that dynamically discover references at build time\n\n## Optimizing Project References\n\n- Reduce a `\u003CProjectReference>` only after proving it is unnecessary; a slow but\n  valid dependency must stay in the graph\n- Use `\u003CProjectReference ... SkipGetTargetFrameworkProperties=\"true\">` to avoid extra evaluations\n- `\u003CProjectReference ... ReferenceOutputAssembly=\"false\">` for build-order-only dependencies\n- Consider if a ProjectReference should be a PackageReference instead (pre-built NuGet)\n- Use `solution filters` (`.slnf`) to build subsets of the solution\n\n## BuildInParallel\n\n- `\u003CMSBuild Projects=\"@(ProjectsToBuild)\" BuildInParallel=\"true\" \u002F>` in custom targets\n- Without `BuildInParallel=\"true\"`, MSBuild task batches projects sequentially\n- Ensure `\u002Fmaxcpucount` > 1 for this to have effect\n\n## Multi-threaded MSBuild Tasks\n\n- Individual tasks can run multi-threaded within a single project build\n- Tasks implementing `IMultiThreadableTask` can run on multiple threads\n- Tasks must declare thread-safety via `[MSBuildMultiThreadableTask]`\n\n## Analyzing Parallelism with Binlog\n\n### Text-log replay\n\nStep-by-step:\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl \"-flp:v=diag;logfile=full.log;performancesummary\"`\n2. Check Project Performance Summary at the end of `full.log`\n3. Ideal: build time should be much less than sum of project times (parallelism)\n4. If build time ≈ sum of project times: too many serial dependencies, or one slow project blocking others\n5. `grep 'Target Performance Summary' -A 30 full.log` → find the bottleneck targets\n6. Consider splitting large projects or optimizing the critical path\n\n## CI\u002FCD Parallelism Tips\n\n- Use `-m` in CI (many CI runners have multiple cores)\n- Consider splitting solution into build stages for extreme parallelism\n- Use build caching (NuGet lock files, deterministic builds) to avoid rebuilding unchanged projects\n- `dotnet build \u002Fgraph` works well with structured CI pipelines\n","## Diagnose a slow parallel build (start here)\n\nWork this checklist in order — it targets the usual root cause (a serial\ndependency chain that no number of cores can parallelize):\n\n1. **Check how many worker nodes actually built the solution.** Capture a\n   binlog with `dotnet build \u002Fbl:{}` (PowerShell: `dotnet build '-bl:{}'`) and\n   inspect the node timeline to see whether more than one node ran. Every\n   `dotnet` CLI command built on the SDK's MSBuild-forwarding path (`build`,\n   `msbuild`, `test`, `pack`, `publish`, etc.) enables `\u002Fmaxcpucount` (multiple\n   nodes) by default; `-m:1` forces a single node. A direct `MSBuild.exe`\n   invocation is sequential by default, so pass `-m` explicitly to enable\n   parallel worker nodes there.\n2. **Find the critical path.** From the binlog, read per-project timings and the\n   node timeline. If total build time ≈ the sum of the projects on one\n   dependency chain, that chain — not CPU count — is the bottleneck.\n3. **Name the chain explicitly**, e.g. `Core → Api → Web → Tests`. A long serial\n   chain stays serial no matter how large `-m` is, because each project waits on\n   its predecessor.\n4. **Look for unnecessary `ProjectReference` edges** that lengthen the chain — a\n   reference that only needs build order (not the output assembly), or one that\n   could be a `PackageReference`, forces serialization it doesn't need.\n5. **Recommend flattening**: break false dependencies so independent projects\n   build concurrently, and consider `\u002Fgraph` for better scheduling.\n\n## MSBuild Parallelism Model\n\n- `\u002Fmaxcpucount` (or `-m`): number of worker nodes (processes)\n- Every `dotnet` CLI command (`build`, `msbuild`, `test`, `pack`, `publish`,\n  etc.) passes `\u002Fmaxcpucount` by default via the SDK's shared MSBuild-forwarding\n  path; `-m:1` overrides it with one node\n- A direct `MSBuild.exe` invocation is sequential by default and requires an\n  explicit `-m`\n- Recommended: `-m` without a number = use all logical processors\n- Each node builds one project at a time\n- Projects are scheduled based on dependency graph\n\n## Project Dependency Graph\n\n- MSBuild builds projects in dependency order (topological sort)\n- Critical path: longest chain of dependent projects determines minimum build time\n- Bottleneck: if project A depends on B, C, D and B takes 60s while C and D take 5s, B is the bottleneck\n- Diagnosis: replay binlog to diagnostic log with `performancesummary` and check Project Performance Summary — shows per-project time; grep for `node.*assigned` to check scheduling\n- Wide graphs (many independent projects) parallelize well; deep graphs (long chains) don't\n\n## Graph Build Mode (`\u002Fgraph`)\n\n- `dotnet build \u002Fgraph` or `msbuild \u002Fgraph`\n- What it changes: MSBuild constructs the full project dependency graph BEFORE building\n- Benefits: better scheduling, avoids redundant evaluations, enables isolated builds\n- Limitations: all projects must use `\u003CProjectReference>` (no programmatic MSBuild task references)\n- When to use: large solutions with many projects, CI builds\n- When NOT to use: projects that dynamically discover references at build time\n\n## Optimizing Project References\n\n- Reduce a `\u003CProjectReference>` only after proving it is unnecessary; a slow but\n  valid dependency must stay in the graph\n- Use `\u003CProjectReference ... SkipGetTargetFrameworkProperties=\"true\">` to avoid extra evaluations\n- `\u003CProjectReference ... ReferenceOutputAssembly=\"false\">` for build-order-only dependencies\n- Consider if a ProjectReference should be a PackageReference instead (pre-built NuGet)\n- Use `solution filters` (`.slnf`) to build subsets of the solution\n\n## BuildInParallel\n\n- `\u003CMSBuild Projects=\"@(ProjectsToBuild)\" BuildInParallel=\"true\" \u002F>` in custom targets\n- Without `BuildInParallel=\"true\"`, MSBuild task batches projects sequentially\n- Ensure `\u002Fmaxcpucount` > 1 for this to have effect\n\n## Multi-threaded MSBuild Tasks\n\n- Individual tasks can run multi-threaded within a single project build\n- Tasks implementing `IMultiThreadableTask` can run on multiple threads\n- Tasks must declare thread-safety via `[MSBuildMultiThreadableTask]`\n\n## Analyzing Parallelism with Binlog\n\n### Text-log replay\n\nStep-by-step:\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl \"-flp:v=diag;logfile=full.log;performancesummary\"`\n2. Check Project Performance Summary at the end of `full.log`\n3. Ideal: build time should be much less than sum of project times (parallelism)\n4. If build time ≈ sum of project times: too many serial dependencies, or one slow project blocking others\n5. `grep 'Target Performance Summary' -A 30 full.log` → find the bottleneck targets\n6. Consider splitting large projects or optimizing the critical path\n\n## CI\u002FCD Parallelism Tips\n\n- Use `-m` in CI (many CI runners have multiple cores)\n- Consider splitting solution into build stages for extreme parallelism\n- Use build caching (NuGet lock files, deterministic builds) to avoid rebuilding unchanged projects\n- `dotnet build \u002Fgraph` works well with structured CI pipelines\n",{"name":5,"license":14,"description":7},"main","ccab8dffc0ecc173838f51e4c5f0d3b51a704f41","plugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fbuild-parallelism","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills","https:\u002F\u002Fgithub.com\u002Fdeadmade","https:\u002F\u002Fdeadmade.github.io\u002F","Blood, an Ocean of blood","2026-11-14 02:03:31",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add deadmade\u002Fdead-agent-skills --skill build-parallelism",{"tool":37,"command":38},"bunx","bunx skills add deadmade\u002Fdead-agent-skills --skill build-parallelism",{"tool":40,"command":41},"pnpm","pnpm dlx skills add deadmade\u002Fdead-agent-skills --skill build-parallelism","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fbuild-parallelism\u002FSKILL.md",true,[],[46,53,62,70,77,84],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7CVRBFTXSTTQ7F5P6PJEFYA","rust-best-practices","Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Frust-skills\u002Fskills\u002Frust-best-practices\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7CVR0W7B8EGTNPSPA7FPC4Z","postgres-database-migration","Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases.\n\n**Trigger when user asks to:**\n- Test a schema migration before applying it to production\n- Add, remove, or rename columns safely on a live table\n- Change a column's data type without downtime\n- Add or drop indexes, constraints, or foreign keys on large tables\n- Understand which ALTER TABLE operations lock the table\n- Roll back a failed migration\n- Plan a zero-downtime migration strategy\n- Fork a database to test a migration safely\n\nCovers: lock-level reference for every common DDL operation, safe migration patterns, fork-based testing, zero-downtime column changes, index creation, constraint addition, backfill strategies, pre\u002Fpost-migration validation, and rollback planning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7CVQWK20ASAZN5VETZC8J99","postgres-best-practices","Best practices and guidelines for working with Postgres. Covers schema design, indexing strategies, query optimization, migrations, and common pitfalls. Use when writing SQL, designing database schemas, optimizing queries, or setting up a Postgres database.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7CVQ5CY7AQHY7A2Y99RE6A7","writing-mstest-tests","ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7CVPWJZ63GB0810F0SCGZ1K","winforms-expert","Create, modify, debug, or review Windows Forms applications only when the request contains a concrete Windows Forms marker. USE FOR: WinForms, Windows Forms, System.Windows.Forms, WinForms Form or UserControl designer files (*.Designer.cs or *.Designer.vb), Visual Studio WinForms Designer, TableLayoutPanel, BindingSource, DataGridView, Control.InvokeAsync, component-tray ownership, or custom control serialization. DO NOT USE FOR: WPF or WPF XAML, including Window.InputBindings, KeyBinding, commands, or DataContext; .NET MAUI; Avalonia; or any request where none of the listed Windows Forms markers is present.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwinforms-expert\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7CVPR0QFZ1HMJ6GZRBQAQ7W","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fvectorization\u002FSKILL.md",[],[]]