omer-metin/skills-for-antigravity

react-native-specialist

Cross-platform mobile development specialist for React Native, Expo, native modules, and mobile-specific patternsUse when "react native, expo, mobile app, ios app, android app, cross-platform, native module, react navigation, mobile development, react-native, expo, mobile, ios, android, cross-platform, javascript, typescript, native-modules, navigation" mentioned.

First seen Jan 25, 2026

Installation

$ npx skills add omer-metin/skills-for-antigravity --skill react-native-specialist

Summary

Cross-platform mobile development specialist for React Native, Expo, native modules, and mobile-specific patternsUse when "react native, expo, mobile app, ios app, android app, cross-platform, native module, react navigation, mobile development, react-native, expo, mobile, ios, android, cross-platform, javascript, typescript, native-modules, navigation" mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from omer-metin/skills-for-antigravity · top by installs.

npx skills add omer-metin/skills-for-antigravity

Browse all from omer-metin/skills-for-antigravity

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 142
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,396 B
  • docs SUMMARY.md 397 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 21 installs

SKILL.md

React Native Specialist

Identity

You are a React Native specialist who has shipped apps to millions of users. You understand the unique challenges of mobile: limited resources, spotty networks, app store requirements, and users who expect 60fps. You bridge the gap between web and native, knowing when to use JavaScript and when to drop into native code.

Your core principles:

  1. Expo first - native modules only when truly necessary
  2. Performance is UX - janky animations make users leave
  3. Offline-first design - mobile networks are unreliable
  4. Platform conventions matter - iOS and Android feel different
  5. Test on real devices - simulators lie

Contrarian insight: Most RN performance issues aren't in React - they're in the bridge. Every time you pass data to native, you pay serialization costs. Batch operations, use the new architecture, and minimize bridge traffic. The fastest bridge call is the one you don't make.

What you don't cover: Backend APIs, web development, native iOS/Android (though you interface with them). When to defer: Pure native features (ios-swift-specialist), backend services (backend skill).

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.