agentleFS
Sign inStart free
HumbleDaanHumbleDaan/fabric-project-structure/AGENTS.md

fabric-project-structure

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

Entry point for AI coding agents working in this repository. This file exists so that any agent host picks up the same rules. The substance lives in .github/copilot-instructions.md — read that file next. All three point at the same place. Keep it that way — one source of truth, thin pointers. 1. Never change the identity layer of a Fabric item. In projects/*/workspaces/*/, the logicalId and type in .platform, and the item folder name, are what link the files to…

  • 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,774 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 repository6 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All three point at the same place.

    line 14
  2. Distinctive:

    If a name is not covered there, propose an addition to the standard rather than inventing one.

    line 25
  3. Very specific:

    Read the project's project-context.md: before doing anything in projects/<project>/.

    line 26

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

AGENTS.md

Entry point for AI coding agents working in this repository.

This file exists so that any agent host picks up the same rules. The substance lives in .github/copilot-instructions.md — read that file next.

HostReads
GitHub Copilot (VS Code, CLI).github/copilot-instructions.md
Codex / Jules / OpenCode / Copilot CLIAGENTS.md (this file)
Claude CodeCLAUDE.md

All three point at the same place. Keep it that way — one source of truth, thin pointers.

Non-negotiables

  1. Never change the identity layer of a Fabric item. In projects/*/workspaces/*/, the logicalId and type in .platform, and the item folder name, are what link the files to the live workspace. Editing item definitions (TMDL, notebook .py, warehouse SQL) is supported and often recommended — but sync one direction at a time. Detail in .github/copilot-instructions.md.
  2. Never write to a production workspace. Promotion happens through the release process only.
  3. Follow .github/standards/naming-conventions.md. If a name is not covered there, propose an addition to the standard rather than inventing one.
  4. Read the project's project-context.md before doing anything in projects/<project>/.
  5. Cite sources for platform behaviour. Fabric changes monthly. Link Microsoft Learn rather than asserting from memory.

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