Post

📜 introducing ossrules.md - learn how leading OSS projects use agent rule files - discover skill files that projects actually use - level up your own projects and workflows I've personally learned a lot just exploring

example use case: search skills for video generation skills (learn how these projects do it)

0 reposts2 likes

Went straight to the rule-file column: across the top twenty, five rows show CLAUDE.md and fifteen show AGENTS.md. Since Claude Code's default is to read AGENTS.md only when no CLAUDE.md exists, and you can opt into both, I can't tell from a row whether a project keeps both and the index picks one.

Makes sense for an import-only CLAUDE.md. The memory docs also have you add Claude-specific lines below that @AGENTS.md import, which leaves content in both files. Which column does a repo like that land in?

In repos I run this way, AGENTS.md holds the rules and CLAUDE.md is the @AGENTS.md import plus a few Claude-specific lines. Content-wise that is the AGENTS.md column. The shim is detectable too, grep for @AGENTS.md in CLAUDE.md, so the index can label it without judgment calls.