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

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  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. Very specific:

   Use flat YAML frontmatter with plural tags, aliases, and cssclasses keys.

   line 18
2. Distinctive:

   Use Obsidian wikilinks for internal knowledge links.

   line 19
3. Very specific:

   Never modify .raw/ source material.

   line 21
4. Very specific:

   Keep wiki/log.md append-only and place new entries first.

   line 22
5. Distinctive:

   Keep Agent Skills frontmatter compatible with the shared skill specification.

   line 24
6. Distinctive:

   Treat Maz Works Knowledge Vault as the umbrella.

   line 26
7. Distinctive:

   Never add credentials, private client information, or private spiritual content.could be automatic

   line 27
8. Very specific:

   Run make test after changing scripts or skills.

   line 29

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