fix: use slice id instead of name for generated TypeScript types

[tomaboro]

Summary

• Fixes a TypeScript error that occurs when a slice's id and name don't match (e.g. when a slice is created by the content modeling agent).
• The generated component was referencing Content.${pascalCase(name)}Slice, but prismic-ts-codegen generates type names based on the slice id, not the name link. This mismatch caused a TypeScript error because the referenced type didn't exist.
• The fix passes the slice id through to the template and uses it for the Content.*Slice type reference, while keeping name for the human-readable component name and comments.

Made with Cursor

---

Note

Low Risk
Low risk change limited to code generation templates; it only affects newly generated slice components and fixes mismatched TypeScript type references when slice name and id differ.

Overview
Fixes Next.js slice component generation to reference Prismic generated types using the slice id (e.g. Content.${pascalCase(id)}Slice) instead of the human-readable name.

sliceTemplate now accepts id and onSliceCreated passes model.id, preventing TS/JSDoc type errors when a slice’s id and name don’t match.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f08eb4e. Configure here.}

[angeloashmore]

Interesting, apparently this is also a bug in Slice Machine: https://github.com/prismicio/slice-machine/blob/875e77fb251a0e4d79a8b6d96e8df14303f36722/packages/adapter-next/src/hooks/slice-create.ts#L33. Thanks for finding it!