docs: team naming proposal — the Prisma App identity, Hexicon, Prisma Dev - #5
Merged
Conversation
…sma Dev) A shareable one-pager pitching the collective 'Prisma App' identity: name components for their role in context rather than as standalone brands (differentiate through synergy), rename MakerKit to Prisma Compose and Prisma Next to Prisma Data, build Hexicon as the Hex registry (hosting on npm), and Prisma Dev for local emulation via Alchemy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
Add a dedicated write-up (prisma-data-rename.md) justifying the rename: Prisma Next isn't the next ORM but a different product, so 'Prisma 8' would over-promise continuity and cap the ambition; 'Data' names the user value, reads for the agent-app-builder audience, and is a superset of 'ORM'. Prisma ORM persists (soft-deprecated); routing is temporal. Expand the proposal's rename bullet to summarize and link to it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
wmadden
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A shareable one-pager pitching the naming direction to the team.
The idea: stop presenting separately-branded products and orient around the one thing people build — a Prisma App — assembled from focused components named for their role in context. The business case is synergy: a piece like Postgres has no unique value alone; the family's value is the whole, and the names should carry that.
What it proposes:
Lives at
agent-os/product/naming-proposal.md. Companion to the reference doc (agent-os/product/naming.md) merged in #4 — this one is the friendly pitch, that one is the spec.🤖 Generated with Claude Code