[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JCY7FJ8WMTRZ18JCY4Y2V":3,"skill-same:01M75JCY7FJ8WMTRZ18JCY4Y2V":46},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75JCY7FJ8WMTRZ18JCY4Y2V","extension-points",null,"Own MSBuild import and hook discovery. USE FOR: CustomBefore\u002FCustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build\u002FbuildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. An import guard remains in scope when it is one defect in a broader hook\u002Fimport flow. DO NOT USE for a focused safety verdict on whether one specific Import needs Exists or is an intentionally unguarded package contract; use msbuild-antipatterns. NEVER INVOKE when imports and hook placement already work and the request is only target Inputs\u002FOutputs, incremental skipping, or FileWrites clean tracking; use incremental-build or target-authoring. Exclude props-versus-targets placement and non-MSBuild systems.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fextension-points\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: extension-points\ndescription: \"Own MSBuild import and hook discovery. USE FOR: CustomBefore\u002FCustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build\u002FbuildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. An import guard remains in scope when it is one defect in a broader hook\u002Fimport flow. DO NOT USE for a focused safety verdict on whether one specific Import needs Exists or is an intentionally unguarded package contract; use msbuild-antipatterns. NEVER INVOKE when imports and hook placement already work and the request is only target Inputs\u002FOutputs, incremental skipping, or FileWrites clean tracking; use incremental-build or target-authoring. Exclude props-versus-targets placement and non-MSBuild systems.\"\nlicense: MIT\n---\n\n# MSBuild Extension Points\n\nHow the MSBuild pipeline provides hooks for SDKs, NuGet packages, repos, and users to inject custom logic.\n\n## CustomBefore \u002F CustomAfter Hooks\n\nEvery major `.targets` file defines import hooks:\n\n```xml\n\u003CPropertyGroup>\n  \u003CCustomBeforeMicrosoftCommonTargets Condition=\"'$(CustomBeforeMicrosoftCommonTargets)' == ''\">\n    $(MSBuildExtensionsPath)\\v$(MSBuildToolsVersion)\\Custom.Before.Microsoft.Common.targets\n  \u003C\u002FCustomBeforeMicrosoftCommonTargets>\n\u003C\u002FPropertyGroup>\n\n\u003CImport Project=\"$(CustomBeforeMicrosoftCommonTargets)\"\n    Condition=\"'$(CustomBeforeMicrosoftCommonTargets)' != '' and Exists('$(CustomBeforeMicrosoftCommonTargets)')\"\u002F>\n\u003C!-- ... core targets ... -->\n\u003CImport Project=\"$(CustomAfterMicrosoftCommonTargets)\"\n    Condition=\"'$(CustomAfterMicrosoftCommonTargets)' != '' and Exists('$(CustomAfterMicrosoftCommonTargets)')\"\u002F>\n```\n\n### Rules\n\n- Default path includes version (`v$(MSBuildToolsVersion)`) for side-by-side installations.\n- Always check `Exists()`. The file may not be present on every machine.\n- **Append** to the property (don't overwrite) to chain multiple hooks:\n\n```xml\n\u003CPropertyGroup>\n  \u003CCustomBeforeMicrosoftCommonTargets>\n    $(CustomBeforeMicrosoftCommonTargets);$(MSBuildThisFileDirectory)MyExtension.targets\n  \u003C\u002FCustomBeforeMicrosoftCommonTargets>\n\u003C\u002FPropertyGroup>\n```\n\n## Wildcard Import Directories\n\nMSBuild imports all files in extension directories, sorted alphabetically:\n\n```xml\n\u003CImport Project=\"$(MSBuildExtensionsPath)\\$(MSBuildToolsVersion)\\Imports\\Microsoft.Common.props\\ImportBefore\\*\"\n    Condition=\"'$(ImportByWildcardBeforeMicrosoftCommonProps)' == 'true'\n               and Exists('$(MSBuildExtensionsPath)\\$(MSBuildToolsVersion)\\Imports\\Microsoft.Common.props\\ImportBefore')\" \u002F>\n```\n\n### Key paths\n\n| Property | Resolves to | Scope |\n|---|---|---|\n| `$(MSBuildUserExtensionsPath)` | `%APPDATA%\\Microsoft\\MSBuild` | Per-user |\n| `$(MSBuildExtensionsPath)` | MSBuild install directory | Machine-wide |\n| `$(MSBuildProjectExtensionsPath)` | `obj\u002F` directory | Per-project (NuGet) |\n\nName files with numeric prefixes for ordering: `01-first.props`, `02-second.props`.\n\n## Import Gating — Control Properties\n\nEvery wildcard import is gated by a boolean property:\n\n```xml\n\u003CPropertyGroup>\n  \u003CImportByWildcardBeforeMicrosoftCommonProps\n      Condition=\"'$(ImportByWildcardBeforeMicrosoftCommonProps)' == ''\">true\u003C\u002FImportByWildcardBeforeMicrosoftCommonProps>\n  \u003CImportDirectoryBuildProps\n      Condition=\"'$(ImportDirectoryBuildProps)' == ''\">true\u003C\u002FImportDirectoryBuildProps>\n\u003C\u002FPropertyGroup>\n```\n\n### Available control properties\n\n| Property | What it disables |\n|---|---|\n| `ImportDirectoryBuildProps` | Directory.Build.props auto-discovery |\n| `ImportDirectoryBuildTargets` | Directory.Build.targets auto-discovery |\n| `ImportProjectExtensionProps` | NuGet-generated `*.props` in obj\u002F |\n| `ImportProjectExtensionTargets` | NuGet-generated `*.targets` in obj\u002F |\n| `ImportByWildcardBefore*` | Machine-level ImportBefore extensions |\n| `ImportByWildcardAfter*` | Machine-level ImportAfter extensions |\n\n## NuGet Package Build Extension Layout\n\nNuGet packages inject build logic via `build\u002F` or `buildTransitive\u002F` folders:\n\n```text\nMyPackage\u002F\n  build\u002F\n    MyPackage.props      ← imported via *.props wildcard\n    MyPackage.targets    ← imported via *.targets wildcard\n  buildTransitive\u002F\n    MyPackage.props      ← imported by transitive consumers\n    MyPackage.targets\n```\n\n### Rules\n\n- File names **must match the package ID** exactly.\n- `build\u002F` affects direct consumers only. `buildTransitive\u002F` affects the entire dependency chain.\n- Props are imported early (before the project), targets are imported late (after the project).\n\n### Forwarding chain: `buildTransitive\u002F` → `build\u002F` → shared\n\nForward `buildTransitive\u002F*.props` and `buildTransitive\u002F*.targets` through their sibling `build\u002F*.props` \u002F `build\u002F*.targets` files (chain `buildTransitive → build → shared`) instead of importing `buildMultiTargeting\u002F` directly. This keeps `build\u002F` as the single source of truth with a clear ownership chain, so transitive consumers stay in sync with direct consumers instead of the two layouts drifting apart.\n\nWhen `build\u002F` is packed **per-TFM** (`build\u002F\u003Ctfm>\u002F`, via `TfmSpecificPackageFile`, a per-TFM `\u003CPackagePath>`, or SDK conventions) while `buildMultiTargeting\u002F` is not, a `buildTransitive\u002F\u003Ctfm>\u002F` forwarder **must include the TFM segment** — dropping it resolves to a non-existent package-root `build\u002FMyPackage.props` and fails transitive consumers with **`MSB4019`**. Derive the segment from the file's own folder, never `$(TargetFramework)` (NuGet nearest-match can serve a `net10.0` consumer the `net9.0` folder, so `$(TargetFramework)` may name a folder that was never restored):\n\n```xml\n\u003C!-- buildTransitive\u002F\u003Ctfm>\u002FMyPackage.props -->\n\u003CImport Project=\"$(MSBuildThisFileDirectory)..\\..\\build\\$([System.IO.Path]::GetFileName($([System.IO.Path]::GetDirectoryName('$(MSBuildThisFileDirectory)'))))\\MyPackage.props\" \u002F>\n```\n\n## Source Tree vs Packed Layout\n\nWhen reviewing a NuGet build-extension package, the **source layout** in the repository can legitimately differ from the **packed layout** inside the produced `.nupkg`. This is a common source of false-positive \"import points at a missing file\" findings.\n\nThree packaging mechanisms reshape the layout at pack time:\n\n1. **`.nuspec` `\u003Cfile src=… target=…>` mappings** — copy a single source file into multiple per-TFM targets:\n\n   ```xml\n   \u003C!-- Source tree has ONE shared file:\n          buildTransitive\\common\\MyAdapter.props\n        Pack rewrites it to per-TFM targets inside the .nupkg:\n          buildTransitive\\net462\\MyAdapter.props\n          buildTransitive\\net8.0\\MyAdapter.props\n          buildTransitive\\net9.0\\MyAdapter.props -->\n   \u003Cfiles>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net462\\MyAdapter.props\" \u002F>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net8.0\\MyAdapter.props\" \u002F>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net9.0\\MyAdapter.props\" \u002F>\n   \u003C\u002Ffiles>\n   ```\n\n   In the `\u003Cfile>` element, a `target` ending in `\\` is treated as a folder (filename preserved from `src`); a `target` ending in a filename renames the file.\n\n2. **`.csproj` `\u003CPackagePath>` metadata** on `\u003CNone Update=…>` or `\u003CContent Include=…>` items — same effect via SDK pack. Use one item per destination to keep the mapping unambiguous:\n\n   ```xml\n   \u003CItemGroup>\n     \u003CNone Include=\"buildTransitive\\common\\MyAdapter.props\" Pack=\"true\" PackagePath=\"buildTransitive\\net8.0\\MyAdapter.props\" \u002F>\n     \u003CNone Include=\"buildTransitive\\common\\MyAdapter.props\" Pack=\"true\" PackagePath=\"buildTransitive\\net9.0\\MyAdapter.props\" \u002F>\n   \u003C\u002FItemGroup>\n   ```\n\n   NuGet\u002FSDK pack also accepts a semicolon-separated list (`PackagePath=\"buildTransitive\\net8.0\\;buildTransitive\\net9.0\\\"`) to fan one source out to multiple destinations, but the multi-item form above is harder to misread.\n\n3. **SDK conventions** — `IncludeBuildOutput`, `BuildOutputTargetFolder`, `IncludeContentInPack` automatically place built outputs under `lib\u002F\u003Ctfm>\u002F` or `build\u002F\u003Ctfm>\u002F`.\n\n### Implication for reviewers\n\nA forwarder like the following inside a packed `build\u002Fnet462\u002F` folder is **not** a \"missing-file\" bug, even if the source tree has no `buildTransitive\u002Fnet462\u002F` directory:\n\n```xml\n\u003C!-- In packed build\u002Fnet462\u002FMyAdapter.props -->\n\u003CProject>\n  \u003CImport Project=\"$(MSBuildThisFileDirectory)..\\..\\buildTransitive\\net462\\MyAdapter.props\" \u002F>\n\u003C\u002FProject>\n```\n\nBefore flagging an unguarded `\u003CImport>` inside a `build\u002F\u003Ctfm>\u002F` or `buildTransitive\u002F\u003Ctfm>\u002F` folder:\n\n1. Look for `*.nuspec` in the project directory and its immediate parent directory (do not walk further up). Read every `\u003Cfile target=…>` whose `target` matches the imported path.\n2. Read the `.csproj` for `\u003CPackagePath>` metadata on `\u003CNone>`\u002F`\u003CContent>` items.\n3. Only flag the import if the target path is missing from **both** the source tree *and* the projected package layout.\n\nSee also `msbuild-antipatterns` AP-13 (\"NuGet package forwarders\" exception).\n\n## Import Guard Pattern\n\nThe `.targets` file ensures `.props` was imported using a guard property:\n\n```xml\n\u003C!-- End of Microsoft.Common.props -->\n\u003CPropertyGroup>\n  \u003CMicrosoftCommonPropsHasBeenImported>true\u003C\u002FMicrosoftCommonPropsHasBeenImported>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- Top of Microsoft.Common.CurrentVersion.targets -->\n\u003CImport Project=\"Microsoft.Common.props\"\n    Condition=\"'$(MicrosoftCommonPropsHasBeenImported)' != 'true'\" \u002F>\n```\n\nThis handles projects that only import `.targets`.\n\n## Directory.Build Discovery\n\nMSBuild walks up the directory tree to find the nearest `Directory.Build.props`:\n\n```xml\n\u003C_DirectoryBuildPropsBasePath>\n  $([MSBuild]::GetDirectoryNameOfFileAbove('$(MSBuildProjectDirectory)', 'Directory.Build.props'))\n\u003C\u002F_DirectoryBuildPropsBasePath>\n```\n\nOnly the **nearest** file is discovered. Nested hierarchies must explicitly import parents:\n\n```xml\n\u003C!-- src\u002FDirectory.Build.props -->\n\u003CPropertyGroup>\n  \u003C_ParentPropsPath>$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)..\u002F'))\u003C\u002F_ParentPropsPath>\n\u003C\u002FPropertyGroup>\n\u003CImport Project=\"$(_ParentPropsPath)\" Condition=\"'$(_ParentPropsPath)' != ''\" \u002F>\n```\n\n## Creating Your Own Extension Point\n\n```xml\n\u003C!-- MySDK.targets -->\n\u003CProject>\n  \u003CImport Project=\"MySDK.props\" Condition=\"'$(MySDKPropsImported)' != 'true'\" \u002F>\n\n  \u003CPropertyGroup>\n    \u003CCustomBeforeMySDK Condition=\"'$(CustomBeforeMySDK)' == ''\">$(MSBuildProjectDirectory)\\MySDK.Before.targets\u003C\u002FCustomBeforeMySDK>\n    \u003CCustomAfterMySDK Condition=\"'$(CustomAfterMySDK)' == ''\">$(MSBuildProjectDirectory)\\MySDK.After.targets\u003C\u002FCustomAfterMySDK>\n  \u003C\u002FPropertyGroup>\n\n  \u003CImport Project=\"$(CustomBeforeMySDK)\" Condition=\"Exists('$(CustomBeforeMySDK)')\" \u002F>\n\n  \u003CPropertyGroup>\n    \u003CMySDKBuildDependsOn>BeforeMySDKBuild;CoreMySDKBuild;AfterMySDKBuild\u003C\u002FMySDKBuildDependsOn>\n  \u003C\u002FPropertyGroup>\n  \u003CTarget Name=\"MySDKBuild\" DependsOnTargets=\"$(MySDKBuildDependsOn)\" \u002F>\n  \u003CTarget Name=\"BeforeMySDKBuild\" \u002F>\n  \u003CTarget Name=\"AfterMySDKBuild\" \u002F>\n  \u003CTarget Name=\"CoreMySDKBuild\">\n    \u003C!-- implementation -->\n  \u003C\u002FTarget>\n\n  \u003CImport Project=\"$(CustomAfterMySDK)\" Condition=\"Exists('$(CustomAfterMySDK)')\" \u002F>\n\u003C\u002FProject>\n```\n\n## Common Pitfalls\n\n- **Missing `Exists()` on optional imports** causes build failures when files are absent. **Exception**: imports inside published `build\u002F\u003Ctfm>\u002F` and `buildTransitive\u002F\u003Ctfm>\u002F` folders of a NuGet package are a package contract — the target is guaranteed by the packed layout (see \"Source Tree vs Packed Layout\" above). Don't guard them and don't flag them.\n- **Overwriting Custom* properties** drops prior hooks. Append with `;` separator.\n- **NuGet package file names not matching package ID** silently skips the import.\n- **Nested Directory.Build.props** without parent import loses repo-root settings.\n","# MSBuild Extension Points\n\nHow the MSBuild pipeline provides hooks for SDKs, NuGet packages, repos, and users to inject custom logic.\n\n## CustomBefore \u002F CustomAfter Hooks\n\nEvery major `.targets` file defines import hooks:\n\n```xml\n\u003CPropertyGroup>\n  \u003CCustomBeforeMicrosoftCommonTargets Condition=\"'$(CustomBeforeMicrosoftCommonTargets)' == ''\">\n    $(MSBuildExtensionsPath)\\v$(MSBuildToolsVersion)\\Custom.Before.Microsoft.Common.targets\n  \u003C\u002FCustomBeforeMicrosoftCommonTargets>\n\u003C\u002FPropertyGroup>\n\n\u003CImport Project=\"$(CustomBeforeMicrosoftCommonTargets)\"\n    Condition=\"'$(CustomBeforeMicrosoftCommonTargets)' != '' and Exists('$(CustomBeforeMicrosoftCommonTargets)')\"\u002F>\n\u003C!-- ... core targets ... -->\n\u003CImport Project=\"$(CustomAfterMicrosoftCommonTargets)\"\n    Condition=\"'$(CustomAfterMicrosoftCommonTargets)' != '' and Exists('$(CustomAfterMicrosoftCommonTargets)')\"\u002F>\n```\n\n### Rules\n\n- Default path includes version (`v$(MSBuildToolsVersion)`) for side-by-side installations.\n- Always check `Exists()`. The file may not be present on every machine.\n- **Append** to the property (don't overwrite) to chain multiple hooks:\n\n```xml\n\u003CPropertyGroup>\n  \u003CCustomBeforeMicrosoftCommonTargets>\n    $(CustomBeforeMicrosoftCommonTargets);$(MSBuildThisFileDirectory)MyExtension.targets\n  \u003C\u002FCustomBeforeMicrosoftCommonTargets>\n\u003C\u002FPropertyGroup>\n```\n\n## Wildcard Import Directories\n\nMSBuild imports all files in extension directories, sorted alphabetically:\n\n```xml\n\u003CImport Project=\"$(MSBuildExtensionsPath)\\$(MSBuildToolsVersion)\\Imports\\Microsoft.Common.props\\ImportBefore\\*\"\n    Condition=\"'$(ImportByWildcardBeforeMicrosoftCommonProps)' == 'true'\n               and Exists('$(MSBuildExtensionsPath)\\$(MSBuildToolsVersion)\\Imports\\Microsoft.Common.props\\ImportBefore')\" \u002F>\n```\n\n### Key paths\n\n| Property | Resolves to | Scope |\n|---|---|---|\n| `$(MSBuildUserExtensionsPath)` | `%APPDATA%\\Microsoft\\MSBuild` | Per-user |\n| `$(MSBuildExtensionsPath)` | MSBuild install directory | Machine-wide |\n| `$(MSBuildProjectExtensionsPath)` | `obj\u002F` directory | Per-project (NuGet) |\n\nName files with numeric prefixes for ordering: `01-first.props`, `02-second.props`.\n\n## Import Gating — Control Properties\n\nEvery wildcard import is gated by a boolean property:\n\n```xml\n\u003CPropertyGroup>\n  \u003CImportByWildcardBeforeMicrosoftCommonProps\n      Condition=\"'$(ImportByWildcardBeforeMicrosoftCommonProps)' == ''\">true\u003C\u002FImportByWildcardBeforeMicrosoftCommonProps>\n  \u003CImportDirectoryBuildProps\n      Condition=\"'$(ImportDirectoryBuildProps)' == ''\">true\u003C\u002FImportDirectoryBuildProps>\n\u003C\u002FPropertyGroup>\n```\n\n### Available control properties\n\n| Property | What it disables |\n|---|---|\n| `ImportDirectoryBuildProps` | Directory.Build.props auto-discovery |\n| `ImportDirectoryBuildTargets` | Directory.Build.targets auto-discovery |\n| `ImportProjectExtensionProps` | NuGet-generated `*.props` in obj\u002F |\n| `ImportProjectExtensionTargets` | NuGet-generated `*.targets` in obj\u002F |\n| `ImportByWildcardBefore*` | Machine-level ImportBefore extensions |\n| `ImportByWildcardAfter*` | Machine-level ImportAfter extensions |\n\n## NuGet Package Build Extension Layout\n\nNuGet packages inject build logic via `build\u002F` or `buildTransitive\u002F` folders:\n\n```text\nMyPackage\u002F\n  build\u002F\n    MyPackage.props      ← imported via *.props wildcard\n    MyPackage.targets    ← imported via *.targets wildcard\n  buildTransitive\u002F\n    MyPackage.props      ← imported by transitive consumers\n    MyPackage.targets\n```\n\n### Rules\n\n- File names **must match the package ID** exactly.\n- `build\u002F` affects direct consumers only. `buildTransitive\u002F` affects the entire dependency chain.\n- Props are imported early (before the project), targets are imported late (after the project).\n\n### Forwarding chain: `buildTransitive\u002F` → `build\u002F` → shared\n\nForward `buildTransitive\u002F*.props` and `buildTransitive\u002F*.targets` through their sibling `build\u002F*.props` \u002F `build\u002F*.targets` files (chain `buildTransitive → build → shared`) instead of importing `buildMultiTargeting\u002F` directly. This keeps `build\u002F` as the single source of truth with a clear ownership chain, so transitive consumers stay in sync with direct consumers instead of the two layouts drifting apart.\n\nWhen `build\u002F` is packed **per-TFM** (`build\u002F\u003Ctfm>\u002F`, via `TfmSpecificPackageFile`, a per-TFM `\u003CPackagePath>`, or SDK conventions) while `buildMultiTargeting\u002F` is not, a `buildTransitive\u002F\u003Ctfm>\u002F` forwarder **must include the TFM segment** — dropping it resolves to a non-existent package-root `build\u002FMyPackage.props` and fails transitive consumers with **`MSB4019`**. Derive the segment from the file's own folder, never `$(TargetFramework)` (NuGet nearest-match can serve a `net10.0` consumer the `net9.0` folder, so `$(TargetFramework)` may name a folder that was never restored):\n\n```xml\n\u003C!-- buildTransitive\u002F\u003Ctfm>\u002FMyPackage.props -->\n\u003CImport Project=\"$(MSBuildThisFileDirectory)..\\..\\build\\$([System.IO.Path]::GetFileName($([System.IO.Path]::GetDirectoryName('$(MSBuildThisFileDirectory)'))))\\MyPackage.props\" \u002F>\n```\n\n## Source Tree vs Packed Layout\n\nWhen reviewing a NuGet build-extension package, the **source layout** in the repository can legitimately differ from the **packed layout** inside the produced `.nupkg`. This is a common source of false-positive \"import points at a missing file\" findings.\n\nThree packaging mechanisms reshape the layout at pack time:\n\n1. **`.nuspec` `\u003Cfile src=… target=…>` mappings** — copy a single source file into multiple per-TFM targets:\n\n   ```xml\n   \u003C!-- Source tree has ONE shared file:\n          buildTransitive\\common\\MyAdapter.props\n        Pack rewrites it to per-TFM targets inside the .nupkg:\n          buildTransitive\\net462\\MyAdapter.props\n          buildTransitive\\net8.0\\MyAdapter.props\n          buildTransitive\\net9.0\\MyAdapter.props -->\n   \u003Cfiles>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net462\\MyAdapter.props\" \u002F>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net8.0\\MyAdapter.props\" \u002F>\n     \u003Cfile src=\"buildTransitive\\common\\MyAdapter.props\" target=\"buildTransitive\\net9.0\\MyAdapter.props\" \u002F>\n   \u003C\u002Ffiles>\n   ```\n\n   In the `\u003Cfile>` element, a `target` ending in `\\` is treated as a folder (filename preserved from `src`); a `target` ending in a filename renames the file.\n\n2. **`.csproj` `\u003CPackagePath>` metadata** on `\u003CNone Update=…>` or `\u003CContent Include=…>` items — same effect via SDK pack. Use one item per destination to keep the mapping unambiguous:\n\n   ```xml\n   \u003CItemGroup>\n     \u003CNone Include=\"buildTransitive\\common\\MyAdapter.props\" Pack=\"true\" PackagePath=\"buildTransitive\\net8.0\\MyAdapter.props\" \u002F>\n     \u003CNone Include=\"buildTransitive\\common\\MyAdapter.props\" Pack=\"true\" PackagePath=\"buildTransitive\\net9.0\\MyAdapter.props\" \u002F>\n   \u003C\u002FItemGroup>\n   ```\n\n   NuGet\u002FSDK pack also accepts a semicolon-separated list (`PackagePath=\"buildTransitive\\net8.0\\;buildTransitive\\net9.0\\\"`) to fan one source out to multiple destinations, but the multi-item form above is harder to misread.\n\n3. **SDK conventions** — `IncludeBuildOutput`, `BuildOutputTargetFolder`, `IncludeContentInPack` automatically place built outputs under `lib\u002F\u003Ctfm>\u002F` or `build\u002F\u003Ctfm>\u002F`.\n\n### Implication for reviewers\n\nA forwarder like the following inside a packed `build\u002Fnet462\u002F` folder is **not** a \"missing-file\" bug, even if the source tree has no `buildTransitive\u002Fnet462\u002F` directory:\n\n```xml\n\u003C!-- In packed build\u002Fnet462\u002FMyAdapter.props -->\n\u003CProject>\n  \u003CImport Project=\"$(MSBuildThisFileDirectory)..\\..\\buildTransitive\\net462\\MyAdapter.props\" \u002F>\n\u003C\u002FProject>\n```\n\nBefore flagging an unguarded `\u003CImport>` inside a `build\u002F\u003Ctfm>\u002F` or `buildTransitive\u002F\u003Ctfm>\u002F` folder:\n\n1. Look for `*.nuspec` in the project directory and its immediate parent directory (do not walk further up). Read every `\u003Cfile target=…>` whose `target` matches the imported path.\n2. Read the `.csproj` for `\u003CPackagePath>` metadata on `\u003CNone>`\u002F`\u003CContent>` items.\n3. Only flag the import if the target path is missing from **both** the source tree *and* the projected package layout.\n\nSee also `msbuild-antipatterns` AP-13 (\"NuGet package forwarders\" exception).\n\n## Import Guard Pattern\n\nThe `.targets` file ensures `.props` was imported using a guard property:\n\n```xml\n\u003C!-- End of Microsoft.Common.props -->\n\u003CPropertyGroup>\n  \u003CMicrosoftCommonPropsHasBeenImported>true\u003C\u002FMicrosoftCommonPropsHasBeenImported>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- Top of Microsoft.Common.CurrentVersion.targets -->\n\u003CImport Project=\"Microsoft.Common.props\"\n    Condition=\"'$(MicrosoftCommonPropsHasBeenImported)' != 'true'\" \u002F>\n```\n\nThis handles projects that only import `.targets`.\n\n## Directory.Build Discovery\n\nMSBuild walks up the directory tree to find the nearest `Directory.Build.props`:\n\n```xml\n\u003C_DirectoryBuildPropsBasePath>\n  $([MSBuild]::GetDirectoryNameOfFileAbove('$(MSBuildProjectDirectory)', 'Directory.Build.props'))\n\u003C\u002F_DirectoryBuildPropsBasePath>\n```\n\nOnly the **nearest** file is discovered. Nested hierarchies must explicitly import parents:\n\n```xml\n\u003C!-- src\u002FDirectory.Build.props -->\n\u003CPropertyGroup>\n  \u003C_ParentPropsPath>$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)..\u002F'))\u003C\u002F_ParentPropsPath>\n\u003C\u002FPropertyGroup>\n\u003CImport Project=\"$(_ParentPropsPath)\" Condition=\"'$(_ParentPropsPath)' != ''\" \u002F>\n```\n\n## Creating Your Own Extension Point\n\n```xml\n\u003C!-- MySDK.targets -->\n\u003CProject>\n  \u003CImport Project=\"MySDK.props\" Condition=\"'$(MySDKPropsImported)' != 'true'\" \u002F>\n\n  \u003CPropertyGroup>\n    \u003CCustomBeforeMySDK Condition=\"'$(CustomBeforeMySDK)' == ''\">$(MSBuildProjectDirectory)\\MySDK.Before.targets\u003C\u002FCustomBeforeMySDK>\n    \u003CCustomAfterMySDK Condition=\"'$(CustomAfterMySDK)' == ''\">$(MSBuildProjectDirectory)\\MySDK.After.targets\u003C\u002FCustomAfterMySDK>\n  \u003C\u002FPropertyGroup>\n\n  \u003CImport Project=\"$(CustomBeforeMySDK)\" Condition=\"Exists('$(CustomBeforeMySDK)')\" \u002F>\n\n  \u003CPropertyGroup>\n    \u003CMySDKBuildDependsOn>BeforeMySDKBuild;CoreMySDKBuild;AfterMySDKBuild\u003C\u002FMySDKBuildDependsOn>\n  \u003C\u002FPropertyGroup>\n  \u003CTarget Name=\"MySDKBuild\" DependsOnTargets=\"$(MySDKBuildDependsOn)\" \u002F>\n  \u003CTarget Name=\"BeforeMySDKBuild\" \u002F>\n  \u003CTarget Name=\"AfterMySDKBuild\" \u002F>\n  \u003CTarget Name=\"CoreMySDKBuild\">\n    \u003C!-- implementation -->\n  \u003C\u002FTarget>\n\n  \u003CImport Project=\"$(CustomAfterMySDK)\" Condition=\"Exists('$(CustomAfterMySDK)')\" \u002F>\n\u003C\u002FProject>\n```\n\n## Common Pitfalls\n\n- **Missing `Exists()` on optional imports** causes build failures when files are absent. **Exception**: imports inside published `build\u002F\u003Ctfm>\u002F` and `buildTransitive\u002F\u003Ctfm>\u002F` folders of a NuGet package are a package contract — the target is guaranteed by the packed layout (see \"Source Tree vs Packed Layout\" above). Don't guard them and don't flag them.\n- **Overwriting Custom* properties** drops prior hooks. Append with `;` separator.\n- **NuGet package file names not matching package ID** silently skips the import.\n- **Nested Directory.Build.props** without parent import loses repo-root settings.\n",{"name":5,"license":15,"description":7},"master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fextension-points",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stanfish06\u002Fskillquarium --skill extension-points",{"tool":38,"command":39},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill extension-points",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill extension-points","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fextension-points\u002FSKILL.md",true,[],[47,54,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","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\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]