Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
itallstartedwithaidea avatar

React Native Guidelines

  • 57 installs
  • 31 repo stars
  • Updated April 12, 2026
  • itallstartedwithaidea/agent-skills

Apply 16 production React Native rules across performance, layout, animation, images, state, architecture, and platform pitfalls while building screens.

About

React Native Guidelines is an agent skill that encodes cross-platform mobile discipline for solo builders shipping React Native apps with Claude Code, Cursor, or similar agents. It codifies sixteen rules in seven sections—Performance, Layout, Animation, Images, State, Architecture, and Platform—each mapping to a concrete failure mode in React Native’s bridge and native rendering pipeline. Unlike web React guidance, it stresses keeping the JavaScript thread unblocked, animating with the native driver, tuning list virtualization, and reducing async chatter between JS, UI, and native module threads. Invoke it when you scaffold screens, refactor navigation, or chase jank on iOS or Android. The skill reads as a checker-style rulebook agents can apply during implementation and review. It pairs well with performance tuning in Ship when production metrics slip, but its canonical home is Build frontend work where architectural choices are cheapest to fix.

  • 16 rules organized across 7 sections: Performance, Layout, Animation, Images, State, Architecture, Platform
  • Targets JS-thread blocking, native-driver animations, FlatList optimization, and minimized bridge crossings
  • Explicit iOS vs Android platform behaviors instead of treating differences as edge cases
  • Calibrated for production apps on both platforms, not demo-only patterns
  • Use when building new screens, components, or debugging mobile performance regressions

React Native Guidelines by the numbers

  • 57 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #585 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill react-native-guidelines

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs57
repo stars31
Security audit3 / 3 scanners passed
Last updatedApril 12, 2026
Repositoryitallstartedwithaidea/agent-skills

What it does

Apply 16 production React Native rules across performance, layout, animation, images, state, architecture, and platform pitfalls while building screens.

Files

SKILL.mdMarkdownGitHub ↗

React Native Guidelines

Part of Agent Skills™ by googleadsagent.ai™

Description

React Native Guidelines codifies 16 rules across 7 sections—Performance, Layout, Animation, Images, State, Architecture, and Platform—that prevent the most common pitfalls in cross-platform mobile development. Each rule addresses a specific failure mode unique to React Native's bridge architecture and native rendering pipeline.

React Native's performance characteristics differ fundamentally from web React. The JavaScript thread, the UI thread, and the native modules thread communicate asynchronously, and bottlenecks in any thread degrade the user experience. These guidelines focus on keeping the JS thread unblocked, using the native driver for animations, optimizing FlatList rendering, and minimizing bridge crossings.

The rules are calibrated for production applications running on both iOS and Android. Platform-specific behaviors, gesture handling differences, and navigation patterns are addressed explicitly rather than treated as edge cases.

Use When

  • Building new React Native screens or components
  • Debugging performance issues on iOS or Android
  • Reviewing React Native code for cross-platform correctness
  • Implementing animations or gesture interactions
  • Optimizing list rendering for large datasets
  • Handling platform-specific behavior differences

How It Works

graph TD
    A[React Native Code] --> B{Section Analysis}
    B --> C[Performance: JS Thread Budget]
    B --> D[Layout: Flexbox + Safe Areas]
    B --> E[Animation: Native Driver]
    B --> F[Images: Caching + Sizing]
    B --> G[State: Minimal Re-renders]
    B --> H[Architecture: Navigation + Deep Links]
    B --> I[Platform: iOS/Android Specifics]
    C --> J[Optimized Output]
    D --> J
    E --> J
    F --> J
    G --> J
    H --> J
    I --> J

Each section contains 2-3 focused rules targeting the highest-impact issues in that category. Rules are applied during code generation and flagged during review.

Implementation

Performance: Optimize FlatList

// BAD: Re-creates renderItem on every render
<FlatList
  data={items}
  renderItem={({ item }) => <Card item={item} />}
/>

// GOOD: Stable renderItem + keyExtractor + windowing config
const renderItem = useCallback(
  ({ item }: { item: Item }) => <Card item={item} />,
  []
);

<FlatList
  data={items}
  renderItem={renderItem}
  keyExtractor={item => item.id}
  getItemLayout={(_, index) => ({
    length: CARD_HEIGHT,
    offset: CARD_HEIGHT * index,
    index,
  })}
  maxToRenderPerBatch={10}
  windowSize={5}
  removeClippedSubviews
/>

Animation: Use Native Driver

// BAD: JS-driven animation blocks the thread
Animated.timing(opacity, {
  toValue: 1,
  duration: 300,
  useNativeDriver: false,
}).start();

// GOOD: Native driver runs on UI thread
Animated.timing(opacity, {
  toValue: 1,
  duration: 300,
  useNativeDriver: true,
}).start();

// BEST: Reanimated for gesture-driven animations
const animatedStyle = useAnimatedStyle(() => ({
  transform: [{ translateX: withSpring(offset.value) }],
}));

Platform: Safe Area Handling

import { useSafeAreaInsets } from "react-native-safe-area-context";

function Screen({ children }: PropsWithChildren) {
  const insets = useSafeAreaInsets();
  return (
    <View style={{ paddingTop: insets.top, paddingBottom: insets.bottom }}>
      {children}
    </View>
  );
}

Best Practices

  • Profile with Flipper or React DevTools before optimizing—measure, do not guess
  • Keep the JS thread under 16ms per frame for 60fps rendering
  • Use useNativeDriver: true for all opacity and transform animations
  • Avoid inline styles in list items—use StyleSheet.create for static styles
  • Handle both iOS and Android safe areas, notches, and gesture navigation
  • Test on real devices, not just simulators—performance differs significantly

Platform Compatibility

PlatformSupportNotes
CursorFullReact Native project support
VS CodeFullReact Native Tools extension
WindsurfFullMobile development support
Claude CodeFullCode generation + review
ClineFullReact Native aware
aiderPartialLimited mobile context

Related Skills

  • React Best Practices
  • Composition Patterns
  • Web Design Guidelines
  • CI/CD Pipelines

Keywords

react-native mobile performance flatlist native-driver animation safe-area cross-platform ios android

---

© 2026 googleadsagent.ai™ | Agent Skills™ | MIT License

Related skills

FAQ

Is React Native Guidelines safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Mobile Developmentfrontendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.