write-hook

To create React hooks with server actions and optimistic updates, implement them using a three-layer Epic architecture that isolates server logic, validates inputs with Zod, and provides rollback support to improve perceived UI performance.

The best way to structure custom React hooks for state management is placing them under app/[role]/[page]/behaviors/[behavior-name]/hooks/ and enforcing a single backend entry point per hook to simplify testing and reasoning.

Yes, you can integrate Zod schemas to validate inputs within React hooks, keeping rendering side effects isolated from server logic while maintaining strict validation before executing backend actions or routes.

Handle streaming route cancellation in React hooks by implementing built-in cancellation support for long-running tasks, ensuring the hook manages loading and error states while preventing orphaned requests during component unmount.

React hooks should avoid direct database access because the Epic architecture enforces a strict rule to call exactly one backend entry point per hook, ensuring server actions or routes handle data fetching while the hook manages state.

write-hook works with both standard and streaming routes, applying validation, loading states, and optimistic UI updates while adding specific cancellation support required for long-running streaming tasks.