agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m2-03-spaces-and-context/lab/solution/.github/copilot-instructions.md

frontier-ghcp-ttt-rvas / solution

Copilot instructions3 starsChanged 2 months agoMITView on GitHub

Express REST API for a product catalog. In-memory data. Synthetic project.

The file

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

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

  • 4

    Very specific

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

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

    Use ES modules (import/export), never require.

    line 7
  2. Very specific:

    Put each resource's routes in its own file in src/routes/.

    line 8
  3. Distinctive:

    Don't add dependencies without asking.

    line 11
  4. Very specific:

    Use node:test and node:assert/strict.

    line 15
  5. Very specific:

    Start the app with NODE_ENV=test, import app from src/app.js, and call it with fetch on a random port.

    line 16

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

Storefront Product API

Express REST API for a product catalog. In-memory data. Synthetic project.

Code

  • Use ES modules (import/export), never require.
  • Put each resource's routes in its own file in src/routes/. Name files in kebab-case.
  • Validate input with the model's static validate() method before changing data.
  • Return { data } on success and { error: { code, message, details } } on failure.
  • Don't add dependencies without asking.

Tests

  • Use node:test and node:assert/strict. No Jest, Mocha, or Supertest.
  • Start the app with NODE_ENV=test, import app from src/app.js, and call it with fetch on a random port.
  • npm test must run the whole suite.

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.

Check your setup, free