effect-usecase-patterns

A set of rules for implementing use cases in T6C with Effect-TS. A use case is a piece of application logic that performs a user or business action, and these rules cover imports, errors, logging, and observability.

In plain words
What is it for?
Use it when writing or reviewing T6C use cases that call stores or other operations and need the required error-handling and logging pattern.
Why use it?
It makes business operations follow the same structure and ensures errors are logged consistently.

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-usecase-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 6,271 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.06271
Opus 5 $0.00000 $0.03136
Sonnet 5 $0.00000 $0.01254
Haiku 4.5 $0.00000 $0.00627

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

Security

Grade A, and why

effect-usecase-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-usecase-patterns.mdc · 792 lines

How it starts

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

Effect-TS Usecase 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 { SearchStore } from '../../stores/search/search.store.js'

// ✅ CORRECT - Package imports for external dependencies
import { BlogPost, BlogPostId } from '@t6c/blog-domain'
import { Effect as E } from 'effect'

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

MANDATORY Usecase Structure

Required Error Handling and Observability Pattern

EVERY usecase MUST follow this exact pattern:

export const myUsecase = (input: MyInput) =>
  E.gen(function* () {
    // Business logic implementation here...
    const result = yield* businessLogic(input)
    return result
  }).pipe(
    // 🔴 MANDATORY: Simple error logging - NO custom messages
    E.tapError(E.logError),
    // 🔴 MANDATORY: Use E.orDie for unexpected errors OR allow domain errors to bubble up
    E.orDie, // Use this for usecases that should only return success
    // 🔴 MANDATORY: Observability span with relevant attributes
    E.withSpan('my-usecase-name', { 
      attributes: { 
        // Only include primitive values, not entire objects
        userId: input.userId,
        page: input.page 
      } 
    }),
  )

Error Handling Strategy by Usecase Type

GET Usecases - Allow NotFoundError to Bubble Up
// ✅ CORRECT - Allow NotFoundError for client handling
export const getBlogByIdUsecase = (id: BlogPostId) =>
  E.gen(function* () {
    const blogStore = yield* BlogStore
    const userStore = yield* UserStore

    const blogPost = yield* blogStore.getById(id) // Can throw NotFoundError
    const author = yield* userStore.getAuthorById(blogPost.authorId)
    
    return BlogPostProfile.make({
      // ... transformation
    })
  }).pipe(
    E.tapError(E.logError), // ✅ Simple logging only
    // ❌ NO E.orDie - let NotFoundError bubble up
    E.withSpan('getBlogByIdUsecase', { 
      attributes: { blogPostId: id } 
    })
  )

Read the full file on GitHub · 792 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 · 792 lines · 6,271 tokens per session scan A e72e9b4f664a

Subscribe to this mod's changes

effect-usecase-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 6,271 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.