Aspire

We split this copilot-instructions.md into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are 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.

• 4

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific
• could be automatic: a setting could enforce it

1. Distinctive:

   Use file-scoped namespaces and the repository's existing formatting.

   line 11
2. Distinctive:

   All public APIs require XML documentation.

   line 12
3. Very specific:

   Prefer is null and is not null over equality checks with null.

   line 14
4. Very specific:

   Do not manually edit generated */api/*.cs files unless API baseline regeneration is explicitly required.could be automatic

   line 15
5. Distinctive:

   Start with the integration being changed, then inspect its tests, example, README, and one or two same-pattern integrations.

   line 19
6. Very specific:

   Use the applicable files under .github/instructions/ for path-specific guidance.

   line 20
7. Very specific:

   Use focused workflows under .agents/skills/ for specialized tasks.

   line 21
8. Distinctive:

   Keep changes scoped to the requested integration and avoid unrelated refactoring.

   line 22
9. Distinctive:

   Run the narrowest relevant build or test command.

   line 23

≈ “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.