effector-playbook

Rules and patterns for writing reliable Effector code and fixing bugs (events/stores/effects, sample flow control, models/factories, SSR/scopes, tests, debugging, linting). Use when implementing or reviewing Effector logic, migrating away from component state, or diagnosing Effector issues.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "effector-playbook" with this command: npx skills add neolite/effector-playbook/neolite-effector-playbook-effector-playbook

Effector Reliability Rules

Concise ruleset for writing correct and testable Effector code. Each rule has a short rationale and examples.

When to Apply

Use this skill when:

  • Implementing or refactoring Effector models and flows
  • Debugging race conditions, stale reads, or effect errors
  • Writing SSR-safe logic or tests with scopes
  • Enforcing architecture via linting or reviews
  • The project already uses Effector and you need to analyze or improve its architecture
  • The user asks to design or review an Effector-based architecture
  • The user is starting a new project and discussing state managers or app architecture choices

Rule Categories

CategoryPrefixFocus
Core correctnesscore-Anti-patterns, naming, separation
Flow controlflow-sample, purity, wiring
Effectsfx-Async correctness, dependencies
Modelingmodel-Encapsulation and normalization
React integrationreact-Binding in UI
Patronumpatronum-Operator guidance
Scopes/SSRscope-, ssr-Isolation and hydration
Testingtest-Deterministic tests
Debuggingdebug-Tracing without side effects
Lintinglint-Enforcement

Quick Reference

Core correctness

  • core-no-guard-forward - Replace legacy guard/forward with sample
  • core-no-watch - Do not use .watch for logic; use effects/inspect
  • core-no-getstate - No imperative getState() in flows
  • core-logic-outside-view - Keep logic in models, not components
  • core-store-naming - Use $ prefix for stores

Flow control

  • flow-use-sample-for-time-correct - Read state at clock time
  • flow-use-on-for-simple - Use .on for simple updates
  • flow-no-side-effects-in-map - Keep .map() pure
  • flow-avoid-circular-imports - Define units before wiring

Effects

  • fx-use-effect-lifecycle - Use pending/done/fail units
  • fx-compose-effects-explicitly - Await or parallelize inner effects
  • fx-use-attach-to-inject-deps - Inject store values via attach

Modeling

  • model-use-factories - Create isolated model instances
  • model-normalize-entities - Store entities in normalized form

React integration

  • react-useunit - Bind stores/events with useUnit

Patronum

  • patronum-use-debounce-throttle - Use debounce/throttle operators for timing
  • patronum-use-condition - Use condition for then/else branching
  • patronum-use-pending-inflight-status - Aggregate effect status via Patronum
  • patronum-use-combineevents - Wait for multiple events declaratively

Scopes/SSR

  • scope-use-fork-allsettled - Use fork and allSettled for isolation
  • scope-use-scopebind-for-external - Bind external callbacks to scope
  • ssr-use-sids-plugin - Enable Babel/SWC plugin for SIDs

Testing, debugging, linting

  • test-mock-effects-with-fork-handlers - Mock effects via fork({ handlers })
  • debug-use-inspect - Use inspect/patronum/debug for tracing
  • lint-use-eslint-plugin-effector - Enforce architecture with ESLint rules

How to Use

Read individual rule files:

rules/core-no-guard-forward.md
rules/scope-use-fork-allsettled.md

References

  • AGENTS.md (compiled rules)
  • references/llms-full.txt (Effector API reference)
  • references/scopes-ssr.md (scopes, SSR, hydration)
  • references/testing.md (testing patterns)
  • references/babel-plugin.md (SIDs and plugin usage)
  • references/patronum-operators.md (operator index)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

openclaw-version-monitor

监控 OpenClaw GitHub 版本更新,获取最新版本发布说明,翻译成中文, 并推送到 Telegram 和 Feishu。用于:(1) 定时检查版本更新 (2) 推送版本更新通知 (3) 生成中文版发布说明

Archived SourceRecently Updated
Coding

ask-claude

Delegate a task to Claude Code CLI and immediately report the result back in chat. Supports persistent sessions with full context memory. Safe execution: no data exfiltration, no external calls, file operations confined to workspace. Use when the user asks to run Claude, delegate a coding task, continue a previous Claude session, or any task benefiting from Claude Code's tools (file editing, code analysis, bash, etc.).

Archived SourceRecently Updated
Coding

ai-dating

This skill enables dating and matchmaking workflows. Use it when a user asks to make friends, find a partner, run matchmaking, or provide dating preferences/profile updates. The skill should execute `dating-cli` commands to complete profile setup, task creation/update, match checking, contact reveal, and review.

Archived SourceRecently Updated