react-feature

To implement React feature changes safely, confine modifications to the dedicated feature slice and follow existing routing, state management, and component patterns. This keeps updates localized and aligned with your codebase conventions.

A feature slice in React frontend development is a localized boundary containing all routing, state management, and component logic for a specific feature. Keeping changes within this slice prevents code from bleeding into unrelated areas of the application.

To add new UI features safely, identify established data fetching and styling patterns, implement the changes within the feature slice, and validate everything using the repository's standard lint, test, and build commands before summarizing the changes for review.

You do not need existing tests to implement React state management changes, but if the repository supports them, you must add or update tests. Validation always runs against repo-standard lint, test, and build commands to ensure safety.

The best way to manage routing and state across React feature boundaries is to identify and follow the codebase's established patterns. Implement changes with minimal new abstractions inside the feature slice to maintain consistency and prevent cross-boundary side effects.

Keeping React feature development localized to a feature slice prevents unintended side effects across boundaries. It forces adherence to existing routing, state management, and component conventions, ensuring changes are safe, fast, and easy to review.