agentleFS
Sign inStart free
ErionisErionis/Jarvis-Lite/AGENTS.md

Jarvis-Lite

AGENTS.md3 starsChanged 3 months agoMITView on GitHub

This file guides maintainers and coding agents working on this repository. It is not packaged for consumers: the build copies the thin consumer adapter at starter/AGENTS.md, whose behavior is defined by the starter core instructions. - Start with the public promise, the contribution workflow, the architecture, and provenance. - Treat skills/ as the skill source, scripts/build_starter.py as the package builder, and tests/ as executable repository contracts. - Use CI and the pull-request template to prepare review evidence. Follow the full…

  • 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,542 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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with the public promise, the contribution workflow, the architecture, and provenance.

    line 10
  2. Very specific:

    Treat skills/ as the skill source, scripts/build_starter.py as the package builder, and tests/ as executable repository contracts.

    line 12
  3. Distinctive:

    Use CI and the pull-request template to prepare review evidence.

    line 15
  4. Distinctive:

    Follow the full process in CONTRIBUTING.md: issue, short-lived branch, focused test, full validation, public-only review, pull request, …

    line 20
  5. Distinctive:

    Every core, skill, starter, build, or release change must classify its documentation impact.

    line 24

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

Repository maintainer guide

This file guides maintainers and coding agents working on this repository. It is not packaged for consumers: the build copies the thin consumer adapter at starter/AGENTS.md, whose behavior is defined by the starter core instructions.

Orient yourself

  • Start with the public promise, the contribution workflow, the architecture, and provenance.
  • Treat skills/ as the skill source, scripts/build_starter.py as the package builder, and tests/ as executable repository contracts.
  • Use CI and the pull-request template to prepare review evidence.

Change flow

Follow the full process in CONTRIBUTING.md: issue, short-lived branch, focused test, full validation, public-only review, pull request, then squash merge. Keep this guide as navigation and do not duplicate that workflow.

Every core, skill, starter, build, or release change must classify its documentation impact. When no durable document needs revision, record No documentation impact and explain why; otherwise update the canonical owner.

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