Utilize Copilot Instructions, Agents files in SDK repos for AzureSDK MCP #13679
Description
Many (all?) of our SDK repos already have a trove of Copilot instructions, prompts, and maybe even agent definition that provide language-specific directory organization, test/sample instructions, etc., that seem best left to the SDK repos. Not only are they easier to update than in a centralized location, but they facilitate GitHub Copilot for the web, in VSCode, and in other use cases outside of azsdk. The language SDK repos become the central place for all things Copilot for any use case.
Case in point: since Azure/azure-sdk-for-rust isn't fully onboarded yet (we need to be closer to GA, I'm told), I did a little refactoring of existing Copilot instructions and wrote up some new Copilot instructions for ARM crates (something we're only starting to tackle officially in the public repo). After a couple iterations of tweaks, I have something working pretty well, but it will be undergoing some refactoring to split into 2 or 3 different PRs to isolate concepts and future git loging.
For context, @ronniegeraghty asked me to open this and attach my Copilot chat log as a source of some ideas and discussion. I think there's a good synergy of what we can consolidate into the azsdk tool and how we can utilize language-repo content in that orchestration. /cc @maririos