agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/xr-ai/CLAUDE.md

xr-ai

CLAUDE.md103 starsChanged 12 days agoApache-2.0View on GitHub

Follow the shared engineering guidance and routing in AGENTS.md, plus the nearest package or application README. For repository contributions, follow Contributing and conventions. Run relevant tests and Ruff before committing, and sign repository commits with git commit -s. After pushing an upstream PR, check gh pr checks; the change is not complete until required CI is green. Never launch models ad hoc (bare vllm serve, from_pretrained scripts). Start servers only through the repo entry points (sample orchestrators and the services/…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

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

    Follow the shared engineering guidance and routing in AGENTS.md, plus the nearest package or application README.

    line 8
  2. Very specific:

    Run relevant tests and Ruff before committing, and sign repository commits with git commit -s.

    line 12
  3. Very specific:

    Never launch models ad hoc (bare vllm serve, from_pretrained scripts).

    line 16
  4. Very specific:

    Start servers only through the repo entry points (sample orchestrators and the services/ wrappers): those are the paths that must be …

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Working instructions

Follow the shared engineering guidance and routing in AGENTS.md, plus the nearest package or application README. For repository contributions, follow Contributing and conventions. Run relevant tests and Ruff before committing, and sign repository commits with git commit -s. After pushing an upstream PR, check gh pr checks; the change is not complete until required CI is green.

Never launch models ad hoc (bare vllm serve, from_pretrained scripts). Start servers only through the repo entry points (sample orchestrators and the services/ wrappers): those are the paths that must be tested, and they default the HuggingFace cache to the repo models/ dir.

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