When the Repository Is Just Indirection

interface UserRepository {
  findById(id: string): Promise<User | null>
  findByEmail(e: string): Promise<User | null>
  findAll(): Promise<User[]>
  create(data: Prisma.UserCreateInput): Promise<User>
  update(id: string, data: Prisma.UserUpdateInput): Promise<User>
  delete(id: string): Promise<void>
}

class PrismaUserRepository implements UserRepository {
  findById(id: string) { return this.p.user.findUnique({ where: { id } }) }
  findByEmail(e: string) { return this.p.user.findUnique({ where: { email: e } }) }
  findAll() { return this.p.user.findMany() }          // no limit. ever.
  create(data: Prisma.UserCreateInput) { return this.p.user.create({ data }) }
  // ...30 more like these, across 6 tables
}

// trivial lookups: call the ORM from the service, directly
const user = await db.user.findUnique({ where: { id } })

// the repository holds only the queries that carry domain meaning
interface UserQueries {
  /** active = verified, not suspended, seat not revoked */
  findBillableSeats(tx: Tx, orgId: OrgId): Promise<Seat[]>
  /** case-insensitive, honours the citext index; used by signup AND invite */
  findByEmailForSignup(tx: Tx, email: Email): Promise<User | null>
  /** batched: one query for N orgs, so callers cannot N+1 */
  countMembersByOrg(tx: Tx, orgIds: OrgId[]): Promise<Map<OrgId, number>>
}