[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D2ASQ6VGF3GXFRVTN7FSS2":3,"skill-same:01M7D2ASQ6VGF3GXFRVTN7FSS2":58},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D2ASQ6VGF3GXFRVTN7FSS2","dump-collect",null,"Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb\u002Fwindbg\u002Fdotnet-dump analyze, profiling or tracing, or for .NET Framework processes.","itsmejay18\u002FAI-Skills-for-My-Development-Stack","itsmejay18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167779943?v=4","01M7CZRFC6DDZA5V2CX8WDSZED","Jay Jemino Ababon ","01M7CZRFCVRNW1SFHSQXEJ3CQN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F14-Debugging-Troubleshooting\u002Fdump-collect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dump-collect\ndescription: \"Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb\u002Fwindbg\u002Fdotnet-dump analyze, profiling or tracing, or for .NET Framework processes.\"\nlicense: MIT\n---\n\n# .NET Crash Dump Collection\n\nThis skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers.\n\n## Stop Signals\n\n🚨 **Read before starting any workflow.**\n\n- **Stop after dumps are enabled or collected.** Do not open, analyze, or triage dump files.\n- **If the user already has a dump file**, this skill does not cover analysis. Let them know analysis is out of scope.\n- **Do not install analysis tools** (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using `lldb` for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis.\n- **Do not trace root cause** of crashes. Report the dump file location and move on.\n- **Do not modify application code.** Configuration is environment-only (env vars, OS settings, container specs).\n\n## Step 1 — Identify the Scenario\n\nAsk or determine:\n\n1. **Goal**: Enable automatic crash dumps, or capture a dump from a running process right now?\n2. **Platform**: Linux, macOS, or Windows? Running in a container (Docker\u002FKubernetes)?\n3. **Runtime**: CoreCLR or NativeAOT?\n\n### Detecting CoreCLR vs NativeAOT\n\n**From a binary file (Linux\u002FmacOS):**\n```bash\n# CoreCLR — has IL metadata \u002F managed entry point\nstrings \u003Cbinary> | grep -q \"CorExeMain\" && echo \"CoreCLR\"\n\n# NativeAOT — has Redhawk runtime symbols\nstrings \u003Cbinary> | grep -q \"Rhp\" && echo \"NativeAOT\"\n\n# On macOS\u002FLinux, also try:\nnm \u003Cbinary> 2>\u002Fdev\u002Fnull | grep -qi \"Rhp\" && echo \"NativeAOT\"\n```\n\n**From a binary file (Windows):**\n```powershell\n# CoreCLR — has a CLI header (IL entry point)\ndumpbin \u002Fclrheader \u003Cbinary.exe> | Select-String \"CLI Header\" -Quiet\n\n# NativeAOT — no CLI header, has Redhawk symbols\ndumpbin \u002Fsymbols \u003Cbinary.exe> | Select-String \"Rhp\" -Quiet\n```\n\n**From a running process (Linux):**\n```bash\n# Resolve the binary, then use the same file checks\nBINARY=$(readlink \u002Fproc\u002F\u003Cpid>\u002Fexe)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (macOS):**\n```bash\n# Resolve the binary path from the running process\nBINARY=$(ps -o comm= -p \u003Cpid>)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (Windows PowerShell):**\n```powershell\n# CoreCLR — loads coreclr.dll\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"coreclr.dll\"\n\n# .NET Framework — loads clr.dll (this skill does not apply)\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"clr.dll\"\n```\n\n> **If the app is .NET Framework (`clr.dll`), stop.** This skill covers modern .NET (CoreCLR and NativeAOT) only.\n>\n> **If neither CoreCLR nor NativeAOT is detected, stop.** This skill only applies to .NET applications — do not proceed.\n\n## Step 2 — Load the Appropriate Reference\n\nBased on the scenario identified in Step 1, read the relevant reference file:\n\n| Scenario | Reference |\n|----------|-----------|\n| CoreCLR app (any platform) | `references\u002Fcoreclr-dumps.md` |\n| NativeAOT app (any platform) | `references\u002Fnativeaot-dumps.md` |\n| Any app in Docker or Kubernetes | `references\u002Fcontainer-dumps.md` (then also load the runtime-specific reference) |\n\n## Step 3 — Execute\n\nFollow the instructions in the loaded reference to configure or collect dumps. Always:\n\n1. **Confirm the dump output directory exists** and has write permissions before enabling collection.\n2. **Report the dump file path** back to the user after collection succeeds.\n3. **Verify configuration took effect** — for env vars, echo them; for OS settings, read them back.\n4. **Remind the user to disable automatic dumps if they were enabled temporarily** — remove or unset `DOTNET_DbgEnableMiniDump` and related env vars to avoid accumulating dump files.\n","# .NET Crash Dump Collection\n\nThis skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers.\n\n## Stop Signals\n\n🚨 **Read before starting any workflow.**\n\n- **Stop after dumps are enabled or collected.** Do not open, analyze, or triage dump files.\n- **If the user already has a dump file**, this skill does not cover analysis. Let them know analysis is out of scope.\n- **Do not install analysis tools** (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using `lldb` for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis.\n- **Do not trace root cause** of crashes. Report the dump file location and move on.\n- **Do not modify application code.** Configuration is environment-only (env vars, OS settings, container specs).\n\n## Step 1 — Identify the Scenario\n\nAsk or determine:\n\n1. **Goal**: Enable automatic crash dumps, or capture a dump from a running process right now?\n2. **Platform**: Linux, macOS, or Windows? Running in a container (Docker\u002FKubernetes)?\n3. **Runtime**: CoreCLR or NativeAOT?\n\n### Detecting CoreCLR vs NativeAOT\n\n**From a binary file (Linux\u002FmacOS):**\n```bash\n# CoreCLR — has IL metadata \u002F managed entry point\nstrings \u003Cbinary> | grep -q \"CorExeMain\" && echo \"CoreCLR\"\n\n# NativeAOT — has Redhawk runtime symbols\nstrings \u003Cbinary> | grep -q \"Rhp\" && echo \"NativeAOT\"\n\n# On macOS\u002FLinux, also try:\nnm \u003Cbinary> 2>\u002Fdev\u002Fnull | grep -qi \"Rhp\" && echo \"NativeAOT\"\n```\n\n**From a binary file (Windows):**\n```powershell\n# CoreCLR — has a CLI header (IL entry point)\ndumpbin \u002Fclrheader \u003Cbinary.exe> | Select-String \"CLI Header\" -Quiet\n\n# NativeAOT — no CLI header, has Redhawk symbols\ndumpbin \u002Fsymbols \u003Cbinary.exe> | Select-String \"Rhp\" -Quiet\n```\n\n**From a running process (Linux):**\n```bash\n# Resolve the binary, then use the same file checks\nBINARY=$(readlink \u002Fproc\u002F\u003Cpid>\u002Fexe)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (macOS):**\n```bash\n# Resolve the binary path from the running process\nBINARY=$(ps -o comm= -p \u003Cpid>)\nstrings \"$BINARY\" | grep -q \"CorExeMain\" && echo \"CoreCLR\" || echo \"NativeAOT\"\n```\n\n**From a running process (Windows PowerShell):**\n```powershell\n# CoreCLR — loads coreclr.dll\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"coreclr.dll\"\n\n# .NET Framework — loads clr.dll (this skill does not apply)\n(Get-Process -Id \u003Cpid>).Modules.ModuleName -contains \"clr.dll\"\n```\n\n> **If the app is .NET Framework (`clr.dll`), stop.** This skill covers modern .NET (CoreCLR and NativeAOT) only.\n>\n> **If neither CoreCLR nor NativeAOT is detected, stop.** This skill only applies to .NET applications — do not proceed.\n\n## Step 2 — Load the Appropriate Reference\n\nBased on the scenario identified in Step 1, read the relevant reference file:\n\n| Scenario | Reference |\n|----------|-----------|\n| CoreCLR app (any platform) | `references\u002Fcoreclr-dumps.md` |\n| NativeAOT app (any platform) | `references\u002Fnativeaot-dumps.md` |\n| Any app in Docker or Kubernetes | `references\u002Fcontainer-dumps.md` (then also load the runtime-specific reference) |\n\n## Step 3 — Execute\n\nFollow the instructions in the loaded reference to configure or collect dumps. Always:\n\n1. **Confirm the dump output directory exists** and has write permissions before enabling collection.\n2. **Report the dump file path** back to the user after collection succeeds.\n3. **Verify configuration took effect** — for env vars, echo them; for OS settings, read them back.\n4. **Remind the user to disable automatic dumps if they were enabled temporarily** — remove or unset `DOTNET_DbgEnableMiniDump` and related env vars to avoid accumulating dump files.\n",{"name":5,"license":15,"description":7},"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","14-Debugging-Troubleshooting\u002Fdump-collect","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack","https:\u002F\u002Fgithub.com\u002Fitsmejay18","2026-09-18 16:06:36",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill dump-collect",{"tool":36,"command":37},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill dump-collect",{"tool":39,"command":40},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill dump-collect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F14-Debugging-Troubleshooting\u002Fdump-collect\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fcontainer-dumps.md","REFERENCE","参考文档",11485,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F14-Debugging-Troubleshooting\u002Fdump-collect\u002Freferences\u002Fcontainer-dumps.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcoreclr-dumps.md",2971,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F14-Debugging-Troubleshooting\u002Fdump-collect\u002Freferences\u002Fcoreclr-dumps.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fnativeaot-dumps.md",8775,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F14-Debugging-Troubleshooting\u002Fdump-collect\u002Freferences\u002Fnativeaot-dumps.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D2RKBHPZ3E1RNN5DWHT550","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 Vector\u003CT>, 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\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D2RDJ7RN3QK8GJR0QTER1D","resolve-project-references","Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fresolve-project-references\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D2R1H2GTNZYHG9YRX3JDQW","optimizing-ef-core-queries","Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database schema. For EF Core, not Dapper or raw ADO.NET.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Foptimizing-ef-core-queries\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D2QREG04W1YT0NEBHEW5C9","microbenchmarking","Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling\u002Ftracing .NET code (dotnet-trace, PerfView), production telemetry, or load\u002Fstress testing (Crank, k6).","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fmicrobenchmarking\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D2QGE175XWPZVACVH2868Z","incremental-build","Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs\u002FOutputs on custom targets, volatile properties in output paths (timestamps\u002FGUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fincremental-build\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7D2Q1DQTC6K49R73WQTTPSB","eval-performance","Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Feval-performance\u002FSKILL.md",[],[]]