agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/frontiertour27-LTG243-fabric-iq-from-rows-to-reliable-answers/.github/copilot-instructions.md

frontiertour27-LTG243-fabric-iq-from-rows-to-reliable-answers

Copilot instructions0 starsChanged 26 days agoMITView on GitHub

Read AGENTS.md, README.md, instructions/README.md, and instructions/copilot.md before helping with setup. - Scope is the Fabric-only LTG243 demo. - Use Node.js 24+ and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed. - Run the manifest check and validator before any deployment work. - Ask for the target workspace ID; do not infer or reuse one from logs. - Run create-data.sh or create-data.ps1 with --dry-run first. - Show the workspace and command before running…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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.

  • In this repositoryOne other file it gives its agents.

The file

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

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read AGENTS.md, README.md, instructions/README.md, and instructions/copilot.md before helping with setup.

    line 3
  2. Very specific:

    Use Node.js 24+ and the exact Fabio version pinned in .fabio-version (0.79.0).

    line 7
  3. Distinctive:

    Run the manifest check and validator before any deployment work.

    line 9
  4. Distinctive:

    Ask for the target workspace ID.

    line 10
  5. Very specific:

    Run create-data.sh or create-data.ps1 with --dry-run first.

    line 11
  6. Very specific:

    Use --overwrite only for data the user intends to replace.

    line 14
  7. Distinctive:

    Do not expose or commit credentials, tokens, tenant IDs, workspace IDs, item IDs, deployment output, screenshots, or generated definitions.

    line 16
  8. Very specific:

    Keep data/scenario.json frozen and preserve deterministic generation.

    line 18

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

LTG243 repository instructions

Read AGENTS.md, README.md, instructions/README.md, and instructions/copilot.md before helping with setup.

  • Scope is the Fabric-only LTG243 demo.
  • Use Node.js 24+ and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed.
  • Run the manifest check and validator before any deployment work.
  • Ask for the target workspace ID; do not infer or reuse one from logs.
  • Run create-data.sh or create-data.ps1 with --dry-run first.
  • Show the workspace and command before running a deployment or authenticated verification, then wait for confirmation.
  • Use --overwrite only for data the user intends to replace. Do not use --with-cosmos for LTG243.
  • Do not expose or commit credentials, tokens, tenant IDs, workspace IDs, item IDs, deployment output, screenshots, or generated definitions.
  • Keep data/scenario.json frozen and preserve deterministic generation.
  • Report local checks, dry-run output, and deployed results separately.

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