agentleFS
Sign inStart free
minorcellminorcell/memo-code/site/AGENTS.md

memo-code / site

AGENTS.md29 starsChanged 9 months agoMITView on GitHub

This file defines local contribution rules for web. The site supports multiple languages via next-intl:

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

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep app behavior consistent on desktop and mobile breakpoints.

    line 8
  2. Distinctive:

    If public docs content, navigation, or examples change, keep related docs in sync.

    line 12
  3. Very specific:

    Keep web docs aligned with current package boundaries (packages/tui contains CLI entry and interactive UI runtime).

    line 13
  4. Very specific:

    Add locale to lib/i18n/config.ts

    line 36
  5. Very specific:

    Create message file lib/i18n/messages/{locale}.json

    line 37
  6. Very specific:

    Create content directories content/docs/{locale}/ and content/blog/{locale}/

    line 38
  7. Distinctive:

    When updating page text, update all language message files

    line 43
  8. Distinctive:

    When updating MDX content, update all language versions

    line 44

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

Web Package Guide

This file defines local contribution rules for web.

Scope

  • Owns Next.js pages, components, and web-facing docs/presentation layer.
  • Keep app behavior consistent on desktop and mobile breakpoints.

Change Rules

  • If public docs content, navigation, or examples change, keep related docs in sync.
  • Keep web docs aligned with current package boundaries (packages/tui contains CLI entry and interactive UI runtime).
  • Preserve established UI patterns unless a deliberate design change is required.
  • 需要维护agents.md的更新。

Internationalization (i18n)

The site supports multiple languages via next-intl:

  • Supported locales: en (default), zh
  • URL pattern: /{lang}/path (e.g., /en/docs, /zh/docs)
  • Content structure:
    • Page text translations: lib/i18n/messages/{locale}.json
    • MDX docs: content/docs/{locale}/
    • MDX blog: content/blog/{locale}/

i18n Configuration Notes

  • No middleware: Static export (output: 'export') doesn't support middleware, so locale detection is handled via URL path
  • Locale from URL: The [lang] dynamic route segment provides the locale
  • Suppress hydration warning: Both layout.tsx files have suppressHydrationWarning on <html> to handle lang attribute differences

Adding a new language

  1. Add locale to lib/i18n/config.ts
  2. Create message file lib/i18n/messages/{locale}.json
  3. Create content directories content/docs/{locale}/ and content/blog/{locale}/
  4. Translate all MDX files

Modifying content

  • When updating page text, update all language message files
  • When updating MDX content, update all language versions

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