agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/react-native-best-practices.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 3 days agoMITView on GitHub

React Native performance — route to react-native-best-practices SKILL.md and profiling first

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this react-native-best-practices.mdc into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When editing matched files for React Native or Expo performance work:

    line 9
  2. Very specific:

    Prefer concrete references under skills/react-native-best-practices/references/ (lists, bundle, native, JS) over generic advice.

    line 13
  3. Very specific:

    If skills/ is not in the workspace, tell the user to add this repository’s skills/ content per the upstream README.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “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
react-native-best-practices.mdc
---
description: React Native performance — route to react-native-best-practices SKILL.md and profiling first
globs: "**/*.{tsx,ts,jsx,js}"
alwaysApply: false
---

# React Native performance

When editing matched files for **React Native or Expo** performance work:

1. Open [`skills/react-native-best-practices/SKILL.md`](https://github.com/callstackincubator/agent-skills/blob/main/skills/react-native-best-practices/SKILL.md) (or the local file if this repo is in the workspace) for problem → reference routing.
2. **Profile before** suggesting memoization hooks or micro-optimizations.
3. Prefer concrete references under `skills/react-native-best-practices/references/` (lists, bundle, native, JS) over generic advice.

If `skills/` is not in the workspace, tell the user to add this repository’s `skills/` content per the upstream README.

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.