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

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

• 9

  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/app.css.

   line 8
2. Very specific:

   Keep theme attributes on src/index.html.

   line 9
3. Very specific:

   Keep Vite root and output behavior in vite.config.ts aligned with the src directory layout.

   line 10
4. Very specific:

   Use Svelte custom event binding such as on:close.

   line 14
5. Very specific:

   Use bind:property only when the Elements property is mutable and the component actually emits a matching event.

   line 15
6. Very specific:

   Prefer explicit attributes for static Elements configuration.

   line 16
7. Very specific:

   Use svelte-check through the package check script for .svelte files.

   line 20
8. Distinctive:

   Keep DOM-only code in component lifecycle or module contexts that Svelte can compile for the current target.

   line 21
9. Very specific:

   Run pnpm run build and pnpm run check in projects/starters/svelte after .svelte, TypeScript, or config changes.

   line 25
10. Very specific:

    Run pnpm run lint after source 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.