PowerToys
microsoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
Copilot instructions139k starsChanged 8 months ago
--- description: 'PowerToys AI contributor guidance' --- # PowerToys – Copilot Instructions Concise guidance for AI contributions. For complete details, see [AGENTS.md](../AGENTS.md). ## Key Rules - Atomic PRs: one logical change, no drive-by refactors - Add tests when changing behavior - Keep hot paths quiet (no logging in hooks/tight loops) ## Style Enforcement - C#: `src/.editorconfig`, StyleCop.Analyzers - C++: `src/.clang-format` - XAML: XamlStyler ## When to Ask for Clarification - Ambiguous spec after scanning docs - Cross-module impact unclear - Security, elevation, or installer changes ## Component-Specific Instructions These are auto-applied based on file location: - [Runner & Settings UI](.github/instructions/runner-settings-ui.instructions.md) - [Common Libraries](.github/instructions/common-libraries.instructions.md) ## Shortcut Guide V2 Manifests When creating or editing Shortcut Guide keyboard shortcut manifest files, follow the schema and naming conventions in the spec: - [WinGet Manifest Keyboard Shortcuts schema](<../doc/specs/WinGet Manifest Keyboard Shortcuts schema.md>) – manifest file format, field definitions, file naming, and the `+` prefix convention for apps without a WinGet package ## Detailed Documentation - [Architecture](../doc/devdocs/core/architecture.md) - [Coding Style](../doc/devdocs/development/style.md)
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

