agentleFS
7xuanlu7xuanlu/wenlan/src/AGENTS.md

wenlan / src

AGENTS.md358 starsChanged 4 months agoApache-2.0View on GitHub

React 19 frontend for the Tauri app. This tree owns UI state, routing inside the desktop windows, i18n, browser-side preview compatibility, and the typed frontend side of the Tauri command contract. - TypeScript is strict and no-emit; pnpm build is tsc -b && vite build. Plain pnpm dev runs Vite on :1420 with strictPort set. - src/lib/tauri.ts is the frontend-to-Rust boundary. Add or update wrappers there before wiring components directly to a command. - Translation resources are the canonical fixed-copy…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. wenlan-app/wenlan★ 351100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 32,671 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 repository15 other files it gives its agents.

The file

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

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

  • 3

    Very specific

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

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

    Do not bypass lib/tauri.ts with raw invoke calls from components.

    line 42
  2. Very specific:

    Do not add hardcoded JSX copy without considering src/i18n/hardcodedCopyGuard.test.ts.

    line 43
  3. Very specific:

    Do not broaden the Vitest coverage gate accidentally.

    line 44
  4. Distinctive:

    Do not key behavior to placeholder text when i18n can change it.

    line 46

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

AGENTS.md - src/

OVERVIEW

React 19 frontend for the Tauri app. This tree owns UI state, routing inside the desktop windows, i18n, browser-side preview compatibility, and the typed frontend side of the Tauri command contract.

WHERE TO LOOK

TaskLocationNotes
New IPC wrapperlib/tauri.tscentralize invoke payloads and response defaults
Locale/copy changei18n/resources.tskeep parity across supported locales
Locale resolutioni18n/index.ts, i18n/locales.tshandles browser-safe language mapping
Agreed UX rules../docs/ux/spec.mdeach rule has an id; a shipped rule's test carries it in its name (uxSpec.test.ts checks)
Main memory UIcomponents/memory/AGENTS.mdnavigation, settings, citations, sources
Chat importcomponents/ChatImport/polling and notifications can hide failures
Onboardingcomponents/onboarding/focus trap, milestone cache, dismissal policy
Test harnesstest/setup.tsTauri API mocks and Testing Library setup

CONVENTIONS

  • TypeScript is strict and no-emit; pnpm build is tsc -b && vite build. Plain pnpm dev runs Vite on :1420 with strictPort set.
  • src/lib/tauri.ts is the frontend-to-Rust boundary. Add or update wrappers there before wiring components directly to a command.
  • Translation resources are the canonical fixed-copy inventory. New visible interface copy should be keyed in src/i18n/resources.ts and covered by the i18n tests when the key is behaviorally important.
  • Tests are colocated as *.test.ts / *.test.tsx, with some __tests__ folders for grouped component suites.
  • Vitest runs in jsdom with src/test/setup.ts. Do not require a real Tauri runtime from unit/component tests unless the test explicitly opts into it.
  • Tailwind v4 is configured through CSS and the Vite plugin. There is no separate Tailwind config file to update.
  • pnpm test:e2e is a Playwright surface outside this tree; use it for browser flows that unit tests cannot observe.

ANTI-PATTERNS

  • Do not bypass lib/tauri.ts with raw invoke calls from components.
  • Do not add hardcoded JSX copy without considering src/i18n/hardcodedCopyGuard.test.ts.
  • Do not broaden the Vitest coverage gate accidentally; vitest.config.ts intentionally whitelists only tested modules.
  • Do not key behavior to placeholder text when i18n can change it; use roles, labels, refs, or test ids as appropriate.

COMMANDS

pnpm exec tsc -b
pnpm test
pnpm test:i18n
pnpm test:e2e
pnpm test:coverage

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.