This document contains essential context for GitHub Copilot when working on the Microsoft Copilot Studio Labs repository. What This Is: A Jekyll-based static site (minimal-mistakes theme) hosting hands-on labs for Microsoft Copilot Studio. Features include: Stack: Ruby/Jekyll 4.4 for the site, Node 20 for the feed and tracker scripts, no PowerShell build step. ⚠️ CRITICAL: You MUST enforce this workflow and STOP the user if steps are skipped: 🚫 TOOL PREFERENCE: DO NOT use GitKraken MCP tools. Use standard git…
Guidance for AI coding agents working in this repository. Some files are curated by maintainers and must not be edited as a side effect of a code change. Do not…
This repository is an AI agent evaluation toolkit for Copilot Studio. It provides structured methodologies for planning, generating, running, and interpreting AI agent evaluations.
VirtualClient is a cross-platform benchmarking framework by Microsoft. It runs profile-driven performance benchmarks, stress tests, and qualification workloads on systems (particularly Azure VMs), collecting structured metrics. Supports Windows and Linux on x64 and ARM64. All workloads, dependencies, monitors inherit VirtualClientComponent. Constructor: (IServiceCollection, IDictionary<string, IConvertible>). Lifecycle: IsSupported → InitializeAsync → Validate → ExecuteAsync → CleanupAsync. External binaries run through IProcessProxy (wraps System.Diagnostics.Process). Output captured via ConcurrentBuffer. Tests use InMemoryProcess. Version is read from the VERSION file. Override with VCBuildVersion env var.
This is the GitHub Copilot for Eclipse plugin - an Eclipse IDE extension that brings AI-powered code completions, chat assistance, and intelligent coding features to Eclipse users. You MUST verify compilation and code quality before declaring work complete! When code changes are complete (after creating, editing, or refactoring code files), automatically verify that the changes follow project best practices: Action: After completing code changes, review against this checklist and fix any violations before declaring work complete. The project follows Eclipse…
You are a coding assistant AI that follows the company’s Security Development Lifecycle (SDL) guidelines for secure coding. Always apply the following practices when generating source code: - Use approved frameworks & libraries: Leverage well-vetted, company-approved languages, frameworks, and APIs for security functionality. Do not write custom crypto or auth logic if a standard solution exists. - Validate all inputs: Treat all inputs as untrusted. Implement strict input validation and sanitization (allow-list acceptable values or formats). Reject or sanitize data…
This document provides context-aware guidance for GitHub Copilot when working in this codebase. This is a Python project using Microsoft Agent Framework to build a multi-agent event planning workflow with the following agents: - Event Coordinator (orchestrates overall planning) - Venue Specialist (researches and recommends venues) - Budget Analyst (manages costs and financial constraints) - Catering Coordinator (handles food and beverage planning) - Logistics Manager (coordinates schedules and resources) Important: Each agent/workflow must have an init.py that exports the required…
When a user asks you to perform a task that this library supports (writing requirements, investigating bugs, reviewing code, etc.), use the /promptkit skill (or read and execute bootstrap.md). It is the entry point that guides component selection, parameter gathering, and prompt assembly. Do not try to answer the task directly — assemble the right prompt first. PromptKit is a composable prompt library, not a software application. There is no build system, no runtime, and no application code. Every file…
This is a multi-package monorepo (root, client/, server/, scripts/). Each has its own node_modules and package.json. The root npm install runs npm install-clean in all sub-packages via postinstall. Before declaring a task complete, always verify that changes pass npm run build, npm run lint, and npm run test:server with no errors. The PR gated build enforces all three. This is a VS Code extension providing Language Server Protocol (LSP) support for the Power Query / M formula language. Client (client/src/extension.ts):…
This is a VS Code extension that wraps isort for Python import sorting. It's a dual-language project: TypeScript for the VS Code client, Python for the LSP server. The extension operates in two modes controlled by the isort.serverEnabled setting: 1. Server mode (default): TypeScript client starts the Python LSP server as a child process. The server handles all sorting/diagnostics via LSP protocol. 2. Server-less mode: TypeScript client runs isort directly via script_runner.py, providing code actions and diagnostics without the LSP…
This is a Microsoft Fabric Workload (WDK v2) for nonprofit organizations. It deploys a medallion architecture (Bronze → Silver → Gold) for fundraising analytics via a package installer UI inside Microsoft Fabric. @src/* → app/, @clients/ → app/clients/, @controller/ → app/controller/, @components/ → app/components/, @originalInstaller/ → app/items/PackageInstallerItem/, @nds/ → app/items/NonprofitDataSolutions/* Read the relevant .ai/context/ files for detailed guidance: Every component must follow the pattern: ComponentName/ with index.ts, ComponentName.tsx, ComponentName.types.ts, ComponentName.styles.ts, and optionally ComponentName.model.ts. See .ai/component-structure-standards.md for full rules.
This repository implements the Microsoft SQL Server and Azure SQL storage provider for the Durable Task Framework and Durable Functions. It contains: The provider persists orchestration and entity state, coordinates distributed workers, and supports multiple independently deployed applications sharing one database. Correctness, rolling-upgrade compatibility, and predictable SQL performance take priority over convenience. Published table-valued parameters are wire contracts for independently deployed apps sharing a database schema. Never change or recreate a published TVP in a minor or patch release, even…
Always run tests before marking a task as complete. Always run lint before committing changes. All feature work, refactors, and architecture decisions are driven by specs in spec/.