[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVK5ZCNA86CBF16DN7TT16":3,"skill-same:01M7CVK5ZCNA86CBF16DN7TT16":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},"01M7CVK5ZCNA86CBF16DN7TT16","template-authoring",null,"Guides creation and validation of custom dotnet new templates from existing projects. Generates a .template.config\u002Ftemplate.json that preserves the source project's conventions. USE FOR: creating a reusable dotnet new template from an existing project, bootstrapping .template.config\u002Ftemplate.json with correct identity, shortName, parameters, and post-actions, adding parameters or conditional content to a template you are authoring, validating the template.json you are authoring before publishing, packaging templates as NuGet packages for distribution. DO NOT USE FOR: validating an existing template.json as a standalone task (use template-validation), finding or using existing templates (use template-discovery and template-instantiation), MSBuild project file issues unrelated to template authoring, NuGet package publishing (only template packaging structure).","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-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: template-authoring\ndescription: >\n  Guides creation and validation of custom dotnet new templates from existing projects.\n  Generates a .template.config\u002Ftemplate.json that preserves the source project's conventions.\n  USE FOR: creating a reusable dotnet new template from an existing project, bootstrapping\n  .template.config\u002Ftemplate.json with correct identity, shortName, parameters, and\n  post-actions, adding parameters or conditional content to a template you are authoring,\n  validating the template.json you are authoring before publishing,\n  packaging templates as NuGet packages for distribution.\n  DO NOT USE FOR: validating an existing template.json as a standalone task (use\n  template-validation), finding or using existing templates (use template-discovery and\n  template-instantiation), MSBuild project file issues unrelated to template authoring,\n  NuGet package publishing (only template packaging structure).\nlicense: MIT\n---\n\n# Template Authoring\n\nThis skill helps an agent create and validate custom `dotnet new` templates. It guides bootstrapping templates from existing projects and validates `template.json` files for authoring issues before publishing.\n\n## When to Use\n\n- User wants to create a reusable template from an existing .csproj\n- User wants to validate a template.json they are authoring before publishing\n- User is setting up `.template.config\u002Ftemplate.json` from scratch\n- User wants to package a template for NuGet distribution\n\n## When Not to Use\n\n- User wants to find or use existing templates — route to `template-discovery` or `template-instantiation`\n- User has MSBuild issues unrelated to template authoring — route to `dotnet-msbuild` plugin\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Source project path | For creation | Path to the .csproj to use as template source |\n| template.json path | For validation | Path to an existing template.json to validate |\n| Template name | For creation | Human-readable name for the template |\n| Short name | Recommended | Short name for `dotnet new \u003Cshortname>` usage |\n\n## Workflow\n\n### Rules that change the answer\n\nUse these structures exactly; do not invent fields from other template features.\n\n**Deliver the requested artifact.** When the user says \"show\", \"write\", or \"give me the\ncontent\", put the complete JSON\u002FXML in the final response even if you also wrote it to disk.\nNever edit this skill's `SKILL.md` or plugin documentation as a substitute for authoring the\nuser's template. Only create or modify template files when the user requested file changes and\nthe target template\u002Fproject is present.\n\n| Need | Correct structure | Never use |\n|------|-------------------|-----------|\n| Conditional XML in a `.csproj` | XML comments such as `\u003C!--#if (database == \"SqlServer\") -->` and `\u003C!--#endif -->` around the complete element | bare `#if` lines, which make the XML invalid |\n| Restore generated projects | restore action `210D431B-A78B-4D2F-B762-4ED3E3EA9025`; use `primaryOutputs`, or `args.files` containing source-template paths\u002Fglobs | run-script fields such as `executable` on the restore action |\n| Restrict to the SDK host | a `host` constraint whose `args` is an array containing `{ \"hostname\": \"dotnetcli\" }`; its optional `version` restricts the host\u002FCLI version | using host `version` when the requirement is specifically the active SDK version, the invalid host ID `dotnet-cli`, or unrelated `pattern` \u002F `value` fields |\n| Restrict the active SDK version | an `sdk-version` constraint with a NuGet version\u002Frange string in `args` | a machine-specific exact patch unless the template truly requires it |\n| Preserve CPM | keep generated `PackageReference` items versionless and package the owning `Directory.Packages.props` when the template is self-contained | adding inline `Version` attributes |\n| Package templates | a pack project with `\u003CPackageType>Template\u003C\u002FPackageType>` and template content packed below `content\u002F` | describing a layout without showing the requested project file |\n\n### Step 1: Bootstrap from existing project\n\nAnalyze the source `.csproj` and create a `.template.config\u002Ftemplate.json`:\n\n1. Copy the source project into a dedicated template-source directory by default, preserving\n   the original project untouched. Modify the original in place only when the user explicitly\n   asks for that layout.\n2. Create `.template.config` inside the template-source directory.\n3. Generate `template.json` with `identity` (reverse-DNS), `name`, `shortName`, `sourceName` (project name for replacement), `classifications`, and `tags`\n4. Preserve from source — generic `dotnet new` templates frequently get these wrong, so verify each is carried over from the original `.csproj`:\n   1. **SDK type** — `Microsoft.NET.Sdk`, `Microsoft.NET.Sdk.Web`, `Microsoft.NET.Sdk.Worker`, etc.\n   2. **Analyzer\u002Fpackage reference metadata** — `PrivateAssets`, `IncludeAssets`, `ExcludeAssets`\n   3. **`OutputType` and other key properties** — `TreatWarningsAsErrors`, `Nullable`, `LangVersion`\n   4. **CPM participation** — no inline `Version` attributes when a `Directory.Packages.props` is present\n   5. **Custom build props\u002Ftargets** and `Directory.Build.props` conventions\n   6. **Repo conventions** — folder layout, naming, `global.json` SDK pin\n\nMinimal example:\n```json\n{\n  \"$schema\": \"http:\u002F\u002Fjson.schemastore.org\u002Ftemplate\",\n  \"author\": \"MyOrg\",\n  \"classifications\": [\"Library\"],\n  \"identity\": \"MyOrg.Templates.MyLib\",\n  \"name\": \"My Library Template\",\n  \"shortName\": \"mylib\",\n  \"sourceName\": \"MyLib\",\n  \"tags\": { \"language\": \"C#\", \"type\": \"project\" }\n}\n```\n\n**Required output — do not stop at a minimal stub.** Write the *complete* `.template.config\u002Ftemplate.json` for the actual source project, then emit a short **conventions-preserved** confirmation so the user can see nothing was silently dropped. This carry-over is the whole value of the skill; a generic `dotnet new` template that loses these is why authoring ties with a hand-written stub.\n\n| Source `.csproj` setting | Carried over? | How |\n|--------------------------|---------------|-----|\n| SDK (`Microsoft.NET.Sdk.*`) | ✅ | template content `.csproj` uses same SDK |\n| `TreatWarningsAsErrors` \u002F `Nullable` \u002F `LangVersion` | ✅ | preserved verbatim in template `.csproj` |\n| PackageReference `PrivateAssets` \u002F `IncludeAssets` \u002F `ExcludeAssets` | ✅ | metadata kept on each reference |\n| CPM (`Directory.Packages.props` present) | ✅ | `ManagePackageVersionsCentrally` remains enabled and no inline `Version` attributes are emitted |\n\nMark any row you intentionally omitted as ⚠️ with a reason — never leave it implicit.\n\n### Step 2: Validate template.json\n\nValidate the generated `template.json` using the **template-validation** skill (it owns the full rule set — required fields, identity format, reserved shortName conflicts, parameter datatypes, post-actions, constraints, and tags).\n\nQuick summary of what gets checked:\n- **Required fields** — `identity`, `name`, and `shortName` must be present.\n- **ShortName conflicts** — avoid names that collide with `dotnet new` subcommands. Read the authoritative set from the `Commands:` section of `dotnet new --help` for the installed SDK and do not hardcode it (it can change between versions); illustrative examples from current SDKs are `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`. A conflict happens because `dotnet new \u003Cname>` would be parsed as the subcommand of the same name. Top-level `dotnet` verbs like `build`, `run`, `test`, and `publish` do NOT conflict. Run `dotnet new list` to confirm the name is not already taken.\n- **Parameters, post-actions, tags** — see template-validation for the complete rules, including the valid datatype list.\n\n### Step 3: Refine the template\n\nBased on validation results and user requirements:\n\n1. **Add parameters** with appropriate types (string, bool, choice), defaults, and descriptions\n2. **Add conditional content** using the file type's valid syntax. In XML use template\n   directives inside XML comments, not bare preprocessor lines:\n\n   ```xml\n   \u003C!--#if (database == \"SqlServer\") -->\n   \u003CPackageReference Include=\"Microsoft.EntityFrameworkCore.SqlServer\" \u002F>\n   \u003C!--#endif -->\n   \u003C!--#if (database == \"Postgres\") -->\n   \u003CPackageReference Include=\"Npgsql.EntityFrameworkCore.PostgreSQL\" \u002F>\n   \u003C!--#endif -->\n   ```\n3. **Configure post-actions** for solution add, restore, or custom scripts\n4. **Set constraints** to restrict which SDKs or workloads the template supports\n5. **Add classifications** and tags for discoverability\n\nFor a restore post-action, prefer `primaryOutputs` when the project path is known:\n\n```json\n\"primaryOutputs\": [{ \"path\": \"MyProject.csproj\" }],\n\"postActions\": [{\n  \"description\": \"Restore NuGet packages.\",\n  \"manualInstructions\": [{ \"text\": \"Run 'dotnet restore'.\" }],\n  \"actionId\": \"210D431B-A78B-4D2F-B762-4ED3E3EA9025\",\n  \"continueOnError\": true\n}]\n```\n\nIf `args.files` is needed, its paths are matched against the **source template** before\nrenames, for example `\"files\": [\"**\u002F*.csproj\"]`. Explain that distinction.\n\n### Step 4: Test the template locally\n\nFor a create-from-existing-project request, this step is required rather than optional:\ninstall the authored template, run a dry-run, instantiate it into a temporary output folder,\nand build the generated project. Report each observed result; inspecting `template.json` alone\ndoes not prove the reusable template works.\n\n```bash\ndotnet new install .\u002Fpath\u002Fto\u002Ftemplate\u002Froot\ndotnet new mylib --name TestProject --dry-run\ndotnet new mylib --name TestProject --output .\u002Ftest-output\ndotnet build .\u002Ftest-output\u002FTestProject\n```\n\nWhen packaging is requested, include the complete pack project, not only a directory tree:\n\n```xml\n\u003CProject Sdk=\"Microsoft.NET.Sdk\">\n  \u003CPropertyGroup>\n    \u003CPackageId>Contoso.ProjectTemplates\u003C\u002FPackageId>\n    \u003CPackageType>Template\u003C\u002FPackageType>\n    \u003CTargetFramework>net8.0\u003C\u002FTargetFramework>\n    \u003CIncludeBuildOutput>false\u003C\u002FIncludeBuildOutput>\n    \u003CNoWarn>$(NoWarn);NU5128\u003C\u002FNoWarn>\n  \u003C\u002FPropertyGroup>\n  \u003CItemGroup>\n    \u003CCompile Remove=\"**\\*\" \u002F>\n    \u003CContent Include=\"templates\\**\\*\" Pack=\"true\" PackagePath=\"content\\\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FProject>\n```\n\nThe pack project's target framework applies only to the content-only packaging project; it\ndoes not retarget projects inside `templates\u002F`. Prefer a broadly available supported framework\nunless the packaging project itself uses newer build features.\n\nFor a self-contained CPM template, the packaged `Directory.Packages.props` must include\n`\u003CManagePackageVersionsCentrally>true\u003C\u002FManagePackageVersionsCentrally>` and every versionless\n`PackageReference` must have a matching `PackageVersion`. Keep the props file at the intended\ngenerated repository root; do not place a duplicate nearer the project where it changes lookup.\n\n## Validation\n\n- [ ] `template.json` passes manual validation with zero errors\n- [ ] Template identity and shortName are unique and meaningful\n- [ ] All parameters have descriptions and appropriate defaults\n- [ ] Template can be installed, dry-run, and instantiated successfully\n- [ ] Created projects build cleanly with `dotnet build`\n- [ ] Conditional content produces correct output for all parameter combinations\n- [ ] XML template directives are wrapped in XML comments and the generated project parses\n- [ ] Host constraints use `args[].hostname`; restore actions use `primaryOutputs` or `args.files`\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Identity format issues | Use reverse-DNS format (e.g., `MyOrg.Templates.WebApi`). Avoid spaces or special characters. |\n| ShortName conflicts with CLI commands | Avoid names that match a `dotnet new` subcommand; read the live set from `dotnet new --help` and don't hardcode it (illustrative examples: `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`). Top-level verbs like `build`\u002F`run`\u002F`test`\u002F`publish` are fine. Run `dotnet new list` to see if the name is already taken. |\n| Missing parameter descriptions | Every parameter should have a `description` and `displayName` for discoverability. |\n| Not testing all parameter combinations | Use `dotnet new \u003Ctemplate> --dry-run` with different parameter values to verify conditional content works correctly. |\n| Hardcoded versions in template | Use `sourceName` replacement for project names and consider parameterizing framework versions. |\n| Not setting classifications | Add appropriate `classifications` (e.g., `[\"Web\", \"API\"]`) for template discovery. |\n| Reusing fields from a different constraint or post-action | Follow the exact schema: `host.args[].hostname`, and restore `args.files` rather than run-script fields. |\n\n## More Info\n\n- [Custom templates for dotnet new](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fcustom-templates) — official authoring guide\n- [template.json reference](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FReference-for-template.json) — full schema reference\n- [Template Engine Wiki](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki) — template engine internals\n","# Template Authoring\n\nThis skill helps an agent create and validate custom `dotnet new` templates. It guides bootstrapping templates from existing projects and validates `template.json` files for authoring issues before publishing.\n\n## When to Use\n\n- User wants to create a reusable template from an existing .csproj\n- User wants to validate a template.json they are authoring before publishing\n- User is setting up `.template.config\u002Ftemplate.json` from scratch\n- User wants to package a template for NuGet distribution\n\n## When Not to Use\n\n- User wants to find or use existing templates — route to `template-discovery` or `template-instantiation`\n- User has MSBuild issues unrelated to template authoring — route to `dotnet-msbuild` plugin\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Source project path | For creation | Path to the .csproj to use as template source |\n| template.json path | For validation | Path to an existing template.json to validate |\n| Template name | For creation | Human-readable name for the template |\n| Short name | Recommended | Short name for `dotnet new \u003Cshortname>` usage |\n\n## Workflow\n\n### Rules that change the answer\n\nUse these structures exactly; do not invent fields from other template features.\n\n**Deliver the requested artifact.** When the user says \"show\", \"write\", or \"give me the\ncontent\", put the complete JSON\u002FXML in the final response even if you also wrote it to disk.\nNever edit this skill's `SKILL.md` or plugin documentation as a substitute for authoring the\nuser's template. Only create or modify template files when the user requested file changes and\nthe target template\u002Fproject is present.\n\n| Need | Correct structure | Never use |\n|------|-------------------|-----------|\n| Conditional XML in a `.csproj` | XML comments such as `\u003C!--#if (database == \"SqlServer\") -->` and `\u003C!--#endif -->` around the complete element | bare `#if` lines, which make the XML invalid |\n| Restore generated projects | restore action `210D431B-A78B-4D2F-B762-4ED3E3EA9025`; use `primaryOutputs`, or `args.files` containing source-template paths\u002Fglobs | run-script fields such as `executable` on the restore action |\n| Restrict to the SDK host | a `host` constraint whose `args` is an array containing `{ \"hostname\": \"dotnetcli\" }`; its optional `version` restricts the host\u002FCLI version | using host `version` when the requirement is specifically the active SDK version, the invalid host ID `dotnet-cli`, or unrelated `pattern` \u002F `value` fields |\n| Restrict the active SDK version | an `sdk-version` constraint with a NuGet version\u002Frange string in `args` | a machine-specific exact patch unless the template truly requires it |\n| Preserve CPM | keep generated `PackageReference` items versionless and package the owning `Directory.Packages.props` when the template is self-contained | adding inline `Version` attributes |\n| Package templates | a pack project with `\u003CPackageType>Template\u003C\u002FPackageType>` and template content packed below `content\u002F` | describing a layout without showing the requested project file |\n\n### Step 1: Bootstrap from existing project\n\nAnalyze the source `.csproj` and create a `.template.config\u002Ftemplate.json`:\n\n1. Copy the source project into a dedicated template-source directory by default, preserving\n   the original project untouched. Modify the original in place only when the user explicitly\n   asks for that layout.\n2. Create `.template.config` inside the template-source directory.\n3. Generate `template.json` with `identity` (reverse-DNS), `name`, `shortName`, `sourceName` (project name for replacement), `classifications`, and `tags`\n4. Preserve from source — generic `dotnet new` templates frequently get these wrong, so verify each is carried over from the original `.csproj`:\n   1. **SDK type** — `Microsoft.NET.Sdk`, `Microsoft.NET.Sdk.Web`, `Microsoft.NET.Sdk.Worker`, etc.\n   2. **Analyzer\u002Fpackage reference metadata** — `PrivateAssets`, `IncludeAssets`, `ExcludeAssets`\n   3. **`OutputType` and other key properties** — `TreatWarningsAsErrors`, `Nullable`, `LangVersion`\n   4. **CPM participation** — no inline `Version` attributes when a `Directory.Packages.props` is present\n   5. **Custom build props\u002Ftargets** and `Directory.Build.props` conventions\n   6. **Repo conventions** — folder layout, naming, `global.json` SDK pin\n\nMinimal example:\n```json\n{\n  \"$schema\": \"http:\u002F\u002Fjson.schemastore.org\u002Ftemplate\",\n  \"author\": \"MyOrg\",\n  \"classifications\": [\"Library\"],\n  \"identity\": \"MyOrg.Templates.MyLib\",\n  \"name\": \"My Library Template\",\n  \"shortName\": \"mylib\",\n  \"sourceName\": \"MyLib\",\n  \"tags\": { \"language\": \"C#\", \"type\": \"project\" }\n}\n```\n\n**Required output — do not stop at a minimal stub.** Write the *complete* `.template.config\u002Ftemplate.json` for the actual source project, then emit a short **conventions-preserved** confirmation so the user can see nothing was silently dropped. This carry-over is the whole value of the skill; a generic `dotnet new` template that loses these is why authoring ties with a hand-written stub.\n\n| Source `.csproj` setting | Carried over? | How |\n|--------------------------|---------------|-----|\n| SDK (`Microsoft.NET.Sdk.*`) | ✅ | template content `.csproj` uses same SDK |\n| `TreatWarningsAsErrors` \u002F `Nullable` \u002F `LangVersion` | ✅ | preserved verbatim in template `.csproj` |\n| PackageReference `PrivateAssets` \u002F `IncludeAssets` \u002F `ExcludeAssets` | ✅ | metadata kept on each reference |\n| CPM (`Directory.Packages.props` present) | ✅ | `ManagePackageVersionsCentrally` remains enabled and no inline `Version` attributes are emitted |\n\nMark any row you intentionally omitted as ⚠️ with a reason — never leave it implicit.\n\n### Step 2: Validate template.json\n\nValidate the generated `template.json` using the **template-validation** skill (it owns the full rule set — required fields, identity format, reserved shortName conflicts, parameter datatypes, post-actions, constraints, and tags).\n\nQuick summary of what gets checked:\n- **Required fields** — `identity`, `name`, and `shortName` must be present.\n- **ShortName conflicts** — avoid names that collide with `dotnet new` subcommands. Read the authoritative set from the `Commands:` section of `dotnet new --help` for the installed SDK and do not hardcode it (it can change between versions); illustrative examples from current SDKs are `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`. A conflict happens because `dotnet new \u003Cname>` would be parsed as the subcommand of the same name. Top-level `dotnet` verbs like `build`, `run`, `test`, and `publish` do NOT conflict. Run `dotnet new list` to confirm the name is not already taken.\n- **Parameters, post-actions, tags** — see template-validation for the complete rules, including the valid datatype list.\n\n### Step 3: Refine the template\n\nBased on validation results and user requirements:\n\n1. **Add parameters** with appropriate types (string, bool, choice), defaults, and descriptions\n2. **Add conditional content** using the file type's valid syntax. In XML use template\n   directives inside XML comments, not bare preprocessor lines:\n\n   ```xml\n   \u003C!--#if (database == \"SqlServer\") -->\n   \u003CPackageReference Include=\"Microsoft.EntityFrameworkCore.SqlServer\" \u002F>\n   \u003C!--#endif -->\n   \u003C!--#if (database == \"Postgres\") -->\n   \u003CPackageReference Include=\"Npgsql.EntityFrameworkCore.PostgreSQL\" \u002F>\n   \u003C!--#endif -->\n   ```\n3. **Configure post-actions** for solution add, restore, or custom scripts\n4. **Set constraints** to restrict which SDKs or workloads the template supports\n5. **Add classifications** and tags for discoverability\n\nFor a restore post-action, prefer `primaryOutputs` when the project path is known:\n\n```json\n\"primaryOutputs\": [{ \"path\": \"MyProject.csproj\" }],\n\"postActions\": [{\n  \"description\": \"Restore NuGet packages.\",\n  \"manualInstructions\": [{ \"text\": \"Run 'dotnet restore'.\" }],\n  \"actionId\": \"210D431B-A78B-4D2F-B762-4ED3E3EA9025\",\n  \"continueOnError\": true\n}]\n```\n\nIf `args.files` is needed, its paths are matched against the **source template** before\nrenames, for example `\"files\": [\"**\u002F*.csproj\"]`. Explain that distinction.\n\n### Step 4: Test the template locally\n\nFor a create-from-existing-project request, this step is required rather than optional:\ninstall the authored template, run a dry-run, instantiate it into a temporary output folder,\nand build the generated project. Report each observed result; inspecting `template.json` alone\ndoes not prove the reusable template works.\n\n```bash\ndotnet new install .\u002Fpath\u002Fto\u002Ftemplate\u002Froot\ndotnet new mylib --name TestProject --dry-run\ndotnet new mylib --name TestProject --output .\u002Ftest-output\ndotnet build .\u002Ftest-output\u002FTestProject\n```\n\nWhen packaging is requested, include the complete pack project, not only a directory tree:\n\n```xml\n\u003CProject Sdk=\"Microsoft.NET.Sdk\">\n  \u003CPropertyGroup>\n    \u003CPackageId>Contoso.ProjectTemplates\u003C\u002FPackageId>\n    \u003CPackageType>Template\u003C\u002FPackageType>\n    \u003CTargetFramework>net8.0\u003C\u002FTargetFramework>\n    \u003CIncludeBuildOutput>false\u003C\u002FIncludeBuildOutput>\n    \u003CNoWarn>$(NoWarn);NU5128\u003C\u002FNoWarn>\n  \u003C\u002FPropertyGroup>\n  \u003CItemGroup>\n    \u003CCompile Remove=\"**\\*\" \u002F>\n    \u003CContent Include=\"templates\\**\\*\" Pack=\"true\" PackagePath=\"content\\\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FProject>\n```\n\nThe pack project's target framework applies only to the content-only packaging project; it\ndoes not retarget projects inside `templates\u002F`. Prefer a broadly available supported framework\nunless the packaging project itself uses newer build features.\n\nFor a self-contained CPM template, the packaged `Directory.Packages.props` must include\n`\u003CManagePackageVersionsCentrally>true\u003C\u002FManagePackageVersionsCentrally>` and every versionless\n`PackageReference` must have a matching `PackageVersion`. Keep the props file at the intended\ngenerated repository root; do not place a duplicate nearer the project where it changes lookup.\n\n## Validation\n\n- [ ] `template.json` passes manual validation with zero errors\n- [ ] Template identity and shortName are unique and meaningful\n- [ ] All parameters have descriptions and appropriate defaults\n- [ ] Template can be installed, dry-run, and instantiated successfully\n- [ ] Created projects build cleanly with `dotnet build`\n- [ ] Conditional content produces correct output for all parameter combinations\n- [ ] XML template directives are wrapped in XML comments and the generated project parses\n- [ ] Host constraints use `args[].hostname`; restore actions use `primaryOutputs` or `args.files`\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Identity format issues | Use reverse-DNS format (e.g., `MyOrg.Templates.WebApi`). Avoid spaces or special characters. |\n| ShortName conflicts with CLI commands | Avoid names that match a `dotnet new` subcommand; read the live set from `dotnet new --help` and don't hardcode it (illustrative examples: `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`). Top-level verbs like `build`\u002F`run`\u002F`test`\u002F`publish` are fine. Run `dotnet new list` to see if the name is already taken. |\n| Missing parameter descriptions | Every parameter should have a `description` and `displayName` for discoverability. |\n| Not testing all parameter combinations | Use `dotnet new \u003Ctemplate> --dry-run` with different parameter values to verify conditional content works correctly. |\n| Hardcoded versions in template | Use `sourceName` replacement for project names and consider parameterizing framework versions. |\n| Not setting classifications | Add appropriate `classifications` (e.g., `[\"Web\", \"API\"]`) for template discovery. |\n| Reusing fields from a different constraint or post-action | Follow the exact schema: `host.args[].hostname`, and restore `args.files` rather than run-script fields. |\n\n## More Info\n\n- [Custom templates for dotnet new](https:\u002F\u002Flearn.microsoft.com\u002Fdotnet\u002Fcore\u002Ftools\u002Fcustom-templates) — official authoring guide\n- [template.json reference](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FReference-for-template.json) — full schema reference\n- [Template Engine Wiki](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki) — template engine internals\n",{"name":5,"license":14,"description":23},"Guides creation and validation of custom dotnet new templates from existing projects. Generates a .template.config\u002Ftemplate.json that preserves the source project's conventions. USE FOR: creating a reusable dotnet new template from an existing project, bootstrapping .template.config\u002Ftemplate.json with correct identity, shortName, parameters, and post-actions, adding parameters or conditional content to a template you are authoring, validating the template.json you are authoring before publishing, packaging templates as NuGet packages for distribution. DO NOT USE FOR: validating an existing template.json as a standalone task (use template-validation), finding or using existing templates (use template-discovery and template-instantiation), MSBuild project file issues unrelated to template authoring, NuGet package publishing (only template packaging structure).\n","main","ccab8dffc0ecc173838f51e4c5f0d3b51a704f41","plugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-authoring","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-authoring",{"tool":38,"command":39},"bunx","bunx skills add deadmade\u002Fdead-agent-skills --skill template-authoring",{"tool":41,"command":42},"pnpm","pnpm dlx skills add deadmade\u002Fdead-agent-skills --skill template-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-authoring\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",[],[]]