frontier-ai-starter-kit-rvas
Copilot instructions7 starsChanged 20 days agoMITView on GitHub
This repository maintains the Agentic Co-build plugin, dependency inventory, and documentation site. Customer application code and architecture artifacts belong in the customer's selected repository. The three bundled skill bodies live under plugins/agentic-cobuild/skills/. Select third-party dependencies in scripts/agentic-skills.json; install them from their upstream sources instead of copying them into this plugin. Preserve the creator's discovery confirmation, architecture approval, diagram review gates, and separately initiated implementation handoff. Before changing decision-bearing Microsoft product guidance or Azure SDK code, consult current Microsoft Learn evidence…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/frontier-agentic-cobuild-rvasword for word, first seen Oct 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- microsoft/frontier-agentic-cobuild-rvas★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,343 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- azure-aigatewaySkill
- azure-aiSkill
- diagram-designSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- finetuningSkill
- capacitySkill
- customizeSkill
- presetSkill
- deploy-modelSkill
- microsoft-foundrySkill
- rvap-brandSkill
- writing-for-agentsSkill
- agentic-workflowsSkill
- content-accuracy-auditSkill
- foundry-hosted-agentsSkill
- foundry-iq-knowledge-basesSkill
- foundry-modelsSkill
- foundry-observabilitySkill
- foundry-projects-resourcesSkill
- foundry-toolboxesSkill
- foundry-workflowsSkill
- impeccableSkill
- ai-agent-creatorSkill
- cloud-architecture-diagramSkill
- idea-forgeSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before changing decision-bearing Microsoft product guidance or Azure SDK code, consult current Microsoft Learn evidence and the relevant …
- Distinctive: line 16
Use verified signatures and run the applicable tests.
- Distinctive: line 18
Write for competent engineers.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workspace instructions
This repository maintains the Agentic Co-build plugin, dependency inventory, and documentation site. Customer application code and architecture artifacts belong in the customer's selected repository.
The three bundled skill bodies live under plugins/agentic-cobuild/skills/.
Select third-party dependencies in scripts/agentic-skills.json; install them
from their upstream sources instead of copying them into this plugin.
Preserve the creator's discovery confirmation, architecture approval, diagram review gates, and separately initiated implementation handoff.
Before changing decision-bearing Microsoft product guidance or Azure SDK code, consult current Microsoft Learn evidence and the relevant specialist skill. Use verified signatures and run the applicable tests.
Write for competent engineers. Lead with the outcome, keep wording concrete, and retain the RVAP/RVAS brand. Do not add verification-date banners or invented customer evidence. Keep the setup guide generated from its Markdown source and the upstream inventory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.