How to use the Community Guidelines Generator.
Guidelines should describe observable behavior and the moderation process. Vague instructions to be nice are harder to apply consistently.
Make the workflow fit your task.
Translate the community's purpose into observable allowed and disallowed behavior. Explain reporting, review and possible moderation responses so members understand both the rule and how it is applied.
- What you provide
- Community purpose, rules and moderation approach.
- What you get
- Readable conduct guidelines and escalation steps.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A learning community allows critique but not personal attacks.
Completed example
Discuss ideas with evidence; do not target individuals. Explain how members report issues and how moderators review repeated violations.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
How specific should community rules be?
Use examples where ambiguity is likely, such as distinguishing critique of an idea from personal attacks. Avoid relying solely on broad values.
Why are moderators applying the same rule inconsistently?
Add decision criteria and examples, then document escalation and review. Consistency depends on a shared process as well as wording.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑