Conventions for any agent (or human) changing amplifier-bundle-recipes. Run all four before opening a PR: Never re-record the legacy-compat baselines to make a change pass. They pin the serialized ToolResult payload of execute / resume / approve for legacy recipes. If your change needs to add something to a result, attach it beside the payload (object.setattr(result, ...), as runneradapter.labelexecutionmode, shutdown.attachshutdownwarning and engineprovenance.labelengineprovenance all do), not inside output. Both are generated artifacts, not hand-maintained ones. They are produced from the repo…
This repository includes custom GitHub Copilot agents to help learners navigate the workshop and troubleshoot issues. This workshop teaches developers how to build AI agents end-to-end on Microsoft Foundry. Each task (02–09) has three components: In GitHub Copilot Chat (VS Code or Codespaces), mention the agent by name: Each agent is scoped to a specific learning path and will only provide guidance for that path. Pick the agent that matches how you want to work through the quest. When providing…
Preserve gameplay behavior unless a change is requested. Before changing gameplay, authentication, SQL persistence, or Function contracts, read Architecture. Consult src/config/gameConfig.ts for executable settings. For Rayfin changes, load .agents/skills/rayfin/SKILL.md and read the installed package documentation identified by rayfinDocs. CLI documentation is in @microsoft/rayfin-guide. Preserve explicit private entity policies and schema discovery; run npm run schema:check after changing them. For deployment or environment changes, read Deployment. Deployment and destructive cloud operations require explicit authorization. Local gameplay is unsupported, and npm run…
Conventions for AI coding agents (Amplifier, Claude Code, Cursor, etc.) and human contributors using them. Read this before making changes. @README.md @docs/development.md @docs/api-reference.md @docs/profiles.md @docs/amplifier-user-sim-launch-flow.dot @agents/dtu-profile-builder.md @profiles/tests/amplifier-user-sim.yaml @profiles/amplifier/amplifier-chat.yaml CLI and library for spawning and managing Digital Twin Universe (DTU) environments. Wraps the incus CLI with profile-driven provisioning, file push/pull (recursive), exec, and lifecycle management. The DTU is how the broader ecosystem gets an isolated, realistic environment for integration verification. Run these before opening a PR. The reviewer expects evidence in…
Remember the law of diminishing returns to decide if something should fit or not here. Before drafting, editing, or returning repository prose, invoke /humanize-writing. This includes technical documentation, session kits, runbooks, Markdown, slide content, and user-facing explanations. In this repository, use the skill to simplify wording and remove AI-patterns from technical content. Its general technical-writing exclusion does not apply here. Use the clear-thinker voice unless the user requests another voice. Before finishing, complete both checks: 1. Apply the prose simplification…
Guidance for AI coding agents (and humans) working in this repository. Keep changes minimal, typed, and covered by tests. For contribution policy see CONTRIBUTING.md; for user-facing docs see README.md. An MCP server that serves GitHub Security Advisories from a local clone of github/advisory-database. Two-tier design: MCP server (stdio or HTTP) → local Express REST API → LocalRepositoryDataSource (reads advisory JSON from disk). Core MCP tools: listadvisories, getadvisory (full parameters in the README). The server reads advisory JSON from ADVISORYREPOPATH (default…
This file is the single entry point for AI agents (Copilot CLI, Copilot Chat, Claude, Cursor, etc.) working in this repository. It points to the tooling, conventions, and build/test loop an agent needs to make a change and validate it before pushing. Purview GitHub Action — a TypeScript GitHub Action that scans repository files on push / pull request and sends them to Microsoft Purview for data governance and compliance tracking. It authenticates with Azure via GitHub OIDC, processes changed…
This repository contains agentic journeys that build and deploy applications to Azure using GitHub Copilot agents, skills, and Azure Developer CLI (azd). Journeys are self-contained — learners can start with any of them. The root README.md → Agentic journeys table lists them all with cost estimates. Plugin (canonical — use everywhere): Do not use alternate marketplace names. Install the Azure Skills plugin for access to Azure-specific MCP and skills tools (Bicep schemas, deployment planning, architecture diagrams, log analysis): Once inside…
Guidance for AI agents and developers working in this bundle repository. Use Foundation validate-bundle-repo v3.16.1 or later. Earlier validators can mistake glob/template storage paths ending in */context-intelligence or {id}/context-intelligence for an invocation of the internal mode. The fix belongs in Foundation's mode-reference matcher, not this bundle's storage paths or mode visibility. Keep modes/context-intelligence.md at advertised: false. Do not delete valid path references, advertise the internal mode, or treat the resulting ERROR as a PASS. Select the corrected recipe with CIVALIDATERECIPE…
Instructions for an AI agent (e.g. GitHub Copilot CLI) driving this read-only-by-default toolkit against an Azure tenant. If you are an agent: read this file fully before running anything. This toolkit is READ-ONLY BY DEFAULT. You exist to observe and report. It contains exactly one write tool — Deploy-QuotaGroups.ps1, which provisions Azure Quota Groups — and you must treat it as off by default: never run it unless the human explicitly asks you to provision quota groups in this run…
This project is a Microsoft Foundry hosted agent fronted by Azure API Management (APIM). Preserve the governed request paths: callers enter through the APIM agent API, the hosted agent reaches its model through the APIM model API, and MCP tools are exposed through APIM tool APIs. This project was built with the microsoft-foundry skill. Before working on or answering questions about Foundry agents, read the microsoft-foundry skill first. - azure.yaml — azd orchestration for the Foundry project, toolbox, hosted agent,…
Preserve the architecture: one Responses-protocol Hosted Agent connects only to one Foundry Toolbox. The Toolbox exposes the composed Foundry IQ Knowledge Base and web_search; the agent must not initialize Search or web clients directly. Keep Search keyless with local authentication disabled. Keep 2026-08-01-preview pinned for all Knowledge Source and Knowledge Base operations. Configuration fragments are native platform payloads and must not contain plaintext secrets. Terraform and azd are the default deployment path; Bicep remains a supported companion implementation. Keep both…
Preserve these invariants: - Terraform and azd are the default deployment path. Bicep remains a supported companion implementation. Keep both implementations behaviorally equivalent. - The default Hosted Agent is Python 3.13 source code with remote_build. - The opt-in ACR scenario consumes only a digest-pinned image from an existing enterprise ACR and creates only its Foundry project connection. - Public fallback, Dockerfiles, template-owned ACR resources, ACR networking, ACR IAM, App Insights, and Log Analytics are out of scope. - Do not…
Project context for AI coding agents working on scope-doc, the Starlight-based documentation site for Scope. A static documentation site published to GitHub Pages. - Framework: Astro 6.x + @astrojs/starlight - Package manager: pnpm (pinned via packageManager in package.json) - TypeScript strict - Lives under the website/ directory of the repo (all site sources, config, and package.json are rooted here; run every command from website/) - Deployed by .github/workflows/static.yml (build + deploy jobs), which builds from website/ via a working-directory default…
VS Code extension that provides a real-time search panel backed by the local Tantivy index managed by the codesearch/ daemon. As the user types, it issues queries against the daemon's HTTP API and renders results with file metadata, highlights, and one-click file opening. The split between client.ts and extension.ts is intentional: client.ts imports nothing from vscode, so it can be unit-tested with plain Node.js. Defined in client.ts MODES array. Each entry has key, label, queryBy, weights, desc, and optionally astMode/uses_kind.…
Event-driven telemetry platform for Amplifier sessions. Captures session events as structured data and builds a property graph in Neo4j. See README.md for full setup instructions. We are cleaning up this repo's documentation and setup instructions so the server + Neo4j run locally without Docker Compose, with API keys primed for local runs. Scope is intentionally narrow — do this and nothing else. - Dockerfile (the server image). This is the shipping-product container and it is S360-compliant via PR #50 (payneio…
When starting the dev server, use background mode: Manage the background server with astro dev stop, astro dev status, and astro dev logs. Before building or serving the gallery, generate content from the exploded submissions: Generated files under src/content/solutions/, src/content/guides/, and public/bundles/ come from submissions/; do not hand-edit them. Full documentation: https://docs.astro.build Consult these guides before working on related tasks: - One gallery entry represents one complete exploded Power Platform solution. - Each submission lives at submissions/<slug>/solution/ with gallery-only metadata.json…
MicrosoftAGENTS.md