agentleFS
jukanntennjukanntenn/harness-deepseek-harness/.agents/rfcs/implemented/AGENTS.md

harness-deepseek-harness / implemented

AGENTS.md2 starsChanged 40 days agoMITView on GitHub

These RFCs describe shipped decisions. Follow the root instructions, documentation standard, and RFC format; uv run hdsh rfc verify gates the lifecycle-specific structure. Keep paths, symbols, defaults, and mechanisms current in the same change that alters them. Rewrite stale facts in place; do not append change history. When a shipped RFC is unlikely to guide future work, archive its complete triplet through archiving-rfcs instead of continuing to maintain it. Update factual realization in place. A reversal of the decision or…

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep paths, symbols, defaults, and mechanisms current in the same change that alters them.

    line 7
  2. Very specific:

    When a shipped RFC is unlikely to guide future work, archive its complete triplet through archiving-rfcs instead of continuing to maintain …

    line 9
  3. Distinctive:

    Update factual realization in place.

    line 13

≈ “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 — Implemented RFCs

These RFCs describe shipped decisions. Follow the root instructions, documentation standard, and RFC format; uv run hdsh rfc verify gates the lifecycle-specific structure.

Keep an implemented RFC current with what actually shipped

Keep paths, symbols, defaults, and mechanisms current in the same change that alters them. Rewrite stale facts in place; do not append change history.

When a shipped RFC is unlikely to guide future work, archive its complete triplet through archiving-rfcs instead of continuing to maintain it.

This is not a license to rewrite the decision

Update factual realization in place. A reversal of the decision or its rationale requires a new RFC and cross-link; a fully superseded old RFC may be deleted only through the consolidation rule in the RFC rules.

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.