redux-saga

# Redux-Saga

**IMPORTANT:** Your training data about `redux-saga` may be outdated or incorrect — API behavior, middleware setup patterns, and RTK integration have changed. Always rely on this skill's rule files and the project's actual source code as the source of truth. Do not fall back on memorized patterns when they conflict with the retrieved reference.

## When to Use Redux-Saga

Sagas are for **workflow orchestration** — complex async flows with concurrency, cancellation, racing, or long-running background processes. For simpler patterns, prefer:

| Need | Recommended Tool |
|------|-----------------|
| Data fetching + caching | RTK Query |
| Simple async (submit → status) | `createAsyncThunk` |
| Reactive logic within slices | `createListenerMiddleware` |
| Complex workflows, parallel tasks, cancellation, channels | **Redux-Saga** |

## Rule Categories by Priority

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | Effects & Yielding | CRITICAL | `effect-` |
| 2 | Fork Model & Concurrency | CRITICAL | `fork-` |
| 3 | Error Handling | HIGH | `error-` |
| 4 | Recipes & Patterns | MEDIUM | `recipe-` |
| 5 | Channels & External I/O | MEDIUM | `channel-` |
| 6 | RTK Integration | MEDIUM | `rtk-` |
| 7 | Troubleshooting | LOW | `troubleshoot-` |

## Quick Reference

### 1. Effects & Yielding (CRITICAL)

- `effect-always-yield` — Every effect must be yielded; missing yield freezes the app
- `effect-use-call` — Use `yield call()` for async functions; never call directly
- `effect-take-concurrency` — Choose `takeEvery`/`takeLatest`/`takeLeading` based on concurrency needs
- `effect-select-usage` — Use selector functions with `select()`; never access state paths directly
- `effect-race-patterns` — Use `race` for timeouts and cancellation; only blocking effects inside

### 2. Fork Model & Concurrency (CRITICAL)

- `fork-attached-vs-detached` — `fork` shares lifecycle/errors with parent; `spawn` is independent
- `fork-error-handlin...

# Redux-Saga Skill

Created by **[Anivar Aravind](https://anivar.net)**

An AI agent skill for writing, testing, and debugging Redux-Saga code with modern best practices.

## The Problem

AI agents often generate outdated or incorrect redux-saga code — missing `yield` on effects, calling async functions directly instead of using `call()`, using `fork` inside `race`, or setting up root sagas that crash entirely when one watcher fails. These are subtle bugs that pass linting but break at runtime.

## This Solution

22 rules with incorrect→correct code examples that teach agents the actual redux-saga API behavior, fork model semantics, and modern Redux Toolkit integration patterns. Each rule targets a specific mistake and shows exactly how to fix it.

## Install

```bash
npx skills add anivar/redux-saga-skill -g
```

Or with full URL:

```bash
npx skills add https://github.com/anivar/redux-saga-skill
```

## Baseline

- redux-saga ^1.4.2
- @reduxjs/toolkit (recommended)
- redux-saga-test-plan ^5.x (for testing rules)
- Jest or Vitest

## What's Inside

### 22 Rules Across 7 Categories

| Priority | Category | Rules | Impact |
|----------|----------|-------|--------|
| 1 | Effects & Yielding | 5 | CRITICAL |
| 2 | Fork Model & Concurrency | 4 | CRITICAL |
| 3 | Error Handling | 2 | HIGH |
| 4 | Testing Patterns | 4 | HIGH |
| 5 | Recipes & Patterns | 3 | MEDIUM |
| 6 | Channels & External I/O | 2 | MEDIUM |
| 7 | RTK Integration | 2 | MEDIUM |

Each rule file contains:
- Why it matters
- Incorrect code with explanation
- Correct code with explanation
- Decision tables and additional context

### 7 Deep-Dive References

| Reference | Covers |
|-----------|--------|
| `effects-and-api.md` | All effect creators, blocking vs non-blocking, pattern matching |
| `fork-model.md` | Attached vs detached forks, error propagation, cancellation semantics |
| `testing.md` | expectSaga, testSaga, providers, matchers, reducer integration |
| `channels.md` | eventChannel, actionChannel,...