📱 Social Media

Circle.so Community Guidelines from Mod Brief (Not Captions, Not Legal Advice)

Draft Circle.so community guidelines from a mod brief only. Not a caption engine. Not legal advice. No invented member counts or banned-word lists beyond the brief.

0.0
0Reviews
P
September 6, 2026

Prompt

Act as a Circle.so community guidelines editor who only uses a pasted mod brief. You write space rules the brief already supports. You do not invent member counts, ban lists beyond the brief, or legal threats. This is not a caption engine, not marketing copy, and not legal advice.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Mod brief I lock (allowed topics, bans, tone): [Brief]
- Space names I may quote (or UNKNOWN): [Spaces]
- Rule cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent (member counts, extra bans, legal threats, fees): [Never]
- Output format: [Format]
- Language: [Lang]
- Escalation contact I may quote (or UNKNOWN): [Escalation]

Generate:
1. Honesty ledger: Brief nouns, Spaces, Cap, Escalation, Lang. Forbidden: invented member counts, extra bans, legal threats, fees. Banner: not legal advice; not captions.
2. Guidelines list: at most Cap rules grounded in Brief. Missing policies write NOT IN INPUTS.
3. Space-specific notes: only for Spaces named. Unnamed spaces stay NOT IN INPUTS.
4. Escalation: quote Escalation or UNKNOWN; do not invent a legal counsel email.
5. Refuse list: inventing 12k members, inventing a fine schedule, inventing caption CTAs, inventing Terms of Service clauses.
6. Compliance pass: quote Banned and Never hits. Cut them. Print rule count. Format as Format.

Constraints:
- Guidelines from Brief only. Not captions. Not legal advice.
- Honor Cap. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Circle.so Community Guidelines from Mod Brief (Not Captions, Not Legal Advice) - Result

Examples

Example Input

Brief: allowed topic self-hosted backups as pasted; allowed config snippets as pasted; banned affiliate dumps as pasted; banned doxxing as pasted. Pledge dollars NOT IN INPUTS. Member count NONE.
Spaces: #ops-chat as pasted; #introductions as pasted. Paid tier space UNKNOWN.
Cap: 5
Banned: guaranteed, 12k members, sue you, buy now CTA
Never: invent member counts, invent extra bans, invent legal threats, invent fees
Format: ledger + rules + spaces + escalation + refuse + compliance
Lang: English
Escalation: UNKNOWN (do not invent legal@)

Example Output

1. Ledger. Brief: self-hosted backups; config snippets allowed; affiliate dumps banned; doxxing banned. Pledge dollars NOT IN INPUTS. Member count NONE. Spaces: #ops-chat; #introductions; paid tier UNKNOWN. Cap 5. Escalation UNKNOWN. Lang English. Banner: not legal advice; not captions. Forbidden: invented member counts, extra bans, legal threats, fees, guaranteed, 12k members, sue you, buy now CTA.

2. Guidelines (4/5).
1. Discuss self-hosted backups as pasted; keep posts on that topic in named spaces.
2. Config snippets are allowed as pasted; strip secrets before posting (secret values NOT IN INPUTS).
3. Affiliate dumps are banned as pasted.
4. Doxxing is banned as pasted.
Fee schedule not added (NOT IN INPUTS). Caption-style CTA not added.

3. Space notes. #ops-chat: backups and config snippets as pasted. #introductions: welcome posts only; sales pitches not in Brief so write NOT IN INPUTS rather than inventing a sales ban beyond affiliate dumps. Paid tier space UNKNOWN.

4. Escalation. Escalation UNKNOWN so write contact NOT IN INPUTS. Do not invent legal@. Moderation path beyond Brief: NOT IN INPUTS.

5. Refuse. 12k members: refused. Fine schedule: refused. Buy now CTA captions: refused. sue you legal threat: refused. Terms clause invent: refused.

6. Compliance. Banned hits none. Rules 4/5. Format ledger+rules+spaces+escalation+refuse+compliance. Gaps: Escalation contact, paid tier space, pledge policy, secret-redaction examples, appeal path.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...