Value-based data structures (Data.struct, tuple, array) and high-performance collections (Chunk, HashSet). Use for safe comparisons and pipelines.
mepuka/effect-ontology
SkillsMP has collected 15 skills from mepuka/effect-ontology. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 15
- GitHub stars
- 5
- GitHub forks
- 0
Skills in this repository
Showing 15 of 15 collected skills.
Concurrency with Effect.all, forEach concurrency, Fiber lifecycle, race and timeouts. Use for parallelizing tasks safely.
Config loading and Schema validation/transform. Use when defining configuration or validating inputs.
Error modeling and recovery with TaggedError, catchTag(s), mapError, and retry schedules. Use when defining errors or adding resilience.
Core Effect foundations and style for a coding agent. Use when starting an Effect task, choosing operators, or structuring a small pipeline.
HTTP server, routing, JSON responses and dependencies via layers. Use when wiring endpoints and services.
Skill index and decision guide. Use to pick the right Effect Skill quickly and follow a minimal decision tree.
Define services, provide layers, compose dependencies, and switch live/test. Use for DI boundaries and app composition.
Complete catalog of 130+ Effect-TS patterns from EffectPatterns repository. Use when looking for specific implementation patterns, best practices, or real-world examples. Complements other skills with concrete, curated patterns.
Queue and PubSub patterns, background fibers, and graceful shutdown. Use for decoupling producers/consumers.
Resource safety with acquireRelease, Effect.scoped, and finalizers. Use when opening files, sockets, servers, or external handles.
Effect patterns for SQL databases (Drizzle/Kysely/Prisma): services, transactions, retries, streaming, and observability.
Stream creation, transformation, sinks, batching, and resilience. Use when building data pipelines with concurrency and backpressure.
Testing patterns with layers, mocks, and deterministic time. Use when preparing testable services and small smoke tests.
Time with Clock/Duration, tracing spans, and structured logging. Use for time-based logic, deadlines, and observability.