Effector Ecosystem Skill

Purpose

Use this skill for frontend applications that use or plan to use:

• React or React-compatible UI
• Effector for business logic and state
• effector-react for binding units to components
• Farfetched for remote operations
• @withease/contracts or compatible contracts for runtime validation
• Supporting packages from the Effector ecosystem: patronum, atomic-router, effector-storage, effector-action, effector-forms, @withease/factories, @withease/i18next, @withease/web-api, @effector/next, @effector/reflect, @withease/redux, eslint-plugin-effector, Effector Babel/SWC plugins

This skill is project-structure agnostic. It may use paths like entities/user or shared/api in examples, but it must not decide Feature-Sliced Design placement rules. When the question is mainly about layers, slices, public APIs, import boundaries, file placement, or project structure in an Effector project, use effector-fsd.

The target architecture:

UI is dumb. Business logic is declarative. Remote data is validated. Startup is explicit and scoped. Remote-operation semantics are modeled, not hidden in React components.