mapping-errors-to-fit-your-domain

mapping-errors-to-fit-your-domain is a cursor rule for Cursor from PaulJPhilp/EffectPatterns. It costs 635 tokens per session, scanned A, original, MIT.

A TypeScript coding rule for translating low-level errors into errors that match the application's domain. For example, several database errors can be exposed as one repository error.

In plain words
What is it for?
Use it at boundaries between services, such as turning database connection and query failures into a repository-level error.
Why use it?
It keeps internal implementation details from leaking across application layers.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it at boundaries between services, such as turning database connection and query failures into a repository-level error.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain
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/PaulJPhilp/EffectPatterns

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 mapping-errors-to-fit-your-domain

README.md
[![agentmods](https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain/github.svg)](https://agentmods.dev/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain)
Your own site
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain/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 mapping-errors-to-fit-your-domain

Your own site · 80×15
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/mapping-errors-to-fit-your-domain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 635 This file is loaded in full into every session.
When invoked 635 The same file — it is already loaded in full.
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.00635 $0.00635
Opus 5.5 $0.00254 $0.00254
Sonnet 5.5 $0.00127 $0.00127
Haiku 4.5 $0.00064 $0.00064

Measured 1mo ago against content hash 0a8841fe230f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mapping-errors-to-fit-your-domain 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 1mo 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.

content/published/rules/cursor/mapping-errors-to-fit-your-domain.mdc · 75 lines

How it starts

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

description: Use Effect.mapError to transform errors and create clean architectural boundaries between layers. globs: "**/*.ts" alwaysApply: true

Mapping Errors to Fit Your Domain

Rule: Use Effect.mapError to transform errors and create clean architectural boundaries between layers.

Example

A UserRepository uses a Database service. The Database can fail with specific errors, but the UserRepository maps them to a single, generic RepositoryError before they are exposed to the rest of the application.

import { Effect, Data } from "effect";

// Low-level, specific errors from the database layer
class ConnectionError extends Data.TaggedError("ConnectionError") {}
class QueryError extends Data.TaggedError("QueryError") {}

// A generic error for the repository layer
class RepositoryError extends Data.TaggedError("RepositoryError")<{
  readonly cause: unknown;
}> {}

// The inner service
const dbQuery = (): Effect.Effect<
  { name: string },
  ConnectionError | QueryError
> => Effect.fail(new ConnectionError());

// The outer service uses `mapError` to create a clean boundary.
// Its public signature only exposes `RepositoryError`.
const findUser = (): Effect.Effect<{ name: string }, RepositoryError> =>
  dbQuery().pipe(
    Effect.mapError((error) => new RepositoryError({ cause: error }))
  );

// Demonstrate the error mapping
const program = Effect.gen(function* () {
  yield* Effect.logInfo("Attempting to find user...");

  try {
    const user = yield* findUser();
    yield* Effect.logInfo(`Found user: ${user.name}`);
  } catch (error) {
    yield* Effect.logInfo("This won't be reached due to Effect error handling");
  }
}).pipe(
  Effect.catchAll((error) =>
    Effect.gen(function* () {
      if (error instanceof RepositoryError) {
        yield* Effect.logInfo(`Repository error occurred: ${error._tag}`);
        if (
          error.cause instanceof ConnectionError ||
          error.cause instanceof QueryError
        ) {
          yield* Effect.logInfo(`Original cause: ${error.cause._tag}`);
        }
      } else {
        yield* Effect.logInfo(`Unexpected error: ${error}`);
      }
    })
  )
);

Effect.runPromise(program);

Read the full file on GitHub · 75 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. 1mo ago First seen · 75 lines · 635 tokens per session scan A 0a8841fe230f

Subscribe to this mod's changes

mapping-errors-to-fit-your-domain is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (807 stars, last pushed 4mo ago), licensed MIT. It adds 635 tokens to every session, about $0.0025 per session on Opus 5.5. 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-09-03.