Yes. A component declared inside the parent render function gets a new component identity on every parent render. That can cause it to remount, lose local state, reset effects, and do unnecessary work. Move it to module scope and pass the required values through typed props. If it is reusable, export it as a named function component; if its render cost is significant, consider React.memo after measuring. Keep its styles in StyleSheet.create and use children or composition instead of deeply dr...
Installs into .claude/skills of the current project.
Are you the author of React Native Components?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-react-native-components-51588716)
Yes. A component declared inside the parent render function gets a new component identity on every parent render. That can cause it to remount, lose local state, reset effects, and do unnecessary work.
Move it to module scope and pass the required values through typed props. If it is reusable, export it as a named function component; if its render cost is significant, consider React.memo after measuring. Keep its styles in StyleSheet.create and use children or composition instead of deeply drilling props.
