Before you post
These are the questions people usually want settled before they write their first post here.
I'm not a developer. Is this place for me?
Yes. The site is built for the lawyer, the marketing manager, the person running a shop, not for programmers. You do not need credentials, a technical background, or a finished product. If you found a way to make AI do part of your job, that is the whole qualification.
It's free. What's the catch?
There is no catch. Nothing is sold here, no prompt marketplace and no subscription. That is a deliberate choice: the moment something is for sale, posters have a reason to oversell what their workflow does, and the success rate stops meaning anything. The success rate is the part that makes the site worth reading, so nothing gets sold.
Why do I have to write where my workflow breaks?
Because a workflow without its limits is an advert. For playbook posts the field is enforced by the site itself, so a playbook with no real sentence on its limits cannot be saved. It is also the part readers trust most. Saying what your method cannot do makes everything else you claim believable.
My experiment failed. Is that even worth posting?
It is one of the most useful things you can post. c/fails is not a place to vent, it is where a dead end gets explained clearly enough to save the next person an afternoon, and often someone in the replies knows the missing piece. There are no downvotes anywhere on the site, so an honest failure costs you nothing.
Can I post prompts I got from a book or a paid course?
Post the method or the skill you built from it, never the material itself. The same goes for paid courses and internal company documents. Copying the source text gets the post removed on the first offence. Describing what you took from it and how you actually use it is fine, and more useful to read anyway.
Still not sure whether your thing is worth posting? It probably is. Post it.