agentleFS
Sign inStart free
studyzakomi-ossstudyzakomi-oss/Claude-code/AGENTS.md

Claude-code

AGENTS.md1 starsChanged 24 days agoMITView on GitHub

This is an Expo/React Native mobile application. Prioritize mobile-first patterns, performance, and cross-platform compatibility. Expo ships breaking changes every SDK release. APIs you remember are likely renamed, moved, or removed. Before writing any code that touches an Expo, EAS, or React Native API: Use bunx instead of npx if the project uses bun (bun.lock present). Run lint and typecheck before declaring any task done. Use EAS to build, sign, and submit the app in the cloud (eas build, eas submit)…

8 other projects use a version of this; 3 new projects in the last 4 weeks, against 3 the 4 before.

Adopted by

Steady: 3 new projects took it in the last 4 weeks, 1× the 4 weeks before.thin data

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

Most recently taken up by

  • Other versions8 projects use a version of this.

    Word for word · 8

    1. NanmiCoder/cc-haha★ 15k100% same
    2. NanmiCoder/claude-code-haha★ 15k100% same
    3. hardbeat920/monocode★ 3.8k100% same
    4. DemonDamon/AgenticX★ 1k100% same
    5. savannahfeder/agentbox★ 376100% same
    6. noorjsdivs/Orbitx-App★ 1100% same
    7. thiagosalvatore/korev★ 1100% same
    8. tradernetwork/etf-holdings-tracker★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read the major version of the expo package in package.json.

    line 7
  2. Very specific:

    Use bunx instead of npx if the project uses bun (bun.lock present).

    line 13
  3. Distinctive:

    Run lint and typecheck before declaring any task done.

    line 24
  4. Very specific:

    Use Expo Router for all navigation.

    line 28
  5. Very specific:

    Import Link, router, and useLocalSearchParams from expo-router.

    line 29
  6. Very specific:

    If ios/ and android/ directories do not exist, they are generated (Continuous Native Generation).

    line 39
  7. Distinctive:

    Prefer recommended Expo modules over third-party libraries, and check your available skills before adding dependencies.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

This is an Expo/React Native mobile application. Prioritize mobile-first patterns, performance, and cross-platform compatibility.

Expo has changed — do not trust your training data

Expo ships breaking changes every SDK release. APIs you remember are likely renamed, moved, or removed. Before writing any code that touches an Expo, EAS, or React Native API:

  1. Read the major version of the expo package in package.json.
  2. Fetch the matching versioned docs: https://docs.expo.dev/versions/v<major>.0.0/
  3. For anything else, fetch https://docs.expo.dev/llms.txt — an index of all Expo docs with corrections to common LLM misconceptions. Follow its links to the specific page you need; never answer from memory.

Commands

Use bunx instead of npx if the project uses bun (bun.lock present).

npx expo install <package>  # ALWAYS use instead of npm/yarn/pnpm/bun add — resolves SDK-compatible versions
npx expo start              # start the dev server
npx expo lint               # lint
npx tsc --noEmit            # typecheck
npx expo-doctor             # diagnose dependency and config issues
npx expo install --fix      # fix incompatible package versions

Run lint and typecheck before declaring any task done.

Navigation & Routing

  • Use Expo Router for all navigation. Routes live in src/app/ — every file there is a screen, _layout.tsx files define navigators. Keep non-route code (components, hooks, utils) outside src/app/.
  • Import Link, router, and useLocalSearchParams from expo-router.
  • Docs: https://docs.expo.dev/router/introduction.md

Building with EAS

Use EAS to build, sign, and submit the app in the cloud (eas build, eas submit) and to ship over-the-air updates (eas update) — no local Xcode or Android Studio required. Run EAS CLI as bunx eas-cli <command> in Bun projects, or npx eas-cli@latest <command> otherwise; substitute that for bare eas in docs examples. Docs: https://docs.expo.dev/eas/index.md

Rules

  • If ios/ and android/ directories do not exist, they are generated (Continuous Native Generation). Never create or edit them by hand — configure native behavior in app.json and config plugins.
  • Expo Go only includes its bundled native modules. After adding a library with native code, the app needs a development build: npx expo run:ios|android locally, or eas build --profile development.
  • Prefer recommended Expo modules over third-party libraries, and check your available skills before adding dependencies. Docs: https://docs.expo.dev/versions/latest/index.md

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.

Check your setup, free