[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D22MYMN69YXBXVGRR2RASD":3,"skill-same:01M7D22MYMN69YXBXVGRR2RASD":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7D22MYMN69YXBXVGRR2RASD","filter-syntax",null,"Reference-only filter syntax for VSTest and MTP with MSTest, NUnit, xUnit v3, and TUnit. Load only after the platform\u002Fframework is known and a consumer needs to create or translate a filter. Do not load for unfiltered runs or platform detection. Used by run-tests and mtp-hot-reload; never invoke directly.","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\u002F13-Testing-QA\u002Ffilter-syntax\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: filter-syntax\ndescription: \"Reference-only filter syntax for VSTest and MTP with MSTest, NUnit, xUnit v3, and TUnit. Load only after the platform\u002Fframework is known and a consumer needs to create or translate a filter. Do not load for unfiltered runs or platform detection. Used by run-tests and mtp-hot-reload; never invoke directly.\"\nuser-invocable: false\ndisable-model-invocation: true\nlicense: MIT\n---\n\n# Test Filter Syntax Reference\n\nFilter syntax depends on the **platform** and **test framework**.\n\n## VSTest filters (MSTest, xUnit v2, NUnit on VSTest)\n\n```bash\ndotnet test --filter \u003CEXPRESSION>\n```\n\nExpression syntax: `\u003CProperty>\u003COperator>\u003CValue>[|&\u003CExpression>]`\n\n**Operators:**\n\n| Operator | Meaning |\n|----------|---------|\n| `=` | Exact match |\n| `!=` | Not exact match |\n| `~` | Contains |\n| `!~` | Does not contain |\n\n**Combinators:** `|` (OR), `&` (AND). Parentheses for grouping: `(A|B)&C`\n\n**Supported properties by framework:**\n\n| Framework | Properties |\n|-----------|-----------|\n| MSTest | `FullyQualifiedName`, `Name`, `ClassName`, `Priority`, `TestCategory` |\n| xUnit | `FullyQualifiedName`, `DisplayName`, `Traits` |\n| NUnit | `FullyQualifiedName`, `Name`, `Priority`, `TestCategory` |\n\nAn expression without an operator is treated as `FullyQualifiedName~\u003Cvalue>`.\n\n**Examples (VSTest):**\n\n```bash\n# Run tests whose name contains \"LoginTest\"\ndotnet test --filter \"Name~LoginTest\"\n\n# Run a specific test class\ndotnet test --filter \"ClassName=MyNamespace.MyTestClass\"\n\n# Run tests in a category\ndotnet test --filter \"TestCategory=Integration\"\n\n# Exclude a category\ndotnet test --filter \"TestCategory!=Slow\"\n\n# Combine: class AND category\ndotnet test --filter \"ClassName=MyNamespace.MyTestClass&TestCategory=Unit\"\n\n# Either of two classes\ndotnet test --filter \"ClassName=MyNamespace.ClassA|ClassName=MyNamespace.ClassB\"\n```\n\n## MTP filters — MSTest and NUnit\n\nMSTest and NUnit on MTP use the **same `--filter` syntax** as VSTest (same properties, operators, and combinators). The only difference is how the flag is passed:\n\n```bash\n# .NET SDK 8\u002F9 (after --)\ndotnet test -- --filter \"Name~LoginTest\"\n\n# .NET SDK 10+ (direct)\ndotnet test --filter \"Name~LoginTest\"\n```\n\n## MTP filters — xUnit (v3)\n\nxUnit v3 on MTP uses **framework-specific filter flags** instead of the generic `--filter` expression:\n\n| Flag | Description |\n|------|-------------|\n| `--filter-class \"name\"` | Run all tests in a given class |\n| `--filter-not-class \"name\"` | Exclude all tests in a given class |\n| `--filter-method \"name\"` | Run a specific test method |\n| `--filter-not-method \"name\"` | Exclude a specific test method |\n| `--filter-namespace \"name\"` | Run all tests in a namespace |\n| `--filter-not-namespace \"name\"` | Exclude all tests in a namespace |\n| `--filter-trait \"name=value\"` | Run tests with a matching trait |\n| `--filter-not-trait \"name=value\"` | Exclude tests with a matching trait |\n\nMultiple values can be specified with a single flag: `--filter-class Foo Bar`.\n\n```bash\n# .NET SDK 8\u002F9\ndotnet test -- --filter-class \"MyNamespace.LoginTests\"\n\n# .NET SDK 10+\ndotnet test --filter-class \"MyNamespace.LoginTests\"\n\n# Combine: namespace + trait\ndotnet test --filter-namespace \"MyApp.Tests.Integration\" --filter-trait \"Category=Smoke\"\n```\n\n### xUnit v3 query filter language\n\nFor complex expressions, use `--filter-query` with a path-segment syntax:\n\n```text\n\u002F\u003CassemblyFilter>\u002F\u003CnamespaceFilter>\u002F\u003CclassFilter>\u002F\u003CmethodFilter>[traitName=traitValue]\n```\n\nEach segment matches against: assembly name, namespace, class name, method name. Use `*` for \"match all\" in any segment. Documentation: \u003Chttps:\u002F\u002Fxunit.net\u002Fdocs\u002Fquery-filter-language>\n\n```shell\n# xUnit.net v3 MTP — using query language (assembly\u002Fnamespace\u002Fclass\u002Fmethod[trait])\ndotnet test -- --filter-query \"\u002F*\u002F*\u002F*IntegrationTests*\u002F*[Category=Smoke]\"\n```\n\n## MTP filters — TUnit\n\nTUnit uses `--treenode-filter` with a path-based syntax:\n\n```text\n--treenode-filter \"\u002F\u003CAssembly>\u002F\u003CNamespace>\u002F\u003CClassName>\u002F\u003CTestName>\"\n```\n\nWildcards (`*`) are supported in any segment. Filter operators can be appended to test names for property-based filtering.\n\n| Operator | Meaning |\n|----------|---------|\n| `*` | Wildcard match |\n| `=` | Exact property match (e.g., `[Category=Unit]`) |\n| `!=` | Exclude property value |\n| `&` | AND (combine conditions) |\n| `\\|` | OR (within a segment, requires parentheses) |\n\n**Examples (TUnit):**\n\n```bash\n# All tests in a class\ndotnet run --treenode-filter \"\u002F*\u002F*\u002FLoginTests\u002F*\"\n\n# A specific test\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002FAcceptCookiesTest\"\n\n# By namespace prefix (wildcard)\ndotnet run --treenode-filter \"\u002F*\u002FMyProject.Tests.Api*\u002F*\u002F*\"\n\n# By custom property\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002F*[Category=Smoke]\"\n\n# Exclude by property\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002F*[Category!=Slow]\"\n\n# OR across classes\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F(LoginTests)|(SignupTests)\u002F*\"\n\n# Combined: namespace + property\ndotnet run --treenode-filter \"\u002F*\u002FMyProject.Tests.Integration\u002F*\u002F*\u002F*[Priority=Critical]\"\n```\n\n## VSTest → MTP filter translation (for migration)\n\n**MSTest, NUnit, and xUnit.net v2 (with `YTest.MTP.XUnit2`)**: The VSTest `--filter` syntax is identical on both VSTest and MTP. No changes needed.\n\n**xUnit.net v3 (native MTP)**: xUnit.net v3 does NOT support the VSTest `--filter` syntax on MTP. Translate filters using xUnit.net v3's native options:\n\n| VSTest `--filter` syntax | xUnit.net v3 MTP equivalent | Notes |\n|---|---|---|\n| `FullyQualifiedName~ClassName` | `--filter-class *ClassName*` | Wildcards required for substring match |\n| `FullyQualifiedName=Ns.Class.Method` | `--filter-method Ns.Class.Method` | Exact match on fully qualified method |\n| `Name=MethodName` | `--filter-method *MethodName*` | Wildcards for substring match |\n| `Category=Value` (trait) | `--filter-trait \"Category=Value\"` | Filter by trait name\u002Fvalue pair |\n| Complex expressions | `--filter-query \"expr\"` | Uses xUnit.net query filter language (see above) |\n","# Test Filter Syntax Reference\n\nFilter syntax depends on the **platform** and **test framework**.\n\n## VSTest filters (MSTest, xUnit v2, NUnit on VSTest)\n\n```bash\ndotnet test --filter \u003CEXPRESSION>\n```\n\nExpression syntax: `\u003CProperty>\u003COperator>\u003CValue>[|&\u003CExpression>]`\n\n**Operators:**\n\n| Operator | Meaning |\n|----------|---------|\n| `=` | Exact match |\n| `!=` | Not exact match |\n| `~` | Contains |\n| `!~` | Does not contain |\n\n**Combinators:** `|` (OR), `&` (AND). Parentheses for grouping: `(A|B)&C`\n\n**Supported properties by framework:**\n\n| Framework | Properties |\n|-----------|-----------|\n| MSTest | `FullyQualifiedName`, `Name`, `ClassName`, `Priority`, `TestCategory` |\n| xUnit | `FullyQualifiedName`, `DisplayName`, `Traits` |\n| NUnit | `FullyQualifiedName`, `Name`, `Priority`, `TestCategory` |\n\nAn expression without an operator is treated as `FullyQualifiedName~\u003Cvalue>`.\n\n**Examples (VSTest):**\n\n```bash\n# Run tests whose name contains \"LoginTest\"\ndotnet test --filter \"Name~LoginTest\"\n\n# Run a specific test class\ndotnet test --filter \"ClassName=MyNamespace.MyTestClass\"\n\n# Run tests in a category\ndotnet test --filter \"TestCategory=Integration\"\n\n# Exclude a category\ndotnet test --filter \"TestCategory!=Slow\"\n\n# Combine: class AND category\ndotnet test --filter \"ClassName=MyNamespace.MyTestClass&TestCategory=Unit\"\n\n# Either of two classes\ndotnet test --filter \"ClassName=MyNamespace.ClassA|ClassName=MyNamespace.ClassB\"\n```\n\n## MTP filters — MSTest and NUnit\n\nMSTest and NUnit on MTP use the **same `--filter` syntax** as VSTest (same properties, operators, and combinators). The only difference is how the flag is passed:\n\n```bash\n# .NET SDK 8\u002F9 (after --)\ndotnet test -- --filter \"Name~LoginTest\"\n\n# .NET SDK 10+ (direct)\ndotnet test --filter \"Name~LoginTest\"\n```\n\n## MTP filters — xUnit (v3)\n\nxUnit v3 on MTP uses **framework-specific filter flags** instead of the generic `--filter` expression:\n\n| Flag | Description |\n|------|-------------|\n| `--filter-class \"name\"` | Run all tests in a given class |\n| `--filter-not-class \"name\"` | Exclude all tests in a given class |\n| `--filter-method \"name\"` | Run a specific test method |\n| `--filter-not-method \"name\"` | Exclude a specific test method |\n| `--filter-namespace \"name\"` | Run all tests in a namespace |\n| `--filter-not-namespace \"name\"` | Exclude all tests in a namespace |\n| `--filter-trait \"name=value\"` | Run tests with a matching trait |\n| `--filter-not-trait \"name=value\"` | Exclude tests with a matching trait |\n\nMultiple values can be specified with a single flag: `--filter-class Foo Bar`.\n\n```bash\n# .NET SDK 8\u002F9\ndotnet test -- --filter-class \"MyNamespace.LoginTests\"\n\n# .NET SDK 10+\ndotnet test --filter-class \"MyNamespace.LoginTests\"\n\n# Combine: namespace + trait\ndotnet test --filter-namespace \"MyApp.Tests.Integration\" --filter-trait \"Category=Smoke\"\n```\n\n### xUnit v3 query filter language\n\nFor complex expressions, use `--filter-query` with a path-segment syntax:\n\n```text\n\u002F\u003CassemblyFilter>\u002F\u003CnamespaceFilter>\u002F\u003CclassFilter>\u002F\u003CmethodFilter>[traitName=traitValue]\n```\n\nEach segment matches against: assembly name, namespace, class name, method name. Use `*` for \"match all\" in any segment. Documentation: \u003Chttps:\u002F\u002Fxunit.net\u002Fdocs\u002Fquery-filter-language>\n\n```shell\n# xUnit.net v3 MTP — using query language (assembly\u002Fnamespace\u002Fclass\u002Fmethod[trait])\ndotnet test -- --filter-query \"\u002F*\u002F*\u002F*IntegrationTests*\u002F*[Category=Smoke]\"\n```\n\n## MTP filters — TUnit\n\nTUnit uses `--treenode-filter` with a path-based syntax:\n\n```text\n--treenode-filter \"\u002F\u003CAssembly>\u002F\u003CNamespace>\u002F\u003CClassName>\u002F\u003CTestName>\"\n```\n\nWildcards (`*`) are supported in any segment. Filter operators can be appended to test names for property-based filtering.\n\n| Operator | Meaning |\n|----------|---------|\n| `*` | Wildcard match |\n| `=` | Exact property match (e.g., `[Category=Unit]`) |\n| `!=` | Exclude property value |\n| `&` | AND (combine conditions) |\n| `\\|` | OR (within a segment, requires parentheses) |\n\n**Examples (TUnit):**\n\n```bash\n# All tests in a class\ndotnet run --treenode-filter \"\u002F*\u002F*\u002FLoginTests\u002F*\"\n\n# A specific test\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002FAcceptCookiesTest\"\n\n# By namespace prefix (wildcard)\ndotnet run --treenode-filter \"\u002F*\u002FMyProject.Tests.Api*\u002F*\u002F*\"\n\n# By custom property\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002F*[Category=Smoke]\"\n\n# Exclude by property\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F*\u002F*[Category!=Slow]\"\n\n# OR across classes\ndotnet run --treenode-filter \"\u002F*\u002F*\u002F(LoginTests)|(SignupTests)\u002F*\"\n\n# Combined: namespace + property\ndotnet run --treenode-filter \"\u002F*\u002FMyProject.Tests.Integration\u002F*\u002F*\u002F*[Priority=Critical]\"\n```\n\n## VSTest → MTP filter translation (for migration)\n\n**MSTest, NUnit, and xUnit.net v2 (with `YTest.MTP.XUnit2`)**: The VSTest `--filter` syntax is identical on both VSTest and MTP. No changes needed.\n\n**xUnit.net v3 (native MTP)**: xUnit.net v3 does NOT support the VSTest `--filter` syntax on MTP. Translate filters using xUnit.net v3's native options:\n\n| VSTest `--filter` syntax | xUnit.net v3 MTP equivalent | Notes |\n|---|---|---|\n| `FullyQualifiedName~ClassName` | `--filter-class *ClassName*` | Wildcards required for substring match |\n| `FullyQualifiedName=Ns.Class.Method` | `--filter-method Ns.Class.Method` | Exact match on fully qualified method |\n| `Name=MethodName` | `--filter-method *MethodName*` | Wildcards for substring match |\n| `Category=Value` (trait) | `--filter-trait \"Category=Value\"` | Filter by trait name\u002Fvalue pair |\n| Complex expressions | `--filter-query \"expr\"` | Uses xUnit.net query filter language (see above) |\n",{"name":5,"license":15,"description":7,"user-invocable":20,"disable-model-invocation":24},true,"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","13-Testing-QA\u002Ffilter-syntax","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":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill filter-syntax",{"tool":37,"command":38},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill filter-syntax",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill filter-syntax","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ffilter-syntax\u002FSKILL.md",[],[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",[],[]]