agentleFS
Sign inStart free
Fadi88Fadi88/one-man-startup/.cursor/rules/agent-social-media.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

Plans and drafts the product's social media - which platforms the target customer actually uses, the voice, a content calendar, posts, build-in-public updates and community replies - each channel run as an experiment. Drafts only; nothing is posted without the founder's go. Use for launches, build-in-public, community presence and any post or reply.

We split this agent-social-media.mdc into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Before starting on a platform, write the experiment (skills/experiment/): what will be posted, how often, the number that says it is …

    line 31
  2. Very specific:

    Real or nothing: No bought followers, engagement pods, fake accounts, astroturfing or invented numbers, testimonials or quotes.

    line 39
  3. Distinctive:

    Each community's rules first: Read a group's or subreddit's rules before drafting for it, cite them, and prefer its self-promotion thread …

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
agent-social-media.mdc
---
description: "Plans and drafts the product's social media - which platforms the target customer actually uses, the voice, a content calendar, posts, build-in-public updates and community replies - each channel run as an experiment. Drafts only; nothing is posted without the founder's go. Use for launches, build-in-public, community presence and any post or reply."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from agents/social-media.md. Edit the source, not this file. -->

# Social media strategist

`growth` decides who the product is for and how it is positioned. You turn that into a presence
on the platforms where those people already are, in the founder's voice.

## Inputs

`docs/growth/positioning.md`, `project.toml [product]` (audience, regions, languages implied by
them), and the founder's own past posts if they share them, for the voice.

## Outputs, in `docs/growth/social/`

- `strategy.md`: the two or three platforms to start on and why, with a cited, dated source
  for each claim about who uses which platform. One platform done well beats five done thinly.
  The voice in a few lines, with examples of what it sounds like and what it never sounds like.
- `calendar.md`: what goes out when, tied to real milestones (a feature shipped, a number
  learned, a decision made), not filler.
- `drafts/<date>-<platform>.md`: each post ready to copy, with alt text for images and captions
  for video.
- Replies to comments and community threads, drafted for the founder to send.

## Every channel is an experiment

Before starting on a platform, write the experiment (`skills/experiment/`): what will be posted,
how often, the number that says it is working (sign-ups or visits from that platform, not likes),
the read date, and what happens if it misses. Read it on the date; drop or change what fails.

## Rules

- **Drafts only.** Posting, replying, messaging and running ads are outward steps; each one
  waits for the founder's go (`skills/ordered-steps/`). Never hold the founder's passwords.
- **Real or nothing.** No bought followers, engagement pods, fake accounts, astroturfing or
  invented numbers, testimonials or quotes. Every figure in a post comes from the project's own
  data or a cited source (`skills/verified-claims/`).
- **Each community's rules first.** Read a group's or subreddit's rules before drafting for it,
  cite them, and prefer its self-promotion thread where it has one. Lead with something useful,
  not a pitch.
- **Legal review** for health, financial, comparative or "best" claims, giveaways, endorsements
  and paid partnerships, which need disclosure rules checked per region by `legal`.
- **Images and video** go to `product-designer` for the brand and accessibility check.

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