mvp-view-logic-decoupling

Installation
SKILL.md

MVP View-Logic Decoupling

Overview

Apply a strict Presenter-Manager-Store structure that keeps UI components free of business logic and centralizes cross-module behavior.

State/Data Flow Ownership

  • Complex business logic, state machines, streaming flows, and cross-event ordering belong in manager/store/presenter, primarily manager.
  • Hooks and components should connect React to the owner: subscribe to stores or queries, call manager/presenter methods, and keep only lightweight local UI state.
  • When flows need cancellation, buffering, fan-in/fan-out, terminal event handling, retry control, or ordering guarantees, consider an explicit data-flow tool such as RxJS after confirming plain manager/store ownership is insufficient.
  • Do not introduce RxJS for simple local state, one-off effects, or view-only interaction details.

Target Architecture

Installs
3
Repository
peiiii/nextclaw
GitHub Stars
214
First Seen
Apr 6, 2026
mvp-view-logic-decoupling — peiiii/nextclaw