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

9 rules. About 0 are common, 0 are distinctive, and 9 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.

• 9

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Add CUSTOM_ELEMENTS_SCHEMA to the standalone component metadata before using nve-* tags in app.html.

   line 8
2. Very specific:

   Keep theme and utility CSS imports in src/styles.css.

   line 9
3. Very specific:

   Keep nve-theme and nve-transition on src/index.html.

   line 10
4. Very specific:

   Use normal Angular template syntax with custom elements: [property] for JavaScript properties, [attr.name] for attributes, and (event) for …

   line 14
5. Very specific:

   Use Angular router primitives outside or inside Elements slots normally.

   line 16
6. Very specific:

   Use Elements form wrappers around native inputs so Angular forms keep owning value and validation state.

   line 20
7. Very specific:

   Put Angular conditional rendering for validation messages on nve-control-message or around it, depending on the control state.

   line 22
8. Very specific:

   Run pnpm run build in projects/starters/angular after schema, import, or template changes.

   line 26
9. Very specific:

   Run pnpm run lint when editing TypeScript, HTML templates, or CSS.

   line 27

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