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

10 rules. About 0 are common, 0 are distinctive, and 10 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈0

  Distinctive · estimate

  This author's own choices. Worth a look.

• 10

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

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

   line 7
2. Very specific:

   Keep global htmlAttrs for lang, nve-theme, and nve-transition in nuxt.config.ts.

   line 8
3. Very specific:

   Keep Elements Vue type references in env.d.ts.

   line 9
4. Very specific:

   Import global Elements CSS in app/app.vue.

   line 10
5. Very specific:

   Use NuxtLink inside Elements navigation components such as nve-tabs-item.

   line 15
6. Very specific:

   Keep route content in app/pages/* and shared shell in layouts.

   line 16
7. Very specific:

   Use Vue custom element syntax: :property for properties and @event for custom events.

   line 20
8. Very specific:

   Run nuxi typecheck through the package build before trusting template types.

   line 21
9. Very specific:

   Run pnpm run build in projects/starters/nuxt after config, layout, page, or type changes.

   line 25
10. Very specific:

    Run pnpm run lint after Vue, TypeScript, or config edits.

    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.