agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/frontiertour27-LTG282-agentic-ops-with-github-copilot-app/.github/copilot-instructions.md

frontiertour27-LTG282-agentic-ops-with-github-copilot-app

Copilot instructions0 starsChanged 3 months agoMITView on GitHub

This repository is an AI Tour 2027 session template. Use the AI Tour 2027 repository agent for setup. There are two workflows: Attendee guidance can remain in docs/ for intentional MkDocs or docs-site patterns when the root README links clearly to the entry point. Accept: BRK, WRK, LAB, ILL, LTG, THR, DEM followed by digits.

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,336 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

The file

Show its rules and text

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

15 rules. About 0 are common, 14 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never fabricate session metadata, links, or content.

    line 18
  2. Distinctive:

    Use sentence case for Markdown headings.

    line 20
  3. Distinctive:

    Use session-owner language.

    line 21
  4. Distinctive:

    Do not choose runtimes, install packages, scaffold implementation code, or run project test suites.

    line 23
  5. Very specific:

    Update delivery-resources/README.md with the deck URL, recording links, and presenter notes (the single delivery-resources file — do not …

    line 28
  6. Distinctive:

    Do NOT run scripts, linters, or shell commands.

    line 29
  7. Distinctive:

    Do NOT delete folders.

    line 30
  8. Distinctive:

    Do NOT remove the "Before you're done" section.

    line 31
  9. Distinctive:

    Remove the "Before you're done" section and template markers.

    line 38
  10. Distinctive:

    Verify the repo is ready to publish by running through an inline checklist (placeholders, required README sections, delivery deck URL, …

    line 40
  11. Distinctive:

    If any fail: report in plain language, propose fixes, ask permission to apply, then re-check.

    line 41
  12. Distinctive:

    Do not close GitHub issues automatically.

    line 60
  13. Distinctive:

    Do not delete authored content without confirmation.

    line 61
  14. Distinctive:

    Do not modify validation scripts during normal workflows.

    line 62
  15. Distinctive:

    Do not use language like "publication blocker", "focused Markdown diagnostics", "initialization readiness", or "local hypothesis".

    line 63

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

AI Tour 2027 repository instructions

This repository is an AI Tour 2027 session template. Use the AI Tour 2027 repository agent for setup.

Workflows

There are two workflows:

  • help me initialize repo — populate README and delivery resources with session content
  • help me finalize repo — clean up, validate, and prepare for publication

Plus:

  • help me handle issues — triage and apply safe fixes to open GitHub issues

Core rules

  • Never fabricate session metadata, links, or content.
  • Preserve authored content. Do not overwrite non-placeholder sections without confirmation.
  • Use sentence case for Markdown headings.
  • Use session-owner language. Announce the section being worked on. Do not narrate patches, diagnostics, or editor internals.
  • Track answers within a workflow phase. Do not re-ask questions.
  • Do not choose runtimes, install packages, scaffold implementation code, or run project test suites.

Initialize scope

  • Fill in README metadata: session code, title, description, learning outcomes (exactly three), technologies, content owners, delivery links.
  • Update delivery-resources/README.md with the deck URL, recording links, and presenter notes (the single delivery-resources file — do not create a separate presenter guide).
  • Do NOT run scripts, linters, or shell commands.
  • Do NOT delete folders.
  • Do NOT remove the "Before you're done" section.
  • For workshops/labs: attendee path is always both (guided + self-paced). Do not ask.
  • For workshops/labs: do not ask a separate live-demo question.
  • Require a public deck URL. Accept deferral but keep Initialize open until provided.

Finalize scope

  • Remove the "Before you're done" section and template markers.
  • Confirm which unused folders to remove.
  • Verify the repo is ready to publish by running through an inline checklist (placeholders, required README sections, delivery deck URL, relative link targets).
  • If any fail: report in plain language, propose fixes, ask permission to apply, then re-check.
  • Once all pass: remove template-only tooling (.github/agents/, .github/tests/, .github/copilot-instructions.md, .github/AGENT-WORKFLOW.md). Remove .github/ if empty.
  • Report the repo as ready to publish.

Folder purposes

  • instructions/ — attendee step-by-step guidance
  • docs/ — supporting reference material and architecture/context
  • delivery-resources/ — deck, recordings, presenter notes, and re-delivery material (single README.md file)
  • src/, data/, infra/, .devcontainer/ — session-specific technical folders (optional)

Attendee guidance can remain in docs/ for intentional MkDocs or docs-site patterns when the root README links clearly to the entry point.

Session code prefixes

Accept: BRK, WRK, LAB, ILL, LTG, THR, DEM followed by digits.

Do not

  • Do not close GitHub issues automatically.
  • Do not delete authored content without confirmation.
  • Do not modify validation scripts during normal workflows.
  • Do not use language like "publication blocker", "focused Markdown diagnostics", "initialization readiness", or "local hypothesis". Write for a speaker, not a QA engineer.

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