agentleFS
opencollectiveopencollective/opencollective-frontend/AGENTS.md

opencollective-frontend

AGENTS.md897 starsChanged 52 days agoMITView on GitHub

Next.js/React UI. Prefer user-facing "Contribution" over "Order", and "Account" over "Collective" where the GraphQL API uses Account. Tailwind+ShadCN (primary), Styled Components/Styled System (legacy; do not add new usage). Lucide (primary), Styled Icons (legacy). Apollo Client, Formik+Zod (FormikZod wraps Formik with Zod), React Intl. Jest/RTL + Cypress E2E. When a feature also changes opencollective-api, use the same branch name in both repositories and push both branches. E2E CI in either repository automatically checks out the matching branch in the other repository…

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a feature also changes opencollective-api, use the same branch name in both repositories and push both branches.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

opencollective-frontend

Next.js/React UI. Prefer user-facing "Contribution" over "Order", and "Account" over "Collective" where the GraphQL API uses Account.

Stack

Tailwind+ShadCN (primary), Styled Components/Styled System (legacy; do not add new usage). Lucide (primary), Styled Icons (legacy). Apollo Client, Formik+Zod (FormikZod wraps Formik with Zod), React Intl. Jest/RTL + Cypress E2E.

Rules

  • Reuse existing i18n strings (workspace skill search-i18n-translations). English source: lang/en.json. After i18n source changes, npm run build:langs and npm run langs:check.
  • New UI: Tailwind/ShadCN and Lucide, not styled-components or Styled Icons.

Cross-repository features

When a feature also changes opencollective-api, use the same branch name in both repositories and push both branches. E2E CI in either repository automatically checks out the matching branch in the other repository when available, falling back to main otherwise.

Quality

From this repo: npm run type:check, npm run lint:quiet, npm run prettier:check (fix: prettier:write), npm run ts-unused-exports. Tests: Jest (npm run test); E2E Cypress + Playwright pilot (docs/e2e.md, test/playwright/README.md). Schema/codegen: npm run graphql:update (API must be running).

Playwright E2E (pilot)

Fresh Linux reproduction: ./test/playwright/run-local.sh --spec test/playwright/specs/smoke.spec.ts. Uses disposable opencollective_pw_e2e by default; explicit service paths via --api-dir/--frontend-dir/--images-dir/--pdf-dir for worktrees. Evidence: test/playwright/.artifacts/<run-id>/replay-manifest.json plus owned service logs. Replay: --replay <manifest> (validates inputs, runs fresh). Iteration: --reuse (joins live env, no reset). Cleanup: --cleanup (refuses while active users remain). Mutable journeys: test/playwright/fixtures (test, scenarioTest) with API recipes; pilot specs in test/playwright/specs/**. Upload journeys need a frontend built with DISABLE_MOCK_UPLOADS=1 (docs/e2e.md). CI pilot (CI / e2e-playwright / playwright smoke): observational, same launcher; failure evidence 14d, success 7d.

Download now (ZIP)

  • 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 28,693 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 repositoryOne other file it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.