Fill gaps from assistant conversations: snippet identifier rules

[mintlify]

Summary

Clarify the naming rules for the identifier used when importing a reusable snippet, addressing recurring assistant questions about which identifiers are valid.

Changes

• Add a note to create/reusable-snippets.mdx explaining that the import name must be a valid JSX component identifier (PascalCase, uppercase first letter) and that lowercase names are treated as HTML elements.

Context

Assistant conversations this week showed users asking what identifiers work when inserting a snippet. The existing page shows PascalCase in examples but does not state the requirement explicitly.

---

Note

Low Risk
Documentation-only edits to MDX guides; no runtime, auth, or data paths affected.

Overview
Documents a gap in the reusable snippets guide: snippet tags must use an uppercase-first identifier (e.g. MySnippet) so MDX treats them as components, not lowercase HTML/custom elements like <mySnippet />.

The new note sits under Import snippets into pages in create/reusable-snippets.mdx, with matching copy in es, fr, and zh (locales also mention PascalCase as convention where the English page does not). es, fr, and zh also get a trailing newline fix on the React import example code fence.

^{Reviewed by Cursor Bugbot for commit df4b49b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify	🟢 Ready	View Preview	Jul 24, 2026, 4:15 PM

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
tomee	🟢 Ready	View Preview	Jul 24, 2026, 4:15 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.