Follow .github/copilot-instructions.md for delivery constraints, track and challenge synchronization, and Markdown formatting. Invoke /humanize-writing before drafting, editing, or returning repository prose. This applies to technical documentation, session kits, runbooks, Markdown, slide content, and user-facing explanations. The skill's technical-writing exclusion does not apply here. Use its clear-thinker voice unless the user requests another voice. Load the skill's voice guidance and AI-pattern dictionary before drafting. Write for a competent engineer. Lead with the point and include enough detail for the reader to…
This project was built with the microsoft-foundry skill. Before working on or answering questions about Foundry agents, read the microsoft-foundry skill first. The files under sample-data/ are a synchronized snapshot from pamelafox/aitour27-caldova-data. Do not edit them directly. Make sample-data changes in the upstream repository, then run this repository's sync script and commit the refreshed snapshot and provenance file together. - Make source-data, generator, template, and generated-artifact changes in a checkout of pamelafox/aitour27-caldova-data, usually at ../aitour27-caldova-data. - Change the structured source…
This is the master entry point for humans and coding agents working on SMBBestPracticeTool: repeatable, idempotent PowerShell automation for Microsoft 365 best-practice configurations. Each product's README defines its scope and release status. Read the linked guidance before editing; each topic has one owner below. - Repository layout. - Deployment architecture and shared helpers. - Authoring and safety conventions. - Verification commands and definition of done: repository-wide checks, individual checks, pilot-tenant validation, and docs preview. - Branch, release, and PR workflow.…
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.…
This file orients bundle maintainers, not end-users. End-users see README.md. A generic Amplifier mode bundle. Ships modes that wrap the Karpathy LLM Wiki pattern. Project-side policy (schema, publish, viewer) lives in projects that use this bundle, not here. This is the load-bearing design choice. See docs/ARCHITECTURE.md for the reasoning. Use /mode-design from amplifier-bundle-modes. Three phases: Drop the result in modes/. Verify it parses by including the bundle in a test project and /mode list. The bundle is dogfooded in a…
Read README.md, docs/HANDOFF.md, docs/VISION.md, and the documents relevant to your change: - Catalog, identity, scope or host integration: contracts/routing-catalog.v1.md, docs/CATALOG-SPEC.md, docs/PROVIDER_AVAILABILITY.md. - Model preferences, evaluation or evidence: docs/EVALUATION-PROGRAM.md, docs/MATRIX_CURATOR_GUIDE.md. - Image-operation routing direction: contracts/image-routing.v1.md and docs/IMAGE-ROUTING.md; drafts only, not changed matrix policy or live support. - Offline routing evaluation tooling: evals/AGENTS.md and evals/README.md. - Tests and release gates: .github/workflows/ci.yml, ruff.toml, module pyproject.toml and module tests. The new vision/catalog contract are DRAFT. They describe proposed direction, not delivered behavior, frozen promises…
Read README.md, DESIGN.md, REVIEW.md, RESULT-REUSE.md and ../docs/EVALUATION-PROGRAM.md before changing this maintained routing tooling. Repo conventions and more-specific rules still apply. The v3 offline implementation review and the expanded reuse/catalog method review are distinct: both requested expanded reviewers support scoped planning, not live readiness, fixture clearance or implementation authorization. Keep those boundaries explicit. evidence.py and thin Click cli.py implement offline plan/readiness/analyze. There is no live executor, production event normalizer, budget enforcer or qualified benchmark result archive. Readiness must remain unsupported until…
The chat UI uses a vendored JavaScript bundle at src/chat_plugin/static/vendor.js containing: Prerequisites: Node.js >= 18. The script installs dependencies into a local node_modules/, bundles them via esbuild, and writes the output to src/chat_plugin/static/vendor.js. Entry point: scripts/vendor-entry.js After rebuilding, commit the updated vendor.js. Tests are Python-based (pytest) and include both backend route tests and frontend code-pattern assertions that verify structural invariants in index.html.
Context and ground rules for AI agents (GitHub Copilot, Claude, or similar) running this demo on a user's behalf. A break-fix-prove resilience demo for Azure Chaos Studio Workspaces (public preview). The arc matters: 1. Deploy the AKS store demo app with its default single-replica deployments to a zone-redundant AKS cluster. 2. Run the Compute Zone Down scenario against the zone the store-front pod runs in. The storefront going down is the expected, desired outcome of run 1 — it demonstrates…
A static, single-page web guided assistant (index.html) for Microsoft Purview / data security guidance. No build system or backend — the page is self-contained and served statically (e.g. GitHub Pages). This file is the entry point for humans and coding agents. Run the setup commands once after cloning or when dependencies change. verify.ps1 validates the approved dependency source and lockfile structure without network access, validates the HTML and inline JavaScript, exercises a representative labeling workflow in Chromium, and checks the…
Before drafting, editing, or returning repository prose, invoke /humanize-content. 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. Use the clear-thinker voice unless the user requests another voice. Before finishing, complete both checks: 1. Apply the prose simplification rules in this file. 2. Apply the /humanize-content prose checks and revise the draft until it passes. Write like a senior engineer explaining…
Global Secure Access Troubleshooting Tool — a single-file PowerShell diagnostic utility (GSATool.ps1) for troubleshooting Microsoft Entra Global Secure Access (GSA). This file is the entry point for humans and coding agents. verify.ps1 confirms GSATool.ps1 parses cleanly (no syntax errors) and, if PSScriptAnalyzer is installed, that it reports no errors. A change is done when verify.ps1 passes and the tool still runs against a test tenant per README.md.
The README's Screenshots section and the full gallery show people what MOSAIC looks like. Treat those images and their descriptions as documentation that changes with the UI. - When a change alters a pictured page, whether its layout, wording, navigation, or the data it shows, regenerate the affected shots in the same change. Then reread their gallery and README descriptions and correct any that no longer match. Each description is one or two sentences about what the view is and…
You are a coding agent helping with the Setu project, a high-performance inference engine for large language models. This is a complex C++/Python hybrid project requiring strict adherence to coding standards. The build system intelligently detects what needs to be built and chooses the optimal strategy automatically. Use failed-only test targets during development for faster iteration cycles.
314mo agoReviewMountCreate a free account to mount
The dotnet implementation of the Microsoft GDK idiomatic projection. It is one of eight sibling language repositories split out of the gdk-projections-plans meta repo. The authoritative specification for this repository is plans/dotnet.md in the gdk-projections-plans meta repo, alongside the nine shared, language-agnostic reference docs under reference/ (gdk-surface.md, xuser-pilot.md, state-change.md, multiplayer-pilot.md, roadmap.md, security-privacy.md, compliance.md, glossary.md, testing.md). The plan follows a shared 15-section template; §4 (the mapping table) is the heart, §9 is the acceptance slice (the XUser pilot, plus the PFMP…
Converts Zero Trust Assessment output into a Zero Trust Workshop format via a single PowerShell script (Convert-ZTAssessmentToZTWorkshop.ps1) driven by a JSON mapping (test-mapping.json). This file is the entry point for humans and coding agents. verify.ps1 confirms the converter script parses cleanly and test-mapping.json is valid JSON. A change is done when verify.ps1 passes and a sample conversion still succeeds per readme.md.
Automated product-audit rounds: seed a scratch instance, drive real-browser persona sessions + design reviews, synthesize an evidence-tiered findings spec behind a human gate. Read PRINCIPLES.md before designing changes; SMOKE_TESTS.md before verifying. - The CLI command is amplifier-simulated-user-research — never abbreviate it. The retired four-letter acronym of this tool's name (a‑s‑u‑r) is banned everywhere: code, docs, messages, commits, PRs. - The user-facing browser-node bundle name is simulated-user-research-browser-node. Internal .dot param names (sur_repo_dir) are grandfathered — leave them. pipelines/simulated-user-research.dot is the sole…
MicrosoftAGENTS.md