agentleFS
anivaranivar/redux-saga-skill/SKILL.md

redux-saga

Skill2 starsChanged 3 months agoMITView on GitHub

Redux-Saga best practices, patterns, and API guidance for building, testing, and debugging generator-based side-effect middleware in Redux applications. Covers effect creators, fork model, channels, testing with redux-saga-test-plan, concurrency, cancellation, and modern Redux Toolkit integration. Baseline: redux-saga 1.5.1. Triggers on: saga files, redux-saga imports, generator-based middleware, mentions of "saga", "takeEvery", "takeLatest", "fork model", or "channels".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. intent-hq/cloudlands-fe★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Only take/takeMaybe may omit the argument entirely — take() matches all actions.

    line 133
  2. Distinctive:

    Read individual rule files for detailed explanations and code examples:

    line 141

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

NeedRecommended Tool
Data fetching + cachingRTK Query
Simple async (submit → status)createAsyncThunk
Reactive logic within slicescreateListenerMiddleware
Complex workflows, parallel tasks, cancellation, channelsRedux-Saga

Rule Categories by Priority

PriorityCategoryImpactPrefix
1Effects & YieldingCRITICALeffect-
2Fork Model & ConcurrencyCRITICALfork-
3Error HandlingHIGHerror-
4Recipes & PatternsMEDIUMrecipe-
5Channels & External I/OMEDIUMchannel-
6RTK IntegrationMEDIUMrtk-
7TroubleshootingLOWtroubleshoot-

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-handling — Errors from forks bubble to parent's caller; can't catch at fork site
  • fork-no-race — Never use fork inside race; fork is non-blocking and always wins
  • fork-nonblocking-login — Use fork+take+cancel for auth flows that stay responsive to logout

3. Error Handling (HIGH)

  • error-saga-cleanup — Use try/finally with cancelled() for proper cancellation cleanup
  • error-root-saga — Use spawn in root saga for error isolation; avoid all for critical watchers

4. Recipes & Patterns (MEDIUM)

  • recipe-throttle-debounce — Rate-limiting with throttle, debounce, retry, exponential backoff
  • recipe-polling — Cancellable polling with error backoff using fork+take+cancel
  • recipe-optimistic-update — Optimistic UI with undo using race(undo, delay)

5. Channels & External I/O (MEDIUM)

  • channel-event-channel — Bridge WebSockets, DOM events, timers into sagas via eventChannel
  • channel-action-channel — Buffer Redux actions for sequential or worker-pool processing

6. RTK Integration (MEDIUM)

  • rtk-configure-store — Integrate saga middleware with RTK's configureStore without breaking defaults
  • rtk-with-slices — Use action creators from createSlice for type-safe saga triggers

7. Troubleshooting (LOW)

  • troubleshoot-frozen-app — Frozen apps, missed actions, bad stack traces, TypeScript yield types

Effect Creators Quick Reference

EffectBlockingPurpose
take(pattern)YesWait for matching action
takeMaybe(pattern)YesLike take, receives END
takeEvery(pattern, saga)NoConcurrent on every match
takeLatest(pattern, saga)NoCancel previous, run latest
takeLeading(pattern, saga)NoIgnore until current completes
put(action)NoDispatch action
putResolve(action)YesDispatch, wait for promise
call(fn, ...args)YesCall, wait for result
apply(ctx, fn, [args])YesCall with context
cps(fn, ...args)YesNode-style callback
fork(fn, ...args)NoAttached fork
spawn(fn, ...args)NoDetached fork
join(task)YesWait for task
cancel(task)NoCancel task
cancel()NoSelf-cancel
select(selector)NoQuery store state
actionChannel(pattern)NoBuffer actions
flush(channel)NoDrain buffered messages
cancelled()YesCheck cancellation in finally
delay(ms)YesPause execution
throttle(ms, pattern, saga)NoRate-limit
debounce(ms, pattern, saga)NoWait for silence
retry(n, delay, fn)YesRetry with backoff
race(effects)YesFirst wins
all([effects])If any child blocksParallel, wait all
setContext(props) / getContext(prop)No / YesSaga context

Pattern Matching

take, takeEvery, takeLatest, takeLeading, throttle, debounce accept:

PatternMatches
'*'All actions
'ACTION_TYPE'Exact action.type match
[type1, type2]Any type in array
fn => booleanCustom predicate

Only take/takeMaybe may omit the argument entirely — take() matches all actions. For takeEvery, takeLatest, takeLeading, throttle, and debounce the pattern is a required parameter; use '*' for a catch-all watcher.

Taking from a multicastChannel also requires a pattern: take(chan, '*'), not take(chan).

How to Use

Read individual rule files for detailed explanations and code examples:

rules/effect-always-yield.md
rules/fork-attached-vs-detached.md

Each rule file contains:

  • Brief explanation of why it matters
  • Incorrect code example with explanation
  • Correct code example with explanation
  • Additional context and decision tables

References

PriorityReferenceWhen to read
1references/effects-and-api.mdWriting or debugging any saga
2references/fork-model.mdConcurrency, error propagation, cancellation
3references/testing.mdWriting or reviewing saga tests
4references/channels.mdExternal I/O, buffering, worker pools
5references/recipes.mdThrottle, debounce, retry, undo, batching, polling
6references/anti-patterns.mdCommon mistakes to avoid
7references/troubleshooting.mdDebugging frozen apps, missed actions, stack traces

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.