agentleFS
clarknova99clarknova99/multi-provider-harness/.github/copilot-instructions.md

multi-provider-harness

Copilot instructions1 starsChanged 4 months agoMITView on GitHub

All project conventions, invariants, and skill routing live in AGENTS.md at the repository root. Read it first. Before starting work, read docs/state/CURRENT.md — it holds the active task and the exact next action. This project is worked across multiple AI providers (Claude Code, Codex, Cursor, Gemini) switched mid-task when usage limits trip; on-disk state in docs/state/ is the only source of continuity between them. This file is a thin pointer — it exists so Copilot surfaces that look for .github/copilot-instructions.md…

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All project conventions, invariants, and skill routing live in AGENTS.md at the repository root.

    line 3

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Copilot instructions

All project conventions, invariants, and skill routing live in AGENTS.md at the repository root. Read it first.

Before starting work, read docs/state/CURRENT.md — it holds the active task and the exact next action. This project is worked across multiple AI providers (Claude Code, Codex, Cursor, Gemini) switched mid-task when usage limits trip; on-disk state in docs/state/ is the only source of continuity between them.

This file is a thin pointer — it exists so Copilot surfaces that look for .github/copilot-instructions.md still find their way to the canonical AGENTS.md. Do not duplicate content here.

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.