agentleFS
Sign inStart free
m-binimranm-binimran/marketing-pack/CLAUDE.md

marketing-pack

CLAUDE.md1 starsChanged 5 months agoMITView on GitHub

This is the repo for the pack itself. (To use the pack in your workspace, run an installer - see README.)

The file

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

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

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every item serves a goal: fewer tokens, accuracy, truth-telling, speed, quality/conversion/compliance.

    line 11
  2. Very specific:

    Hooks must be tested: add a case to tests/test_hooks.py and run python tests/test_hooks.py.

    line 14
  3. Distinctive:

    Truth: never push unsubstantiated claims or fabricated metrics.

    line 16
  4. Very specific:

    Keep rule/skill files short.

    line 17
  5. Very specific:

    Commit format <type>: <description>.

    line 26

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

CLAUDE.md - working ON marketing-pack

This is the repo for the pack itself. (To use the pack in your workspace, run an installer - see README.)

What this repo is

A full-stack Claude Code pack for marketers. Layers: rules/ (advisory) · skills/ (on-demand) · hooks/ (deterministic) · loops/ + commands/ (slash commands) · agents/ (review subagents) · mcp/ (optional connectors) · templates/. Full list in INVENTORY.md.

House rules for changing this repo

  • Every item serves a goal: fewer tokens, accuracy, truth-telling, speed, quality/conversion/compliance.
  • Compliance content must be correct + sourced (FTC, CAN-SPAM, GDPR/CCPA, platform policy). Never frame anything as legal advice.
  • Hooks must be tested: add a case to tests/test_hooks.py and run python tests/test_hooks.py. State the fail mode (open/closed) in the docstring.
  • Truth: never push unsubstantiated claims or fabricated metrics. New repo = 0 stars; no inflated claims.
  • Keep rule/skill files short. Update INVENTORY.md + CHANGELOG.md; add a commands/ wrapper for new skills/agents.

Verify

python tests/test_hooks.py        # 15 cases / 6 hooks
python -c "import json;json.load(open('hooks/settings.json'));json.load(open('mcp/.mcp.json'))"

Conventions

  • Commit format <type>: <description>. Hooks are Python 3.8+ (cross-platform). One logical change per PR.

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