expo-rn-conventions

Apply consistent React Native + Expo conventions for project structure, Expo Router navigation, theming primitives, icons, sqlite data patterns, safe area handling, and bun/bunx tooling. Use when adding or updating screens, components, navigation, data, or dependencies in Expo/React Native apps so work matches these practices.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill streamlines React Native and Expo development by enforcing standardized project structures and coding conventions. It automates the application of best practices for Expo Router navigation, theming, SQLite data patterns, and safe area handling, ensuring high-quality, maintainable, and scalable mobile applications.

Use Cases

  • Standardizing Project Structure: Automatically organize React Native and Expo directories, files, and dependencies using Bun/Bunx for optimal performance and consistency.
  • Consistent Navigation & UI Implementation: Seamlessly integrate Expo Router navigation and theming primitives that align with established design systems and safe area requirements.
  • Data Pattern Enforcement: Apply uniform SQLite data access patterns and state management logic across the entire mobile application to prevent technical debt.
  • Code Quality & Maintenance: Use as a real-time reference when adding new screens or components to ensure every update matches existing project conventions and architectural standards.
nameexpo-rn-conventions
descriptionApply consistent React Native + Expo conventions for project structure, Expo Router navigation, theming primitives, icons, sqlite data patterns, safe area handling, and bun/bunx tooling. Use when adding or updating screens, components, navigation, data, or dependencies in Expo/React Native apps so work matches these practices.
licenseMIT

Expo RN Conventions

Overview

Use this skill to enforce a reusable set of React Native + Expo do and don'ts across projects.

Workflow

  1. Load references/context.md and treat it as the source of truth for conventions.
  2. Apply the guidance while editing screens, components, navigation, data, and config.
  3. Call out conflicts with a target project's local guidelines before deviating.
  4. Update references/context.md when new conventions are agreed on.

Reference

  • references/context.md