agentleFS
Alex5350Alex5350/arsenal/.github/copilot-instructions.md

arsenal

Copilot instructions0 starsChanged 16 days agoMITView on GitHub

GitHub Copilot reads this file in VS Code chats and agent sessions. The universal entry point for all harnesses is AGENTS.md at the repository root; treat it as the authority. The essentials, restated: 1. docs/ is the single source of truth. Start at docs/README.md, and read docs/harness/copilot.md for Copilot-specific wiring. 2. Work the loop defined in docs/workflows/: research, plan, execute, verify, track, publish. Do not write code before a plan exists in writing. 3. Route by tier per docs/models/routing.md: you…

The file

Files
copilot-instructions.md

Copilot instructions (arsenal)

GitHub Copilot reads this file in VS Code chats and agent sessions. The universal entry point for all harnesses is AGENTS.md at the repository root; treat it as the authority. The essentials, restated:

  1. docs/ is the single source of truth. Start at docs/README.md, and read docs/harness/copilot.md for Copilot-specific wiring.
  2. Work the loop defined in docs/workflows/: research, plan, execute, verify, track, publish. Do not write code before a plan exists in writing.
  3. Route by tier per docs/models/routing.md: you plan and review as the strategist, you hand implementation to the executor tier when the harness supports it, and you never skip the test gate in docs/standards/testing.md.
  4. Mirror every unit of work to the team tracker using docs/integrations/ and scripts/work-item.sh. Stamp work-item IDs in commits and PRs.
  5. Conventional commits only. No secrets in code, logs, or commands.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.