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

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈3

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep the import map in src/index.html aligned with the packages copied by build.js.

   line 7
2. Very specific:

   Import individual define.js files from the mapped @nvidia-elements/core/ prefix.

   line 9
3. Very specific:

   Update build.js whenever the import map references a new package that must exist in dist/node_modules.

   line 14
4. Distinctive:

   Keep the copy list explicit.

   line 16
5. Distinctive:

   Use this starter for no-build prototypes and browser-native module loading.

   line 20
6. Distinctive:

   Prefer a Vite starter when tree-shaking, TypeScript transforms, or production bundling matter.

   line 21
7. Very specific:

   Run pnpm run build in projects/starters/importmaps after import map or copy script changes.

   line 25
8. Very specific:

   Use pnpm run dev to catch browser import resolution errors.

   line 26

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