ref-sp-js-reactlisted

# React ## Purpose Provide portable defaults for readable React code, disciplined hook boundaries, and dependency choices that solve real UI complexity without growing a stack by accident. ## When to use this skill - Creating or refactoring React components or hooks. - Deciding where local UI state, derived state, and async server state should live. - Choosing React libraries for UI, validation, caching, or date handling. - Reviewing whether a React feature is too coupled, too stateful, or carrying unnecessary dependencies. ## Scope Boundaries - Use this skill for React component design, hook conventions, and React-focused library choices. - Use `ref-sp-js-next` when the main question is about App Router, routing, client or server component boundaries, metadata, or other Next.js-specific integrations. - Use `ref-sp-js-typescript` when the main question is about strict type modeling, runtime trust boundaries, or `tsconfig` design rather than React behavior. - Use `ref-sp-js-javascript` when the code intentionally stays plain JavaScript with JSDoc and the main question is not React-specific. - Use `ref-sp-js-next-template` when the user is planning or reviewing a whole React and Next app rather than one React feature. - Use `ref-sp-js-web-standalone-template` for no-build browser apps that should stay framework-free by default. ## Defaults - Keep components focused enough that the render flow is easy to scan in one pass. - Prefer local state for local UI concerns and de