Separate the screen into a container and presentational components. A custom hook or feature service should own API calls, state transitions, and business logic. The screen can call that hook and pass the resulting data, loading/error state, and callbacks into focused presentational components. Use function components only, TypeScript interfaces for props, and named exports. Keep each component small and single-purpose, define styles with StyleSheet.create, and use composition to avoid prop d...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add HoangNguyen0403/agent-skills-standard --skill react-native-components --agent claude-codeInstalls 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 automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-react-native-components-40d8ccb2)More formats (shields.io, HTML) on the badges page.
Separate the screen into a container and presentational components. A custom hook or feature service should own API calls, state transitions, and business logic. The screen can call that hook and pass the resulting data, loading/error state, and callbacks into focused presentational components.
Use function components only, TypeScript interfaces for props, and named exports. Keep each component small and single-purpose, define styles with StyleSheet.create, and use composition to avoid prop drilling. Keep feature-specific pieces colocated while moving truly reusable components to a shared components directory.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!