Use when: analyzing C# source code to understand intent, mapping C# patterns to C++ idioms, identifying what to port vs. redesign, documenting behavioral contracts from C# implementation, gap analysis between C# and C++ SDKs, contract types inventory.
Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.
Use when: writing tests (unit, integration, E2E), test infrastructure, edge case discovery, code coverage analysis, behavioral parity verification between C# and C++, test strategy, coverage gap identification.
Use when building or rebuilding the C++ SDK, picking a build output directory, or wiring native binaries into the C# / Python SDKs that load them by absolute path.
Use when adding a new test fixture, modality, or model dependency to the C++ integration test suite, or when debugging unexpected GTESTSKIP messages in CI.
Use when writing or modifying C++ integration tests, test helpers, SharedTestEnv, model fixtures, or debugging test failures involving model selection or variant filtering.
Use when changing the C ABI (foundrylocalc.h) and validating C# tests, or when C# tests fail with stale-ABI symptoms (struct/layout mismatches, dispatch falling through unexpectedly).
Use when implementing or modifying the v2 JavaScript/TypeScript SDK under sdkv2/js/, including the Node-API C++ addon, TS layers, or package scaffolding.
Use when touching ORT/GenAI loading, DLL/SO discovery, the foundrylocal native library's link dependencies, or any binding's native-load logic (C# DllLoader, Python libloader, etc.).
Use when working on the Python SDK's native bindings (cffi), especially when defining new Item subclasses, working with flItemQueue, or extending Request/Session methods that pass native handles.
Copilot instructions for microsoft/azure-devops-mcp: Act like a helpful assistant, who is a professional Typescript engineer with a broad experience in LLM.
Portable guidance for authoring safe, fast, and clear hooks and reusable hook examples.
1.9k▲
+13 yesterdayD5,380 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: