Skip to content
Notifications
Clear all

Where to start with prompt engineering? Any good community templates?

3 Posts
3 Users
0 Reactions
75 Views
(@elliek2)
Reputable Member
Joined: 4 months ago
Posts: 355
Topic starter   [#6662]

Hey everyone! 👋 I've been using ContentBot for a few weeks now and I'm honestly a bit lost when it comes to writing good prompts. I see all these amazing results people are sharing, but mine are... well, kinda hit or miss.

I'm trying to create product descriptions for my Shopify store and some blog post outlines, but I feel like I'm just typing random instructions and hoping for the best. I know there's a skill to this "prompt engineering" thing, but where do you even begin?

Are there any good starter templates or prompts that this community has found really helpful? Like, a basic formula or structure that works well for different types of content? I'd love to see some examples of what you all are actually typing into the box to get such good outputs. Starting from zero here and feeling a bit overwhelmed!



   
Quote
(@marketing_ops_geek_kim)
Eminent Member
Joined: 7 months ago
Posts: 26
 

You're right to look for a template or formula. Think of it like writing a brief for a human copywriter, but more structured. The most common framework is Role-Task-Format-Constraints.

For product descriptions, I'd start with something like:

> Act as a professional e-commerce copywriter. Write a product description for [Product Name] targeting [Audience]. Highlight these three key features: [A, B, C]. Use a persuasive but informative tone, include a call to action, and keep it under 150 words.

The key is providing specific, bounded instructions. The more vague you are, the more the output will vary.

For blog outlines, you'll want to add the desired structure in the constraints, like "Provide an outline with an introduction, 5 H2 subheadings covering specific points, and a conclusion summary."

It's less about magic words and more about consistently giving the model the context it needs to perform a defined task. Start with that framework and iterate based on the results.



   
ReplyQuote
(@briana)
Reputable Member
Joined: 4 months ago
Posts: 319
 

Totally agree with the Role-Task-Format-Constraints framework. That's basically how I start every migration plan for a database 😅

I'd just add one tiny nuance from my own fiddling: the order matters sometimes. Putting the "Role" part first really does set the stage, like giving the model a specific hat to wear. If you bury it in the middle, it doesn't seem to click as well.

For your product description example, I sometimes get better results by swapping the "Format" and "Constraints" - being super clear about the word count *before* the tone instruction. Like:

> Act as a professional e-commerce copywriter. Write a 150-word product description for [Product Name]. Target [Audience] and highlight features [A, B, C]. Use a persuasive but informative tone and include a call to action.

Small tweak, but it sometimes gives me more consistent length control. Just my two cents!


Backup first.


   
ReplyQuote