agentleFS
mihirkavimihirkavi/open-media/AGENTS.md

open-media

AGENTS.md1 starsChanged 10 days agoMITView on GitHub

Open Media ships as one app on web, iOS, and Android. A change is not done until it is tested on every platform it can affect, not just the one it was written on.

  • 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,700 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.

  • In this repository4 other files it gives its agents.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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. Distinctive:

    Read the exact Expo SDK 56 documentation at <https://docs.expo.dev/versions/v56.0.0/> before changing Expo or React Native code.

    line 3
  2. Common:

    Never add real credentials, tokens, mailbox exports, or personal message data to the repository.

    line 5
  3. Distinctive:

    Keep connector support claims aligned with working code.

    line 6
  4. Distinctive:

    Keep generated output inside this repository or an operating-system temporary directory.

    line 7
  5. Very specific:

    Web: run the app (npm run local, or the web preview) and exercise the change in a browser at desktop width and at phone width (375 px), …

    line 13
  6. Very specific:

    Android: run it on the Android emulator (npx expo run:android).

    line 15
  7. Very specific:

    Shared logic: add or update unit tests (npm run check covers the typecheck, app and Worker tests, and the web export), and run npm run …

    line 16
  8. Distinctive:

    Never accept an ONDC order action until phase 2 is built.

    line 35

≈ “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

Convo repository guidance

  • Read the exact Expo SDK 56 documentation at https://docs.expo.dev/versions/v56.0.0/ before changing Expo or React Native code.
  • Preserve the boundary between src/domain, src/connectors, src/data, and src/ui.
  • Never add real credentials, tokens, mailbox exports, or personal message data to the repository.
  • Keep connector support claims aligned with working code. Mock or proposed connectors must be labeled clearly.
  • Keep generated output inside this repository or an operating-system temporary directory.

Cross-platform verification (required for every change)

Open Media ships as one app on web, iOS, and Android. A change is not done until it is tested on every platform it can affect, not just the one it was written on.

  • Web: run the app (npm run local, or the web preview) and exercise the change in a browser at desktop width and at phone width (375 px), signed out and signed in. Check the console for errors.
  • iOS: run it on the iOS Simulator (npx expo prebuild --platform ios when native modules change, pod install, then npx expo run:ios --no-bundler against the running Metro server). Check layout at phone size, the keyboard, safe areas, and native modules such as video. Local sign-in works on the simulator. A physical iPhone needs a TestFlight build from npx eas-cli build -p ios --profile production --auto-submit, which the owner runs.
  • Android: run it on the Android emulator (npx expo run:android). This needs JDK 17 or newer; the Mac currently has JDK 11, so install a newer JDK before the first Android run.
  • Shared logic: add or update unit tests (npm run check covers the typecheck, app and Worker tests, and the web export), and run npm run test:db for database changes.
  • Report honestly: say which platforms were verified and how, and name anything not verified (for example, a feature that needs a real network account, a physical device, or production-only services) instead of implying it works.

Web performance

  • Icons come from src/ui/Icon.tsx (Ionicons cut down to the icons used). Never import @expo/vector-icons or its barrel directly: the barrel alone adds about 450 KB. After using a new icon, run npm run icons:subset; the typecheck fails until you do.
  • Screens and heavy features that aren't on the first page load with lazyComponent (src/ui/lazyComponent.tsx) or import(), so the web build splits them into their own files. Keep large data (catalogs, SDKs, signing code) out of modules the first page imports.
  • Content-hashed build files are served with a one-year immutable cache (services/mail-sync/src/webApp.ts), and npm run build:web adds font preloads and preconnects to the page.

Agent plugin and agent site

  • Skills live in src/domain/agentSkills.ts; run npm run agent-plugin:sync after changing them (a test fails if agent-plugin/skills drifts). Never edit the generated SKILL.md files.
  • One plugin, many marketplaces (ADR 0027): agent-plugin/ holds the Claude (.claude-plugin/), Codex (.codex-plugin/), Agent Plugins standard (plugin.json + mcp.json), Antigravity (.antigravity-plugin/ + mcp_config.json) and MCP Registry (registry/) manifests; Gemini CLI's is gemini-extension.json at the repo root. Keep name, version and the three servers equal everywhere (a test checks). The account server is /account/mcp with OAuth, so no manifest ever holds a token, header or env placeholder.
  • WebMCP tools are data in src/domain/webMcpTools.ts, used by both the Worker's pages and the web app. Keep them read-only.

ONDC seller app

  • ADR 0015. Protocol code is in services/mail-sync/src/ondc/, store rules are in src/domain/ondc.ts, and the database is supabase/migrations/20261028120000_ondc_stores.sql.
  • ONDC keys exist only as Worker secrets (npm run ondc:keys prints them; never commit or paste them). Keep crypto.test.ts passing against ONDC's published signing example.
  • Never accept an ONDC order action until phase 2 is built. Unsupported actions must NACK with 40001. Callbacks go only to the buyer app's registered host.

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.