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

9 rules. About 0 are common, 2 are distinctive, and 7 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.

• 7

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Every task must go through the process: Specify → Plan → Tasks → Implement.

   line 11
2. Very specific:

   Use Workflows in .agents/workflows/ and Skills in .agents/skills/.

   line 12
3. Very specific:

   DO NOT hardcoding URLs, Tokens, Keys.

   line 18
4. Very specific:

   DO NOT run docker compose down -v on Production.

   line 21
5. Very specific:

   Check logs immediately on error: docker compose logs -f <service>.

   line 23
6. Distinctive:

   Auto-Commit: MUST perform git commit & push immediately after completing any function or task according to Conventional Commits standards.

   line 24
7. Very specific:

   Task Tracking: Use task_boundary to synchronize status with @speckit.tasks (tasks.md).

   line 27
8. Very specific:

   Planning Artifacts: Always create implementation_plan.md when making large changes (atomic > 3 files).

   line 28
9. Very specific:

   Verification: After completing the task, use walkthrough.md to compare the results with spec.md.

   line 29

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

• 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.

• In this repository64 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • .cursor/rules/bro-skills.mdcCursor rule
  • .agents/skills/llms.txtllms.txt
  • brandkitSkill
  • bro-mcp-loopSkill
  • ci-security-scanning-with-strixSkill
  • design-taste-frontendSkill
  • fix-security-vulnerabilities-with-strixSkill
  • full-output-enforcementSkill
  • gpt-tasteSkill
  • high-end-visual-designSkill
  • imagegen-frontend-mobileSkill
  • imagegen-frontend-webSkill
  • image-to-codeSkill
  • industrial-brutalist-uiSkill
  • managed-pentesting-with-strixSkill
  • minimalist-uiSkill
  • penetration-testing-with-strixSkill
  • ponytailSkill
  • redesign-existing-projectsSkill
  • speckit.ai-engineerSkill
  • speckit.analyzeSkill
  • speckit.architectureSkill
  • speckit.backendSkill
  • speckit.backlogSkill
  • speckit.checkerSkill
  • speckit.checklistSkill
  • speckit.clarifySkill
  • speckit.constitutionSkill
  • speckit.contentSkill
  • speckit.databaseSkill
  • speckit.dddSkill
  • speckit.debugSkill
  • speckit.devopsSkill
  • speckit.diffSkill
  • speckit.event-realtimeSkill
  • speckit.frontendSkill
  • speckit.game-embeddedSkill
  • speckit.game-native-jsSkill
  • speckit.geoSkill
  • speckit.identity-accessSkill
  • speckit.identitySkill
  • speckit.implementSkill
  • speckit.mapSkill
  • speckit.migrateSkill
  • speckit.payment-fintechSkill
  • speckit.planSkill
  • speckit.quizmeSkill
  • speckit.reviewerSkill
  • speckit.roadmapSkill
  • speckit.securitySkill
  • speckit.seoSkill
  • speckit.specifySkill
  • speckit.sre-observabilitySkill
  • speckit.statusSkill
  • speckit.tasksSkill
  • speckit.taskstoissuesSkill
  • speckit.testerSkill
  • speckit.uatSkill
  • The first 60 shown.