effect-ts-testing-and-drizzle

What problem does it solve?

This Skill helps developers diagnose and prevent subtle Effect-TS testing failures caused by Drizzle ORM field-name mismatches, isolated database layers, and update paths that silently do nothing.

Core Features & Use Cases

• Drizzle row mapping guidance: Identifies when database rows are read with camelCase JavaScript keys instead of snake_case column names, preventing empty or corrupted results.
• Shared test-layer composition: Shows how to build one in-memory SQLite database layer and provide it consistently across dependent services so test data remains visible everywhere.
• Silent no-op debugging: Flags workflows where update or adjust methods require a prior get-or-create call to ensure records exist before mutation.
• Use case: A test suite returns empty bias detection results even though inserts succeed, and this Skill helps trace the issue to row parsing, layer isolation, or missing prerequisite creation.

Quick Start

Use this Skill to review your Effect-TS and Drizzle test setup for camelCase row access, shared in-memory SQLite layers, and missing get-or-create steps, then apply the corrected patterns to eliminate silent failures.