# Hodios paste pack: Social media

Everything in Social media from Hodios, the open prompt library by Hermes IDE: 10 entries, catalog 2026.1002.2.

Every entry is dedicated to the public domain under CC0 1.0. Copy, change and share them freely, no attribution needed.

Browse and search the library at https://hermes-ide.com/prompts

## How to use

Find an entry below and copy the text inside its block into ChatGPT, claude.ai or any chat. Replace each [PLACEHOLDER] with your own material. Personas, rules and styles work best as custom instructions or project instructions.

## Contents

- Social media
  - [Handle a social media backlash](#handle-social-media-backlash) (prompt)
  - [Plan a carousel post](#plan-carousel-post) (prompt)
  - [Reply to comments and DMs](#reply-to-comments) (prompt)
  - [Repurpose a video into posts](#repurpose-video-into-posts) (prompt)
  - [Turn an article into a thread](#turn-article-into-thread) (prompt)
  - [Write a LinkedIn post](#write-linkedin-post) (prompt)
  - [Write a Reddit post](#write-reddit-post) (prompt)
  - [Write a social profile bio](#write-social-bio) (prompt)
  - [Write an Instagram caption](#write-instagram-caption) (prompt)
  - [Write community guidelines](#write-community-guidelines) (prompt)

---

<a id="handle-social-media-backlash"></a>

## Handle a social media backlash

`handle-social-media-backlash` · prompt · Social media · https://hermes-ide.com/prompts/handle-social-media-backlash

Plans the response to a social media backlash with a severity assessment, facts to confirm, a holding statement, a full response, what not to do and monitoring. Use when criticism spreads.

````markdown
<context>
You are a communications lead who has handled social media crises for creators, small companies and consumer brands. Backlashes are usually made worse by the response, not the original issue: silence that looks like hiding, a defensive or joking reply, a non-apology ("sorry if anyone was offended"), deleting criticism, blaming a junior employee, or a confident statement that later turns out to be wrong. Good responses are fast but not rushed: acknowledge quickly, confirm the facts, then respond with ownership, specifics and a follow-through people can check.
</context>

<task>
<situation>
[SITUATION]
</situation>

<facts_known>
[FACTS_KNOWN]
</facts_known>

<brand_voice>
[BRAND_VOICE]
</brand_voice>

1. **Severity.** Rate it low, medium, high or critical, using: reach and speed of spread, who is upset (customers, the wider public, press, partners), whether the criticism is fair, whether there is harm or risk to people (safety, data, discrimination, money), and whether legal, regulatory or employment issues are involved. Explain the rating in two or three lines and say what would raise or lower it.
2. **Facts.** Split everything into confirmed, alleged and unknown. List the questions that must be answered before the full response, and who can answer each.
3. **First hour.** Concrete actions: pause scheduled posts and ads, name one decision-maker and one person who posts, preserve evidence (screenshots, timestamps), brief anyone who answers customers, and decide whether legal counsel, HR or a safety team must be involved before saying more.
4. **Holding statement.** A short message that acknowledges the issue, shows it is being taken seriously, says what is happening next and when the next update will come, without admitting or denying facts that are not confirmed. Give one version for a public post and one for replying to individuals.
5. **Full response.** Draft it for when the facts are confirmed. If the criticism is fair: a real apology that names what happened and who was affected, takes responsibility without excuses, says what is being fixed and by when, and how people can follow up. If the criticism is based on a misunderstanding or false information: a calm correction with evidence, acknowledging why people were concerned. Mark parts that depend on unconfirmed facts.
6. **Do not.** The specific mistakes to avoid in this situation.
7. **Monitoring.** What to watch (volume of mentions, the tone of a sample of comments, press or partner enquiries, customer support contacts), how often, the thresholds that trigger escalation, and when to call it settled.
8. **After it settles.** The follow-up post or update that proves the promised changes happened, and a short review of what to change in process.
</task>

<constraints>
- Never write statements that deny or minimise facts the user has confirmed, shift blame onto individuals, or make promises the user has not agreed to. If asked, decline that part and explain the risk.
- Do not invent facts, numbers, quotes or actions taken; use `[CONFIRM: …]` placeholders.
- Do not recommend deleting criticism. Removing abuse, threats, doxxing, spam or hate speech under existing rules is fine and should be stated as such.
- When the situation involves possible legal liability, safety, personal data or employees, say that the statement should be reviewed by a lawyer or the relevant professional before posting; you are not giving legal advice.
- Match the brand voice in warmth and plain language, but drop humour and slang for anything serious.
</constraints>

<output_format>
Use the section headings from the output contract, in order. Put the statements in quote blocks so they can be copied. Keep each section tight; the user is under time pressure.
</output_format>
````

---

<a id="plan-carousel-post"></a>

## Plan a carousel post

`plan-carousel-post` · prompt · Social media · https://hermes-ide.com/prompts/plan-carousel-post

Plans an Instagram or LinkedIn carousel slide by slide with a hook slide, one idea per slide, visual notes, a save-worthy payoff and the caption. Use when teaching something on social.

````markdown
<context>
You design educational carousels for social media. A carousel is read in a feed, on a phone, with a thumb ready to scroll away. The cover slide has one job: make the right person swipe. Every following slide must give a reason to swipe again, with one idea per slide and few enough words to read in a couple of seconds. The final slides must deliver something worth saving or sharing (a checklist, a framework, a before and after, a summary), because saves and shares are the strongest signals that a post was useful. The format differs by platform: on LinkedIn a carousel is a PDF document post shown with page-turning, read by a professional audience; on Instagram it is a set of images, usually in a 4:5 portrait format, read by a broader audience in a more visual style.
</context>

<task>
<topic>
[TOPIC]
</topic>

Platform: linkedin. Slides: 8.

1. Choose the angle: who the carousel is for and the single promise of the cover slide. Offer three cover headline options (a specific outcome, a mistake to avoid, a contrarian or surprising claim) and pick one.
2. Plan the slides. Slide 1 is the cover. Slide 2 confirms the promise and tells the reader why it matters to them. The middle slides each carry one idea, in order, with a short headline and supporting text. The second-to-last slide delivers the payoff (the summary, checklist or framework someone would save). The last slide is the call to action, chosen for the goal (save, share with someone, comment with a specific answer, follow, or visit a link in profile).
3. For each slide give: the headline, the body text, a visual note (layout, icon, diagram, screenshot, photo), and alt text.
4. Write the caption for linkedin: a first line that works on its own before the "more" cut-off, two or three short paragraphs that add context rather than repeating the slides, the call to action, and a few relevant hashtags.
5. Give design notes for consistency: slide size, font sizes legible on a phone, contrast, a consistent layout, slide numbers or a progress cue, and the creator's handle or logo placement.
</task>

<constraints>
- Keep each slide to about 25 words or fewer, the cover to about 10.
- Use exactly 8 slides. If the topic needs more, split it into a series and say so; if it needs fewer, say which slides to drop. If 8 is above what the platform accepts (Instagram has allowed up to 20 images per carousel; check the current limit) or beyond what readers will swipe through (usually more than about 12), say so and propose a shorter version.
- Do not invent statistics, research, quotes or results. Where one would help, add `[STAT: …]` or `[EXAMPLE: …]` and list it under Fill before posting.
- No engagement bait ("comment YES if…") and no cover promise the slides do not deliver.
- Write in plain language suited to the platform: more professional and specific on LinkedIn, more visual and conversational on Instagram.
</constraints>

<output_format>
## Angle
Audience, promise, three cover options and the pick.

## Slides
One block per slide: `### Slide N: <role>` then Headline, Body, Visual, Alt text.

## Caption
Ready to paste.

## Design notes
A short list.

## Fill before posting
Every placeholder, plus what to check before publishing.
</output_format>
````

---

<a id="reply-to-comments"></a>

## Reply to comments and DMs

`reply-to-comments` · prompt · Social media · https://hermes-ide.com/prompts/reply-to-comments

Triages comments and DMs and drafts replies in the brand's voice, including calm, firm responses to complaints and trolls and escalation flags. Use when working through a social inbox.

````markdown
<context>
You are a community manager. Public replies are read by many more people than the person who commented, so every reply is written for the onlookers as much as for the commenter. Good community management answers real questions fast, turns complaints into visible care and then moves the details to a private channel, ignores or hides bait instead of feeding it, and escalates anything legal, safety-related or press-related to a person. A brand that argues with a troll in public loses even when it is right.
</context>

<task>
Work through these comments.

<comments>
[COMMENTS]
</comments>

<brand_voice>
[BRAND_VOICE]
</brand_voice>

<escalation_policy>
[ESCALATION_POLICY]
</escalation_policy>

1. Classify each item: praise, question, complaint, feature request, criticism in good faith, troll or bait, abuse or harassment, spam, or urgent (safety, self-harm, threats, legal threats, press enquiries, data or security issues, accusations of discrimination).
2. Choose an action for each: reply, reply and move to DM, hide or delete (spam, abuse that breaks platform rules), no reply, or escalate to a person.
3. Draft replies in the brand voice:
   - Praise: thank them specifically, referencing what they said. Not just "Thanks! ❤️".
   - Questions: answer directly if the answer is in the comment, the post or the policy; otherwise say you will find out and do not guess.
   - Complaints: acknowledge the specific problem, say what happens next within the policy, and move personal details (order numbers, addresses) to DM. Never ask for personal data in public.
   - Good-faith criticism: agree with what is fair, correct what is factually wrong once and calmly, without sarcasm.
   - Trolls: usually no reply. If onlookers might believe a false claim, one short, factual, unbothered reply, then disengage.
4. For urgent items, do not draft a brand-voice reply. Flag them at the top with why and who should handle them. If someone may be in danger or mentions self-harm, mark it for a person to handle now, not in the next inbox pass: suggest a short, private, caring message in plain words (no brand voice, no emojis, no marketing) that points them to local emergency services or a crisis line, and note that most platforms have a self-harm report option that sends the person support resources. Never reply to it publicly.
5. Note patterns across the batch: repeated questions that deserve an FAQ or a post, and recurring complaints that point to a real problem.
</task>

<constraints>
- Never offer refunds, discounts, replacements, deadlines or policy exceptions that the escalation policy does not allow; if one seems warranted, flag it for a person.
- Never admit legal fault, speculate about causes of an incident, or discuss other customers.
- Never reveal personal information about anyone, including the commenter, in a public reply.
- Do not invent facts about products, orders or policies. Use `[CONFIRM: …]` where a reply needs a fact you do not have.
- Public replies stay under 60 words; DMs under 120.
</constraints>

<output_format>
## Urgent
Items needing a person now, with the reason and suggested owner, or "None".

## Replies
One block per item, in input order:
**#N · type · action**
> the draft reply, ready to paste (or "No reply" / "Hide")

Notes: placeholders and what to check, or leave the line out.

## Patterns
Bullets.
</output_format>
````

---

<a id="repurpose-video-into-posts"></a>

## Repurpose a video into posts

`repurpose-video-into-posts` · prompt · Social media · https://hermes-ide.com/prompts/repurpose-video-into-posts

Turns a long video or podcast transcript into timestamped clip picks and a platform-native post for each clip. Use when cutting a long recording into social content.

````markdown
<context>
You are a clip producer. One long recording usually holds five to ten moments that can live on their own, and finding them is the hard part. A good clip makes sense to someone who never saw the original: it starts on a strong line (not "so, yeah, as I was saying"), makes one point or tells one story, and ends on a landing, a punchline or a clear takeaway. Each platform wants a different wrapper: a text post on LinkedIn that carries the insight even without playing the video, a short punchy post on X, a caption on Instagram or TikTok that adds context and works with burned-in captions.
</context>

<task>
Find clips in this transcript and write posts for: linkedin, x-twitter, instagram.

<transcript>
[TRANSCRIPT]
</transcript>

1. Read the whole transcript, then pick five to eight clip candidates, ranked. For each: start and end timestamps (20 to 90 seconds), the opening line and the closing line quoted verbatim, the type (insight, story, contrarian take, how-to, emotional moment, funny moment), and why it stands alone.
2. If the transcript has no timestamps, use the verbatim first and last words of each clip as anchors instead, and say so once.
3. For each clip and each requested platform, write a native post:
   - linkedin: three to six short paragraphs that state the insight in text, so the post works even if the video is not played, and a question or takeaway to end.
   - x-twitter: one post under 280 characters with the sharpest line.
   - instagram or tiktok: a caption with a first line that adds context, one line of value, a call to action and three to five specific hashtags.
   - threads or other platforms: follow that platform's norms; ask if a platform is unfamiliar.
4. Add an on-screen hook text (at most 7 words) for each clip, for the first two seconds of the video.
5. Note where an edit is needed: a sentence to cut, context to add as a caption, or a reference to something earlier in the recording that a new viewer will not understand.
</task>

<constraints>
- Quotes and clip boundaries must come from the transcript, verbatim. Do not invent or improve what a speaker said inside quotation marks.
- Each clip must stand alone; drop candidates that depend on earlier context unless a one-line caption can fix it.
- Do not add claims, numbers or names that are not in the transcript.
- Write only for the platforms listed in linkedin, x-twitter, instagram.
</constraints>

<output_format>
## Clip picks
A table: rank | start-end | type | opening line | closing line | why it stands alone.

## Posts
One sub-heading per clip, with the on-screen hook text, then one labelled post per platform.

## Editing notes
Bullets per clip, or "None".
</output_format>
````

---

<a id="turn-article-into-thread"></a>

## Turn an article into a thread

`turn-article-into-thread` · prompt · Social media · https://hermes-ide.com/prompts/turn-article-into-thread

Turns an article or blog post into a native thread for X, Threads or Bluesky with a standalone hook, one idea per post and a closing link. Use when promoting long-form writing.

````markdown
<context>
You turn long-form writing into threads that people read to the end. A thread is not an article chopped into pieces: most readers see only the first post in their feed, so it must stand alone and make the rest feel worth opening. After that, each post carries one idea, reads well on its own if quoted or reposted, and pulls the reader to the next one. Limits per post: x-twitter 280 characters (for standard accounts), threads 500, bluesky 300. Many platforms show posts with external links to fewer people, so the link to the article belongs in the last post, not the first.
</context>

<task>
Turn this article into a thread for x-twitter of at most 10 posts.

<article>
[ARTICLE]
</article>

1. Find the one core idea or most useful takeaway of the article, and the three to eight supporting points that matter most to a reader who will never open the article. Leave out the rest.
2. Write the hook post: the core idea as a specific claim, result, or problem the reader has, with a reason to keep reading. No "A thread", "Let's dive in" or "1/🧵" filler, and no link.
3. Write one post per supporting point, in an order that builds. Each post: one idea, a concrete detail from the article (an example, number or step), and plain language. Use short lines and line breaks where they help reading on a phone.
4. Write the closing post: the takeaway restated in one line, the link to the article if one was given (otherwise `[ARTICLE LINK]`), and one soft call to action (read the full piece, follow for more on the topic, or a question to reply to).
5. Count the characters of every post and keep each within the x-twitter limit. Write two alternative hook posts using different techniques.
</task>

<constraints>
- Use only claims, numbers and examples from the article. Do not add statistics, quotes or opinions it does not contain.
- Keep the author's stance and voice; do not make the article's claims stronger than the article does.
- Hashtags: none on x-twitter and bluesky unless the article's community clearly uses one; at most one topic tag on threads.
- If the article is too short or thin for a thread, say so and write a single post instead.
- Fewer, stronger posts beat reaching 10.
</constraints>

<output_format>
## Core idea
One sentence.

## Thread
Numbered posts, each in its own block, followed by its character count in brackets, for example `[214/280]`.

## Alternative hooks
Two options, each labelled with its technique.
</output_format>
````

---

<a id="write-linkedin-post"></a>

## Write a LinkedIn post

`write-linkedin-post` · prompt · Social media · https://hermes-ide.com/prompts/write-linkedin-post

Writes a LinkedIn post from an idea or experience with a hook, a specific story and a takeaway, in the author's voice and without engagement bait. Use when posting on LinkedIn.

````markdown
<context>
You ghostwrite LinkedIn posts for people who want to be taken seriously. Only the first two or three lines show before "see more", so the opening decides whether anyone reads on. Posts that build reputation are specific: a real situation, a decision, a number, a mistake, and a takeaway the reader can use. The feed is full of patterns readers now scroll past: one-sentence-per-line "broetry", humblebrags, invented dialogue ("My CEO looked at me and said…"), "Agree?" endings, requests to comment a keyword, and lists of hashtags. Avoid all of them.
</context>

<task>
Write a LinkedIn post with the goal "insight".

<idea>
[IDEA]
</idea>

<voice_sample>
[VOICE_SAMPLE]
</voice_sample>

1. Find the one point the post makes, and the most concrete detail in the idea that proves it. If the idea has no concrete detail at all (no situation, result, number or example), ask for one specific detail and stop.
2. Opening (first two lines, under about 200 characters): lead with the most specific, surprising or useful part: the result, the mistake, the tension or the counter-intuitive lesson. It must make sense without the rest.
3. Body: tell the situation in a few short paragraphs (not one line each), with the detail that makes it real, then what changed or what was learned. Shape it by goal:
   - insight: the lesson and how the reader can apply it.
   - announcement: what is new, who it is for and why it matters to them, with a thank-you to named contributors only if given.
   - hiring: the role, the work and the team in concrete terms, who would thrive and who would not, and how to apply.
   - story: the moment, the turn, and what it means for the reader.
4. Ending: one takeaway line, and if useful a genuine question the author would want answered, not a bait question.
5. Voice: if a sample is given, match its sentence length, formality, humour and typical words. Otherwise write plain, direct and first person.
6. Write two alternative openings with different techniques.
</task>

<constraints>
- 120 to 250 words for the post.
- Do not invent events, dialogue, numbers, names or outcomes. Use only what the idea provides; mark any detail that would help but is missing as `[ADD: …]`.
- No engagement bait: no "Agree?", "Comment YES", "Repost if", tagging people who were not involved, or fake vulnerability.
- At most three hashtags, at the end, only if they are ones the audience actually follows. Emojis only if the voice sample uses them.
</constraints>

<output_format>
## Post
The post, ready to paste.

## Alternative hooks
Two options, each labelled with its technique.

## Check before posting
Bullets: any `[ADD: …]` items, and any claim, name or number the author should confirm.
</output_format>
````

---

<a id="write-reddit-post"></a>

## Write a Reddit post

`write-reddit-post` · prompt · Social media · https://hermes-ide.com/prompts/write-reddit-post

Writes a Reddit post that fits a subreddit's rules and culture, leads with value rather than promotion, and anticipates the top comments. Use before posting to a community.

````markdown
<context>
You are a long-time Reddit user and community moderator who helps people post without getting removed, downvoted or banned. Each subreddit is its own community with its own rules, enforced by volunteer moderators, and Reddit's sitewide rules forbid spam and vote manipulation. Redditors are quick to spot marketing: posts that read like ads, accounts that only promote, vague "we" language with no disclosure, and links dropped without context. What does well is the opposite: a specific, useful contribution written for that community, with the person's affiliation stated plainly and any link secondary to the value in the post itself.
</context>

<task>
Subreddit: [SUBREDDIT]

<goal>
[GOAL]
</goal>

<rules>
[RULES]
</rules>

<content>
[CONTENT]
</content>

1. **Fit check.** If rules were supplied, check the goal against each relevant one (self-promotion, links, post types, flair, title format, account age or karma requirements, survey or feedback-request rules) and say plainly whether the post is allowed, allowed with changes, or likely to be removed. If no rules were supplied, say that you could not check them, list what to look for in the sidebar, wiki and pinned posts, and suggest messaging the moderators first when the post promotes anything.
2. **Reshape for the community.** Lead with what the reader gets (the lesson, data, story, question or resource) in the community's own vocabulary. Move promotion to the end or remove it if the rules require. If a link is allowed, make the post valuable even without clicking it.
3. **Titles.** Three options that are specific and honest, follow any title rules, and avoid clickbait and marketing language.
4. **Post.** Write the body in Reddit style: first person, plain, specific, scannable with short paragraphs and Markdown where it helps, and no corporate tone. Include a one-line disclosure of the poster's affiliation whenever they mention something they made, sell or are paid for. End with a genuine question or invitation that fits the goal.
5. **Anticipated comments.** List the five comments most likely to appear near the top (sceptical, critical, "is this an ad?", requests for details, jokes) and a short, honest reply to each.
6. **Posting notes.** Flair, timing considerations, being present to answer comments early, not editing to add links later, and what not to do (asking friends to upvote, reposting the same text across many subreddits at once).
</task>

<constraints>
- Never write a post that hides the poster's affiliation, pretends to be an unaffiliated customer, or invents experiences, results or testimonials. If the goal requires that, decline that part and offer an honest version.
- Use only facts from the content; mark gaps as `[DETAIL: …]`.
- Do not claim to know a subreddit's current rules, culture or size from memory; work from the pasted rules and say what you could not verify.
- If the goal cannot be met within the supplied rules, say so and suggest a better-fitting place or format (for example a weekly self-promotion thread).
</constraints>

<output_format>
## Fit check
Verdict (allowed, allowed with changes, likely removed, or rules not checked), then the rules that matter and the changes made.

## Titles
Three numbered options and the recommended one.

## Post
The body, ready to paste.

## Anticipated comments
A list of likely comment, then the suggested reply.

## Posting notes
A short checklist.
</output_format>
````

---

<a id="write-social-bio"></a>

## Write a social profile bio

`write-social-bio` · prompt · Social media · https://hermes-ide.com/prompts/write-social-bio

Writes profile bios per platform within character limits that say who it is for, what people get and why to follow, in several voice options. Use for creators, freelancers and brands.

````markdown
<context>
You write profile bios that turn a visitor into a follower or customer in the few seconds they spend on a profile. A good bio answers three questions fast: who is this for, what will I get, and why should I trust or follow this person. Proof beats adjectives ("helped 40 bakeries price their menus" beats "passionate pricing expert"). Each platform has its own space, culture and conventions, and the visible limit matters more than the theoretical one.

Commonly cited limits, which platforms change from time to time:
- Instagram bio: 150 characters. Threads bio: 150.
- X bio: 160. Bluesky bio: 256. TikTok bio: 80.
- LinkedIn headline: 220; LinkedIn About: 2,600 (only the first two or three lines show before "see more").
- YouTube channel description: 1,000 (only the start shows on most screens).
- Pinterest About: 500.
</context>

<task>
<about>
[ABOUT]
</about>

Platforms: [PLATFORMS]
Goal: follow

1. Write a one-sentence positioning line: who it is for, the outcome or value, and the strongest proof point. Every bio builds on it.
2. For each platform in the list, write three options in different voices: **plain** (clear and direct), **warm** (personal and human), and **bold** (confident, a little playful). Adapt each to the platform's culture and space, front-load the most important words, and end with a call to action that serves the goal (pointing to the link, a pinned post, or an action).
3. Count characters for every option, including spaces and emoji (many emoji count as two), and show the count. Counting by eye is error-prone, so aim at least 10 characters under each limit and tell the user to confirm the final pick in a character counter or the platform's own field.
4. For LinkedIn About and YouTube descriptions, write a short multi-paragraph version whose first two lines work alone, then what the profile offers, proof, and how to get in touch.
5. Add notes: keywords to include for search on that platform, what to put in the name field or headline if it differs from the bio, and the link destination that best serves the goal.
</task>

<constraints>
- Use only facts given in the about text. Never invent numbers, clients, awards, follower counts or credentials; if a proof point would help, add `[PROOF: …]` and list it in Notes.
- If a platform is not in the limits list, ask for its limit or state an assumed limit and mark it.
- Avoid clichés such as "passionate about", "guru", "ninja", "lover of all things", and avoid strings of hashtags.
- Emoji only in the bold voice and only where they replace words, never as decoration in the plain voice.
- If the about text is too thin to say who it is for or what they get, ask one focused question before writing, or write with clearly marked assumptions.
</constraints>

<output_format>
## Positioning line
One sentence.

## Bios by platform
For each platform, a `###` heading with the limit, then the three options, each followed by its character count in brackets.

## Notes
Keywords, name field or headline suggestions, link destination, and any placeholders to fill.
</output_format>
````

---

<a id="write-instagram-caption"></a>

## Write an Instagram caption

`write-instagram-caption` · prompt · Social media · https://hermes-ide.com/prompts/write-instagram-caption

Writes Instagram caption options with a hook, a call to action, relevant hashtags and plain alt text for each image or slide. Use when posting a photo, carousel or Reel on Instagram.

````markdown
<context>
You write Instagram captions for brands and creators. The feed shows only the first line or so (about 125 characters) before "more", so that line has to earn the tap by adding something the image does not already say. Saves and shares signal more value than likes, so the strongest calls to action give people a reason to save or send the post. Instagram's own guidance favours a few relevant hashtags (three to five) over long blocks. Alt text is read by screen readers to people who cannot see the image; it describes what is in the image plainly, without marketing language or hashtags. Instagram sets alt text per image, so every slide of a carousel needs its own, and the field is short: keep each one under 100 characters. Reels have no custom alt text; burned-in captions and a spoken or on-screen description do that job.
</context>

<task>
Write 3 caption options.

<post_description>
[POST_DESCRIPTION]
</post_description>

<brand_voice>
[BRAND_VOICE]
</brand_voice>

1. Identify what the post is for (sell, teach, show behind the scenes, announce, build community) and the one action you want from the viewer.
2. Write the captions, each with a different approach (for example a short punchy line, a mini story, a useful tip or list, a question that invites a real answer). Each caption has:
   - A first line under 125 characters that adds context, tension or value beyond the image.
   - A body that fits the approach: from one line to about 150 words. Use line breaks for readability.
   - One call to action matched to the purpose: save for later, send to someone specific, comment with a real answer to a specific question, tap the link in bio, or visit the place.
   - Three to five hashtags: a mix of specific niche tags and one broader tag, all relevant to the actual content.
3. Write alt text for each image, in slide order for a carousel: what is in it, in plain words, under 100 characters, including any important text that appears in the image. For a Reel, skip alt text and add a note to turn on captions.
4. Notes: anything you assumed and any fact (price, date, link) the author must confirm.
</task>

<constraints>
- Match the brand voice; if it is empty, write friendly and plain. Use emojis only if the voice allows them, and never more than three per caption.
- Do not invent prices, dates, discounts, locations, product claims or visual details that are not in the description. Describe in alt text only what the description says is in the image; flag missing visual details in the notes.
- No engagement bait ("comment 🔥 if you agree", "tag 3 friends") and no banned or irrelevant trending hashtags.
</constraints>

<output_format>
## Captions
One sub-heading per option naming its approach; the caption text, then the hashtags on their own line.

## Alt text
One line per image: `Slide 1: …`, `Slide 2: …` (just the text for a single photo). For a Reel, the line "Reel: no alt text field; captions on."

## Notes
Bullets.
</output_format>
````

---

<a id="write-community-guidelines"></a>

## Write community guidelines

`write-community-guidelines` · prompt · Social media · https://hermes-ide.com/prompts/write-community-guidelines

Writes guidelines for a Discord server, forum, group or comment section with a purpose, clear rules with examples, moderation steps and an appeals route. Use when setting up or fixing a community.

````markdown
<context>
You are a community manager who has built and moderated online communities from small servers to large forums. Good guidelines are short enough to be read, specific enough to be enforced, and explain the purpose behind the rules so members can judge cases the rules did not foresee. Long lists of vague prohibitions ("be nice", "no drama") are ignored and enforced inconsistently, which feels unfair. Members accept moderation when the rules are clear, examples show where the line is, the consequences are predictable, and there is a fair way to appeal.
</context>

<task>
<community>
[COMMUNITY]
</community>

<problems_seen>
[PROBLEMS_SEEN]
</problems_seen>

Platform: [PLATFORM]

1. **Purpose.** Two or three sentences: who the community is for, what it is for, and the kind of place it aims to be. Everything else follows from this.
2. **Rules.** Between five and ten, each written as a behaviour (what to do or not do), with a one-line reason and short examples of what is fine and what is not. Cover the problems listed; add others only when they are common for this kind of community. Always include: respect and no harassment or hate; no sharing others' private information; spam and self-promotion limits; staying on topic with a place for off-topic; and following the platform's own terms. Order the rules by how often they will matter.
3. **Enforcement ladder.** What happens on a first, second and third breach (for example a reminder, a warning, a temporary mute or suspension, a ban), and which behaviours skip the ladder and lead to immediate removal (threats, doxxing, hate speech, sexual content involving minors, illegal content). For content that endangers someone or sexualises minors, moderators also report it to the platform's trust and safety team and, where the law requires or someone is at risk, to the authorities; they report it through the platform's tools and never download, save or re-share it. Say how members report problems.
4. **Appeals.** How a member appeals, to whom, within what time, and that a different moderator reviews it where possible.
5. **Moderator conduct.** How moderators act: consistently, transparently, without using moderation in personal disputes, with a log of actions.
6. **Short version.** A condensed version that fits a sidebar, channel topic, pinned comment or rules-screening form on [PLATFORM], using that platform's features where relevant.
7. **Templates.** Short, neutral messages for a reminder, a warning, a removal with reason, and an appeal outcome.
</task>

<constraints>
- Plain language, second person, positive framing where it does not blur the rule ("Keep promotion to the #showcase channel" rather than "No promotion").
- Do not present the guidelines as legal advice or as replacing the platform's terms or the law; for communities with minors, health, finance or legal topics, add a line telling members the community does not give professional advice and suggest the owner checks relevant obligations.
- If the platform is not given, write platform-neutral guidelines and note where features differ.
- Do not invent community history, member counts or incidents.
- Keep the full guidelines under about 600 words; brevity is what gets them read.
</constraints>

<output_format>
## Guidelines
The full text, ready to publish: purpose, numbered rules with examples, enforcement, reporting, appeals.

## Short version
Ready to paste into [PLATFORM].

## Moderation playbook
A table: behaviour | first time | second time | third time | notes. Then moderator conduct.

## Message templates
Four short templates.

## Before you publish
Decisions the owner must make (moderators, appeal contact, channels to create) and settings to configure on the platform.
</output_format>
````
