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

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

• 7

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep shared Elements CSS in src/common/index.css.

   line 7
2. Very specific:

   Keep shared Elements registrations in src/common/index.ts.

   line 8
3. Very specific:

   Import ./common/index.js from each page entrypoint before page-specific code.

   line 9
4. Very specific:

   Add new HTML pages to vite.config.ts build.rolldownOptions.input.

   line 10
5. Distinctive:

   Keep selected navigation state local to each page's static HTML.

   line 15
6. Distinctive:

   Use root-relative dev paths in source HTML when Vite owns serving.

   line 16
7. Very specific:

   Keep nve-transition on the root HTML for global transitions.

   line 20
8. Distinctive:

   Add component-level transition attributes only to pages that need them.

   line 21
9. Very specific:

   Run pnpm run build in projects/starters/mpa after adding pages or changing shared entries.

   line 25
10. Very specific:

    Run pnpm run lint after TypeScript or config changes.

    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.