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

1. Distinctive:

   When a doc needs to be exported to PDF or HTML, do not rebuild it ad hoc in chat or as a one-off prompt flow.

   line 5
2. Distinctive:

   Use the repo-local generator in the git-ignored docs folder instead:

   line 7
3. Very specific:

   keep generated docs under .agentic-dev-kit/

   line 16
4. Distinctive:

   prefer the repo-local generator over re-rendering markdown through chat

   line 17
5. Distinctive:

   update the source markdown first, then regenerate the PDF from the same script

   line 18
6. Distinctive:

   do not duplicate ad hoc export commands in prompts when the script already exists

   line 19

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