agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/elements/projects/starters/bundles/AGENTS.md

elements / bundles

AGENTS.md115 starsChanged 54 days agoApache-2.0View on GitHub

This file only covers how this starter wires Elements into a static bundle page. For component APIs, template validation, and project setup commands, use the Elements CLI/MCP documentation instead.

The file

We split this AGENTS.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
  1. Very specific:

    Keep bundle paths rooted through the Vite alias for ./node_modules from vite.config.ts.

    line 9
  2. Distinctive:

    Use this starter only when loading all registered components is acceptable.

    line 10
  3. Very specific:

    Run pnpm run build in projects/starters/bundles after changing bundle paths or static HTML.

    line 24
  4. Very specific:

    Run pnpm run dev only when visual browser verification is needed.

    line 25

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

Elements Bundles Starter

This file only covers how this starter wires Elements into a static bundle page. For component APIs, template validation, and project setup commands, use the Elements CLI/MCP documentation instead.

Integration Points

  • Load pre-built CSS bundles from @nvidia-elements/styles, @nvidia-elements/themes, and any optional package bundle in src/index.html.
  • Load pre-built JavaScript bundles with module scripts in src/index.html.
  • Keep bundle paths rooted through the Vite alias for ./node_modules from vite.config.ts.
  • Use this starter only when loading all registered components is acceptable; it trades tree-shaking for drop-in integration.

Optional Package Bundles

  • Include an optional package bundle only when the page uses that package. The current starter includes Monaco because it renders nve-monaco-input.
  • Pair optional package JavaScript and CSS bundles when the package ships both.

DOM Events

  • Attach listeners with script code, not inline event handler attributes.
  • Query typed Elements only after the bundle import has run.

Verification

  • Run pnpm run build in projects/starters/bundles after changing bundle paths or static HTML.
  • Run pnpm run dev only when visual browser verification is needed.

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