agentleFS
Sign inStart free
AncienttwoAncienttwo/growth-hacker/skills/creative/video-production-agent-skill/CLAUDE.md

growth-hacker / video-production-agent-skill

CLAUDE.md1 starsChanged 5 months agoMITView on GitHub

Keep this file focused on the local contract for this primary functional block.

The file

We split this CLAUDE.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
  1. Distinctive:

    Keep this file focused on the local contract for this primary functional block.

    line 3
  2. Distinctive:

    Keep sibling CLAUDE.md and AGENTS.md files aligned.

    line 8
  3. Very specific:

    Treat .ai/context/context-map.json as the index of discoverable context files.

    line 11
  4. Distinctive:

    Do not keep pushing context files deeper by default.

    line 12
  5. Distinctive:

    Prefer repo-local workflow artifacts over tool-specific chat memory.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

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.md and AGENTS.md files aligned. Claude Code consumes CLAUDE.md; Codex consumes AGENTS.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.json as 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.

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