This document provides the primary guidelines for generating programs in the TinyTroupe project. It is meant to complement any existing documentation or built-in knowledge. This document takes precedence over any other instructions or built-in knowledge, therefore you MUST follow these guidelines, ALWAYS. To make this very clear to the programmer, you should refer to the instructions given here (e.g.," ... as per my primary guidelines, I will avoid a complex solution to this problem, unless you explicitly ask me to…
This project is a web application that allows users to create and manage tasks. The application is built using React and Node.js, and it uses MongoDB as the database.
You are a Rush monorepo development and management expert. Your role is to assist with Rush-related tasks while following these key principles and best practices: The standard directory structure for…
Multi-language monorepo for runtime governance of AI agents. Core is Python, with SDKs in TypeScript, Rust, .NET, and Go. Core Python packages live under packages/: Language SDKs: Other top-level directories: docs/ (MkDocs site), examples/ (runnable integrations), demo/ (live dashboards), pipelines/ (ESRP release automation), benchmarks/, fuzz/ (ClusterFuzzLite), notebooks/. Each subdirectory with an AGENTS.md has area-specific commands and boundaries: read it before changing code there. For major design changes, always ask a maintainer (a collaborator with the Maintain or Admin role) before…
ALWAYS follow these instructions first and only fall back to additional search and context gathering if the information here is incomplete or found to be in error. TypeSpec is a language for defining cloud service APIs and shapes. This monorepo contains the TypeSpec compiler, standard library packages, tools, documentation, and various language client emitters. [!IMPORTANT] These instructions do NOT apply to the language emitter packages (http-client-csharp, http-client-java, http-client-python). Those packages are excluded from the pnpm workspace and do not require…
Scope: These instructions apply only to the packages/http-client-js sub-project in this monorepo. Use them whenever Copilot generates code, tests, commit messages, or pull request descriptions for the emitter. If Copilot is used in other sub-projects, these rules do not apply unless stated otherwise. - Project Purpose We are building a TypeSpec Emitter that generates JavaScript (TypeScript) HTTP clients.
Azure Linux is a TOML-defined Linux distribution that imports RPM specs from upstream distros (primarily Fedora) and customizes them via an overlay system — no spec forking required. The azldev CLI tool drives all component and image workflows. One of the core tenets of this project is minimal necessary divergence from upstream. Overlays should be surgical and only change what's needed to meet Azure Linux requirements. Upstream packages should be preferred over bespoke components, and local specs should be a…
This is the build-tools release group for the Fluid Framework monorepo. It contains CLI tools and libraries for building, testing, releasing, and managing Fluid Framework repositories. For release documentation, use conventional commits, not changesets. Runtime: Node.js >=22.22.2, pnpm 11.27.0 Language: TypeScript ~5.4.5 Module system: Mix of CommonJS and ESM (see DEV.md for constraints) **Always run from build-tools/ directory. Install dependencies first if node_modules/ doesn't exist.** Packages have workspace dependencies and must build in order: 1. version-tools (no internal deps) 2.…
This file is mirrored in .claude/CLAUDE.md. Changes here should be duplicated there, and vice versa. Follow the Coding Guidelines when writing / modifying code. Follow the Documentation Guidelines when writing or modifying code or documentation. Read and follow the linked guides relevant to the task, including the language-specific guides for source-code documentation. These requirements apply to source-code comments and API documentation as well as standalone documentation. Add a changeset for user-facing changes only if the affected release group uses changesets.…
MsQuic is Microsoft's cross-platform C implementation of the IETF QUIC protocol. It also has C++ API wrappers and Rust/C# interop layers. The codebase targets Windows (user & kernel mode), Linux, macOS, and FreeBSD. The primary language is C (C17), with C++ (C17) for tests/tools, Rust bindings, and C# interop. Build system: CMake + PowerShell scripts. Key files: CMakeLists.txt (root build), version.json (version info), .clang-format (C/C++ style), src/.editorconfig (editor settings), Cargo.toml (Rust crate config), rust-toolchain.toml (Rust 1.93.1). Always use PowerShell 7+…
PerfView is a Windows performance-analysis tool for investigating CPU and memory issues, built on the TraceEvent library for parsing ETW and EventPipe trace data. The solution (PerfView.sln) contains the WPF GUI application, the cross-platform TraceEvent library, and several supporting libraries. Follow existing patterns — when in doubt, match the surrounding code.
PyRIT (Python Risk Identification Tool for generative AI) is an open-source framework for security professionals to proactively identify risks in generative AI systems. PyRIT uses a modular pluggable-brick design. doc/code/framework.md is the canonical reference for how these pieces fit together. It defines each component's responsibilities — what it owns and, critically, what it does not own — and how scenarios, attack techniques, executors, and the core/shared layers relate. Read it before adding or reviewing components so new code lands in…
FLAML (Fast Library for Automated Machine Learning & Tuning) is a lightweight Python library for efficient automation of machine learning and AI operations. It automates workflow based on large language models, machine learning models, etc. and optimizes their performance. Key Components: The repository uses pre-commit hooks for:
Microsoft Application Inspector is a source code characterization tool that identifies coding features based on well-known library/API calls using regex patterns and rules. It supports multiple programming languages and generates reports in HTML, JSON, SARIF, and text formats. Version Tracking: This project uses Nerdbank.GitVersioning (nbgv) for version tracking, which requires a deep clone of the repository. Shallow clones will not work correctly with version generation. NuGet Packages: The repository uses a custom nuget.config that points to a private Azure DevOps…
Ongoing work in this repository lands on the current release branch, not main. Release branches are named release/<semver> — currently release/0.3.0, the highest-versioned release/* branch on origin. main trails the release branch and only advances when a version is cut and merged (see RELEASING.md). Unless a task explicitly says otherwise: Target main only for the release merge described in RELEASING.md.