programming-react

Guide React application design with state boundaries and data fetching patterns.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Muvon/octomind-tap --skill programming-react
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: programming-react
Source: https://github.com/Muvon/octomind-tap/tree/main/skills/programming-react
Command: npx skills add https://github.com/Muvon/octomind-tap --skill programming-react

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design and implement React applications that stay maintainable as features and complexity grow, especially when state management, data fetching, and component boundaries start to blur.

Core Features & Use Cases

  • Clear state boundaries: separate server state from client state, keep derived data computed during render, and avoid swallowing the app in global stores.
  • React architecture best practices: establish component/composition rules, feature-first folder layout, and correct Server/Client Component usage for Next.js/React 19.
  • Predictable hooks and data fetching: useEffect discipline, server-state libraries for caching and retries, and pragmatic patterns for forms, performance, and testing.
  • Use case: you’re starting a new Next.js (App Router) project and want a robust baseline that avoids common pitfalls like overusing useEffect, prop drilling, and ad-hoc fetch+state patterns.

Quick Start

Activate the programming-react Skill while working in your React project and ask it to refactor your current state/data-fetching approach to match React and Next.js best practices.

Frequently Asked Questions about programming-react

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate server state from client state in React and Next.js?

To separate server state from client state in React, keep server state in server-state libraries for caching and invalidation, while isolating client state to UI interactions. This prevents global stores from swallowing the app and ensures derived data is computed during render.

What is the best way to structure a scalable React architecture with Server Components?

A scalable React architecture uses a feature-first folder layout, enforces clear component ownership boundaries, and correctly splits Server and Client Components. This composition prevents prop drilling and keeps Next.js App Router projects maintainable as complexity grows.

When should I use useEffect for data fetching in React?

useEffect should be limited to external synchronization, not data fetching. For data fetching, use server-state libraries to handle caching, retries, and invalidation, which avoids the common pitfalls of ad-hoc fetch and state patterns.

Does this approach work for refactoring existing Next.js App Router projects?

Yes, you can refactor existing Next.js App Router projects by applying these React architecture best practices. It resolves blurred state boundaries and data-fetching patterns, transitioning your app to predictable hooks discipline and clear Server Component usage.

How do I set up testing with realistic network mocking in a React application?

Set up testing with realistic network mocking by using pragmatic patterns that align with your server-state libraries. This approach ensures your tests accurately reflect caching and invalidation behavior without relying on fragile ad-hoc fetch mocks.

Why does my global state management approach cause performance issues in React?

Global state management causes performance issues when it swallows server state and derived data. By separating server state into dedicated libraries and computing derived data during render, you reduce unnecessary re-renders and improve performance.