schema-validation

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

A set of project rules for using Effect Schema, a TypeScript library for describing and checking data shapes. It covers schemas, validation, imports, and branded types such as distinct user or blog-post IDs.

In plain words
What is it for?
Use it when creating or editing TypeScript type, schema, domain, or branded-ID files that match the rule’s file patterns.
Why use it?
It keeps data definitions and validation consistent across the project, reducing mismatches between expected and received values.

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 { BlogPostId } from '../../domain-common/branded.js'.

Good fit Use it when creating or editing TypeScript type, schema, domain, or branded-ID files that match the rule’s file patterns.

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/schema-validation

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 schema-validation

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/schema-validation"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/schema-validation.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 598 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00598
Opus 5.5 $0.00000 $0.00239
Sonnet 5.5 $0.00000 $0.00120
Haiku 4.5 $0.00000 $0.00060

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

Security

Grade A, and why

schema-validation 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.

rules/schema-validation.mdc · 90 lines

How it starts

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

Effect Schema Validation Patterns

Guidelines for using Effect's Schema system for data validation in the T6C project.

When This Rule Applies

This rule is automatically applied to files that match these patterns:

  • **/*.types.ts - Type definition files
  • **/schema/**/*.ts - Schema directory files
  • **/schemas/**/*.ts - Schemas directory files
  • **/*-schema.ts - Files ending with -schema.ts
  • **/*-schemas.ts - Files ending with -schemas.ts
  • **/branded.ts - Branded type definition files
  • **/domain/**/*.ts - Domain model files

Import Patterns

Standard Schema Import

  • Always use Schema as S for Effect Schema imports
  • Use relative paths for internal imports
// ✅ CORRECT - Standard import pattern
import { Schema as S } from 'effect'
import { Data, Effect as E } from 'effect'

// ✅ CORRECT - Relative imports for internal types
import { BlogPostId } from '../../domain-common/branded.js'

Branded Types

Basic Branded Types

  • Use S.pipe with S.brand to create type-branded primitives
  • Export both the schema and the type
export const UserId = S.String.pipe(S.brand('UserId'))
export type UserId = typeof UserId.Type

export const BlogPostId = S.String.pipe(S.brand('BlogPostId'))
export type BlogPostId = typeof BlogPostId.Type

Error Types

Tagged Errors with Data.TaggedError

  • Use Data.TaggedError for domain-specific error types
  • Include relevant identifiers and context in error data
export class NotFoundError extends Data.TaggedError('NotFoundError')<{
  resource: string
  id: string
}> {}

export class BlogPostLikeNotFoundError extends Data.TaggedError(
  'BlogPostLikeNotFoundError',
)<{
  blogPostId: BlogPostId
  userId: UserId
}> {}

Schema Testing

Use @effect/vitest for Schema Tests

  • Test schema validation with valid and invalid inputs
  • Use Effect-based test patterns
import { describe, expect, it } from '@effect/vitest'
import { Effect as E } from 'effect'

describe('BlogPost schema', () => {
  it.effect('should decode valid blog post', () =>
    E.gen(function* () {
      const input = { id: 'blog-1', title: 'Test Post' }
      const result = yield* S.decodeUnknown(BlogPost)(input)
      expect(result.id).toBe('blog-1')
    })
  )
})

Read the full file on GitHub · 90 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 · 90 lines · 598 tokens per session scan A 6c1f42d574df

Subscribe to this mod's changes

schema-validation 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 598 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.