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

9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  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 global Elements CSS in src/_layouts/index.css.

   line 7
2. Very specific:

   Keep shared page shell markup in src/_layouts/index.11ty.js.

   line 9
3. Very specific:

   Use @11ty/eleventy-plugin-vite for bundling the layout entrypoint.

   line 10
4. Very specific:

   Add nve-text and nve-layout attributes through the markdown-it renderer in eleventy.config.js when markdown should receive Elements …

   line 14
5. Distinctive:

   Keep renderer mappings constrained to token types that markdown-it exposes predictably: headings, paragraphs, links, and lists.

   line 15
6. Very specific:

   Keep the <base> URL and Vite base aligned with PAGES_BASE_URL.

   line 20
7. Distinctive:

   Use relative links in generated tab markup so static output works under the starter base path.

   line 21
8. Very specific:

   Run pnpm run build in projects/starters/eleventy after layout, renderer, or asset pipeline changes.

   line 25
9. Very specific:

   Run pnpm run lint when editing Eleventy config or layout TypeScript.

   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.