agentleFS
Sign inStart free
chrysogonuschrysogonus/prompt-maker-studio/frontend/AGENTS.md

prompt-maker-studio / frontend

AGENTS.md7 starsChanged 18 days agoApache-2.0View on GitHub

Next.js 16 (App Router), React 18, TypeScript 6. CSS Modules co-located with components (Component.tsx + Component.module.css). Tests co-located in __tests__/ subfolders using Vitest + Testing Library + jsdom. No Prettier — ESLint 9 flat config (eslint-config-next/core-web-vitals, see frontend/eslint.config.mjs) provides the lint rules. Run make lint-frontend (runs tsc --noEmit then ESLint). Inner loop: npm test in frontend/. make test-frontend wraps npm ci && npm run test:coverage — slower, but it's the gate that matches CI. Coverage floors live in vitest.config.ts. make…

  • 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,439 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 repository10 other files it gives its agents.

The file

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

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    No Prettier — ESLint 9 flat config (eslint-config-next/core-web-vitals, see frontend/eslint.config.mjs) provides the lint rules.

    line 5
  2. Distinctive:

    Use it for shared library loading/invalidation.

    line 22

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

frontend/ — agent operating notes

Next.js 16 (App Router), React 18, TypeScript 6. CSS Modules co-located with components (Component.tsx + Component.module.css). Tests co-located in __tests__/ subfolders using Vitest + Testing Library + jsdom.

No Prettier — ESLint 9 flat config (eslint-config-next/core-web-vitals, see frontend/eslint.config.mjs) provides the lint rules. Run make lint-frontend (runs tsc --noEmit then ESLint).

Inner loop: npm test in frontend/. make test-frontend wraps npm ci && npm run test:coverage — slower, but it's the gate that matches CI. Coverage floors live in vitest.config.ts. make lint-frontend also checks e2e/ and playwright.config.ts; npm run lint checks only src/.

API calls to the backend go through frontend/src/lib/api.ts — extend that rather than calling fetch ad hoc from components. The exceptions are src/lib/auth.ts (session and account endpoints) and LegalLinks, which reads the frontend's own /legal.json.

Feature UI, controllers and tests live under src/features/{editor,library,settings,auth,evaluation,gallery,tools}/. App Router pages stay thin; shared design primitives and the authenticated shell live under src/components/. Preserve presentation and browser storage keys during refactors.

src/lib/api.ts is the stable ApiClient facade; domain methods live in src/lib/api/. Its transport preserves explicit session-renewal opt-ins and rebuilds CSRF headers on retries. Keep password/auth failures distinguishable from session expiry.

LibraryDataProvider belongs inside the authenticated shell and is keyed by account. Use it for shared library loading/invalidation; keep pending undo mutations local until they commit. Never use a global cache for account data.

src/app/layout.tsx applies the stored theme before first paint on every route. Light is the app default; with no stored choice, public pages (isPublicPath in src/lib/theme.ts) follow the system. Preserve the unnamespaced theme key and explicit light/dark choices. The JWT stays in an HttpOnly cookie; browser storage contains session-expiry hints, preferences, and account-scoped drafts. Preserve draft recovery on session expiry and content cleanup on explicit sign-out.

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