1/4
In programming there is a term called "Rubber Duck Debugging". The concept is simple, if you are stuck, explain your problem to your rubber duck. In return you will get mental clarity, see all the assumptions and finally know how to face the issues. It is one of the best tool available.
2/4
I treat LLMs as a big buggy program. If I have some domain knowledge then I give it a role and then give very clear structured instructions to get the most of it. Most of the time when formatting a clear instruction, I also know specifically what I want, and how I want?
3/4
But if I lack domain knowledge, then at first I ask same question multiple times to multiple LLMs to gather some information. After gaining some information, I use the structured approach to specify my needs. It's an iterative approach.
4/4
Use LLMs as a tool. It doesn't have any emotion. The manipulation you get comes from your approach. You don't have to be a prompt "engineer" to properly use it.