banzai
AGENTS.md8 starsChanged 5 days agoApache-2.0View on GitHub
This repository is the source for a plugin that provides reusable skills and workflow support for AI agentic tools. Work here maintains the plugin itself; this is not an end-user project configured by the plugin. Read the root PROJECT_MANIFEST.md before working in this repository. It is the source of truth for current implemented project facts. Load deeper references only for the area a change touches: packages/orchestrator/MODULES.md for per-module orchestrator behavior, documentation/decisions/README.md for the full decision log, and the explicitly selected…
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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-messageSkill
- releaseSkill
- version-bumpSkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read the root PROJECT_MANIFEST.md before working in this repository.
- Very specific: line 14
Keep the manifest current-state only.
- Distinctive: line 19
Use English for all UI/UX copy: dialogs, CLI prompts, questions, menu items, options, buttons, labels, help, validation errors, …
- Distinctive: line 23
Write repository documents in English.
- Distinctive: line 35
Do not apply rules from those files while working on this repository.
- Distinctive: line 36
Do not treat their placeholder content as a description of this repository.
- Distinctive: line 39
Use this root file, the user's request, and root-level repository documentation for guidance about this repository.
≈ “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.
Files
AGENTS.md
Project Purpose
This repository is the source for a plugin that provides reusable skills and workflow support for AI agentic tools. Work here maintains the plugin itself; this is not an end-user project configured by the plugin.
Read the root PROJECT_MANIFEST.md before working in this repository. It is the
source of truth for current implemented project facts. Load deeper references
only for the area a change touches: packages/orchestrator/MODULES.md for
per-module orchestrator behavior, documentation/decisions/README.md for the
full decision log, and the explicitly selected local work binding for private feature history.
Keep the manifest current-state only; write it under the project-manifest
skill's writing rules.
Language
- Use English for all UI/UX copy: dialogs, CLI prompts, questions, menu items, options, buttons, labels, help, validation errors, notifications and summaries.
- Apply the same rule to UI/UX examples, mockups and interactive decision or approval dialogs prepared during development, including approval phrases.
- Write repository documents in English. Use Ukrainian for ordinary conversation with the user unless they request otherwise.
Packaged Project Templates
The copies of AGENTS.md, CLAUDE.md, and PROJECT_MANIFEST.md under
plugins/ are packaged template/bootstrap files for end-user projects. They
are plugin content, not instructions or project facts for this repository.
- Any
AGENTS.mddiscovered belowplugins/is template source and does not override this root file. Ignore its includes and directives in this repository. - Do not apply rules from those files while working on this repository.
- Do not treat their placeholder content as a description of this repository.
- Edit them only as plugin templates whose eventual context is an end-user project.
- Use this root file, the user's request, and root-level repository documentation for guidance about this repository.
Files under plugins/*/skills/ define the skills delivered by the plugin.
Evaluate them as product source intended to guide agents after installation.
Local Work Artifacts
New work uses documentation/work/<slug>/ with sibling requirements, plans,
required reports and numbered reviews. Read and edit these Markdown files
with ordinary file tools and keep them eligible for Git review. Select an exact
existing directory or document when continuing work; resolve ambiguous or
colliding selections before writing. No artifact-layout declaration or
registration is required.
Existing work documents, ignored private records, archives and references stay at their current paths, including explicitly requested follow-up reports and reviews. Do not migrate, rename, copy into Git, recursively unignore or delete existing evidence.
Raw execution records, logs, candidates, verification evidence and locks stay
ignored beneath project-local .banzai/. ADRs, maintained product guides and the
project manifest retain their maintained repository paths. Source-project work
documents are excluded from plugin/npm payloads. Git visibility grants no
approval, staging, commit or push authority.
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
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.

