The Java client is a port of the JavaScript client in ../playwright/packages/playwright-core/src/client/. When implementing or changing a method, read the corresponding JS file first and mirror its logic. Project checkouts (including the upstream playwright repo) live in the parent directory (../). Use the gh cli to interact with GitHub. Semantic commit messages: label(scope): description Labels: fix, feat, chore, docs, test, devops Never add Co-Authored-By agents in commit message. Never add "Generated with" in commit message. Never add test plan to…
Core project guidelines, coding conventions, and architectural principles are in AGENTS.md — read it first. This file adds Claude-specific skill activation instructions. Skills live in .github/skills/<skill-name>/SKILL.md. Claude cannot discover them automatically — use the Read tool to load the relevant skill before starting any architecture task. Example: Read(".github/skills/create-adr/SKILL.md") Happy coding!
Updates: fabric-collection is a third-party marketplace, so enable auto-update once: run /plugin, open Marketplaces, select fabric-collection, and choose Enable auto-update. Administrators can instead set "autoUpdate": true on its extraKnownMarketplaces entry in managed settings. To update on demand, run claude plugin update <plugin>@fabric-collection. If these files were copied in loosely rather than installed as a plugin, compare the local package.json version against the remote (git fetch origin main --quiet && git show origin/main:package.json) and re-copy if it is newer. This project…
This is the marketplace plugin wrapper for FlowAgent (Power Automate cloud flow tooling). Flow-definition rules, the two-provider auth model (Azure CLI + MSAL), the error reference, and known issues are documented in references/ — see definition-reference.md, connection-patterns.md, and error-troubleshooting.md. Read those before building or editing flows. This file only covers plugin-local specifics; see AGENTS.md (this folder) for the tool-routing rule. - skills/ — verb-first user-invocable skills (create-flow, build-flow, debug-flow, diagnose-flow, manage-flows, browse-flows, manage-desktop-flows, route-environments, setup) - references/ — shared docs…
This document provides comprehensive instructions for AI-assisted development of the MicrosoftFabricMgmt PowerShell module located in tools/MicrosoftFabricMgmt/. This module provides a robust interface for managing Microsoft Fabric resources via the Fabric API. Module Purpose: Enterprise-grade PowerShell module for Microsoft Fabric resource management with excellent error handling, comprehensive logging, and outstanding documentation. Build System: Sampler - Modern PowerShell module scaffolding and build framework Key Frameworks: - PSFramework: Configuration management and logging (Documentation) - Pester: Unit and integration testing - PlatyPS: Help documentation…
This directory contains a Python-based Model Context Protocol (MCP) server that wraps the MicrosoftFabricMgmt PowerShell module and exposes its capabilities to AI assistants (Claude, GitHub Copilot, etc.). DO NOT edit the PowerShell module source here. All PowerShell module development belongs in ../MicrosoftFabricMgmt/source/ and must follow the module's own CLAUDE.md. Key principle: Python is a thin protocol-translation layer only. All Fabric API logic lives in the PowerShell module. Python does not call Fabric REST APIs directly. Maintains a single long-lived pwsh…
Microsoft Copilot Studio samples repo with a Just the Docs (Jekyll) site for navigation and search. Live site: https://microsoft.github.io/CopilotStudioSamples/ Solutions follow the PnP format: Front matter: README should include: - What the solution does and which Copilot Studio features it demonstrates - Screenshots in assets/ (reference as ) - Installation steps (import zip via make.powerapps.com > Solutions > Import) - Any connection references or environment variables to configure - Known issues or limitations Update authoring/solutions/README.md Contents table after adding. Add…
This project is governed by a plan-validation MCP server. *Every file access and shell call you make must go through the validated_ tools.** The built-in Read, Write, Edit, Bash, Glob, Grep tools are NOT available in this session — only the MCP tools provided by the plan-validation server. A live dashboard is running at http://localhost:3100 — every tool call you make is visible there, including blocks. Call getplanschema. Read it carefully — the AgentPlan DSL has strict shape requirements and…
PowerShell captures and reuses PowerShell scripts from reasoning traces. Scripts persist in instance storage (~/.typeagent/profiles/<profile>/powershell/) across sessions. Grammar rules are registered dynamically at runtime — no build step needed for user-created flows. scripts/compileRecipes.mjs reads pending/*.recipe.json and generates build-time artifacts. This is useful for testing but not used in production — production flows are loaded from instance storage at runtime.
TaskFlow runs user-taught multi-step macros over existing TypeAgent actions. Flows are pure JSON — no TypeScript logic. A deterministic compile script handles all boilerplate generation (TypeScript type, grammar rule, manifest entry). When asked to "compile pending recipes" or similar: That's it. scripts/compileRecipes.mjs reads pending/*.recipe.json and: If the build fails, fix the error in the generated files and re-run pnpm run build. When asked to write a recipe for a new flow (or if you notice a missing flow): Do NOT…
This is the Windows Protocol Test Suites repository — a .NET-based interoperability testing framework for Microsoft Open Specification protocols. Follow these steps before starting any task: Use kebab-case for the…
Semantic commit messages: label(scope): description Labels: fix, feat, chore, docs, test, devops Never add Co-Authored-By agents in commit message. Never add "Generated with" in commit message. Never add test plan to PR description. Keep PR description short — a few bullet points at most. Branch naming for issue fixes: fix-<issue-number> Never git push without an explicit instruction to push. Applies even when a PR is already open for the branch — additional commits are immediately visible to reviewers. Commit locally,…
A sophisticated dual-mode assistant that facilitates collaborative knowledge sharing between Coordinators (knowledge creators) and Team members (knowledge receivers) within the Semantic Workbench platform.
Using AI Context for Development: * New developers: Read CONFIGURATION.md + PYTHONLIBRARIESCORE.md for project overview * Building assistants: - Start with ASSISTANTSOVERVIEW.md for common patterns - Use specific assistant files (e.g., ASSISTANTPROJECT.md) as implementation templates * Working on specific assistants: Load the relevant ASSISTANT_*.md file for focused context * Library development: Choose appropriate PYTHONLIBRARIES*.md file by functional area * Frontend work: Study component patterns in WORKBENCH_FRONTEND.md * API development: Follow service patterns from WORKBENCH_SERVICE.md * MCP servers: Use existing servers…
NEVER commit or git add without explicit user permission. When asked for a commit message, provide the message text only - do not execute git commit or git add. IMPORTANT: Always use Release configuration (-c Release). The user runs Release builds, not Debug. If running, ask the user to close it before building.
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
MicrosoftCLAUDE.md