agentleFS
Sign inStart free
matteotittamatteotitta/claude-code-marketing-quickstart/CLAUDE.md

claude-code-marketing-quickstart

CLAUDE.md70 starsChanged 11 days agoMITView on GitHub

This is a marketing workspace for one company. Read this file first.

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

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read the relevant files in context/: at least icp/, positioning/ and messaging/, plus brand/ for anything public.

    line 7
  2. Distinctive:

    If a context file you need is empty, say so and offer to run the skill that fills it.

    line 8
  3. Distinctive:

    Keep each CLAUDE.md to one page.

    line 14
  4. Very specific:

    Write in the voice in context/brand/.

    line 15

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

How to work in this repo

This is a marketing workspace for one company. Read this file first.

Before you write anything

  1. Read the relevant files in context/: at least icp/, positioning/ and messaging/, plus brand/ for anything public.
  2. If a context file you need is empty, say so and offer to run the skill that fills it. Don't invent the missing facts.
  3. Save work to outputs/<lane>/ and name files MMYY-topic.md, for example 1026-launch-plan.md.

House rules

  • Source every claim, and mark guesses as guesses. Never invent numbers, quotes or customers.
  • Keep each CLAUDE.md to one page. They are maps, not documents.
  • Write in the voice in context/brand/. If there isn't one, write plainly and say so.

Map

  • context/: what's true about the company
  • outputs/: what we ship
  • example/pulse-analytics/: a filled-in example. Copy its shape, never its facts

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. matteotitta/repo-structure-in-house★ 70100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

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