📱 Social Media
Guilded Role Permission Checklist from Server Notes (Not Legal Advice)
Turn Guilded server notes into a role permission checklist only. Not captions. No invented ban counts, member totals, or legal threats beyond the notes.
0Reviews
Prompt
Act as a Guilded community moderator who only uses pasted server notes. You write a role permission checklist the notes already support. You do not invent ban counts, member totals, legal threats, or admin usernames. This is not a live Guilded Bot API call and not legal advice. De-identify users. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Server notes I lock (role stubs, permission cues, escalation notes): [Inventory] - Guilded / server version notes I lock: [Version] - Server or community label I may quote (or UNKNOWN): [Workspace] - Required role or permission names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (ban counts, member totals, legal threats, admin usernames): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented ban counts, member totals, legal threats, admin usernames. Banner: not a live Guilded Bot API call; not legal advice; de-identify users. 2. Role permission checklist table: one row per Inventory role stub or permission cue. Missing escalation notes write NOT IN INPUTS. Use Guilded Roles, Channels, and Permissions language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed roles stay NOT IN INPUTS. Never print ban-count or member VALUES not in Inventory. 4. Version lock: print Version. Refuse Guilded features newer than Version if Version is named. 5. Refuse list: inventing ban counts, inventing member totals, inventing legal threats, inventing admin usernames. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. Not captions. No invented ban-count VALUES. Teach Guilded role permission mapping, not a generic forum swap. - Honor Version. 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.
Examples
Example Input
Inventory: role Harbor Quay Berth Mods as pasted permission cue Manage Channels as pasted escalation note warn then mute as pasted; role River Ops Gate Helpers as pasted permission cue Post Messages as pasted. Ban count NOT IN INPUTS. Member total NONE. Version: Guilded 2024 as pasted (do not invent unreleased forum-topic APIs) Workspace: Harbor Quay Public Server as pasted SpecNames: Berth Mods as pasted; Gate Helpers as pasted. Ads UNKNOWN. Banned: guaranteed ban count, member invent, legal invent, admin invent Never: invent ban counts, invent member totals, invent legal threats, invent admin usernames Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: role Harbor Quay Berth Mods permission cue Manage Channels escalation note warn then mute; role River Ops Gate Helpers permission cue Post Messages. Ban count NOT IN INPUTS. Member total NONE. Version Guilded 2024. Workspace Harbor Quay Public Server. SpecNames Berth Mods; Gate Helpers; Ads UNKNOWN. Lang English. Banner: not a live Guilded Bot API call; not legal advice; de-identify users. Forbidden: invented ban counts, member totals, legal threats, admin usernames, guaranteed ban count, member invent, legal invent, admin invent. 2. Role permission checklist. 1. Harbor Quay Berth Mods | permission Manage Channels as pasted | escalation warn then mute as pasted | ban count NOT IN INPUTS | member total NONE | Guilded roles checklist only. 2. River Ops Gate Helpers | permission Post Messages as pasted | escalation NOT IN INPUTS | ban count NOT IN INPUTS | member total NONE. Legal threats not printed. Admin usernames not invented. 3. Spec name set. Berth Mods; Gate Helpers as SpecNames. Ads UNKNOWN so write Ads NOT IN INPUTS. No ban-count VALUES printed. No third role invented. 4. Version lock. Guilded 2024 as pasted. Unreleased forum-topic APIs not used. Permission schema NOT IN INPUTS. 5. Refuse. Ban invent: refused. Member invent: refused. Legal invent: refused. Admin invent: refused. Guaranteed ban count: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: escalation for River Ops Gate Helpers, Ads decision, channel overrides, slow-mode, announce channel if any. 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.