[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVKDTRETH7KNE2EEFD0V3S":3,"skill-same:01M7CVKDTRETH7KNE2EEFD0V3S":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CVKDTRETH7KNE2EEFD0V3S","template-comparison",null,"Compares two or more dotnet new templates side by side to help users choose between them based on parameters, feature support, frameworks, and classifications. USE FOR: deciding between similar templates (webapi vs webapp, blazor vs blazorwasm, console vs worker), producing a side-by-side comparison of parameters and feature support, understanding how templates differ before creating a project. DO NOT USE FOR: creating a project from a template (use template-instantiation), authoring or validating custom templates (use template-authoring and template-validation), general single-template discovery (use template-discovery).","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\u002Ftemplate-comparison\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: template-comparison\ndescription: >\n  Compares two or more dotnet new templates side by side to help users choose between\n  them based on parameters, feature support, frameworks, and classifications.\n  USE FOR: deciding between similar templates (webapi vs webapp, blazor vs\n  blazorwasm, console vs worker), producing a side-by-side comparison of parameters and\n  feature support, understanding how templates differ before creating a project.\n  DO NOT USE FOR: creating a project from a template (use template-instantiation),\n  authoring or validating custom templates (use template-authoring and template-validation),\n  general single-template discovery (use template-discovery).\nlicense: MIT\n---\n\n# Template Comparison\n\nThis skill helps an agent compare 2+ `dotnet new` templates side by side so the user can\npick the right one. It inspects each template's parameters and feature support and renders\na comparison table.\n\n## When to Use\n\n- User is deciding between similar templates (e.g., `webapi` vs `webapp`, `blazor` vs `blazorwasm`)\n- User asks \"which template should I use for X?\"\n- User wants to understand how two or more templates differ before creating a project\n\n## When Not to Use\n\n- User wants to create a project — route to `template-instantiation`\n- User wants to author or validate a custom template — route to `template-authoring` or `template-validation`\n- User just needs to find or inspect a single template — route to `template-discovery`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Template short names | Yes | Two or more template short names to compare (e.g., `webapi`, `webapp`) |\n| Comparison focus | No | Optional aspect to emphasize (auth, AOT, frameworks, interactivity) |\n\n## Workflow\n\n**Evidence contract:** a side-by-side table is useful only when every option claim is\ngrounded in the currently installed templates. Run each `--help` command sequentially,\ncapture the same requested dimensions for each template, and label an unavailable option\nas `Not exposed` rather than guessing or borrowing a flag from another template.\n\n**Decision contract:** optimize the comparison for the user's stated decision, not table\nsize. Cover every requested dimension, omit unrelated option rows, give a scenario-specific\nreason, and include one safe `--dry-run` command for the recommended starting point when it\nwould make the recommendation actionable.\n\n### Step 1: Inspect each template\n\nRun `dotnet new \u003Ctemplate> --help` for each template being compared to collect its\nparameters (names, types, defaults, choices) and supported frameworks:\n\n```bash\ndotnet new webapi --help\ndotnet new webapp --help\n```\n\nIf a template is not installed, search for its provider and report the missing prerequisite.\nInstall it only when the user asked you to modify the environment or approved the install.\n\n> **Run `--help` calls sequentially.** The template engine uses a global mutex, so running\n> several `dotnet new \u003Ctemplate> --help` commands concurrently can fail with a transient\n> \"mutex\"\u002F\"persistence\" error and empty output. Inspect templates one at a time; if a call\n> fails, retry it once before moving on, and still produce the comparison from whatever\n> parameter knowledge you have rather than ending with no answer.\n\n### Step 2: Build the comparison table\n\nProduce a side-by-side table covering:\n\n- **Parameters** — name, type, default, choices\n- **Feature support** — auth, AOT, Docker, controllers, interactivity\n- **Available frameworks** — e.g., net8.0, net9.0, net10.0\n- **Classifications** — categories the template advertises (Web, API, Blazor, etc.)\n\nUse one row per requested decision dimension and cite the observed option name in the cell.\nDo not fill a requested row with general framework knowledge when it is specifically about\nwhat the template generates or exposes.\n\nWhen the user asks about **generated dependencies** without allowing project creation,\ninspect the installed template package's source `.csproj` files. `--help` and `--dry-run`\ndo not reveal package references. Do not create temporary projects merely to inspect them,\nand do not guess current package IDs or test-platform defaults.\n\nExample shape:\n\n| Aspect | `webapi` | `webapp` |\n|--------|----------|----------|\n| Auth (`--auth`) | None, Individual, SingleOrg, Windows | None, Individual, SingleOrg, ... |\n| AOT (`--aot` flag) | present if `dotnet new webapi --help` lists `--aot` | present if `dotnet new webapp --help` lists `--aot` |\n| Controllers (`--use-controllers`) | Yes | n\u002Fa |\n| Interactivity | n\u002Fa | n\u002Fa |\n| Frameworks | net8.0 \u002F net9.0 \u002F net10.0 | net8.0 \u002F net9.0 \u002F net10.0 |\n| Classifications | Web, WebAPI | Web, Razor Pages |\n\n### Step 3: Recommend\n\nEnd with a decisive **Recommendation** line — never leave the user with just a table. Format:\n\n> **Recommendation: `\u003Ctemplate>`** — one sentence tying the choice to the user's stated scenario. (Pick the other if `\u003Ccondition>`.)\n\nThen link to `template-instantiation` to create it. A comparison that ends without naming a winner (or a clear \"it depends on X\") is incomplete — that indecision is what makes this skill tie with a plain answer.\n\n### Decision shortcuts for common pairs\n\nUse these only for the recommendation, not as evidence of current parameter support. Still\ninspect with `--help` before filling the comparison table:\n\n| Pair | Default pick | Because |\n|------|-------------|---------|\n| `webapi` vs `webapp` | **`webapi`** for a JSON\u002FREST backend; `webapp` for server-rendered HTML\u002FRazor Pages | webapi ships controllers\u002Fminimal APIs + OpenAPI, no UI |\n| `blazor` vs `blazorwasm` | **`blazorwasm`** when offline \u002F no server is required; `blazor` (Web App) for flexible server + client interactivity | Standalone WASM runs fully client-side, works offline |\n| `worker` vs `console` | **`worker`** for long-lived\u002Fqueue\u002Fbackground processing | Generic Host: DI, logging, config, graceful shutdown, `IHostedService` lifecycle |\n| `mvc` vs `webapp` | **`webapp`** (Razor Pages) for page-focused apps; `mvc` for controller\u002Fview separation at scale | Razor Pages is lighter for CRUD-style pages |\n\nThese constraints override the shorthand above:\n\n- Choose **`mvc`** when the user explicitly anticipates a large application or shared\n  controller logic, even if its first pages are CRUD-focused.\n- Choose **`blazor` with Server interactivity** over `webapp` when rich interactive forms\n  are central but useful HTML must arrive on the first response. Explain that the initial\n  render is server-produced and that interactive components use the Blazor form\u002Fcomponent\n  model rather than Razor Pages `PageModel`.\n- For **offline support**, choose `blazorwasm` and explain the PWA\u002Fservice-worker requirement,\n  cached-after-first-load behavior, and lack of a required live server for execution.\n- For a **durable queue processor**, choose `worker` and tie the decision to Generic Host\n  lifecycle, dependency injection, configuration, logging, graceful shutdown, and a real\n  durable queue rather than an in-memory loop.\n\n## Validation\n\n- [ ] Every template requested was inspected via `dotnet new \u003Ctemplate> --help`\n- [ ] The comparison covers parameters, feature support, frameworks, and classifications\n- [ ] Differences relevant to the user's scenario are called out explicitly\n- [ ] A recommendation (or clear trade-off) is provided\n- [ ] Unsupported or absent options are labeled instead of guessed\n- [ ] The final recommendation is a single decisive `Recommendation:` line\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Comparing uninstalled templates from memory | Install and inspect each template so the comparison reflects the real parameters and choices. |\n| Assuming feature parity | Parameter names and feature support vary by template — confirm each with `--help`. |\n| Comparing fundamentally different template types | Only compare templates that solve overlapping problems; note when they target different scenarios. |\n\n## More Info\n\n- [dotnet new templates](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fdotnet-new-sdk-templates) — built-in template reference\n- [dotnet new](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fdotnet-new) — CLI reference\n","# Template Comparison\n\nThis skill helps an agent compare 2+ `dotnet new` templates side by side so the user can\npick the right one. It inspects each template's parameters and feature support and renders\na comparison table.\n\n## When to Use\n\n- User is deciding between similar templates (e.g., `webapi` vs `webapp`, `blazor` vs `blazorwasm`)\n- User asks \"which template should I use for X?\"\n- User wants to understand how two or more templates differ before creating a project\n\n## When Not to Use\n\n- User wants to create a project — route to `template-instantiation`\n- User wants to author or validate a custom template — route to `template-authoring` or `template-validation`\n- User just needs to find or inspect a single template — route to `template-discovery`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Template short names | Yes | Two or more template short names to compare (e.g., `webapi`, `webapp`) |\n| Comparison focus | No | Optional aspect to emphasize (auth, AOT, frameworks, interactivity) |\n\n## Workflow\n\n**Evidence contract:** a side-by-side table is useful only when every option claim is\ngrounded in the currently installed templates. Run each `--help` command sequentially,\ncapture the same requested dimensions for each template, and label an unavailable option\nas `Not exposed` rather than guessing or borrowing a flag from another template.\n\n**Decision contract:** optimize the comparison for the user's stated decision, not table\nsize. Cover every requested dimension, omit unrelated option rows, give a scenario-specific\nreason, and include one safe `--dry-run` command for the recommended starting point when it\nwould make the recommendation actionable.\n\n### Step 1: Inspect each template\n\nRun `dotnet new \u003Ctemplate> --help` for each template being compared to collect its\nparameters (names, types, defaults, choices) and supported frameworks:\n\n```bash\ndotnet new webapi --help\ndotnet new webapp --help\n```\n\nIf a template is not installed, search for its provider and report the missing prerequisite.\nInstall it only when the user asked you to modify the environment or approved the install.\n\n> **Run `--help` calls sequentially.** The template engine uses a global mutex, so running\n> several `dotnet new \u003Ctemplate> --help` commands concurrently can fail with a transient\n> \"mutex\"\u002F\"persistence\" error and empty output. Inspect templates one at a time; if a call\n> fails, retry it once before moving on, and still produce the comparison from whatever\n> parameter knowledge you have rather than ending with no answer.\n\n### Step 2: Build the comparison table\n\nProduce a side-by-side table covering:\n\n- **Parameters** — name, type, default, choices\n- **Feature support** — auth, AOT, Docker, controllers, interactivity\n- **Available frameworks** — e.g., net8.0, net9.0, net10.0\n- **Classifications** — categories the template advertises (Web, API, Blazor, etc.)\n\nUse one row per requested decision dimension and cite the observed option name in the cell.\nDo not fill a requested row with general framework knowledge when it is specifically about\nwhat the template generates or exposes.\n\nWhen the user asks about **generated dependencies** without allowing project creation,\ninspect the installed template package's source `.csproj` files. `--help` and `--dry-run`\ndo not reveal package references. Do not create temporary projects merely to inspect them,\nand do not guess current package IDs or test-platform defaults.\n\nExample shape:\n\n| Aspect | `webapi` | `webapp` |\n|--------|----------|----------|\n| Auth (`--auth`) | None, Individual, SingleOrg, Windows | None, Individual, SingleOrg, ... |\n| AOT (`--aot` flag) | present if `dotnet new webapi --help` lists `--aot` | present if `dotnet new webapp --help` lists `--aot` |\n| Controllers (`--use-controllers`) | Yes | n\u002Fa |\n| Interactivity | n\u002Fa | n\u002Fa |\n| Frameworks | net8.0 \u002F net9.0 \u002F net10.0 | net8.0 \u002F net9.0 \u002F net10.0 |\n| Classifications | Web, WebAPI | Web, Razor Pages |\n\n### Step 3: Recommend\n\nEnd with a decisive **Recommendation** line — never leave the user with just a table. Format:\n\n> **Recommendation: `\u003Ctemplate>`** — one sentence tying the choice to the user's stated scenario. (Pick the other if `\u003Ccondition>`.)\n\nThen link to `template-instantiation` to create it. A comparison that ends without naming a winner (or a clear \"it depends on X\") is incomplete — that indecision is what makes this skill tie with a plain answer.\n\n### Decision shortcuts for common pairs\n\nUse these only for the recommendation, not as evidence of current parameter support. Still\ninspect with `--help` before filling the comparison table:\n\n| Pair | Default pick | Because |\n|------|-------------|---------|\n| `webapi` vs `webapp` | **`webapi`** for a JSON\u002FREST backend; `webapp` for server-rendered HTML\u002FRazor Pages | webapi ships controllers\u002Fminimal APIs + OpenAPI, no UI |\n| `blazor` vs `blazorwasm` | **`blazorwasm`** when offline \u002F no server is required; `blazor` (Web App) for flexible server + client interactivity | Standalone WASM runs fully client-side, works offline |\n| `worker` vs `console` | **`worker`** for long-lived\u002Fqueue\u002Fbackground processing | Generic Host: DI, logging, config, graceful shutdown, `IHostedService` lifecycle |\n| `mvc` vs `webapp` | **`webapp`** (Razor Pages) for page-focused apps; `mvc` for controller\u002Fview separation at scale | Razor Pages is lighter for CRUD-style pages |\n\nThese constraints override the shorthand above:\n\n- Choose **`mvc`** when the user explicitly anticipates a large application or shared\n  controller logic, even if its first pages are CRUD-focused.\n- Choose **`blazor` with Server interactivity** over `webapp` when rich interactive forms\n  are central but useful HTML must arrive on the first response. Explain that the initial\n  render is server-produced and that interactive components use the Blazor form\u002Fcomponent\n  model rather than Razor Pages `PageModel`.\n- For **offline support**, choose `blazorwasm` and explain the PWA\u002Fservice-worker requirement,\n  cached-after-first-load behavior, and lack of a required live server for execution.\n- For a **durable queue processor**, choose `worker` and tie the decision to Generic Host\n  lifecycle, dependency injection, configuration, logging, graceful shutdown, and a real\n  durable queue rather than an in-memory loop.\n\n## Validation\n\n- [ ] Every template requested was inspected via `dotnet new \u003Ctemplate> --help`\n- [ ] The comparison covers parameters, feature support, frameworks, and classifications\n- [ ] Differences relevant to the user's scenario are called out explicitly\n- [ ] A recommendation (or clear trade-off) is provided\n- [ ] Unsupported or absent options are labeled instead of guessed\n- [ ] The final recommendation is a single decisive `Recommendation:` line\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Comparing uninstalled templates from memory | Install and inspect each template so the comparison reflects the real parameters and choices. |\n| Assuming feature parity | Parameter names and feature support vary by template — confirm each with `--help`. |\n| Comparing fundamentally different template types | Only compare templates that solve overlapping problems; note when they target different scenarios. |\n\n## More Info\n\n- [dotnet new templates](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fdotnet-new-sdk-templates) — built-in template reference\n- [dotnet new](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fdotnet-new) — CLI reference\n",{"name":5,"license":14,"description":23},"Compares two or more dotnet new templates side by side to help users choose between them based on parameters, feature support, frameworks, and classifications. USE FOR: deciding between similar templates (webapi vs webapp, blazor vs blazorwasm, console vs worker), producing a side-by-side comparison of parameters and feature support, understanding how templates differ before creating a project. DO NOT USE FOR: creating a project from a template (use template-instantiation), authoring or validating custom templates (use template-authoring and template-validation), general single-template discovery (use template-discovery).\n","main","ccab8dffc0ecc173838f51e4c5f0d3b51a704f41","plugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-comparison","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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add deadmade\u002Fdead-agent-skills --skill template-comparison",{"tool":38,"command":39},"bunx","bunx skills add deadmade\u002Fdead-agent-skills --skill template-comparison",{"tool":41,"command":42},"pnpm","pnpm dlx skills add deadmade\u002Fdead-agent-skills --skill template-comparison","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-comparison\u002FSKILL.md",true,[],[47,54,63,71,78,85],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]