agentleFS
Sign inStart free
nikshipsnikships/droidproxy/windows-wip/AGENTS.md

droidproxy / windows-wip

AGENTS.md128 starsChanged 5 months agoMITView on GitHub

These instructions apply only to windows-wip/. This folder is a Windows-only Electron app for DroidProxy. Keep it isolated from the macOS Swift app in ../src. Run commands from windows-wip/: Use npm run check as the default validator for code changes.

  • Installs packages
  • 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,700 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 repository5 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run commands from windows-wip/:

    line 13
  2. Very specific:

    Use npm run check as the default validator for code changes.

    line 22
  3. Very specific:

    Treat src/ and resources/ as the source of truth.

    line 26
  4. Very specific:

    Do not edit node_modules/, dist/, or packaged build outputs.

    line 27
  5. Distinctive:

    Keep Factory custom-model writes GPT-only unless the Windows app scope changes.

    line 28
  6. Distinctive:

    Prefer small, Windows-specific changes that do not affect the repo root macOS app.

    line 29

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

AGENTS.md

Scope

These instructions apply only to windows-wip/.

Project

This folder is a Windows-only Electron app for DroidProxy. Keep it isolated from the macOS Swift app in ../src.

Commands

Run commands from windows-wip/:

npm install
npm start
npm run check
npm run build:win

Use npm run check as the default validator for code changes.

Conventions

  • Treat src/ and resources/ as the source of truth.
  • Do not edit node_modules/, dist/, or packaged build outputs.
  • Keep Factory custom-model writes GPT-only unless the Windows app scope changes.
  • Prefer small, Windows-specific changes that do not affect the repo root macOS app.

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