agentleFS
Sign inStart free
TerminallyLazyTerminallyLazy/Tree-Ring-Memory/marketing/AGENTS.md

Tree-Ring-Memory / marketing

AGENTS.md18 starsChanged 3 months agoMITView on GitHub

Public campaign and visual source material. Campaign folders, image/video assets and editorial copy. Keep source/editable artifacts distinguishable from exports. Describe only verified runtime and release capabilities. Preserve approved visual direction and source attribution. Do not include private project data. Inspect changed renders and check referenced public links; no separate automated marketing gate is defined. None. This document owns the full subtree.

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

The file

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep source/editable artifacts distinguishable from exports.

    line 13

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

marketing

Purpose

Public campaign and visual source material.

Ownership

Campaign folders, image/video assets and editorial copy.

Local Contracts

Keep source/editable artifacts distinguishable from exports. Describe only verified runtime and release capabilities.

Work Guidance

Preserve approved visual direction and source attribution. Do not include private project data.

Verification

Inspect changed renders and check referenced public links; no separate automated marketing gate is defined.

Child DOX Index

None. This document owns the full subtree.

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