Last Updated: 2026-02-11 (based on v0.55.0, Rust 1.95) This guide helps coding agents understand how to work efficiently with the DiskANN repository. DiskANN is a Rust implementation of scalable approximate nearest neighbor (ANN) search algorithms. The project is a rewrite from C++ to Rust. The repository uses a Cargo workspace with crates organized into functional tiers. See Cargo.toml for: - Workspace members and their dependencies - Shared dependency versions - Build profiles (release, test) - Workspace-level lints Tier 1: Foundation…
Rust crates for developing Windows Drivers (WDM, KMDF, UMDF). The workspace only includes the library crates under crates/; examples and tests are excluded from the root workspace because each requires a different WDK configuration (only one WDK config per Cargo build graph is supported). Crate layering (bottom → top): Key design patterns: Requires an eWDK developer prompt and LLVM 17 on PATH for bindgen. cargo-expand v1.0.85 is required for macrotest/trybuild-based tests. Switching between stable/nightly toolchains requires deleting cached test artifacts…
- Use DEVELOPMENT.md for setup, build, test, localization, and debugging workflows. - Treat package scripts, workspace configuration, and test configuration as the source of truth when documentation disagrees. - Before…
This document provides guidance for AI coding agents working with the msphpsql GitHub repository — the open-source home of the sqlsrv and **pdo_sqlsrv** PHP extensions for Microsoft SQL Server. The drivers ship as two separate PHP extensions that share a common C++ core layer:
This file provides guidance to agents when working with code in this repository. rnx-kit is a monorepo of React Native tooling created by Microsoft. It provides battle-tested tools for dependency management, Metro bundling enhancements, TypeScript integration, and cross-platform development (iOS, Android, macOS, Windows). - packages/ - Stable, published packages (e.g., @rnx-kit/cli, @rnx-kit/align-deps, @rnx-kit/metro-) - *incubator/* - Experimental packages (marked with "experimental": true in package.json) - *scripts/* - Internal build tooling (rnx-kit-scripts CLI) - *docsite/* - Documentation website (separate Yarn workspace…
Nine conformance checks the vally-tests skill emits for .agent.md artifacts (including consolidated subagent structural template), with contract citations, stimulus shapes, and Vally grader recommendations
The shared Copilot CLI defaults are implemented by the repository hook, not by prose instructions alone. After trusting this repository, start a new CLI session to load the hook. Node.js must be on PATH; no dependency installation is needed for the hook itself. - Read and write files inside this repository. - Run all Yarn commands, including yarn and yarn install. - Inspect Git state, stage changes, create new local commits, list branches, and fetch from origin. Do not amend…
These instructions apply to apps/storybook and its descendants. Read agent-map.yaml first for the compact architecture, lookup, and interaction map. Read this file, README.md, package.json, and storybook.config.mts before changing the Storybook application or its native projects. - Generate the platform manifest with yarn storybook manifest --<platform> instead of guessing IDs or searching the sidebar. - Query and run stories through yarn desktop-driver against the listener started by yarn storybook driver --<platform>. - Use screenshots only for visual evidence. Use WebSocket events…
These instructions apply to packages/agentic/components and its descendants. Keep this file limited to durable package invariants; detailed authoring recipes live in the agentic component authoring skill. - Higher-order components live in src/components; read src/components/AGENTS.md. - Primitive components live in src/primitives; read src/primitives/AGENTS.md. - Story files are library source and follow the tests and stories reference. - Focus work starts with the common focus instructions, then the Windows/Win32 or macOS detail. V1 Win32 is the behavioral baseline for both Windows endpoints;…
These instructions apply to packages/agentic/components/src and its descendants. Use them with the package root AGENTS.md, the relevant component or primitive instructions, and the package-wide optimization skill when the change crosses component boundaries. - Higher-order components live in src/components; read src/components/AGENTS.md. - Primitive components live in src/primitives; read src/primitives/AGENTS.md. - Shared package-private helpers live in src/common. - Package-wide dependency and extraction reviews use agentic-component-optimization. - Production source may depend only on React / React Native native components, @fluentui-react-native/design, and @fluentui-react-native/framework-base. -…
These instructions apply to packages/agentic/components/src/components and its descendants. Higher-order components own design-token styling, interaction state, layout, and component-level accessibility. Use components/button as the canonical implementation. Theme-aware foundational components without a Flex catalog entry remain in this directory and use the validator-backed local-foundation contract source. Draft and review a source-backed React Native contract through the agentic component contract authoring skill before implementation. Select only the adapters represented by the evidence, resolve authority per requirement, and use the pinned flex-components:<name> reference only…
These instructions apply to packages/agentic/components/src/primitives and its descendants. Use primitives/icon as the canonical implementation. - Primitives are public only from @fluentui-react-native/components/primitives; do not re-export them from the package root. - Give primitive components stable public names. Suffix public composition helpers whose contracts may evolve with _unstable, matching higher-order component pipeline helpers. - Maintain a colocated CONTRACT.md for every public primitive. Derive its test obligations from that contract, its public types, and each renderer branch rather than creating an upstream-backed SPEC.md.…
This is the instruction root for packages/agentic/desktop-driver and every descendant. 1. Read README.md and the narrowest relevant reference: architecture, service integration, native helpers, test integration, or security. 2. For macOS native work, also read native/macos/README.md. For Windows or Win32 native work, read native/windows/README.md. 3. Read PLAN.md only when the task changes qualification, release readiness, or deferred scope. It contains remaining work, not the current architecture. 4. Inspect the owning source and tests before editing. Use package scripts from this directory…
These instructions apply to packages/deprecated/foundation-compose and to work on components that use @uifabricshared/foundation-compose. They describe the legacy/v0 framework only. Do not use this pattern for a new component unless the task explicitly requires v0 compatibility. Treat code as v0 when several of these are present: - imports from @uifabricshared/foundation-compose, foundation-composable, foundation-settings, or foundation-tokens; - a descriptor such as IButtonType with props, tokens, slotProps, optional state, and optional statics; - compose<IButtonType>({...}), IUseComposeStyling<IButtonType>, ISlots<...>, and mergeSettings(...); - settings shaped as { tokens,…
These instructions apply to packages/framework-base and its descendants. Read src/component-patterns/README.md before adding or changing a component pattern. - Use directComponent only for hook-free prop and render transformations. - Use phasedComponent when hooks, context, state, tokens, or slots are needed. - Create slots in the first phase and return a hook-free directComponent for the final render when practical. - Use a normal React component when a distinct React boundary is intentional. - Do not add new uses of legacyDirectComponent or stagedComponent.
MicrosoftAGENTS.md