agentleFS
MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m5-03-hve-core-challenge/lab/solution/decision-api/.github/copilot-instructions.md

frontier-ghcp-ttt-rvas / decision-api

Copilot instructions3 starsChanged 54 days agoMITView on GitHub

Repository context for HVE agents working on the Engineering Decision API

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

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Keep the service in CommonJS JavaScript with Express.

    line 14
  2. Distinctive:

    Keep decision state in memory and scoped to one app instance.

    line 16
  3. Distinctive:

    Do not add dependencies or endpoints outside the challenge brief.

    line 17
  4. Distinctive:

    Use synthetic records. Do not connect to a remote service or persistent store.

    line 18
  5. Distinctive:

    Test observable HTTP behavior with Jest and Supertest.

    line 23
  6. Distinctive:

    Treat learner-provided strings as untrusted input.

    line 25

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

Engineering Decision API repository instructions

Project context

This Express service captures structured engineering decisions. HVE agents must keep the first slice limited to decision creation and preserve the health route.

Architecture and delivery boundary

  • Keep the service in CommonJS JavaScript with Express.
  • Preserve GET /health and the exported createApp test boundary.
  • Keep decision state in memory and scoped to one app instance.
  • Do not add dependencies or endpoints outside the challenge brief.
  • Use synthetic records. Do not connect to a remote service or persistent store.

Quality bar

  • Return success data under data and errors under error.
  • Test observable HTTP behavior with Jest and Supertest.
  • Build tested source into a production-only container that runs as a non-root user.
  • Treat learner-provided strings as untrusted input. Do not echo stack traces.

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.