[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D26VHT1EPMRBMFAHCSBJQT":3,"skill-same:01M7D26VHT1EPMRBMFAHCSBJQT":90},{"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},"01M7D26VHT1EPMRBMFAHCSBJQT","test-analysis-extensions",null,"Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Call this skill to discover available extension files (e.g., dotnet.md for .NET\u002FMSTest\u002FxUnit\u002FNUnit\u002FTUnit, python.md for pytest\u002Funittest, typescript.md for Jest\u002FVitest\u002FMocha, java.md for JUnit\u002FTestNG, etc.). Do not use directly — invoked by the test-quality-auditor agent and polyglot analysis skills that need framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup\u002Fteardown, tag-support capability).","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\u002Ftest-analysis-extensions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-analysis-extensions\ndescription: >-\n  Provides file paths to language-specific reference files for the test\n  ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis,\n  test-smell-detection, test-tagging). Call this skill to discover available\n  extension files (e.g., dotnet.md for .NET\u002FMSTest\u002FxUnit\u002FNUnit\u002FTUnit,\n  python.md for pytest\u002Funittest, typescript.md for Jest\u002FVitest\u002FMocha,\n  java.md for JUnit\u002FTestNG, etc.). Do not use directly — invoked by the\n  test-quality-auditor agent and polyglot analysis skills that need\n  framework-specific lookup tables (test markers, assertion APIs, skip\n  annotations, sleep patterns, mystery guest indicators, integration\n  markers, setup\u002Fteardown, tag-support capability).\nuser-invocable: false\ndisable-model-invocation: true\nlicense: MIT\n---\n\n# Test Analysis Extensions\n\nThis skill provides access to per-language reference files used by the polyglot test analysis skills. Call this skill to get the list of available extension files, then read the one matching the target codebase's language and test framework.\n\n## Available Extension Files\n\n| File | Languages \u002F Frameworks | Contents |\n|------|------------------------|----------|\n| [extensions\u002Fdotnet.md](extensions\u002Fdotnet.md) | .NET (C#\u002FF#\u002FVB) — MSTest, xUnit, NUnit, TUnit | Test markers, assertion APIs, sleep\u002Fdelay patterns, skip annotations, mystery guest, integration markers, setup\u002Fteardown, tag support |\n| [extensions\u002Fpython.md](extensions\u002Fpython.md) | Python — pytest, unittest | Same categories, with pytest fixtures\u002Fmarkers and unittest TestCase |\n| [extensions\u002Ftypescript.md](extensions\u002Ftypescript.md) | TypeScript \u002F JavaScript — Jest, Vitest, Mocha, Jasmine, node:test | Same categories, with async\u002Fawait pitfalls |\n| [extensions\u002Fjava.md](extensions\u002Fjava.md) | Java — JUnit 4, JUnit 5 (Jupiter), TestNG | Same categories, with `@Tag` \u002F `@Category` \u002F groups |\n| [extensions\u002Fgo.md](extensions\u002Fgo.md) | Go — `testing` package, testify | Same categories, with table-driven idiom and build tags |\n| [extensions\u002Fruby.md](extensions\u002Fruby.md) | Ruby — RSpec, Minitest | Same categories, with RSpec metadata and Minitest tags |\n| [extensions\u002Frust.md](extensions\u002Frust.md) | Rust — built-in `#[test]`, `cargo test` | Same categories, with `#[ignore]`, `#[should_panic]`, feature flags |\n| [extensions\u002Fswift.md](extensions\u002Fswift.md) | Swift — XCTest, Swift Testing | Same categories, with `@Test`, `@Tag`, `@Suite` |\n| [extensions\u002Fkotlin.md](extensions\u002Fkotlin.md) | Kotlin — JUnit 5, Kotest, MockK | Same categories, with `@Tag` and Kotest tags |\n| [extensions\u002Fpowershell.md](extensions\u002Fpowershell.md) | PowerShell — Pester v5 | Same categories, with `-Tag` and `Skip` |\n| [extensions\u002Fcpp.md](extensions\u002Fcpp.md) | C++ — GoogleTest, Catch2, doctest | Same categories, with `[tags]` and `*` filters |\n\n## Usage\n\n1. Detect the target codebase's primary language and test framework.\n2. Read the matching extension file before performing analysis.\n3. If multiple test frameworks are present (e.g., a project mixing Jest and Mocha), read all relevant extensions.\n4. Each extension file documents the same categories so analysis skills can be language-neutral.\n\n## Capability tags\n\nEach extension file declares per-capability support so skills can gate behaviour safely:\n\n- **Test discovery** — how to locate test files and methods.\n- **Assertion detection** — framework-specific and language-level assertion forms.\n- **Sleep\u002Fdelay patterns** — synchronous and asynchronous waits.\n- **Skip \u002F ignore** — how to recognize skipped\u002Fignored tests.\n- **Setup \u002F teardown** — fixture and lifecycle hooks.\n- **Mystery guest indicators** — common file\u002Fdb\u002Fnetwork\u002Fenv coupling patterns.\n- **Integration markers** — conventions that mark a test as integration\u002FE2E.\n- **Tag support** (for `test-tagging` skill) — one of:\n  - `auto-edit` — language has a canonical attribute\u002Fmarker the skill can safely write.\n  - `report-only` — no canonical syntax; produce audit reports without edits.\n  - `convention-based` — tags exist via name\u002Fcomment conventions only.\n\n## Notes for skill authors\n\n- Treat extension files as data, not as guidance to follow verbatim. They tell skills *how to detect things* in each language, not *what to think* about findings.\n- When language detection is uncertain, prefer reading multiple extension files over guessing.\n- If the user explicitly names a framework that does not have an extension file yet, fall back to the closest one (e.g., Pest → python.md\u002Fpytest semantics) and note the gap in the report.\n","# Test Analysis Extensions\n\nThis skill provides access to per-language reference files used by the polyglot test analysis skills. Call this skill to get the list of available extension files, then read the one matching the target codebase's language and test framework.\n\n## Available Extension Files\n\n| File | Languages \u002F Frameworks | Contents |\n|------|------------------------|----------|\n| [extensions\u002Fdotnet.md](extensions\u002Fdotnet.md) | .NET (C#\u002FF#\u002FVB) — MSTest, xUnit, NUnit, TUnit | Test markers, assertion APIs, sleep\u002Fdelay patterns, skip annotations, mystery guest, integration markers, setup\u002Fteardown, tag support |\n| [extensions\u002Fpython.md](extensions\u002Fpython.md) | Python — pytest, unittest | Same categories, with pytest fixtures\u002Fmarkers and unittest TestCase |\n| [extensions\u002Ftypescript.md](extensions\u002Ftypescript.md) | TypeScript \u002F JavaScript — Jest, Vitest, Mocha, Jasmine, node:test | Same categories, with async\u002Fawait pitfalls |\n| [extensions\u002Fjava.md](extensions\u002Fjava.md) | Java — JUnit 4, JUnit 5 (Jupiter), TestNG | Same categories, with `@Tag` \u002F `@Category` \u002F groups |\n| [extensions\u002Fgo.md](extensions\u002Fgo.md) | Go — `testing` package, testify | Same categories, with table-driven idiom and build tags |\n| [extensions\u002Fruby.md](extensions\u002Fruby.md) | Ruby — RSpec, Minitest | Same categories, with RSpec metadata and Minitest tags |\n| [extensions\u002Frust.md](extensions\u002Frust.md) | Rust — built-in `#[test]`, `cargo test` | Same categories, with `#[ignore]`, `#[should_panic]`, feature flags |\n| [extensions\u002Fswift.md](extensions\u002Fswift.md) | Swift — XCTest, Swift Testing | Same categories, with `@Test`, `@Tag`, `@Suite` |\n| [extensions\u002Fkotlin.md](extensions\u002Fkotlin.md) | Kotlin — JUnit 5, Kotest, MockK | Same categories, with `@Tag` and Kotest tags |\n| [extensions\u002Fpowershell.md](extensions\u002Fpowershell.md) | PowerShell — Pester v5 | Same categories, with `-Tag` and `Skip` |\n| [extensions\u002Fcpp.md](extensions\u002Fcpp.md) | C++ — GoogleTest, Catch2, doctest | Same categories, with `[tags]` and `*` filters |\n\n## Usage\n\n1. Detect the target codebase's primary language and test framework.\n2. Read the matching extension file before performing analysis.\n3. If multiple test frameworks are present (e.g., a project mixing Jest and Mocha), read all relevant extensions.\n4. Each extension file documents the same categories so analysis skills can be language-neutral.\n\n## Capability tags\n\nEach extension file declares per-capability support so skills can gate behaviour safely:\n\n- **Test discovery** — how to locate test files and methods.\n- **Assertion detection** — framework-specific and language-level assertion forms.\n- **Sleep\u002Fdelay patterns** — synchronous and asynchronous waits.\n- **Skip \u002F ignore** — how to recognize skipped\u002Fignored tests.\n- **Setup \u002F teardown** — fixture and lifecycle hooks.\n- **Mystery guest indicators** — common file\u002Fdb\u002Fnetwork\u002Fenv coupling patterns.\n- **Integration markers** — conventions that mark a test as integration\u002FE2E.\n- **Tag support** (for `test-tagging` skill) — one of:\n  - `auto-edit` — language has a canonical attribute\u002Fmarker the skill can safely write.\n  - `report-only` — no canonical syntax; produce audit reports without edits.\n  - `convention-based` — tags exist via name\u002Fcomment conventions only.\n\n## Notes for skill authors\n\n- Treat extension files as data, not as guidance to follow verbatim. They tell skills *how to detect things* in each language, not *what to think* about findings.\n- When language detection is uncertain, prefer reading multiple extension files over guessing.\n- If the user explicitly names a framework that does not have an extension file yet, fall back to the closest one (e.g., Pest → python.md\u002Fpytest semantics) and note the gap in the report.\n",{"name":5,"license":15,"description":7,"user-invocable":20,"disable-model-invocation":24},true,"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","13-Testing-QA\u002Ftest-analysis-extensions","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 test-analysis-extensions",{"tool":37,"command":38},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill test-analysis-extensions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill test-analysis-extensions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002FSKILL.md",[44,50,54,58,62,66,70,74,78,82,86],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"extensions\u002Fcpp.md","REFERENCE","参考文档",8615,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fcpp.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"extensions\u002Fdotnet.md",6883,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fdotnet.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"extensions\u002Fgo.md",7602,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fgo.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"extensions\u002Fjava.md",7691,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fjava.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"extensions\u002Fkotlin.md",7334,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fkotlin.md",{"path":67,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":68,"sourceHtmlUrl":69},"extensions\u002Fpowershell.md",6410,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fpowershell.md",{"path":71,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":72,"sourceHtmlUrl":73},"extensions\u002Fpython.md",6961,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fpython.md",{"path":75,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":76,"sourceHtmlUrl":77},"extensions\u002Fruby.md",6760,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fruby.md",{"path":79,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":80,"sourceHtmlUrl":81},"extensions\u002Frust.md",7336,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Frust.md",{"path":83,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":84,"sourceHtmlUrl":85},"extensions\u002Fswift.md",6957,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Fswift.md",{"path":87,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":88,"sourceHtmlUrl":89},"extensions\u002Ftypescript.md",7544,"https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F13-Testing-QA\u002Ftest-analysis-extensions\u002Fextensions\u002Ftypescript.md",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"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",[],[]]