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

frontier-ghcp-ttt-rvas / instructions-lab

Copilot instructions3 starsChanged 54 days agoMITView on GitHub

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

7 rules. About 1 is common, 1 is distinctive, and 5 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Use CommonJS syntax (require/module.exports) to match the existing project

    line 5
  2. Very specific:

    Use async/await for asynchronous operations.

    line 6
  3. Very specific:

    Use const by default. Use let only for reassignment.

    line 7
  4. Distinctive:

    Use the correct HTTP status: 200, 201, 400, 404, or 500.

    line 14
  5. Very specific:

    Use Node.js's built-in test runner

    line 31
  6. Very specific:

    Test files go in test/ with a .test.js extension

    line 32
  7. Common:

    Every endpoint needs success, validation-error, and not-found tests.

    line 33

≈ “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

Project Coding Standards

Language & Style

  • Use CommonJS syntax (require/module.exports) to match the existing project
  • Use async/await for asynchronous operations. Do not use .then() chains.
  • Use const by default. Use let only for reassignment. Do not use var.

Express Patterns

  • Route handlers must use async/await and try/catch.
  • Return errors as { "error": { "code": "ERROR_CODE", "message": "..." } }.
  • Validate request bodies with a dedicated validation function.
  • Use the correct HTTP status: 200, 201, 400, 404, or 500.

Naming Conventions

  • Files: kebab-case (user-routes.js)
  • Functions: camelCase (getUserById)
  • Constants: SCREAMING_SNAKE_CASE (MAX_PAGE_SIZE)
  • Classes: PascalCase (ProductService)

Response Format

  • Wrap successful single-item responses in { "data": ... }.
  • Return lists as { "data": [...], "total": N }.
  • Return errors as { "error": { "code": "...", "message": "...", "details": [...] } }.

Testing

  • Use Node.js's built-in test runner
  • Test files go in test/ with a .test.js extension
  • Every endpoint needs success, validation-error, and not-found tests.

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