no-family-vocabulary-in-framework

no-family-vocabulary-in-framework is a cursor rule for Cursor from prisma/prisma-next. It costs 0 tokens per session (476 once invoked), scanned A, original, Apache-2.0.

A framework-design rule requiring shared framework code to use concepts that apply equally across all supported database families and targets.

In plain words
What is it for?
It guides where types, fields, hooks, and strategies belong, and is checked by a framework-vocabulary lint command.
Why use it?
It prevents SQL- or Mongo-specific terms and behavior from leaking into code that every family must use.

Cursor rule for Cursor ✓ vendor

Written for Cursor: a Cursor rule (.mdc). Also seen: installed under .agents/ (shared by several agents).

Good fit It guides where types, fields, hooks, and strategies belong, and is checked by a framework-vocabulary lint command.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/prisma/prisma-next/no-family-vocabulary-in-framework
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for no-family-vocabulary-in-framework

README.md
[![agentmods](https://agentmods.dev/badge/rules/prisma/prisma-next/no-family-vocabulary-in-framework/github.svg)](https://agentmods.dev/rules/prisma/prisma-next/no-family-vocabulary-in-framework)
Your own site
<a href="https://agentmods.dev/rules/prisma/prisma-next/no-family-vocabulary-in-framework"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/no-family-vocabulary-in-framework/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for no-family-vocabulary-in-framework

Your own site · 80×15
<a href="https://agentmods.dev/rules/prisma/prisma-next/no-family-vocabulary-in-framework"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/no-family-vocabulary-in-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00476
Opus 5 $0.00000 $0.00238
Sonnet 5 $0.00000 $0.00095
Haiku 4.5 $0.00000 $0.00048

Measured 11d ago against content hash dcf438be1c62, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

no-family-vocabulary-in-framework scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/rules/no-family-vocabulary-in-framework.mdc · 25 lines

What it actually says

No family vocabulary in the framework domain

packages/1-framework is consumed by every family (SQL, Mongo) and every target. A concept may enter it only if it is genuinely family-blind.

The test for every new framework export, field, hook, or member: would Mongo populate or consume this meaningfully? If not, it belongs in the family layer (e.g. @prisma-next/sql-contract), behind a structural interface + type predicate at the boundary.

Do

  • Keep framework mechanisms family-blind: registries, opaque payloads (object | undefined narrowed by the consuming family), merge/collision plumbing.
  • Put family vocabulary (nativeType, CHECK constraints, schema qualification, dialect names) in the owning family layer; targets implement family interfaces structurally.
  • Express strategies as codec-owned hooks/behavior on the strategy owner's descriptor — never as string-enum fields threaded through shared types (see storage-type-hooks.mdc).
  • Run pnpm lint:framework-vocabulary — a committed high-water-mark threshold over a forbidden-term list (scripts/lint-framework-vocabulary.config.json); the count may only shrink, and the recorded threshold must be lowered whenever it does.

Don't

  • Don't add a family term to a framework type because a sibling already has one — pre-existing surface is grandfathered debt (tracked, e.g. TML-2966), never precedent for new surface.
  • Don't dress family concepts as generic. The tells, each seen in practice: a never-typed parameter bridge to make a family callback assignable; a shape "declared here (not imported from the family) so the surface stays family-agnostic"; a 'strategy-a' | 'strategy-b' union naming family mechanisms; a doc comment that needs a family example to explain the member.
  • Don't argue by analogy to an existing framework member without checking the analogy's ground: renderValueLiteral is framework because Mongo renders value literals; a member only SQL renders is not.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 25 lines · 0 tokens per session scan A dcf438be1c62

Subscribe to this mod's changes

no-family-vocabulary-in-framework is a cursor rule published in the GitHub repository prisma/prisma-next (418 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 476 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.