agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-sdk-for-rust/samples/AGENTS.md

azure-sdk-for-rust / samples

AGENTS.md887 starsChanged 29 days agoMITView on GitHub

Follow ../AGENTS.md.

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the latest stable published versions of repo crates.

    line 7
  2. Very specific:

    Use path dependencies only to show unpublished functionality that cannot live in a crate's examples/ directory.

    line 8
  3. Distinctive:

    Never use path dependencies for convenience or to track unreleased versions.

    line 9
  4. Very specific:

    If a sample uses a local path crate, mirror its direct Azure SDK path + version dependencies for any public types that cross the boundary.

    line 10
  5. Very specific:

    Place each sample in samples/{service directory}/{sample}.

    line 14

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

Follow ../AGENTS.md.

Samples

  • Use the latest stable published versions of repo crates.
  • Use path dependencies only to show unpublished functionality that cannot live in a crate's examples/ directory.
  • Never use path dependencies for convenience or to track unreleased versions.
  • If a sample uses a local path crate, mirror its direct Azure SDK path + version dependencies for any public types that cross the boundary; do not mix published and local crate instances there.

Organization

  • Place each sample in samples/{service directory}/{sample}. The service directory must match an existing service directory under sdk/; for example, samples/cosmos contains samples for sdk/cosmos.
  • Choose the sdk/ service directory for the predominant Azure service crate used by the sample. If the predominant service is indeterminate, ask the user which service directory to use before creating or moving the sample.
  • For every samples/{service directory}, ensure .github/CODEOWNERS has a matching /sdk/{service directory}/ entry and a /samples/{service directory}/ entry with the same owners.
  • Apply spelling corrections to samples/{service directory} using the same pattern as the corresponding sdk/{service directory}.

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.

Reviews can't be read right now.

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