effect-ts

Run Effect-TS detectors and output violations without spawning agents

Look up Effect-TS API documentation for a specific function, type, or module

Run Effect-TS compliance checks - diagnose root causes, then fix grouped violations

Review ALL TypeScript code and flag violations - all non-Effect patterns MUST be converted

Enforce idiomatic Effect code style - Schema-first, Match-first, no if/else, no switch/case, no ternaries

You are an Effect-TS violation analyzer. You receive a **single violation** and provide focused analysis with a copy-paste-ready fix recommendation.

You are an expert at migrating code to Effect-TS. Your role is to transform existing Promise-based, callback-based, or fp-ts code into idiomatic Effect code.

You are a strict Effect-TS code compliance reviewer. ALL TypeScript code MUST use Effect patterns. Non-Effect code is not acceptable - it is a violation that MUST be fixed.

Pairwise branch merger for tournament-style parallel merging. Merges branch_b INTO branch_a, resolves ALL conflicts by keeping fixes from BOTH sides, cleans up branch_b.

Execute a single task from the task list in an isolated git worktree. Spawn multiple of these in parallel for concurrent task execution.

This skill should be used when the user asks to "look up Effect API", "check the Effect docs", "find Effect function signature", "what does Effect.X do", "how to use Effect.X", "Effect API reference", "fetch Effect documentation", or needs to look up specific function signatures, parameters, or usage examples from the official Effect-TS API documentation.

This skill should be used when the user asks about "Effect batching", "request batching", "Effect caching", "Cache", "Request", "RequestResolver", "Effect.cached", "Effect.cachedWithTTL", "automatic batching", "N+1 problem", "data loader pattern", "deduplication", or needs to understand how Effect optimizes API calls through batching and caching.

This skill should be used EVERY TIME you're writing TypeScript with Effect, especially when the user asks about "Effect best practices", "Effect code style", "idiomatic Effect", "functional programming", "no loops", "no for loops", "avoid imperative", "Effect Array", "Effect Record", "Effect Struct", "Effect Tuple", "Effect Predicate", "Schema-first", "Match-first", "when to use Schema", "when to use Match", "branded types", "dual APIs", "Effect guidelines", "do notation", "Effect.gen", "pipe vs method chaining", "Effect naming conventions", "Effect project structure", "data modeling in Effect", or needs to understand idiomatic Effect-TS patterns and conventions.

This skill should be used when the user asks about "Effect concurrency", "fibers", "Fiber", "forking", "Effect.fork", "Effect.forkDaemon", "parallel execution", "Effect.all concurrency", "Deferred", "Queue", "PubSub", "Semaphore", "Latch", "fiber interruption", "Effect.race", "Effect.raceAll", "concurrent effects", or needs to understand how Effect handles parallel and concurrent execution.

This skill should be used when the user asks about "Effect Config", "environment variables", "configuration management", "Config.string", "Config.number", "ConfigProvider", "Config.nested", "Config.withDefault", "Config.redacted", "sensitive values", "config validation", "loading config from JSON", "config schema", or needs to understand how Effect handles application configuration.