agentleFS
erikunhaerikunha/vault-of-loci/.github/copilot-instructions.md

vault-of-loci

Copilot instructions0 starsChanged 5 days agoMITView on GitHub

This repository's rules live in AGENTS.md at the root. Read it before answering or editing. The minimum, in case AGENTS.md is not in context:

  • Reads credentials

The file

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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read INDEX.md first, open only the needed section by line range from 90_System/index.json, and never read a file over 300 lines whole.

    line 7
  2. Very specific:

    Never read or quote /.env or plugin data.json files.

    line 8
  3. Distinctive:

    Do not invent references: a paper needs a verifiable arXiv ID or DOI.

    line 9

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

This repository's rules live in AGENTS.md at the root. Read it before answering or editing.

The minimum, in case AGENTS.md is not in context:

  • Read INDEX.md first, open only the needed section by line range from 90_System/index.json, and never read a file over 300 lines whole.
  • Never read or quote **/.env or plugin data.json files.
  • Do not invent references: a paper needs a verifiable arXiv ID or DOI.
  • File and folder names use underscores instead of spaces.
  • What was not checked says "not verified".
  • Concept, reference and guide notes keep the two headings in 90_System/Specs/study_layer.json first and second.

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.