🧠 [platform] Configure organization-wide Copilot instructions

[szmyty]

Context

GitHub supports organization-level Copilot instructions that guide how Copilot generates code across repositories.

This enables consistent:

• coding standards
• architecture patterns
• developer experience
• AI behavior alignment

This is a foundational step for Ego Hygiene’s spec-driven + AI-assisted workflow.

---

References

• https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-organization-instructions
• https://docs.github.com/en/copilot/tutorials/coding-agent/get-the-best-results#path-specific-instructions

---

Goals

• Define global Copilot behavior for the egohygiene organization
• Align Copilot with:
  • spec-driven development
  • explicit/verbose coding style
  • long-form CLI flags
  • strong commenting and structure
• Explore path-specific overrides for:
  • shell scripts
  • Python
  • CI workflows
  • documentation

---

Scope

Phase 1 — Global Instructions

• Create organization-level Copilot instruction file
• Define:
  • naming conventions
  • code verbosity expectations
  • commenting standards
  • architectural principles

Phase 2 — Path-Specific Instructions

• Add rules for:
  • /scripts (bash conventions, shdoc)
  • /src (language-specific standards)
  • /.github/workflows (CI best practices)
  • /docs (structured writing patterns)

Phase 3 — Validation

• Test Copilot outputs in multiple repos
• Verify consistency across:
  • new files
  • refactors
  • suggestions

---

Acceptance Criteria

• Copilot follows defined coding standards consistently
• Generated code uses:
  • verbose naming
  • explicit structure
  • long-form CLI flags
• Path-specific behavior works as expected
• Instructions are reusable across repositories

---

Notes

This is a core building block for:

"Copilot as a junior engineer executing structured system design"

This should integrate tightly with:

• .github repo templates
• issue templates
• future automation workflows