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

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈7

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Every skill must live in a root-level folder named exactly like the skill.

   line 7
2. Very specific:

   Every skill folder must include SKILL.md.

   line 8
3. Very specific:

   Keep each SKILL.md concise.

   line 12
4. Distinctive:

   Do not include private client details, API keys, internal repo paths, or proprietary credentials.

   line 13
5. Distinctive:

   Use MIT license for public skills.

   line 14
6. Distinctive:

   Write direct, practical copy for founders, operators, marketers, and builders.

   line 18
7. Distinctive:

   Avoid hype that cannot be backed up.

   line 19
8. Distinctive:

   Use normal hyphens instead of em dashes or en dashes.

   line 20
9. Distinctive:

   When adding a skill, update:

   line 25

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