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

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

• 17

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep the MCP stdio server entrypoint in src/index.ts.

   line 7
2. Very specific:

   Keep app resource URIs stable and use the same URI in the tool _meta.ui.resourceUri and resource registration.

   line 9
3. Very specific:

   Keep the app resource HTML in src/ui/*.html and browser-side resource logic in the matching src/ui/*.ts file.

   line 10
4. Very specific:

   Keep Elements component registration imports in the browser-side src/ui/*.ts file that renders the corresponding nve-* tags.

   line 11
5. Very specific:

   Keep global Elements theme and style imports inside the app resource HTML so the single-file Vite build embeds them.

   line 12
6. Very specific:

   Use zod schemas for tool input validation.

   line 16
7. Very specific:

   Keep stdio startup at module scope with StdioServerTransport.

   line 18
8. Very specific:

   Avoid DOM access in src/index.ts.

   line 19
9. Very specific:

   Use App from @modelcontextprotocol/ext-apps for host communication.

   line 24
10. Very specific:

    Treat tool results as untrusted data: narrow unknown values before rendering.

    line 26
11. Distinctive:

    Use direct DOM APIs for small starter interactions.

    line 27
12. Very specific:

    Prefer Elements components and nve-layout/nve-text attributes over starter-specific CSS.

    line 28
13. Very specific:

    Keep vite-plugin-singlefile enabled so the MCP resource is emitted as one portable HTML file.

    line 32
14. Very specific:

    Keep base: './' for archive-friendly output.

    line 33
15. Distinctive:

    Keep the Rollup input pointed at the app resource HTML, not the Node server entrypoint.

    line 34
16. Very specific:

    Keep tsconfig.server.json responsible for compiling the stdio server to dist/index.js.

    line 35
17. Very specific:

    Run pnpm run build in projects/starters/mcp-app after MCP server, app resource, TypeScript, or Vite changes.

    line 39
18. Very specific:

    Run pnpm run lint after TypeScript or config edits.

    line 40
19. Very specific:

    Run pnpm run ci before treating starter changes as complete.

    line 41

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