sqlhyperscalemechanics
Copilot instructions0 starsChanged 8 days agoMITView on GitHub
- Do not display subscription IDs or tenant IDs in chat, plans, summaries, copied commands, or screenshots intended for recording. - Verify and use those IDs internally as needed. Limit tool output with explicit queries so account objects and full Azure resource IDs do not expose them. - Identify approved targets by subscription display name, resource group, server, and database name. Redact subscription/tenant IDs from errors and resource paths before presenting them; retain the actionable error details. - Follow .github/skills/start-and-grow-hyperscale-demo/SKILL.md…
In this repository2 other files it gives its agents.
The file
We split this copilot-instructions.md into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Do not display subscription IDs or tenant IDs in chat, plans, summaries, copied commands, or screenshots intended for recording.
- Distinctive: line 5
Verify and use those IDs internally as needed.
- Very specific: line 13
Follow .github/skills/start-and-grow-hyperscale-demo/SKILL.md for Caldova deployment, rehearsal, population, and reset.
- Distinctive: line 15
Use the currently logged-in Azure CLI user and subscription after read-only verification.
- Distinctive: line 17
Use supplied qualitative requirements.
- Distinctive: line 19
Never delete either demo logical SQL server or the shared resource group.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 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
Azure identifier privacy
- Do not display subscription IDs or tenant IDs in chat, plans, summaries, copied commands, or screenshots intended for recording.
- Verify and use those IDs internally as needed. Limit tool output with explicit queries so account objects and full Azure resource IDs do not expose them.
- Identify approved targets by subscription display name, resource group, server, and database name. Redact subscription/tenant IDs from errors and resource paths before presenting them; retain the actionable error details.
Start and Grow demo
- Follow .github/skills/start-and-grow-hyperscale-demo/SKILL.md for Caldova deployment, rehearsal, population, and reset.
- Use the currently logged-in Azure CLI user and subscription after read-only verification. Do not ask the user to select them again or silently switch.
- Use supplied qualitative requirements; do not request numerical usage or cost estimates for the pilot. State sizing assumptions in the deployment plan.
- Never delete either demo logical SQL server or the shared resource group. Preserve their server-level cross-database preview settings.
- Scene 2 reset deletes only the explicitly approved Start database. Keep all databases on the network server, both logical servers, and the pool.
- Get explicit typed approval in chat before any Azure change.
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.

