react-stack

Keep each component responsible for one concern and pass data through explicit props with predictable flow. This Skill's guidance helps decide where logic belongs and when a component should be split during feature work or review.

Only add a state library when there is a concrete need that local state and props cannot handle. The guidance favors simple state ownership and warns against abstraction-heavy hooks introduced without justification.

No. Cargo-cult memoization adds complexity without measurable benefit. Apply memoization only after identifying an actual rendering performance issue, not as a default pattern.

Check keyboard interaction, focus management during user-state transitions, responsive behavior, and hydration-related regressions. The guidance treats accessibility, rendering behavior, and failure states as part of every UI change.

It is less suited to greenfield architecture decisions like choosing a framework or routing library from scratch. It assumes an existing React codebase with established styling, routing, and data-fetching patterns to preserve.