From react-native-best-practices
Use this skill for ANY React Native task involving performance, architecture, or platform-specific concerns. Triggers on: Metro bundler config/optimization, FlatList vs ScrollView choice, platform-specific code audit (Platform.OS, .ios.js/.android.js splits), Expo vs bare workflow guidance, React Navigation setup/patterns, bundle size analysis, slow list rendering, navigation performance, or any RN project audit. Always use this skill when the user mentions React Native, Expo, Metro, React Navigation, or mobile app performance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/react-native-best-practices:react-native-best-practicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Performance problem?** → Check FlatList/ScrollView first → then Metro config
Read the relevant file from the plugin's references/ directory based on the task:
Parse user request → map to one or more reference files → read them.
# Check for common issues
grep -r 'ScrollView' src/ --include='*.tsx' --include='*.ts' -l
grep -r 'Platform.OS' src/ --include='*.tsx' -n
find . -name '*.ios.js' -o -name '*.android.js' | head -20
cat metro.config.js 2>/dev/null || cat metro.config.ts 2>/dev/null
Provide: diagnosis → concrete code fixes → before/after → why it matters.
List Detox or Maestro test commands relevant to the fix.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub petro-nazarenko/mobile-skills --plugin react-native-best-practices