What problem does it solve?
It keeps React 19 component development across the admin dashboard and customer app consistent by enforcing container/presentational separation, React Query for data, Zustand for client state, and strict form validation so teams do not drift into ad hoc patterns.
Core Features & Use Cases
- Container/presentational separation ensures data fetching, loading states, and error handling stay inside containers that render pure presentation components, preventing tangled JSX.
- Hook and form conventions mandate custom React Query hooks, Zustand stores, and Zod-backed React Hook Form to provide stable server data, client cache, and validated user input for bookings, members, and inventory flows.
- Behavior rules cover code splitting, component sizing, semantic HTML, ARIA labels, and naming conventions so teams can build accessible, maintainable features without prop drilling or unnecessary inline reactivity.
Quick Start
Compose a React 19 container and presentation pair that relies on a React Query hook, Zustand store, and Zod-validated form as described above.