effect-testing-patterns

effect-testing-patterns is a cursor rule for Cursor from CharLEE-X/effect-cursor-rules. It costs 0 tokens per session (5,746 once invoked), scanned A, original, MIT.

A set of testing rules for Effect-TS, a TypeScript library for building programs from composable effects such as asynchronous or failure-prone operations. It covers test setup, imports, and patterns for testing AI services.

In plain words
What is it for?
Use it when writing or reviewing tests for Effect-TS code, especially tests using the @effect/vitest test library, internal stores, external packages, or AI services.
Why use it?
It helps keep Effect-based tests consistent and avoids import paths that can fail or behave differently across project environments.

Cursor rule for Cursor

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { BlogStore } from '../../stores/blog/blog.store.js'.

Good fit Use it when writing or reviewing tests for Effect-TS code, especially tests using the @effect/vitest test library, internal stores, external packages, or AI services.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rules
agentmods
npx agentmods add rules/charlee-x/effect-cursor-rules/effect-testing-patterns

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 effect-testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/effect-testing-patterns/github.svg)](https://agentmods.dev/rules/charlee-x/effect-cursor-rules/effect-testing-patterns)
Your own site
<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/effect-testing-patterns"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/effect-testing-patterns/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 effect-testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/effect-testing-patterns"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/effect-testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 5,746 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00000 $0.05746
Opus 5.5 $0.00000 $0.02298
Sonnet 5.5 $0.00000 $0.01149
Haiku 4.5 $0.00000 $0.00575

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

Security

Grade A, and why

effect-testing-patterns scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

try: () => fetch(url).then(res => res.json()),
rules/effect-testing-patterns.mdc · 836 lines

How it starts

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

Effect-TS Testing Patterns and Best Practices

Test Framework Setup

Use @effect/vitest for Effect-TS Tests

  • Always use @effect/vitest for tests involving Effect-based code
  • Import test functions from @effect/vitest, not regular vitest
  • Use describe, expect, and it from @effect/vitest
import { describe, expect, it } from '@effect/vitest'
import { Effect as E, Exit } from 'effect'

Import Patterns - ALWAYS Use Relative Paths

  • CRITICAL: Always use relative paths for internal imports, never src/ aliases
  • Use relative paths like ../../stores/blog/blog.store.js
  • Use package imports for external dependencies like @t6c/blog-domain
  • 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, mockBlogPost1 } from '@t6c/blog-domain'
import { Effect as E } from 'effect'

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

AI Service Testing Patterns

AiStore.generateObject Mocking

  • Use AiStore.makeTestService to mock AI operations
  • Create proper AiResponse.WithStructuredOutput responses
  • Use generic type parameter <A>() for flexible type handling
  • Include realistic mock data that matches your schema
import { AiResponse, AiStore } from '@t6c/lib-ai'

// ✅ CORRECT - Complete AI service mocking pattern
const testAiStore = AiStore.makeTestService({
  generateObject: <A>() =>
    E.succeed(
      new AiResponse.WithStructuredOutput({
        id: AiResponse.ToolCallId.make('1'),
        name: '1',
        parts: mockResponse.parts,
        value: CommentProcessingOutput.make({
          htmlContent: 'test',
          status: 'active',
          toxicityScore: 0,
          sentiment: 'positive',
          moderationReason: 'test',
          categories: [],
        }) as A,
      }),
    ),
})

// ❌ WRONG - Incomplete or incorrect AI mocking
const testAiStore = AiStore.makeTestService({
  generateObject: () => E.succeed({ htmlContent: 'test' }), // Missing proper structure
})

Read the full file on GitHub · 836 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 · 836 lines · 5,746 tokens per session scan A 6bf53625f148

Subscribe to this mod's changes

effect-testing-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 5,746 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.