Dynamics 365 Business Central is Microsoft's cloud-based ERP solution for small and medium-sized businesses, covering finance, supply chain, sales, inventory, manufacturing, and service management. AL (Application Language) is a domain specific programming language for Business Central development: - Each AL project is defined by an app.json file at its root folder - Apps are compiled into .app packages for deployment - Object types: Tables, Pages, Codeunits, Reports, Queries, XMLports, etc. - Extensibility through events and object (table/page/enum) extensions
Dynamics 365 Business Central is Microsoft's cloud-based ERP solution for small and medium-sized businesses, covering finance, supply chain, sales, inventory, manufacturing, and service management. AL (Application Language) is a domain specific programming language for Business Central development: - Each AL project is defined by an app.json file at its root folder - Apps are compiled into .app packages for deployment - Object types: Tables, Pages, Codeunits, Reports, Queries, XMLports, etc. - Extensibility through events and object (table/page/enum) extensions This repository…
Nx monorepo of @fluentui-contrib/* packages extending Microsoft's Fluent UI v9 design system. Package manager: Yarn 4 (yarn@4.12.0). Build orchestration: Nx 22. Node: ^22.12.0 || ^24.0.0. Use Corepack to ensure the expected Yarn version is active: All commands run from the repo root. Never cd into a package folder. Order imports in groups separated by blank lines:
5625d agoReviewMountCreate a free account to mount
The @fluentui-contrib/react-cap-theme package implements a @fluentui/react-components theme. A component's source code lives in its own folder, ./src/components/<ComponentName>. Using Button as an example, these files should exist: The custom styles hook that is exported from <ComponentName>.styles.ts is wired up to the FluentProvider inside CAPThemeProvider. If there are multiple pieces or slots to a component, each of those slots gets its own .styles.ts file. Each of these must be wired up to the CAPThemeProvider as well. For example:
5625d agoReviewMountCreate a free account to mount
Current Brewlet is a rewrite; 0.x E2E tiers, core/ paths and JDK-specific runbooks do not apply to this branch. The contract is the Brewlet specification; obligations and evidence rules live in acceptance/. - live-v2/ — private real-node acceptance. harness.py creates its own invocation-unique kind cluster, kubeconfig, registry and checkout-built images; it never uses an existing cluster or context. See live-v2/README.md for scenarios (pr, control, complete and focused suites) and wasm.py/managed_wasm.py companions. - fixtures/ — the Python qualification fixture, Java/Node.js/.NET/PHP example…
5520d agoReviewMountCreate a free account to mount
The README embeds the root screenshot.png. Refresh it when requested or when visible main-window changes make the image stale (for example, picker layout, toolbar, comparison tree, or diff display). Screenshots intentionally omit the entire build-version label; build-label changes alone do not require a refresh. On Windows, with PowerShell 7.2 or newer, a desktop session, and an SDK compatible with global.json (a stable .NET 10.0 SDK at or above 10.0.402), run from the repository root: The command builds the current code…
4713d agoReviewMountCreate a free account to mount
You are a triage-dispatch agent. Understand the user's request and delegate to the appropriate agent. You do not write code or make direct file changes. All code changes go through the orchestrator agent.
456mo agoReviewMountCreate a free account to mount
Instructions for coding agents that work on this repository. Operators should read README.md and docs/OSWORLD.md instead. Never copy, mount, summarize or inject this file or any other repository documentation into an evaluated OSWorld agent. The evaluated agent receives only: - the original OSWorld task instruction; - instructions/base.md, the common safety and outcome policy; - one selected interaction guide, normally instructions/hybrid.md, unless the run explicitly selects no operating profile; - the runner's TASK_COMPLETE, TASK_INFEASIBLE and ASK_USER contract. Product instructions are plain…
4516d agoReviewMountCreate a free account to mount
Audience: Contributors modifying the core extension (extension) and shared packages (api, util). Emphasis: safe core evolution, API contract stewardship, and maximal reuse of @microsoft/vscode-fabric-util. Treat as public surface. Before changing an interface: Always check util/src before introducing new helpers: Commands (root orchestrates sequencing):
4513mo agoReviewMountCreate a free account to mount
This file tells coding agents (GitHub Copilot, Claude Code, Cursor, Aider, Codex CLI, etc.) how to invoke sqlsim when a user asks them to run SQL workloads. It is shipped at the root of the sqlsim release package so any agent operating in the user's project picks it up automatically. A companion VS Code skill descriptor lives at ../.github/skills/sqlsim/SKILL.md and is discovered automatically by skill-aware agents. sqlsim is a single-binary SQL workload simulator for SQL Server, Azure SQL Database, Azure…
4233d agoReviewMountCreate a free account to mount
Use .github/copilot-instructions.md for implementation, verification, and review rules. Subsystem contracts live in .github/instructions. package.json contributions and package.nls.json labels -> src/commands/registerCommands.ts -> command and wizard steps -> Azure Tools helpers or src/utils/azureClients.ts -> ARM operation or local revision draft -> tree state, activity/output, and tests.
This section outlines the core implementation philosophy and guidelines for software development projects. It serves as a central reference for decision-making and development approach throughout the project. Embodies a Zen-like minimalism that values simplicity and clarity above all. This approach reflects: This development philosophy values clear documentation, readable code, and belief that good architecture emerges from simplicity rather than being imposed through complexity.
3518mo agoReviewMountCreate a free account to mount
Compose context by including only the modules needed for the current task. Keep the context lean and relevant to maximize the model’s effectiveness during long sessions. This repo contains innovation…
356mo agoReviewMountCreate a free account to mount
Guidance for AI coding agents working in this repository (the Azure SQL Database container Private Preview). If you instead want your own agent to run and build against the container…
3434d agoReviewMountCreate a free account to mount
You will help the user build out this React-based web app that visualizes data from Power BI semantic models. The app fetches live data via DAX queries, renders charts and grids using Vega-Lite and a built-in DataGrid component, and supports light/dark theming. Your job is to discover the user's data, write correct DAX queries, build React components that fetch and display that data, and validate the result in the browser. Break tasks into independent pieces and delegate them to sub-agents…
3322d agoReviewMountCreate a free account to mount
Use AgentFactory for built-in agents or --agent-import-path for a custom BaseAgent subclass. ::: loopsbench.agents.agent_name ::: loopsbench.agents.base_agent ::: loopsbench.agents.agent_factory
334mo agoReviewMountCreate a free account to mount
Purpose This repository follows Specification-Driven Development (SDD). Specifications are the source of truth. Code is an implementation of those specifications. AI agents are expected to behave as disciplined software engineers—not autonomous designers. When specifications are ambiguous, stop and ask for clarification rather than inventing behavior. This repository is intentionally specification-first. Development always follows the same lifecycle: Implementation is never the first step. The repository is divided into independent layers. Every layer depends only on layers above it. Never implement code…
316mo agoReviewMountCreate a free account to mount
You are working inside the samples/ folder of the Employee Self-Service Agent Developer Kit. This file is the authoritative briefing for any AI agent making changes here. For changes scoped to samples/, follow this file unless higher-priority system, security, or repository instructions say otherwise. Reference samples for the Microsoft Copilot Studio Employee Self-Service (ESS) agent. Samples contain Copilot Studio topics and their integration configuration. Workday DA GA uses a single shared configuration topic; other areas use ESS Template Configuration XML(s).…
316mo agoReviewMountCreate a free account to mount
If you are an AI coding agent (Copilot CLI, Claude, or any other) working in this directory tree, read this file first and follow it strictly. This document covers the rules for the production checks themselves (the code customers run via /flightcheck). Test-authoring rules are in tests/AGENTS.md. They complement each other; you need both. DA maker full/local/workday/servicenow diagnostics use diagnostic-only outcomes, not release approval. The maker skill and standalone command use the same CLI execution path for the same scope;…
316mo agoReviewMountCreate a free account to mount