Rules
Short, and enforced. The whole promise of this site is that what you find here has been run by a real person. These rules are what protects that.
- 1
Show, don’t just tell.
A post that says AI helped you is not a post. Include the prompt, the output, the file, or the screenshot. If there is nothing to copy or look at, there is nothing to learn.
- 2
Share the method, not the copyrighted source.
Post the skill you built from a book. Do not post the book. The same goes for paid courses, internal company documents, and anything you do not have the right to distribute. This one gets you removed on the first offence.
- 3
No engagement bait.
No “AI will replace us all” takes, no threads that are really a pitch, no ten-part hooks. If the value is in the comments of your own post, put it in the post.
- 4
Disclose any commercial interest.
If you built the tool, work for them, or get paid when someone signs up, say so in the post. Not in a reply. Not in your bio. In the post.
- 5
Failures are welcome. Fabrications are not.
c/fails exists because what did not work is often more useful than what did. But post what actually happened. A workflow you never ran is a fabrication, however plausible it reads.
- 6
No legal, medical, or financial advice without a disclaimer.
You can absolutely post how you used AI to understand a contract. Make it clear it is not professional advice — these setups are very good at sounding like it is.
Reporting
Every post, comment, and file has a report button. Copyright reports go to a priority queue and are handled first — if you are a rights holder, that is the fastest route.