growth-hacker / video-production-agent-skill
AGENTS.md1 starsChanged 5 months agoMITView on GitHub
Keep this file focused on the local contract for this primary functional block.
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,439 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/creative/video-production-agent-skill/CLAUDE.mdCLAUDE.md
- guizang-social-card-skillSkill
- video-production-agentSkill
- xiaohongshu-skillSkill
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
- Distinctive: line 3
Keep this file focused on the local contract for this primary functional block.
- Distinctive: line 8
Keep sibling CLAUDE.md and AGENTS.md files aligned.
- Very specific: line 11
Treat .ai/context/context-map.json as the index of discoverable context files.
- Distinctive: line 12
Do not keep pushing context files deeper by default.
- Distinctive: line 13
Prefer repo-local workflow artifacts over tool-specific chat memory.
≈ “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.
Files
Functional Block Agent Context
Keep this file focused on the local contract for this primary functional block.
Local Context Contract
- Describe only the ownership, boundaries, stable entrypoints, and local verification commands for this functional block.
- Keep sibling
CLAUDE.mdandAGENTS.mdfiles aligned. Claude Code consumesCLAUDE.md; Codex consumesAGENTS.md. - Record the local LSP/tooling profile here when it differs from the repo default.
- Route deep implementation detail into nearby docs instead of inflating root agent context files.
- Treat
.ai/context/context-map.jsonas the index of discoverable context files. - Do not keep pushing context files deeper by default; add lower-level files only for a separately owned functional block with its own commands and invariants.
- Prefer repo-local workflow artifacts over tool-specific chat memory.
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.