What problem does it solve? Codebases drift into inconsistent patterns: redundant type annotations, hand-rolled wrappers over library primitives, leaked error types, and tests that assert nothing. This Skill gives an AI a concrete rulebook of good and bad TypeScript/Effect patterns so generated and reviewed code follows one consistent engineering standard. ## Core Features & Use Cases - Type and Schema Rules: Enforces inferred types, satisfies over assertions, Schema.Struct over Schema.Class, and schema-owned validation via .make. - Effect Patterns: Standardizes Effect.fn for functions with arguments, standalone pipe, Context.Service with static layers, Schema.TaggedError with preserved causes, and Effect.acquireRelease for resource lifetimes. - Code Quality Gates: Bans native globals (Date, Math.random, process.env) in favor of Effect services, forbids wrapper functions and legacy compatibility code, and defines what meaningful tests look like. - Use Case: When implementing a new service in an Effect-based monorepo, apply this Skill so the generated code uses the correct service shape, error handling, and module layout on the first pass. ## Quick Start Use the engineering skill to review this TypeScript service implementation and rewrite any code that violates the Effect and Schema rules.
