What problem does it solve? Redux-saga has a large API surface—middleware setup, blocking versus non-blocking effects, watcher helpers, channels, buffers, and cancellation semantics—and misusing any of them causes subtle concurrency bugs. This Skill gives an AI agent the correct API behavior and repository-specific conventions before it writes or edits saga code. ## Core Features & Use Cases - API Reference Coverage: Documents middleware startup, take/put/call/fork/select effects, watcher helpers, channels, buffers, race/all combinators, runSaga, and testing utilities with TypeScript examples. - Repository Compliance Rules: Enforces themis conventions such as attached fork over detached spawn, takeLatest/takeLeading plus delay for debounce, and watcher ownership verification. - Use Case: When asked to add a saga that debounces search input, the agent writes a takeLatest watcher with an explicit delay in the worker instead of introducing a wrapper debounce utility, and avoids detached spawn so cancellation propagates correctly. ## Quick Start Ask the agent to write a redux-saga watcher that loads a user on USER_REQUESTED and cancels stale searches, following this skill's effect and cancellation conventions.