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

9 rules. About 1 is common, 6 are distinctive, and 2 are very specific to this project.

• ≈1

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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:

   Follow standard TypeScript conventions and best practices

   line 7
2. Distinctive:

   Use the Composition API when creating Vue components

   line 8
3. Distinctive:

   Use clear, descriptive variable and function names

   line 9
4. Distinctive:

   Add comments only to explain complex logic or non-obvious implementations

   line 11
5. Very specific:

   Write unit tests for core functionality using vitest

   line 12
6. Very specific:

   Write end-to-end tests using Playwright and @nuxt/test-utils

   line 13
7. Distinctive:

   Keep functions focused and manageable (generally under 50 lines)

   line 14
8. Common:

   Use error handling patterns consistently

   line 15
9. Distinctive:

   Ensure you write strictly type-safe code, for example by ensuring you always check when accessing an array value by index

   line 16

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 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.

• Other versions1 project uses a version of this.

  Word for word · 1

  1. npmx-dev/npmx.dev★ 3.7k100% same

  Edited · 0

  None found.

  Wrote their own version · 0

  None found.

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

  Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.