agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/IsaacTeleop/src/core/schema/AGENTS.md

IsaacTeleop / schema

AGENTS.md438 starsChanged 31 days agoApache-2.0View on GitHub

CRITICAL (non-optional): Before editing this package, complete the mandatory AGENTS.md preflight in ../../../AGENTS.md (read every applicable AGENTS.md on your paths, not just this file). Every MCAP recording embeds the schema it was written under, and both the build and the replay path compare that against what these schemas compile to now. An edit here can make recordings already on disk unreadable, so treat fbs/ as a published contract rather than ordinary source. README.md has the evolution rules and what to…

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    CRITICAL (non-optional): Before editing this package, complete the mandatory

    line 8
  2. Distinctive:

    Every MCAP recording embeds the schema it was written under, and both the build and the replay path compare that against what these schemas …

    line 14
  3. Very specific:

    Append, with a fresh id, and leave it optional: Never renumber or reuse an id.

    line 22

≈ “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
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Agent notes — schema

CRITICAL (non-optional): Before editing this package, complete the mandatory AGENTS.md preflight in ../../../AGENTS.md (read every applicable AGENTS.md on your paths, not just this file).

Read README.md before changing anything under fbs/

Every MCAP recording embeds the schema it was written under, and both the build and the replay path compare that against what these schemas compile to now. An edit here can make recordings already on disk unreadable, so treat fbs/ as a published contract rather than ordinary source.

README.md has the evolution rules and what to do when the conform test fails. The short version:

  • Append, with a fresh id, and leave it optional. Never renumber or reuse an id; (required) breaks every message recorded before the field existed.
  • Deprecate, never delete. (deprecated) keeps the ids after it in their slots.
  • A root_type rename is a break, even though no byte moves — the recording carries the old name and the reader matches it exactly.
  • Never change a struct — not a field added, removed, reordered, or retyped. An appended struct field is the one break flatc --conform does not report, because every existing offset survives; check_schema_compat() catches it on the struct's size.
  • Never refresh golden/ to clear a failing test. The failure is the signal. Refresh only once breaking existing recordings is a decision you have made and stated.

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