[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ETDJSDRXKSXGGFTEXXDCZ":3,"skill-same:01M74ETDJSDRXKSXGGFTEXXDCZ":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},"01M74ETDJSDRXKSXGGFTEXXDCZ","binlog-generation",null,"Generates MSBuild binary logs (binlogs) by adding \u002Fbl:{} to dotnet build, test, pack, publish, or restore commands, capturing a full build trace for later investigation. Use when a build error or build-performance problem needs a binlog and none exists. The {} placeholder needs a recent MSBuild; PowerShell must quote the switch as '-bl:{}'. Not for analyzing an existing binlog or measuring build performance (use the msbuild skill) or for non-MSBuild build systems such as npm, Maven, or CMake.","Cratis\u002FArchitecture","Cratis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16456213?v=4","01M6BXRH290K4C8RS4PTKK3HXQ","01M74ET2PT8TQK44HAHJBABW28",0,"MIT","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fbinlog-generation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fbinlog-generation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: binlog-generation\ndescription: 'Generates MSBuild binary logs (binlogs) by adding \u002Fbl:{} to dotnet build, test, pack, publish, or restore commands, capturing a full build trace for later investigation. Use when a build error or build-performance problem needs a binlog and none exists. The {} placeholder needs a recent MSBuild; PowerShell must quote the switch as ''-bl:{}''. Not for analyzing an existing binlog or measuring build performance (use the msbuild skill) or for non-MSBuild build systems such as npm, Maven, or CMake.'\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Fbinlog-generation\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\u002Fbinlog-generation\u002FSKILL.md; see NOTICE) -->\n\n# Generate Binary Logs\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. Binlogs embed project and imported file contents: keep them local and task-scoped.\n\n**Pass the `\u002Fbl` switch when running any MSBuild-based command.** This is a non-negotiable requirement for all .NET builds.\n\n## Commands That Require \u002Fbl\n\nYou MUST add the `\u002Fbl:{}` flag to:\n- `dotnet build`\n- `dotnet test`\n- `dotnet pack`\n- `dotnet publish`\n- `dotnet restore`\n- `msbuild` or `msbuild.exe`\n- Any other command that invokes MSBuild\n\n## Preferred: Use `{}` for Automatic Unique Names\n\n> **Note:** The `{}` placeholder requires MSBuild 17.12+ \u002F .NET 9.0.100 SDK or later.\n\nThe `{}` placeholder in the binlog filename is replaced by MSBuild with a unique identifier, guaranteeing no two builds ever overwrite each other — without needing to track or check existing files.\n\n```bash\n# Every invocation produces a distinct file automatically\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\ndotnet build --configuration Release \u002Fbl:{}\n```\n\n**PowerShell requires quoting the complete switch:**\n\n```powershell\n# Keep the literal {} placeholder in one argument\ndotnet build '-bl:{}'\ndotnet test '-bl:{}'\n```\n\n## Why This Matters\n\n1. **Unique names prevent overwrites** - You can always go back and analyze previous builds\n2. **Failure analysis** - When a build fails, the binlog is already there for immediate analysis\n3. **Comparison** - You can compare builds before and after changes\n4. **No re-running builds** - You never need to re-run a failed build just to generate a binlog\n\n## Examples\n\n```bash\n# ✅ CORRECT - {} generates a unique name automatically (bash\u002Fcmd)\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\n\n# ✅ CORRECT - quote the complete PowerShell argument\ndotnet build '-bl:{}'\ndotnet test '-bl:{}'\n\n# ❌ WRONG - Missing \u002Fbl flag entirely\ndotnet build\ndotnet test\n\n# ❌ WRONG - No filename (overwrites the same msbuild.binlog every time)\ndotnet build \u002Fbl\ndotnet build \u002Fbl\n```\n\n## One build = one binlog\n\nAdd `\u002Fbl:{}` to **every** MSBuild invocation separately — never reuse a name and\nnever rely on bare `\u002Fbl`:\n\n- Building several configurations, projects, or retrying a failed build? Each\n  command still gets its own `\u002Fbl:{}` so the logs never overwrite each other.\n\n```bash\ndotnet build -c Debug   \u002Fbl:{}   # unique file\ndotnet build -c Release \u002Fbl:{}   # another unique file\n```\n\n## Verify the binlog exists\n\nAfter the build, confirm a `.binlog` was actually produced before moving on to\nanalysis — a build that fails *before* MSBuild starts (e.g. a bad argument)\nwrites no binlog:\n\n```bash\nls -1 *.binlog       # bash\ndir \u002Fb *.binlog      # Windows cmd\n```\n\n```powershell\nGet-ChildItem *.binlog   # PowerShell\n```\n\nNote the resulting path so binlog failure analysis or build perf diagnostics\ncan consume it.\n\n## When a Specific Filename Is Required\n\nIf the binlog filename needs to be known upfront (e.g., for CI artifact upload), or if `{}` is not available in the installed MSBuild version, pick a name that won't collide with existing files:\n\n1. Check for existing `*.binlog` files in the directory\n2. Choose a name not already taken (e.g., by incrementing a counter from the highest existing number)\n\n```bash\n# Example: directory contains 3.binlog — use 4.binlog\ndotnet build \u002Fbl:4.binlog\n```\n\n## Cleaning the Repository\n\nWhen cleaning the repository with `git clean`, **always exclude binlog files** to preserve your build history:\n\n```bash\n# ✅ CORRECT - Exclude binlog files from cleaning\ngit clean -fdx -e \"*.binlog\"\n\n# ❌ WRONG - This deletes binlog files (they're usually in .gitignore)\ngit clean -fdx\n```\n\nThis is especially important when iterating on build fixes - you need the binlogs to analyze what changed between builds.\n","\u003C!-- cratis-ai-managed: skills\u002Fbinlog-generation\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\u002Fbinlog-generation\u002FSKILL.md; see NOTICE) -->\n\n# Generate Binary Logs\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. Binlogs embed project and imported file contents: keep them local and task-scoped.\n\n**Pass the `\u002Fbl` switch when running any MSBuild-based command.** This is a non-negotiable requirement for all .NET builds.\n\n## Commands That Require \u002Fbl\n\nYou MUST add the `\u002Fbl:{}` flag to:\n- `dotnet build`\n- `dotnet test`\n- `dotnet pack`\n- `dotnet publish`\n- `dotnet restore`\n- `msbuild` or `msbuild.exe`\n- Any other command that invokes MSBuild\n\n## Preferred: Use `{}` for Automatic Unique Names\n\n> **Note:** The `{}` placeholder requires MSBuild 17.12+ \u002F .NET 9.0.100 SDK or later.\n\nThe `{}` placeholder in the binlog filename is replaced by MSBuild with a unique identifier, guaranteeing no two builds ever overwrite each other — without needing to track or check existing files.\n\n```bash\n# Every invocation produces a distinct file automatically\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\ndotnet build --configuration Release \u002Fbl:{}\n```\n\n**PowerShell requires quoting the complete switch:**\n\n```powershell\n# Keep the literal {} placeholder in one argument\ndotnet build '-bl:{}'\ndotnet test '-bl:{}'\n```\n\n## Why This Matters\n\n1. **Unique names prevent overwrites** - You can always go back and analyze previous builds\n2. **Failure analysis** - When a build fails, the binlog is already there for immediate analysis\n3. **Comparison** - You can compare builds before and after changes\n4. **No re-running builds** - You never need to re-run a failed build just to generate a binlog\n\n## Examples\n\n```bash\n# ✅ CORRECT - {} generates a unique name automatically (bash\u002Fcmd)\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\n\n# ✅ CORRECT - quote the complete PowerShell argument\ndotnet build '-bl:{}'\ndotnet test '-bl:{}'\n\n# ❌ WRONG - Missing \u002Fbl flag entirely\ndotnet build\ndotnet test\n\n# ❌ WRONG - No filename (overwrites the same msbuild.binlog every time)\ndotnet build \u002Fbl\ndotnet build \u002Fbl\n```\n\n## One build = one binlog\n\nAdd `\u002Fbl:{}` to **every** MSBuild invocation separately — never reuse a name and\nnever rely on bare `\u002Fbl`:\n\n- Building several configurations, projects, or retrying a failed build? Each\n  command still gets its own `\u002Fbl:{}` so the logs never overwrite each other.\n\n```bash\ndotnet build -c Debug   \u002Fbl:{}   # unique file\ndotnet build -c Release \u002Fbl:{}   # another unique file\n```\n\n## Verify the binlog exists\n\nAfter the build, confirm a `.binlog` was actually produced before moving on to\nanalysis — a build that fails *before* MSBuild starts (e.g. a bad argument)\nwrites no binlog:\n\n```bash\nls -1 *.binlog       # bash\ndir \u002Fb *.binlog      # Windows cmd\n```\n\n```powershell\nGet-ChildItem *.binlog   # PowerShell\n```\n\nNote the resulting path so binlog failure analysis or build perf diagnostics\ncan consume it.\n\n## When a Specific Filename Is Required\n\nIf the binlog filename needs to be known upfront (e.g., for CI artifact upload), or if `{}` is not available in the installed MSBuild version, pick a name that won't collide with existing files:\n\n1. Check for existing `*.binlog` files in the directory\n2. Choose a name not already taken (e.g., by incrementing a counter from the highest existing number)\n\n```bash\n# Example: directory contains 3.binlog — use 4.binlog\ndotnet build \u002Fbl:4.binlog\n```\n\n## Cleaning the Repository\n\nWhen cleaning the repository with `git clean`, **always exclude binlog files** to preserve your build history:\n\n```bash\n# ✅ CORRECT - Exclude binlog files from cleaning\ngit clean -fdx -e \"*.binlog\"\n\n# ❌ WRONG - This deletes binlog files (they're usually in .gitignore)\ngit clean -fdx\n```\n\nThis is especially important when iterating on build fixes - you need the binlogs to analyze what changed between builds.\n",{"name":5,"license":14,"description":7},"main","68f67ef8a166617b7a614aae2545f77d3c7d5ab8",".cratis\u002Fai\u002Fskills\u002Fbinlog-generation","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture","https:\u002F\u002Fwww.cratis.io\u002Farchitecture\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:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Cratis\u002FArchitecture --skill binlog-generation",{"tool":39,"command":40},"bunx","bunx skills add Cratis\u002FArchitecture --skill binlog-generation",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Cratis\u002FArchitecture --skill binlog-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fbinlog-generation\u002FSKILL.md",true,[47,51],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":15},"LICENSE","许可证",1170,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"NOTICE","OTHER","其他",1279,"https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fbinlog-generation\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},"01M74EZHX4AJ09G25KF026Q7P5","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fvectorization\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\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},"01M74EZD5Y0JQAJATM11TTSZRA","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Ftarget-authoring\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\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},"01M74EZ8ZSW7M8ZR2WBDED4YNA","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Frun-tests\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\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},"01M74EZ4Q0W4B632KY77V6K5EP","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fprofiling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\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},"01M74EZ08N8PGKKZY6Z1DRR5YS","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\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},"01M74EYW35N2Y22QQXANX9TQ1V","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\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FArchitecture\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FSKILL.md",[],[]]