feat(rules,skills): add React Native / Expo rules pack and react-native-patterns skill (#2275)

* feat(rules,skills): add React Native / Expo rules pack and react-native-patterns skill

* fix(rules,skills): address review feedback — safeParse nav example, drop deprecated sentry-expo, memoize list renderItem, clarify New Architecture SDK support

* fix(rules,skills): drop deprecated Flipper, surface permission-denied state in location hook

rules/README.md

@@ -1,4 +1,5 @@
 # Rules
+
 ## Structure
 
 Rules are organized into a **common** layer plus **language-specific** directories:
@@ -21,6 +22,7 @@ rules/
 ├── python/          # Python specific
 ├── golang/          # Go specific
 ├── web/             # Web and frontend specific
+├── react-native/    # React Native / Expo specific
 ├── swift/           # Swift specific
 ├── php/             # PHP specific
 ├── ruby/            # Ruby / Rails specific
@@ -43,6 +45,7 @@ rules/
 ./install.sh python
 ./install.sh golang
 ./install.sh web
+./install.sh react-native
 ./install.sh swift
 ./install.sh php
 ./install.sh ruby
@@ -79,6 +82,7 @@ cp -r rules/nuxt ~/.claude/rules/ecc/
 cp -r rules/python ~/.claude/rules/ecc/
 cp -r rules/golang ~/.claude/rules/ecc/
 cp -r rules/web ~/.claude/rules/ecc/
+cp -r rules/react-native ~/.claude/rules/ecc/
 cp -r rules/swift ~/.claude/rules/ecc/
 cp -r rules/php ~/.claude/rules/ecc/
 cp -r rules/ruby ~/.claude/rules/ecc/
@@ -100,7 +104,7 @@ cp -r rules/typescript .claude/rules/ecc/
 - **Rules** define standards, conventions, and checklists that apply broadly (e.g., "80% test coverage", "no hardcoded secrets").
 - **Skills** (`skills/` directory) provide deep, actionable reference material for specific tasks (e.g., `python-patterns`, `golang-testing`).
 
-Language-specific rule files reference relevant skills where appropriate. Rules tell you *what* to do; skills tell you *how* to do it.
+Language-specific rule files reference relevant skills where appropriate. Rules tell you _what_ to do; skills tell you _how_ to do it.
 
 ## Adding a New Language
 
@@ -126,7 +130,7 @@ For non-language domains like `web/`, follow the same layered pattern when there
 When language-specific rules and common rules conflict, **language-specific rules take precedence** (specific overrides general). This follows the standard layered configuration pattern (similar to CSS specificity or `.gitignore` precedence).
 
 - `rules/common/` defines universal defaults applicable to all projects.
-- `rules/golang/`, `rules/python/`, `rules/swift/`, `rules/php/`, `rules/typescript/`, etc. override those defaults where language idioms differ.
+- `rules/golang/`, `rules/python/`, `rules/swift/`, `rules/php/`, `rules/typescript/`, `rules/react-native/`, etc. override those defaults where language idioms differ.
 
 ### Example