agentleFS
remix-runremix-run/remix-store/AGENTS.md

remix-store

AGENTS.md218 starsChanged 7 days agoMITView on GitHub

Load .agents/skills/remix-store/SKILL.md for app structure, conventions, and verification steps. The overrides in pnpm-workspace.yaml patch vulnerable transitive dependencies of @shopify/mini-oxygen 4.2.3, which still runs Miniflare 3. Hydrogen merged the move to Miniflare 4 (Shopify/hydrogen#4245); it ships as @shopify/mini-oxygen 4.3.0 in the release from Shopify/hydrogen#4229. Whenever you touch dependencies, check npm view @shopify/mini-oxygen version. Once it is 4.3.0 or newer: 1. Bump @shopify/mini-oxygen in package.json (and @shopify/hydrogen if the same release bumps it; then follow the skill's Hydrogen upgrade steps). 2. Remove…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    Remove the ws and cookie overrides.

    line 22
  2. Very specific:

    Keep undici and qs unless the reasons below no longer hold:

    line 24
  3. Very specific:

    Run pnpm install, then confirm with pnpm why <package> and the GitHub advisory database (gh api …

    line 30
  4. Very specific:

    Verify with pnpm lint, pnpm typecheck, pnpm test, pnpm build:oxygen, and pnpm dev:oxygen or pnpm preview:oxygen, since MiniOxygen runs the …

    line 34
  5. Very specific:

    Update the comment above overrides in pnpm-workspace.yaml, and update or delete this section.

    line 37

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

Agent Notes

Load .agents/skills/remix-store/SKILL.md for app structure, conventions, and verification steps.

Pending Dependency Cleanup

Drop pnpm overrides once @shopify/mini-oxygen 4.3.0 ships

The overrides in pnpm-workspace.yaml patch vulnerable transitive dependencies of @shopify/mini-oxygen 4.2.3, which still runs Miniflare 3. Hydrogen merged the move to Miniflare 4 (Shopify/hydrogen#4245); it ships as @shopify/mini-oxygen 4.3.0 in the release from Shopify/hydrogen#4229.

Whenever you touch dependencies, check npm view @shopify/mini-oxygen version. Once it is 4.3.0 or newer:

  1. Bump @shopify/mini-oxygen in package.json (and @shopify/hydrogen if the same release bumps it; then follow the skill's Hydrogen upgrade steps).
  2. Remove the ws and cookie overrides. Miniflare 4 pins a patched ws and its youch 4 no longer depends on cookie.
  3. Keep undici and qs unless the reasons below no longer hold:
    • undici: Miniflare 4 pins 7.28.0, which is affected by advisories fixed in 7.29.1 and 7.30.1. Drop the override once pnpm why undici without it resolves only to a version with no open advisories.
    • qs: mini-oxygen depends on body-parser 1.20.4, which asks for qs ~6.14. Drop it once that range resolves to a patched release.
  4. Run pnpm install, then confirm with pnpm why <package> and the GitHub advisory database (gh api "/advisories?ecosystem=npm&affects=<package>") that nothing regresses. pnpm audit does not work through Shopify's package proxy.
  5. Verify with pnpm lint, pnpm typecheck, pnpm test, pnpm build:oxygen, and pnpm dev:oxygen or pnpm preview:oxygen, since MiniOxygen runs the local Worker.
  6. Update the comment above overrides in pnpm-workspace.yaml, and update or delete this section.

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.