agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/deploy/stacks/stargate-dev/AGENTS.md

nvcf / stargate-dev

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

This stack owns the mock deployment charts, environments, load profiles, and deployment scripts. Keep changes within the existing Helmfile and Python patterns. Image builds and local/AWS setup are documented in README.md. Run from the repository root: For the benchmark controller, also follow benchmark/AGENTS.md. Meaningful stack changes must satisfy the Stargate mock integration and performance gates. Rendering and fake-runner checks validate wiring; retain a runtime mock receipt for the changed deployment behavior. Scheduling, resources, engine settings, and load profiles also require…

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the repository root:

    line 9
  2. Distinctive:

    Follow the root local QA safety rules before provisioning or modifying test environments.

    line 27
  3. Common:

    Use plain ASCII in committed prose.

    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

Stargate development stack

This stack owns the mock deployment charts, environments, load profiles, and deployment scripts. Keep changes within the existing Helmfile and Python patterns. Image builds and local/AWS setup are documented in README.md.

Build and test

Run from the repository root:

python3 -m unittest discover -s deploy/stacks/stargate-dev/tests
make -C deploy/helm/llm-request-router test
git diff --check

For the benchmark controller, also follow benchmark/AGENTS.md.

Pull Request gates

Meaningful stack changes must satisfy the Stargate mock integration and performance gates. Rendering and fake-runner checks validate wiring; retain a runtime mock receipt for the changed deployment behavior. Scheduling, resources, engine settings, and load profiles also require baseline/candidate performance evidence.

Follow the root local QA safety rules before provisioning or modifying test environments. Campaigns that share backends must run exclusively because they can reset caches and restart Pods.

Use plain ASCII in committed prose. Keep credentials and private environment details out of public files and Pull Request evidence.

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