[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D2PW9A72PBPDGS5FH87BMR":3,"skill-same:01M7D2PW9A72PBPDGS5FH87BMR":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D2PW9A72PBPDGS5FH87BMR","copy-to-output-directory",null,"Choosing an MSBuild CopyToOutputDirectory \u002F CopyToPublishDirectory mode: Never, PreserveNewest, Always, and IfDifferent (MSBuild 17.13+), plus $(SkipUnchangedFilesOnCopyAlways). USE FOR: removing the per-build Always copy perf hit; resetting output files mutated between builds. DO NOT USE FOR: general incremental-build diagnosis (use incremental-build); non-MSBuild build systems.","itsmejay18\u002FAI-Skills-for-My-Development-Stack","itsmejay18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167779943?v=4","01M7CZRFC6DDZA5V2CX8WDSZED","Jay Jemino Ababon ","01M7CZRFCVRNW1SFHSQXEJ3CQN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fcopy-to-output-directory\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: copy-to-output-directory\ndescription: \"Choosing an MSBuild CopyToOutputDirectory \u002F CopyToPublishDirectory mode: Never, PreserveNewest, Always, and IfDifferent (MSBuild 17.13+), plus $(SkipUnchangedFilesOnCopyAlways). USE FOR: removing the per-build Always copy perf hit; resetting output files mutated between builds. DO NOT USE FOR: general incremental-build diagnosis (use incremental-build); non-MSBuild build systems.\"\nlicense: MIT\n---\n\n# Choosing a CopyToOutputDirectory Mode\n\n## Overview\n\nThe `CopyToOutputDirectory` metadata (and its publish counterpart `CopyToPublishDirectory`) controls whether an item — `Content`, `None`, `EmbeddedResource`, or `Compile` — is copied next to your build output, and under what conditions the copy happens. Picking the wrong mode causes either stale files in `bin\u002F` or an unnecessary per-build performance hit.\n\nAs of **MSBuild 17.13 \u002F .NET SDK 9.0.2xx** there are four values:\n\n| Mode | Copies when… | Incremental cost | Typical use |\n| --- | --- | --- | --- |\n| `Never` (default) | Never | None | Files not needed at runtime |\n| `PreserveNewest` | Source is **newer** than destination (or destination missing) | Cheap (timestamp check) | The common case — source files you edit |\n| `Always` | **Every build**, unconditionally | Expensive — copies on every build even in no-op builds | Legacy workaround; avoid (see below) |\n| `IfDifferent` | Source **differs** from destination in either direction (newer **or** older, or size differs, or destination missing) | Cheap (timestamp + size check) | Destination may be mutated between builds |\n\n```xml\n\u003CItemGroup>\n  \u003CNone Include=\"appsettings.json\" CopyToOutputDirectory=\"PreserveNewest\" \u002F>\n  \u003CNone Include=\"testdata\\seed.db\"  CopyToOutputDirectory=\"IfDifferent\" \u002F>\n\u003C\u002FItemGroup>\n```\n\nYou can use either the attribute form shown above or the child-element form:\n\n```xml\n\u003CNone Include=\"testdata\\seed.db\">\n  \u003CCopyToOutputDirectory>IfDifferent\u003C\u002FCopyToOutputDirectory>\n\u003C\u002FNone>\n```\n\n## Why `Always` is usually the wrong choice\n\n`Always` re-copies the file on **every** build, including otherwise-clean incremental\u002Fno-op builds. On projects with many or large content files this is a measurable, recurring cost and a common cause of \"why is my no-op build not instant?\" reports.\n\nHistorically `Always` was the only way to handle a specific scenario: **the destination file can change between builds** — for example an SQLite database, a storage\u002Fstate file, or a config file that a test run mutates. With `PreserveNewest`, if the destination is modified (making its timestamp *newer* than the source) MSBuild will *not* restore the original source file, because the source is no longer newer. People reached for `Always` to force the file back into a known-good state — paying the copy cost on every build as a side effect.\n\n## `IfDifferent`: copy when different, in either direction\n\n`IfDifferent` is the targeted fix for that scenario. It copies the source over the destination whenever MSBuild considers the two **different** — whether the source is newer *or* older than the destination, whether the size differs, or the destination is missing — and skips the copy when the destination is unchanged per MSBuild's heuristic.\n\nUnder the hood the `_CopyDifferingSourceItemsToOutputDirectory` target uses the `Copy` task with `SkipUnchangedFiles=\"true\"`. That \"unchanged\" check is a **heuristic**: it compares **last-write timestamp and file size only** — not a content hash — so a destination that was edited to the same size and timestamp as the source is treated as unchanged and is *not* re-copied. In practice this restores a mutated destination back to the source version on the next build (the reason people reached for `Always`) while avoiding the unconditional per-build copy.\n\nUse `IfDifferent` when:\n\n- A test run or the app itself writes to the copied file (databases, caches, state\u002Fstorage files, editable config) and you want each build to reset it to the source version.\n- You were using `Always` purely as a \"keep the output in sync with the source\" mechanism, not because you truly need a copy on every single build.\n\n```xml\n\u003CItemGroup>\n  \u003C!-- Reset the fixture DB to the source copy whenever it has drifted,\n       but don't pay a copy on every no-op build. -->\n  \u003CNone Include=\"fixtures\\catalog.db\" CopyToOutputDirectory=\"IfDifferent\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n## Globally softening `Always` with `$(SkipUnchangedFilesOnCopyAlways)`\n\nIf you have an existing codebase full of `CopyToOutputDirectory=\"Always\"` items and want the performance benefit without editing every item, set the property:\n\n```xml\n\u003CPropertyGroup>\n  \u003CSkipUnchangedFilesOnCopyAlways>true\u003C\u002FSkipUnchangedFilesOnCopyAlways>\n\u003C\u002FPropertyGroup>\n```\n\nThis makes the `_CopyOutOfDateSourceItemsToOutputDirectoryAlways` target pass `SkipUnchangedFiles=\"true\"` to its `Copy` task, so `Always` items are only copied when they actually differ — effectively giving `Always` the same skip-unchanged behavior as `IfDifferent`.\n\n- Default is `false` for backwards compatibility (classic `Always` = copy every build).\n- Set it in `Directory.Build.props` to opt an entire repo in at once.\n- Prefer converting individual items to `IfDifferent` when you can; use this property when a bulk, non-invasive opt-in is more practical.\n\n## How the modes flow through the build\n\n`GetCopyToOutputDirectoryItems` buckets each item by its `CopyToOutputDirectory` value. Three copy targets then do the work as dependencies of `_CopySourceItemsToOutputDirectory` (which is itself invoked by `CopyFilesToOutputDirectory`):\n\n- `_CopyOutOfDateSourceItemsToOutputDirectory` — `PreserveNewest` items (incremental via `Inputs`\u002F`Outputs` timestamp comparison).\n- `_CopyOutOfDateSourceItemsToOutputDirectoryAlways` — `Always` items (unconditional copy unless `$(SkipUnchangedFilesOnCopyAlways)` is `true`).\n- `_CopyDifferingSourceItemsToOutputDirectory` — `IfDifferent` items (`SkipUnchangedFiles=\"true\"`).\n\nAll copied files are registered in `FileWrites`, so `dotnet clean` removes them.\n\n**Transitive copy:** items marked `Always`, `PreserveNewest`, or `IfDifferent` also flow to referencing projects through `ProjectReference` (via `_CopyToOutputDirectoryTransitiveItems`). `Never` items do not. `IfDifferent` participates in ClickOnce publish item collection alongside `Always`\u002F`PreserveNewest`.\n\n## Version requirement\n\n`IfDifferent` and `$(SkipUnchangedFilesOnCopyAlways)` require **MSBuild 17.13 or later** (**.NET SDK 9.0.2xx+ \u002F Visual Studio 2022 17.13+**). On older toolsets the value is not recognized: it will not match the `Always`\u002F`PreserveNewest`\u002F`IfDifferent` conditions in the common targets, so the item is silently **not copied**. Gate usage on the toolset if you must support older SDKs, or require the minimum SDK via `global.json`.\n\n## Quick decision guide\n\n- Don't need the file at runtime → `Never` (or omit — it's the default).\n- Normal source file you edit → `PreserveNewest`.\n- Destination gets mutated between builds and must be reset to the source → `IfDifferent`.\n- You truly need a fresh copy on literally every build → `Always` (rare).\n- Stuck with lots of legacy `Always` and want the perf win without edits → keep `Always` but set `$(SkipUnchangedFilesOnCopyAlways)=true`.\n","# Choosing a CopyToOutputDirectory Mode\n\n## Overview\n\nThe `CopyToOutputDirectory` metadata (and its publish counterpart `CopyToPublishDirectory`) controls whether an item — `Content`, `None`, `EmbeddedResource`, or `Compile` — is copied next to your build output, and under what conditions the copy happens. Picking the wrong mode causes either stale files in `bin\u002F` or an unnecessary per-build performance hit.\n\nAs of **MSBuild 17.13 \u002F .NET SDK 9.0.2xx** there are four values:\n\n| Mode | Copies when… | Incremental cost | Typical use |\n| --- | --- | --- | --- |\n| `Never` (default) | Never | None | Files not needed at runtime |\n| `PreserveNewest` | Source is **newer** than destination (or destination missing) | Cheap (timestamp check) | The common case — source files you edit |\n| `Always` | **Every build**, unconditionally | Expensive — copies on every build even in no-op builds | Legacy workaround; avoid (see below) |\n| `IfDifferent` | Source **differs** from destination in either direction (newer **or** older, or size differs, or destination missing) | Cheap (timestamp + size check) | Destination may be mutated between builds |\n\n```xml\n\u003CItemGroup>\n  \u003CNone Include=\"appsettings.json\" CopyToOutputDirectory=\"PreserveNewest\" \u002F>\n  \u003CNone Include=\"testdata\\seed.db\"  CopyToOutputDirectory=\"IfDifferent\" \u002F>\n\u003C\u002FItemGroup>\n```\n\nYou can use either the attribute form shown above or the child-element form:\n\n```xml\n\u003CNone Include=\"testdata\\seed.db\">\n  \u003CCopyToOutputDirectory>IfDifferent\u003C\u002FCopyToOutputDirectory>\n\u003C\u002FNone>\n```\n\n## Why `Always` is usually the wrong choice\n\n`Always` re-copies the file on **every** build, including otherwise-clean incremental\u002Fno-op builds. On projects with many or large content files this is a measurable, recurring cost and a common cause of \"why is my no-op build not instant?\" reports.\n\nHistorically `Always` was the only way to handle a specific scenario: **the destination file can change between builds** — for example an SQLite database, a storage\u002Fstate file, or a config file that a test run mutates. With `PreserveNewest`, if the destination is modified (making its timestamp *newer* than the source) MSBuild will *not* restore the original source file, because the source is no longer newer. People reached for `Always` to force the file back into a known-good state — paying the copy cost on every build as a side effect.\n\n## `IfDifferent`: copy when different, in either direction\n\n`IfDifferent` is the targeted fix for that scenario. It copies the source over the destination whenever MSBuild considers the two **different** — whether the source is newer *or* older than the destination, whether the size differs, or the destination is missing — and skips the copy when the destination is unchanged per MSBuild's heuristic.\n\nUnder the hood the `_CopyDifferingSourceItemsToOutputDirectory` target uses the `Copy` task with `SkipUnchangedFiles=\"true\"`. That \"unchanged\" check is a **heuristic**: it compares **last-write timestamp and file size only** — not a content hash — so a destination that was edited to the same size and timestamp as the source is treated as unchanged and is *not* re-copied. In practice this restores a mutated destination back to the source version on the next build (the reason people reached for `Always`) while avoiding the unconditional per-build copy.\n\nUse `IfDifferent` when:\n\n- A test run or the app itself writes to the copied file (databases, caches, state\u002Fstorage files, editable config) and you want each build to reset it to the source version.\n- You were using `Always` purely as a \"keep the output in sync with the source\" mechanism, not because you truly need a copy on every single build.\n\n```xml\n\u003CItemGroup>\n  \u003C!-- Reset the fixture DB to the source copy whenever it has drifted,\n       but don't pay a copy on every no-op build. -->\n  \u003CNone Include=\"fixtures\\catalog.db\" CopyToOutputDirectory=\"IfDifferent\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n## Globally softening `Always` with `$(SkipUnchangedFilesOnCopyAlways)`\n\nIf you have an existing codebase full of `CopyToOutputDirectory=\"Always\"` items and want the performance benefit without editing every item, set the property:\n\n```xml\n\u003CPropertyGroup>\n  \u003CSkipUnchangedFilesOnCopyAlways>true\u003C\u002FSkipUnchangedFilesOnCopyAlways>\n\u003C\u002FPropertyGroup>\n```\n\nThis makes the `_CopyOutOfDateSourceItemsToOutputDirectoryAlways` target pass `SkipUnchangedFiles=\"true\"` to its `Copy` task, so `Always` items are only copied when they actually differ — effectively giving `Always` the same skip-unchanged behavior as `IfDifferent`.\n\n- Default is `false` for backwards compatibility (classic `Always` = copy every build).\n- Set it in `Directory.Build.props` to opt an entire repo in at once.\n- Prefer converting individual items to `IfDifferent` when you can; use this property when a bulk, non-invasive opt-in is more practical.\n\n## How the modes flow through the build\n\n`GetCopyToOutputDirectoryItems` buckets each item by its `CopyToOutputDirectory` value. Three copy targets then do the work as dependencies of `_CopySourceItemsToOutputDirectory` (which is itself invoked by `CopyFilesToOutputDirectory`):\n\n- `_CopyOutOfDateSourceItemsToOutputDirectory` — `PreserveNewest` items (incremental via `Inputs`\u002F`Outputs` timestamp comparison).\n- `_CopyOutOfDateSourceItemsToOutputDirectoryAlways` — `Always` items (unconditional copy unless `$(SkipUnchangedFilesOnCopyAlways)` is `true`).\n- `_CopyDifferingSourceItemsToOutputDirectory` — `IfDifferent` items (`SkipUnchangedFiles=\"true\"`).\n\nAll copied files are registered in `FileWrites`, so `dotnet clean` removes them.\n\n**Transitive copy:** items marked `Always`, `PreserveNewest`, or `IfDifferent` also flow to referencing projects through `ProjectReference` (via `_CopyToOutputDirectoryTransitiveItems`). `Never` items do not. `IfDifferent` participates in ClickOnce publish item collection alongside `Always`\u002F`PreserveNewest`.\n\n## Version requirement\n\n`IfDifferent` and `$(SkipUnchangedFilesOnCopyAlways)` require **MSBuild 17.13 or later** (**.NET SDK 9.0.2xx+ \u002F Visual Studio 2022 17.13+**). On older toolsets the value is not recognized: it will not match the `Always`\u002F`PreserveNewest`\u002F`IfDifferent` conditions in the common targets, so the item is silently **not copied**. Gate usage on the toolset if you must support older SDKs, or require the minimum SDK via `global.json`.\n\n## Quick decision guide\n\n- Don't need the file at runtime → `Never` (or omit — it's the default).\n- Normal source file you edit → `PreserveNewest`.\n- Destination gets mutated between builds and must be reset to the source → `IfDifferent`.\n- You truly need a fresh copy on literally every build → `Always` (rare).\n- Stuck with lots of legacy `Always` and want the perf win without edits → keep `Always` but set `$(SkipUnchangedFilesOnCopyAlways)=true`.\n",{"name":5,"license":15,"description":7},"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","20-Performance-Optimization\u002Fcopy-to-output-directory","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack","https:\u002F\u002Fgithub.com\u002Fitsmejay18","2026-09-18 16:06:36",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill copy-to-output-directory",{"tool":36,"command":37},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill copy-to-output-directory",{"tool":39,"command":40},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill copy-to-output-directory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fcopy-to-output-directory\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7D2RKBHPZ3E1RNN5DWHT550","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including Vector\u003CT>, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D2RDJ7RN3QK8GJR0QTER1D","resolve-project-references","Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fresolve-project-references\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D2R1H2GTNZYHG9YRX3JDQW","optimizing-ef-core-queries","Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database schema. For EF Core, not Dapper or raw ADO.NET.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Foptimizing-ef-core-queries\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D2QREG04W1YT0NEBHEW5C9","microbenchmarking","Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling\u002Ftracing .NET code (dotnet-trace, PerfView), production telemetry, or load\u002Fstress testing (Crank, k6).","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fmicrobenchmarking\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D2QGE175XWPZVACVH2868Z","incremental-build","Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs\u002FOutputs on custom targets, volatile properties in output paths (timestamps\u002FGUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fincremental-build\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D2Q1DQTC6K49R73WQTTPSB","eval-performance","Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Feval-performance\u002FSKILL.md",[],[]]