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

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep dynamic values in the Go PageData shape and pass them into the template.

   line 8
2. Distinctive:

   Use static bundles or a separate frontend build pipeline.

   line 9
3. Distinctive:

   Use pre-built browser-loadable bundles when keeping the starter free of frontend build tooling.

   line 13
4. Very specific:

   If serving local bundles instead, add explicit static file handling in main.go and point CSS and module imports at that route.

   line 14
5. Distinctive:

   Keep theme attributes on the root HTML template, not in Go handler code.

   line 15
6. Distinctive:

   Use escaped template output for data values.

   line 19
7. Very specific:

   Only use trusted template HTML for checked Elements markup.

   line 20
8. Distinctive:

   Keep routing and rendering small.

   line 21
9. Very specific:

   Run pnpm run build in projects/starters/go after Go or template changes.

   line 25
10. Very specific:

    Run pnpm run dev for local rendering checks on http://localhost:8080.

    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.