agentleFS
EstebanT1112EstebanT1112/codex-engineering-workflow/skills/react-native-patterns/SKILL.md

react-native-patterns

Skill0 starsChanged 2 months agoMITView on GitHub

Implement or review React Native and Expo screens, navigation, state, data access, lists, native APIs, and platform behavior using the repository's actual SDK and libraries. Use for React Native or Expo work; do not apply React DOM assumptions.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow repository-native screen, component, hook, route, and test conventions.

    line 14
  2. Distinctive:

    Verify focused behavior, typecheck, and the relevant device or simulator path when available.

    line 20
  3. Distinctive:

    Do not assume Expo Router, NativeWind, TanStack Query, or another library unless the repository already uses it or the user approves its …

    line 25
  4. Distinctive:

    Do not claim device behavior verified from static checks alone.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

React Native and Expo Patterns

Workflow

  1. Detect the installed React Native or Expo SDK, navigation system, build workflow, styling approach, state/data libraries, and supported platforms.
  2. Follow repository-native screen, component, hook, route, and test conventions.
  3. Separate server cache, local UI state, route state, and form state according to their real lifetimes.
  4. Validate external data at the boundary using existing dependencies; do not add a validation or state package by default.
  5. Account for safe areas, keyboard behavior, touch targets, list performance, loading/error/empty states, offline behavior when required, and platform differences.
  6. Request native permissions at the point of need and handle denial or restricted states.
  7. Store sensitive material only through the project's secure-storage mechanism.
  8. Verify focused behavior, typecheck, and the relevant device or simulator path when available.

Boundaries

  • React Native has no browser DOM; do not use HTML elements or browser-only APIs.
  • Do not assume Expo Router, NativeWind, TanStack Query, or another library unless the repository already uses it or the user approves its addition.
  • Do not claim device behavior verified from static checks alone.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.