How to Write Bluesky Starter Pack Rules from a Community Brief
Starter-pack rules fail when they add hashtags and a 12k member boast. The brief was night-shift library workarounds. Not a caption thread.
The matching generator is the Bluesky Starter Pack Rules and Welcome from a Community Brief (Not Captions) (Bluesky Starter Pack Rules And Welcome From 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).
Number rules from the brief only
Write Bluesky starter-pack rules and a welcome note from a community brief. Not a caption engine and not a crosspost pack. 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 (purpose, topics I allow): [Brief]
Rules I lock (or topics to turn into rules): [Rules]
Handles I allow as mods (or NONE): [Mods]
Words I must not use: [Banned]
What I must never invent (member counts, extra rules, captions): [Never]
Output format: [Format]
Language: [Lang]
Max rules: [Max]
Welcome length cap (words): [WelcomeCap]
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.
Keep MODS NONE if no handles were pasted
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, Rules, Mods, Lang, Max, WelcomeCap. Forbidden: member counts, extra rules, captions, hashtags.
- Rules list: numbered from Brief and Rules only. Extra civic rules write NOT IN INPUTS unless pasted.
- Welcome: purpose from Brief. No growth boasts. Stay at WelcomeCap words.
- Mods: quote Mods or write MODS NONE. Do not invent @handles.
- Refuse list: caption threads, hashtag stacks, Threads crosspost, Signal group rules, Discord #welcome.
- Pack name: only if Brief names one. Else PACK NAME UNKNOWN.
- Never: do not write 12k members. Do not add a weekly prompt unless Brief has one.
- Compliance pass: quote Banned and Never hits. Cut them. Count rules vs Max. 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 Signal Discord and caption fields
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:
- Bluesky starter-pack rules from Brief only. Not captions and not Signal.
- Never invent member counts, extra rules, or handles.
- Stay at or under Max rules and WelcomeCap words.
- 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.
Count rules against Max and welcome words against the cap
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 (bluesky starter pack rules, community brief welcome, not captions) 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.