Guide React 19 UI development with component architecture and state boundaries.
npx skills add https://github.com/marcoamu/openclaw-workspace --skill react-marcoamu
Please help me install this Agent Skill. Skill: React Source: https://github.com/marcoamu/openclaw-workspace/tree/main/skills/react Command: npx skills add https://github.com/marcoamu/openclaw-workspace --skill react-marcoamu
React-based UI development benefits from a component-driven architecture, but teams often struggle with consistency, state boundaries, and performance at scale. This guide outlines patterns, rules, and best practices to help engineers build maintainable, scalable interfaces.
Create a new React project and scaffold a minimal component-driven UI to observe React patterns in action.
High-intent search queries and answers about installing and using this skill.
Separating server and client state in React ensures predictable UI and maintainability. Use TanStack Query for server state and Zustand for client state to enforce clear boundaries and optimize rendering across SPA and SSR deployments.
To start building a React 19 component-driven UI, scaffold a minimal project observing standard patterns. This guide directs end-to-end development by detailing component architecture, naming rules, and production-ready practices with documentation and tests.
Yes, this guide fully supports React Server Components with Next.js. It outlines specific React 19 patterns to optimize rendering, data loading, and developer experience across SPA, SSR, and hybrid deployments.
React Server Components improve data loading performance by optimizing rendering strategies on the server. This reduces client-side JavaScript overhead and enforces explicit separation of server and client state for faster hybrid deployments.
Yes, you can use Zustand and TanStack Query together for state management. This guide enforces using TanStack Query for server state and Zustand for client state to maintain clear architecture and predictable UI behavior.
Common performance traps in production React apps include poor state boundaries and inconsistent component architecture. This guide outlines specific rules and best practices to avoid these traps and ensure scalable, maintainable interfaces.
WesleySmitsGenerate React/Next.js component scaffolds with TypeScript, CSS modules, tests, and Storybook.
vladm3105Decompose BRD, PRD, and EARS inputs into atomic REQ v3.0 documents.
alejandro-technologyManage client and server state with Zustand, TanStack React Query, and MMKV.
bonnguyenitcGuide frontend architecture and review tasks with reusable component patterns.
