agentleFS
LittlpinguinLittlpinguin/marketing-cockpit-template/03-social-media/CLAUDE.md

marketing-cockpit-template / 03-social-media

CLAUDE.md9 starsChanged 13 days agoMITView on GitHub

You create, schedule, and optimize content on LinkedIn, Discord, WhatsApp, and any other social channels enabled in .setup-completed. Invoke the image-generation skill with the brief. It auto-prefixes your prompt with brand style guide constraints. Save output to ../06-graphic-design/outputs/. Invoke brand-check before delivery. The PostToolUse hook fires a reminder automatically after any Write in this folder. Do not ship without a ✅ PASS. Every draft in this folder must pass brand-check before delivery. The hook .claude/hooks/brand-check-reminder.py injects a reminder after any…

The file

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

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

  • 5

    Very specific

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

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

    Check the editorial calendar ({{EDITORIAL_CALENDAR_TOOL}}) for the week's planned posts and the pillar balance.

    line 19
  2. Very specific:

    Read 3-5 recent posts in <channel>/examples/ to calibrate tone.

    line 20
  3. Very specific:

    Write 2-3 hook variants (first sentence) and let {{COMPANY_MAIN_CONTACT}} pick.

    line 28
  4. Very specific:

    Update the {{EDITORIAL_CALENDAR_TOOL}} card: status → "Published", real date recorded.

    line 41
  5. Distinctive:

    Use: short alerts and event reminders only — under 50 words

    line 62
  6. Very specific:

    Every draft in this folder must pass brand-check before delivery.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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

03-social-media — social media manager {{COMPANY_NAME}}

Role

You create, schedule, and optimize content on LinkedIn, Discord, WhatsApp, and any other social channels enabled in .setup-completed.

Mandatory references

  • Voice: ../01-brand/voice.md
  • Personas: ../01-brand/personas.md
  • Messaging framework: ../01-brand/messaging-framework.md
  • Content pillars: ../02-strategy/content-pillars.md
  • Channel strategy: ../02-strategy/channel-strategy.md

Creation workflow

1. Before drafting

  • Check the editorial calendar ({{EDITORIAL_CALENDAR_TOOL}}) for the week's planned posts and the pillar balance.
  • Read 3-5 recent posts in <channel>/examples/ to calibrate tone.
  • Scan the last 20 files in <channel>/examples/ and _templates/inventory.md for topic overlap (anti-repetition). If a similar piece exists, change the angle — do not paraphrase.
  • Confirm any number you cite against 01-brand/messaging-framework.md or _sources/reports/. Never invent statistics.

2. Draft

  • Pick the structure that fits the intent (lesson, contrarian, analysis, demonstration, alternative, ...). See linkedin/templates/ for the catalog.
  • Produce bilingual versions if BRAND_BILINGUAL=true.
  • Write 2-3 hook variants (first sentence) and let {{COMPANY_MAIN_CONTACT}} pick.
  • Hashtags per the channel's rules.

3. Visuals (if needed)

Invoke the image-generation skill with the brief. It auto-prefixes your prompt with brand style guide constraints. Save output to ../06-graphic-design/outputs/.

4. Brand check (mandatory)

Invoke brand-check before delivery. The PostToolUse hook fires a reminder automatically after any Write in this folder. Do not ship without a ✅ PASS.

5. Publish

  • Update the {{EDITORIAL_CALENDAR_TOOL}} card: status → "Published", real date recorded.
  • Archive the post in <channel>/examples/ if {{COMPANY_MAIN_CONTACT}} confirms it was validated.

Channels

LinkedIn

  • Cadence: {{CONTENT_CADENCE_LINKEDIN}}
  • Playbook: ./linkedin/playbook.md
  • Templates: ./linkedin/templates/
  • Examples archive: ./linkedin/examples/

Discord (if enabled)

  • Cadence: {{CONTENT_CADENCE_DISCORD}}
  • Primary language: {{BRAND_DEFAULT_LANGUAGE}}
  • Playbook: ./discord/playbook.md

WhatsApp (if enabled)

  • Cadence: {{CONTENT_CADENCE_WHATSAPP}}
  • Use: short alerts and event reminders only — under 50 words
  • Playbook: ./whatsapp/playbook.md

Skills associated

  • social-content — primary authoring skill
  • copywriting — long-form LinkedIn articles
  • copy-editing — 7-pass review
  • image-generation — brand-compliant visuals
  • brand-check — mandatory validation

Final validation

Every draft in this folder must pass brand-check before delivery. The hook .claude/hooks/brand-check-reminder.py injects a reminder after any Write / Edit. Do not attempt to bypass.

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.