Home/Blog/How to Write Lemmy Community Rules and a Sidebar from a Mod Brief
Blog

How to Write Lemmy Community Rules and a Sidebar from a Mod Brief

P
promptstudio
How to Write Lemmy Community Rules and a Sidebar from a Mod Brief

Lemmy sidebars invent 12k subscribers and lemmy.example. The brief allowed config snippets and banned affiliate links. Mods NONE.

The matching generator is the Lemmy Community Rules and Sidebar from a Mod Brief (Not Captions) (Lemmy Community Rules And Sidebar From A Mod Brief Not Captions) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Write only the rule count the brief locked

Write Lemmy community rules and a sidebar from a mod brief. Not a caption engine. No invented bans or member counts. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Mod brief I lock (topic, allowed posts, banned behaviors I name): [Brief]
Instance I may name (or UNKNOWN): [Instance]
Rule count I lock: [Count]
Words I must not use: [Banned]
What I must never invent (member counts, federated instances, extra bans): [Never]
Output format: [Format]
Language: [Lang]
Sidebar character cap I lock: [SideCap]
Mods I may name (or NONE): [Mods]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Stay inside the sidebar character cap

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: Brief nouns, Instance, Count, SideCap, Mods, Lang. Forbidden: invented member counts, invented federation, extra bans.
  2. Rule list: Count rules from Brief only. Extra behaviors write NOT IN INPUTS.
  3. Sidebar: stay at or under SideCap. Topic from Brief. Instance from Instance or INSTANCE UNKNOWN.
  4. Welcome: one short post. Not a caption pack. No hashtag spray.
  5. Refuse list: Reddit sidebar markdown dump, Discord Automod YAML, Mastodon instance rules, Bluesky starter pack, caption engines.
  6. Mods: quote Mods or write NONE. Do not mint @admin.
  7. Never: do not write 12k subscribers. Do not invent lemmy.example federation.
  8. Compliance pass: quote Banned and Never hits. Cut them. Print sidebar character count. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Refuse Reddit wikis and caption engines

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Lemmy rules and sidebar from Brief only. Not Reddit and not captions.
  • Never invent member counts, federation, or extra bans.
  • Honor Count and SideCap.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Print the sidebar character count

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (lemmy community rules, mod brief sidebar, not a caption engine) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.