agentsclimarketplace

Frontend rn expo

Skill byerlikaya/claude-starter-kit/plugin/skills/frontend-rn-expo

OPTIONAL, stack-specific: React Native + Expo (prebuild). Mobile RN projects only; the generic principles live in the `frontend` skill. Trigger phrases: "expo", "react native", "native bridge", "expo router", "rn screen", "prebuild"From its SKILL.md

Install
npx -y skills add byerlikaya/claude-starter-kit --skill frontend-rn-expo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 223 tokens by cl100k_base, as published. Nobody here has run it

React Native + Expo (stack-specific layer)

For generic frontend discipline, applies the frontend skill; this file only covers the RN+Expo-specific additions. Not used in web/desktop projects (delete it if needed).

RN + Expo specifics

  • Navigation: expo-router (file-based) or react-navigation — follow whichever the project uses.
  • Lists: FlatList/FlashList + keyExtractor; virtualization for heavy lists.
  • Native bridge: only when needed; the JS side is typed, error paths are explicit (what the UI does if native rejects). Via Expo prebuild / config plugin; mind the platform difference (iOS/Android).
  • Render by capability: do not promise in the UI a capability the device lacks; show it conditionally.
  • Assets: image size/resolution, expo-image cache, splash/icon prebuild compatibility.

DoD (in addition to the generic frontend DoD)

  • Works across the target iOS/Android version matrix; native bridge error paths are tested.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in 223 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • follow the project navigation convention
  • type native bridge interfaces
  • handle native bridge error paths explicitly
  • use prebuild or config plugins for native bridge
  • account for iOS and Android platform differences
  • optimize image size and resolution

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.