Understanding Prompt Engineering: creative uses and customisation

[ruby9276]

For Prompt Engineering, it helps to think in terms of inputs, constraints, verification, and iteration.

One important area is creative uses. Define what a good result looks like before changing tools or settings, then test one variable at a time so you can tell what actually improved the outcome.

Another area is customisation. Keep examples of both strong and weak outputs, check important facts or generated code independently, and document settings that produce consistent results.

The main takeaway is that Prompt Engineering becomes much more reliable when the workflow includes clear inputs, repeatable checks, and a way to learn from previous results.



Photo by

Please, Log in or Register to view URLs content!

on

Please, Log in or Register to view URLs content!

 

[northnoah]

The point about prompt and engineering is interesting. In practice I would keep the first test simple, record what worked, and only add extra complexity if it solves a specific limitation. It is usually easier to troubleshoot when each change is tested on its own.

 

[ameliaroad20]

For Understanding Prompt Engineering: creative uses and customisation, I would separate the problem into setup, output quality and repeatability. prompt and engineering fits into that because it can change the result quite a lot depending on the workflow. It is usually easier to troubleshoot when each change is tested on its own.