effect-schema

Enforce parity between Effect schemas and TypeScript domain types with tsafe assertions.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/morgs32/skills --skill effect-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-schema
Source: https://github.com/morgs32/skills/tree/main/skills/effect-schema
Command: npx skills add https://github.com/morgs32/skills --skill effect-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps define and verify Effect schemas that align with TypeScript domain types, ensuring parity and type safety across schema definitions.

Core Features & Use Cases

  • Schema parity: Ensure that an Effect schema's Type matches the corresponding domain interface.
  • Type safety: Enforce tsafe-style assertions and parity checks to catch mismatches early.
  • Developer workflow: Helpful when authoring or updating Effect Schema definitions, or when users mention parity, satisfies, or tsafe Equals checks in documentation or code.

Quick Start

To begin, define your domain interface and create a matching Effect schema. Ensure the schema satisfies Schema.Schema<YourType, any> and includes parity assertions such as an Equals check to confirm Readonly<YourType> is the schema's Type.

Frequently Asked Questions about effect-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Effect schema parity with a TypeScript domain type?

To verify Effect schema parity, define your domain interface and create a matching schema, then apply tsafe-style Equals assertions to confirm Readonly<YourType> matches the schema's Type at compile time.

What is Effect schema parity and when do I need to enforce it?

Effect schema parity ensures an Effect schema's Type exactly matches your corresponding TypeScript domain interface. You need to enforce it when authoring or updating schemas to catch type mismatches early.

How do I use tsafe Equals checks to validate an Effect schema definition?

Use tsafe Equals checks by asserting that Readonly<YourType> is the schema's Type. This enforces compile-time validation, requiring the TypeScript type system and Effect Schema definitions to confirm type safety.

Does Effect schema type safety work with standard TypeScript satisfies checks?

Yes, Effect schema type safety works with TypeScript by using satisfies Schema.Schema<YourType, any> alongside tsafe-style parity assertions to enforce alignment and catch domain type mismatches early.

What's the best way to catch domain type misalignment in Effect schemas?

The best way to catch domain type misalignment is enforcing parity and type-safety checks using tsafe-style assertions. This validates that your Effect schema's Type matches the domain interface during authoring.

Why does my Effect schema not match my TypeScript domain type?

Your Effect schema may not match your TypeScript domain type due to missing parity assertions. Apply tsafe-style Equals checks to enforce type safety and identify structural mismatches at compile time.