effect-handler-patterns

Rules for implementing Effect-TS Lambda handlers, which are functions run by AWS in response to events. They specify import paths, file placement, and how handlers should be organised with their use cases.

In plain words
What is it for?
Use them when adding or reviewing Lambda handlers, their use cases, tests, stores, and internal or external imports.
Why use it?
They prevent inconsistent project structure and imports that make handlers harder to find, test, and maintain.

Cursor rule

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/charlee-x/effect-cursor-rules/effect-handler-patterns
Clone the repo
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,007 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.02007
Opus 5 $0.00000 $0.01004
Sonnet 5 $0.00000 $0.00401
Haiku 4.5 $0.00000 $0.00201

Measured yesterday against content hash c1165d1e0eba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

effect-handler-patterns 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 yesterday.

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.

rules/effect-handler-patterns.mdc · 309 lines

How it starts

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

Effect-TS Lambda Handler Implementation Patterns and Best Practices

Import Patterns

Always Use Relative Paths for Internal Imports

  • CRITICAL: Never use src/ aliases for internal imports
  • Always use relative paths like ../../stores/blog/blog.store.js
  • Use package imports only for external dependencies
  • Store files follow pattern: store-name.store.ts
// ✅ CORRECT - Relative paths for internal imports
import { BlogStore } from '../../stores/blog/blog.store.js'
import { getBlogByIdUsecase } from './usecase.js'

// ✅ CORRECT - Package imports for external dependencies
import { BlogPostId } from '@t6c/domain-common'
import { okResponse, toHandler } from '@t6c/lib-api'
import { Effect as E } from 'effect'

// ❌ WRONG - Never use src/ aliases
import { BlogStore } from 'src/stores/blog/blog.store.js'

Usecase Co-location Pattern

Usecases Must Be Co-located with Handlers

  • MANDATORY: Place usecases in the same directory as their handlers
  • MANDATORY: Place usecase tests in the same directory as the usecase
  • This ensures clear ownership and easier maintenance
src/lambdas/
├── get-blog-by-id/
│   ├── handler.ts
│   ├── handler.test.ts
│   ├── get-blog-by-id.usecase.ts
│   └── get-blog-by-id.usecase.test.ts
└── create-blog-post/
    ├── handler.ts
    ├── handler.test.ts
    ├── create-blog-post.usecase.ts
    └── create-blog-post.usecase.test.ts

Usecase Import Pattern

// ✅ CORRECT - Co-located usecase import
import { getBlogByIdUsecase } from './get-blog-by-id.usecase.js'

// ❌ WRONG - Separate usecases directory
import { getBlogByIdUsecase } from '../../usecases/get-blog-by-id.usecase.js'

Handler Structure Pattern

Standard REST API Handler

/**
 * JSDoc description of the endpoint
 * HTTP_METHOD /api/path
 */
export const _handler = schemaInputMethod(InputSchema).pipe(
  E.flatMap(usecaseFunction),
  E.flatMap(responseFunction),
  E.tapError(E.logError),
  E.catchTags({
    ParseError: (error) => badRequestResponse(error.message),
    NotFoundError: () => notFoundResponse(),
    ConflictError: (error) => conflictResponse(error.message),
  }),
  E.orDie,
  E.withSpan('handler-name'),
)

export const handler = _handler.pipe(
  E.provide(RequiredStore.Default),
  E.withSpan('handler-name-full'),
  toHandler,
)

Read the full file on GitHub · 309 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. yesterday First seen · 309 lines · 2,007 tokens per session scan A c1165d1e0eba

Subscribe to this mod's changes

effect-handler-patterns is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,007 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-31.