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

12 rules. About 0 are common, 1 is distinctive, and 11 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.

• 11

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep template.compilerOptions.isCustomElement in vite.config.ts so Vue treats nve-* tags as custom elements.

   line 7
2. Very specific:

   Keep custom-elements-vue.d.ts referenced from env.d.ts.

   line 8
3. Very specific:

   Keep env.d.ts included by tsconfig.app.json.

   line 9
4. Very specific:

   Keep global Elements CSS in src/main.css.

   line 11
5. Very specific:

   Use :property for custom element properties.

   line 15
6. Very specific:

   Use @event for custom Events.

   line 16
7. Distinctive:

   Use plain attributes for static string values.

   line 17
8. Very specific:

   Keep router links or app-specific components inside Elements slots normally.

   line 18
9. Very specific:

   Use vue-tsc through the package build so invalid Elements attributes fail CI.

   line 22
10. Very specific:

    If a new nve-* tag has no template type, verify the referenced generated type file includes it before adding local declarations.

    line 23
11. Very specific:

    Run pnpm run build in projects/starters/vue after Vue, type, or config changes.

    line 27
12. Very specific:

    Run pnpm run lint after source edits.

    line 28

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