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

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  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:

   keep apps/cli as a thin adapter — it exposes both the runmark CLI and the runmark mcp stdio MCP server

   line 9
2. Very specific:

   keep tracked request intent in runmark/ and runtime state in runmark/artifacts/

   line 10
3. Distinctive:

   do not add secret literals to tracked filescould be automatic

   line 11
4. Distinctive:

   prefer path-derived IDs and explicit schemas at public boundaries

   line 12
5. Very specific:

   put judge-oriented validation assets under testing/runmark/

   line 13

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