agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aitour27-LTG243-fabric-iq-from-rows-to-reliable-answers/AGENTS.md

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

AGENTS.md0 starsChanged 27 days agoMITView on GitHub

This repository publishes the LTG243 Fabric-only demo. The deployable source is the synthetic data under data/, the Fabric item definitions under src/fabric/, and the two root deployment entry points. - Read instructions/README.md before running deployment commands. - Use Node.js 24 or later and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed. - Keep data/scenario.json frozen. Do not hardcode values already defined by the scenario. - Generated output must remain deterministic. Do not…

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 AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 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 AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read instructions/README.md before running deployment commands.

    line 9
  2. Very specific:

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

    line 10
  3. Very specific:

    Keep data/scenario.json frozen.

    line 12
  4. Distinctive:

    After a data or model change, run:

    line 16
  5. Distinctive:

    Do not weaken a failing validator or expected-answer check.

    line 24
  6. Very specific:

    Do not commit data/.staging/, generated semantic-model definitions, build output, tokens, tenant/workspace/item IDs, screenshots, or …

    line 25
  7. Very specific:

    Run local validation and --dry-run first.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Repository instructions for coding agents

This repository publishes the LTG243 Fabric-only demo. The deployable source is the synthetic data under data/, the Fabric item definitions under src/fabric/, and the two root deployment entry points.

Working rules

  • Read instructions/README.md before running deployment commands.
  • Use Node.js 24 or later and the exact Fabio version pinned in .fabio-version (0.79.0). Upgrade with fabio upgrade --target-version 0.79.0 if needed.
  • Keep data/scenario.json frozen. Do not hardcode values already defined by the scenario.
  • Generated output must remain deterministic. Do not use current time or unseeded randomness in data generation.

  • After a data or model change, run:

    node data/tools/generate.ts
node data/tools/validate.ts
node data/tools/manifest.ts
  • Do not weaken a failing validator or expected-answer check.
  • Do not commit data/.staging/, generated semantic-model definitions, build output, tokens, tenant/workspace/item IDs, screenshots, or command output with private values.

Fabric commands

Run local validation and --dry-run first. Before executing a command that changes Fabric, show the workspace and command to the user and wait for confirmation.

LTG243 does not use --with-cosmos. Use --overwrite only for data the user intends to replace. If a command times out, inspect the workspace before retrying.

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