CommandBar Development

Quick Orientation

Treat "CommandBar" as the user's shorthand for Microsoft PowerToys Command Palette extension development.

Prefer official Microsoft Learn and PowerToys GitHub sources. The docs are still evolving, so browse the official docs when exact API names, packaging rules, or publishing steps matter.

Read references/docs-map.md when you need doc links, the current conceptual model, common gotchas, or a refresher on project structure.

Default Workflow

1. Identify whether the task is about scaffold/setup, commands/pages, debugging, packaging/publishing, or API lookup.
2. Inspect the local repo before suggesting changes. Command Palette extension projects are usually C#/.NET Windows App SDK projects generated by the Command Palette template.
3. Use the template's existing structure and namespaces. Avoid inventing a different architecture unless the user asks for a redesign.
4. For runtime behavior, make changes in the command provider, page classes, and command classes rather than manifest/package files unless discovery, deployment, or publishing is the issue.
5. After code changes, prefer building with the repo's solution/project commands, then remind that Visual Studio deploy plus Command Palette Reload Command Palette Extension may be required for the installed package to refresh.

Common Implementation Targets