[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D0F2FJ30M7F0K6R22SCPKS":3,"skill-same:01M7D0F2FJ30M7F0K6R22SCPKS":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},"01M7D0F2FJ30M7F0K6R22SCPKS","including-generated-files",null,"Fix MSBuild targets that generate files during the build but those files are missing from compilation or output. USE FOR: generated source files not compiling (CS0246 for a type that should exist), custom build tasks that create files but they are invisible to subsequent targets, globs not capturing build-generated files because they expand at evaluation time before execution creates them, ensuring generated files are cleaned by the Clean target. Covers correct BeforeTargets timing (CoreCompile, BeforeBuild, AssignTargetPaths), adding to Compile\u002FFileWrites item groups, using $(IntermediateOutputPath) instead of hardcoded obj\u002F paths. DO NOT USE FOR: C# source generators that already work via the Roslyn pipeline, T4 design-time generation that runs in Visual Studio, 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\u002F02-CSharp-WPF-Desktop-Development\u002Fincluding-generated-files\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: including-generated-files\ndescription: \"Fix MSBuild targets that generate files during the build but those files are missing from compilation or output. USE FOR: generated source files not compiling (CS0246 for a type that should exist), custom build tasks that create files but they are invisible to subsequent targets, globs not capturing build-generated files because they expand at evaluation time before execution creates them, ensuring generated files are cleaned by the Clean target. Covers correct BeforeTargets timing (CoreCompile, BeforeBuild, AssignTargetPaths), adding to Compile\u002FFileWrites item groups, using $(IntermediateOutputPath) instead of hardcoded obj\u002F paths. DO NOT USE FOR: C# source generators that already work via the Roslyn pipeline, T4 design-time generation that runs in Visual Studio, non-MSBuild build systems.\"\nlicense: MIT\n---\n\n# Including Generated Files Into Your Build\n\n## Overview\n\nFiles generated during the build are generally ignored by the build process. This leads to confusing results such as:\n- Generated files not being included in the output directory\n- Generated source files not being compiled\n- Globs not capturing files created during the build\n\nThis happens because of how MSBuild's build phases work.\n\n## Quick Takeaway\n\nFor code files generated during the build - we need to add those to `Compile` and `FileWrites` item groups within the target generating the file(s):\n\n```xml\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n```\n\nThe target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - `BeforeTargets=\"CoreCompile;BeforeCompile\"`\n\n## Why Generated Files Are Ignored\n\nFor detailed explanation, see [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n### Evaluation Phase\n\nMSBuild reads your project, imports everything, creates Properties, expands globs for Items **outside of Targets**, and sets up the build process.\n\n### Execution Phase\n\nMSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.\n\n**Key Takeaway:** Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (`.cs`).\n\n## Solution: Manually Add Generated Files\n\nWhen files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.\n\n### Use `$(IntermediateOutputPath)` for Generated File Location\n\nAlways use `$(IntermediateOutputPath)` as the base directory for generated files. **Do not** hardcode `obj\\` or construct the intermediary path manually (e.g., `obj\\$(Configuration)\\$(TargetFramework)\\`). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using `$(IntermediateOutputPath)` ensures your target works correctly regardless of the actual path.\n\n### Always Add Generated Files to `FileWrites`\n\nEvery generated file should be added to the `FileWrites` item group. This ensures that MSBuild's `Clean` target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.\n\n```xml\n\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n### Basic Pattern (Non-Code Files)\n\nFor generated files that need to be copied to output (config files, data files, etc.), add them to `Content` or `None` items before `BeforeBuild`:\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\n### For Generated Source Files (Code That Needs Compilation)\n\nIf you're generating `.cs` files that need to be compiled, use **`BeforeTargets=\"CoreCompile;BeforeCompile\"`**. This is the correct timing for adding `Compile` items — it runs late enough that the file generation has occurred, but before the compiler runs. Using `BeforeBuild` is too early for some scenarios and may not work reliably with all SDK features.\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\nNote: Specifying both `CoreCompile` and `BeforeCompile` ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.\n\n## Target Timing\n\nChoose the `BeforeTargets` value based on the type of file being generated:\n\n- **`BeforeTargets=\"BeforeBuild\"`** — For non-code files added to `None` or `Content`. Runs early enough for copy-to-output scenarios.\n- **`BeforeTargets=\"CoreCompile;BeforeCompile\"`** — For generated source files added to `Compile`. Ensures the file is included before the compiler runs.\n- **`BeforeTargets=\"AssignTargetPaths\"`** — The \"final stop\" before `None` and `Content` items (among others) are transformed into new items. Use as a fallback if `BeforeBuild` is too early.\n\n## Globbing Behavior\n\nGlobs behave according to **when** the glob took place:\n\n| Glob Location | Files Captured |\n|---------------|----------------|\n| Outside of a target | Only files visible during Evaluation phase (before build starts) |\n| Inside of a target | Files visible when the target runs (can capture generated files if timed correctly) |\n\nThis is why the solution places the `\u003CItemGroup>` inside a `\u003CTarget>` - the glob runs during execution when the generated files exist.\n\n## Relevant Links\n\n- [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview)\n- [Evaluation Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase)\n- [Execution Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase)\n- [Common Item Types](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items)\n- [How the SDK imports items by default](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props)\n- [Official docs: Handle generated files](https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files)\n","# Including Generated Files Into Your Build\n\n## Overview\n\nFiles generated during the build are generally ignored by the build process. This leads to confusing results such as:\n- Generated files not being included in the output directory\n- Generated source files not being compiled\n- Globs not capturing files created during the build\n\nThis happens because of how MSBuild's build phases work.\n\n## Quick Takeaway\n\nFor code files generated during the build - we need to add those to `Compile` and `FileWrites` item groups within the target generating the file(s):\n\n```xml\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n```\n\nThe target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - `BeforeTargets=\"CoreCompile;BeforeCompile\"`\n\n## Why Generated Files Are Ignored\n\nFor detailed explanation, see [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n### Evaluation Phase\n\nMSBuild reads your project, imports everything, creates Properties, expands globs for Items **outside of Targets**, and sets up the build process.\n\n### Execution Phase\n\nMSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.\n\n**Key Takeaway:** Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (`.cs`).\n\n## Solution: Manually Add Generated Files\n\nWhen files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.\n\n### Use `$(IntermediateOutputPath)` for Generated File Location\n\nAlways use `$(IntermediateOutputPath)` as the base directory for generated files. **Do not** hardcode `obj\\` or construct the intermediary path manually (e.g., `obj\\$(Configuration)\\$(TargetFramework)\\`). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using `$(IntermediateOutputPath)` ensures your target works correctly regardless of the actual path.\n\n### Always Add Generated Files to `FileWrites`\n\nEvery generated file should be added to the `FileWrites` item group. This ensures that MSBuild's `Clean` target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.\n\n```xml\n\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n### Basic Pattern (Non-Code Files)\n\nFor generated files that need to be copied to output (config files, data files, etc.), add them to `Content` or `None` items before `BeforeBuild`:\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\n### For Generated Source Files (Code That Needs Compilation)\n\nIf you're generating `.cs` files that need to be compiled, use **`BeforeTargets=\"CoreCompile;BeforeCompile\"`**. This is the correct timing for adding `Compile` items — it runs late enough that the file generation has occurred, but before the compiler runs. Using `BeforeBuild` is too early for some scenarios and may not work reliably with all SDK features.\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\nNote: Specifying both `CoreCompile` and `BeforeCompile` ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.\n\n## Target Timing\n\nChoose the `BeforeTargets` value based on the type of file being generated:\n\n- **`BeforeTargets=\"BeforeBuild\"`** — For non-code files added to `None` or `Content`. Runs early enough for copy-to-output scenarios.\n- **`BeforeTargets=\"CoreCompile;BeforeCompile\"`** — For generated source files added to `Compile`. Ensures the file is included before the compiler runs.\n- **`BeforeTargets=\"AssignTargetPaths\"`** — The \"final stop\" before `None` and `Content` items (among others) are transformed into new items. Use as a fallback if `BeforeBuild` is too early.\n\n## Globbing Behavior\n\nGlobs behave according to **when** the glob took place:\n\n| Glob Location | Files Captured |\n|---------------|----------------|\n| Outside of a target | Only files visible during Evaluation phase (before build starts) |\n| Inside of a target | Files visible when the target runs (can capture generated files if timed correctly) |\n\nThis is why the solution places the `\u003CItemGroup>` inside a `\u003CTarget>` - the glob runs during execution when the generated files exist.\n\n## Relevant Links\n\n- [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview)\n- [Evaluation Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase)\n- [Execution Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase)\n- [Common Item Types](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items)\n- [How the SDK imports items by default](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props)\n- [Official docs: Handle generated files](https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files)\n",{"name":5,"license":15,"description":7},"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","02-CSharp-WPF-Desktop-Development\u002Fincluding-generated-files","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 including-generated-files",{"tool":36,"command":37},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill including-generated-files",{"tool":39,"command":40},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill including-generated-files","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fincluding-generated-files\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",[],[]]