effect-claude-primitives

Plugin effect-claude-primitives from marketplace effect-primitives in stiproot/effect-claude-primitives. Commands read from the repo's manifest — 1 month ago.

Skills (17)

• effect-concurrency

  Effect-TS concurrency and parallelism patterns – fibers, Effect.fork/forEach/all with the concurrency option, racing and timeouts, shared state via Ref/SynchronizedRef/SubscriptionRef, and coordination primitives Deferred, Semaphore, Latch, Queue, and PubSub, plus Scope-based lifecycles and graceful

• effect-core-concepts

  Effect-TS foundational mental model and primitives – the three-channel Effect type, Effect.gen vs .pipe, map/flatMap/andThen/tap, Option and Either, the Data module (TaggedError, Data.struct/case/Class, structural Equal), Layers for dependency injection, lazy blueprints, and wrapping sync/async code

• effect-data-pipelines

  Effect-TS data-pipeline patterns – building end-to-end pipelines with Stream: sourcing from lists/files/paginated APIs, processing in constant memory, mapEffect with bounded concurrency, grouped batching, buffer/throttle/debounce backpressure, broadcast/partition/groupByKey fan-out, merge/concat/zip

• effect-domain-modeling

  Effect-TS domain-modeling patterns – Schema contracts (Schema.Struct, decode/decodeUnknown, validate, Schema.transform during parsing), Brand for validated domain types (Email, UserId, PositiveInt), Data.TaggedError for typed domain errors, Option for missing/optional values, and distinguishing "not

• effect-error-handling

  Effect-TS error-handling patterns – typed/tagged errors, catchTag/catchTags/catchAll, retry with Schedule, timeouts, Cause inspection, error mapping across domain boundaries, match/matchEffect on success and failure, and accumulating multiple errors. Use whenever working with failures in Effect code

• effect-getting-started

  First steps with Effect-TS – Hello World, Effect.succeed / Effect.fail, transforming with Effect.map, recovering with catchAll / catchTag, and actually running an effect with Effect.runSync / Effect.runPromise. Also covers bootstrapping a brand-new Effect project (deps, tsconfig, src/index.ts) and c

• effect-http-api

  Effect-TS server-side HTTP patterns with @effect/platform – building an HTTP server, defining routes and GET/POST handlers, extracting path params, returning JSON responses, validating request bodies with Schema, composing middleware, CORS, authentication, rate limiting, API error mapping, OpenAPI d

• effect-http-client

  Effect-TS HTTP client patterns for outgoing requests – making a first GET/POST with @effect/platform HttpClient, parsing JSON responses safely with Schema, timeouts, retry with Schedule backoff, response caching and stale-while-revalidate, handling 429 rate-limit responses, and modelling the client

• effect-mcp-server

  Effect-TS patterns for building MCP (Model Context Protocol) servers — tool registration with Effect Schema, the Effect.Service layer for business logic, createMcpApp bootstrap, session handling, resilience (timeout/retry/Config), and the anti-patterns to avoid. Use whenever building or extending an

• effect-observability

  Effect-TS observability patterns – structured logging with Effect.log/logInfo/logError and annotateLogs, custom metrics via Metric.counter/gauge/histogram/timer, exporting a /metrics endpoint for Prometheus, distributed tracing with Effect.withSpan, OpenTelemetry integration, instrumenting function

• effect-platform

  Effect-TS @effect/platform patterns for OS-level operations — executing shell commands with Command, filesystem operations with FileSystem (read/write/stat/ mkdir/readDirectory plus advanced atomic-write, streaming, recursive traversal, locking, copy), persistent KeyValueStore, interactive Terminal

• effect-resource-management

  Effect-TS resource-management patterns – acquireRelease bracketing, Scope and addFinalizer for manual lifecycles, composing scoped layers with Layer.merge, managed runtimes for scoped resources, building service layers from managed resources (Layer.scoped / Effect.Service scoped), hierarchical paren

• effect-scheduling

  Effect-TS scheduling and recurrence with Schedule – repeating an effect on a fixed interval, retrying failed operations, exponential backoff, cron-style periodic jobs, debounce/throttle, and advanced retry chains with circuit breakers. Use whenever you need an effect to recur or retry over time: pol

• effect-service-pattern

  Effect-TS service and dependency-injection patterns — defining services with Effect.Service and Context.Tag, wiring dependencies, composing and merging Layers, and structuring a service or agent module. Use whenever building or organising Effect code that exposes capabilities behind an interface: im

• effect-streams

  Effect-TS Stream and Sink patterns – building and running streams (runCollect/runForEach/runDrain/runFold), map/filter/scan/take/drop, merging and combining streams, controlling backpressure with buffer/throttle, grouping and windowing, resource management inside streams, stream error handling and r

• effect-testing

  Effect-TS testing patterns – running effects in tests with Effect.runPromise, asserting success/failure, providing mock services via Effect.provideService and test Layers, the auto-generated .Default layer, controlling time deterministically with TestClock/Clock, property-based testing with fast-che

• effect-tooling-debugging

  Effect-TS developer tooling and debugging — dev-environment setup, the Effect LSP, reading Effect type errors, Biome/ESLint linting config, GitHub Actions CI/CD, Effect DevTools (debug logging, fiber inspection, log spans, Cause inspection, custom loggers), performance profiling (withLogSpan, Metric

Similar plugins