How to Write Meetup Group Rules and a Welcome from a Community Brief
Meetup blurbs invent 400 RSVPs and a downtown library venue. The brief allowed tool demos and banned affiliate links. Organizers NONE. Group UNKNOWN.
The matching generator is the Meetup Group Rules and Welcome from a Community Brief (Not Captions) (Meetup Group Rules And Welcome From A Community 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 Meetup group rules and a welcome from a community brief. Not a caption engine. No invented RSVP 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:
Community brief I lock (topic, allowed events, banned behaviors I name): [Brief]
Group I may name (or UNKNOWN): [Group]
Rule count I lock: [Count]
Words I must not use: [Banned]
What I must never invent (RSVP counts, venues, extra bans, member totals): [Never]
Output format: [Format]
Language: [Lang]
Blurb character cap I lock: [SideCap]
Organizers I may name (or NONE): [Orgs]
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 blurb 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:
- Honesty ledger: Brief nouns, Group, Count, SideCap, Orgs, Lang. Forbidden: invented RSVP counts, invented venues, extra bans.
- Rule list: Count rules from Brief only. Extra behaviors write NOT IN INPUTS.
- Blurb: stay at or under SideCap. Topic from Brief. Group from Group or GROUP UNKNOWN.
- Welcome: one short post. Not a caption pack. No hashtag spray.
- Refuse list: Discord Automod YAML, Facebook Group dump, Farcaster channel pack, Meetup trending claims, caption engines.
- Organizers: quote Orgs or write NONE. Do not mint @admin.
- Never: do not write 400 RSVPs. Do not invent a downtown library venue.
- Compliance pass: quote Banned and Never hits. Cut them. Print blurb 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 Discord YAML 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:
- Meetup group rules and welcome from Brief only. Not Discord and not captions.
- Never invent RSVP counts, venues, 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 blurb 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 (meetup group rules, community brief welcome, 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.