no-target-branches

A design rule for shared code that supports multiple targets, such as database systems, requiring target-specific behavior to live in adapters.

In plain words
What is it for?
Use it when adding target-dependent logic: define a common adapter interface and put each target's implementation in its own adapter or package.
Why use it?
Branches and constants for one target make supposedly reusable code harder to extend and maintain.

Cursor rule for Codex

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.

agentmods
npx agentmods add rules/prisma/orm/no-target-branches
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01088
Opus 5 $0.00000 $0.00544
Sonnet 5 $0.00000 $0.00218
Haiku 4.5 $0.00000 $0.00109

Measured 2d ago against content hash 570091e14bf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

no-target-branches 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/rules/no-target-branches.mdc · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

No Target-Specific Branches

CRITICAL: Never name a target in target-agnostic code. This covers two forms of the same mistake: branching on a target value, and embedding target-named constants, helpers, or data in framework/core packages. Target-specific logic and target-specific facts belong in adapters and target packages.

❌ WRONG: Branch on target in core packages

function canonicalizeColumnType(scalar: string, target: string): string {
  if (target === 'postgres') {
    const scalarMap: Record<string, string> = {
      int4: 'pg/int4@1',
      text: 'pg/text@1',
    };
    return scalarMap[scalar] ?? scalar;
  }
  return scalar;
}

✅ CORRECT: Put target-specific logic behind an adapter interface

interface Adapter {
  canonicalizeType(scalar: string): string;
}

class PostgresAdapter implements Adapter {
  canonicalizeType(scalar: string): string {
    const scalarMap: Record<string, string> = {
      int4: 'pg/int4@1',
      text: 'pg/text@1',
    };
    return scalarMap[scalar] ?? scalar;
  }
}

Named-target constants and data are the same violation

The branch is the obvious form. The subtler form is a target-agnostic package that names a target in a constant, a helper name, or static data — even with no if in sight. A POSTGRES_DEFAULT_NAMESPACE_ID constant or a defaultNamespaceIdForSqlTarget() helper sitting in the framework core is just a branch that has been pre-evaluated: the framework now knows a Postgres-specific fact.

❌ WRONG: Target-named constant / helper in a target-agnostic package

// in packages/1-framework/** (target-agnostic)
export const POSTGRES_DEFAULT_NAMESPACE_ID = 'public';

export function defaultNamespaceIdForSqlTarget(targetId: string): string {
  return targetId === 'postgres' ? 'public' : '__unbound__';
}

✅ CORRECT: The target declares the fact on its descriptor; the framework reads it generically

// in the target package's descriptor (static data the target owns)
const postgresDescriptorMeta = {
  // …
  defaultNamespaceId: 'public',
};

// in the target-agnostic consumer — reads the fact, never names the target
const defaultNamespaceId = target.defaultNamespaceId;

Read the full file on GitHub · 107 lines

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. 2d ago First seen · 107 lines · 0 tokens per session scan A 570091e14bf9

Subscribe to this mod's changes

no-target-branches is a cursor rule published in the GitHub repository prisma/orm (47,587 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,088 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.