agentleFS
Sign inStart free
garfiecgarfiec/Librechat-Mobile/fastlane/CLAUDE.md

Librechat-Mobile / fastlane

CLAUDE.md149 starsChanged 7 days agoApache-2.0View on GitHub

The only store listings built from this directory are F-Droid and IzzyOnDroid. It does not feed Google Play or the App Store. (The repo README.md also embeds its screenshots.) Nothing uploads it there: play.yml sends only the bundle and the R8 mapping, and appstore.yml only the archive. Each store listing is a separate copy kept by hand in Play Console or App Store Connect. - Text here describes the open-source build (foss flavor). Store builds differ: see ChannelPolicy (:core:common) and…

The file

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

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never copy this text into a store listing unchanged.

    line 15
  2. Distinctive:

    Don't sync either side to match the other without asking.

    line 18

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

Store metadata

The only store listings built from this directory are F-Droid and IzzyOnDroid. It does not feed Google Play or the App Store. (The repo README.md also embeds its screenshots.) Nothing uploads it there: play.yml sends only the bundle and the R8 mapping, and appstore.yml only the archive. Each store listing is a separate copy kept by hand in Play Console or App Store Connect.

  • Text here describes the open-source build (foss flavor). Store builds differ: see ChannelPolicy (:core:common) and the per-channel defaults in AppPreferences (:core:data). Site icons are the known case: the open-source build asks before loading them, and store builds load them by default. A sentence that is true here can be false on Play.
  • Editing a file here never changes the Play listing. If the change should reach Play too, say so and edit the Console copy separately, reworded for the Play build's defaults.
  • Never copy this text into a store listing unchanged. Check every claim about what the app does by default against that store's channel.
  • The store copies already differ from these files (for example the Play short description). Don't sync either side to match the other without asking.

Format rules, character limits, the CI-written changelogs and the screenshot policy are in README.md. Run scripts/check-fdroid-metadata.py after any edit.

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