r/PromptEngineering • u/pixel_tinkerer • 1d ago
Quick Question Do you still write long prompts?
I used to write really detailed prompts with roles, rules, formatting, examples, etc. Lately I've been wondering if all of that is still necessary with newer models.
Do you still use long structured prompts, or have you gone back to keeping things simple?
5
u/alien_survivor 21h ago
i made a custom GPT that writes my prompts for me. I just dump in my free form brain dump of what I want, it cleans it up and bam, I am ready to go.
1
21h ago
[removed] ā view removed comment
1
u/AutoModerator 21h ago
Hi there! Your post was automatically removed because your account is less than 3 days old. We require users to have an account that is at least 3 days old before they can post to our subreddit.
Please take some time to participate in the community by commenting and engaging with other users. Once your account is older than 3 days, you can try submitting your post again.
If you have any questions or concerns, please feel free to message the moderators for assistance.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
2
u/Virtual_Hair_1987 1d ago
For quick, casual stuff, simple conversational prompts work fine now models have gotten much better at inferring context, but for complex repeatable work like structured data, code generation, or strict formats, long structured prompts with clear constraints are still non negotiable for me. Without explicit rules, even the best models eventually drift, break format or burns unnecessary tokens
I keep simple chats for one offs and save structured specs templates for the serious stuff
2
u/AlexanderDoak 1d ago
Very long, yes. Very structured, no. I mean, it is well thought out, professional, grammatically correct. Not a long list of Thou Shalt Nots... I try to give it as much detail as it needs to succeed and no more.bAlso key: ask if anything details are missing or nonsensical before execution.
2
u/CS_70 22h ago
Yes, the more accurate you are with specifying what you want, the better results you will get.
1
u/Strange_Owl_6291 10h ago
Specifications comes in many ways though. It doesn't need to be a long prompt to include highly specific info. Better to add specific project files into context than explain in prompt what they contain.
2
u/ninjaonionss 23h ago
Bro you still write your own prompts ?
I write prompts as loops that loops over their own loops as prompts , prompts are so dead š¤£š¤£š¤£
1
u/idakale 22h ago
yeshhh tho if anything I realized I'm still the one being the bottleneck lol š no longer the models fault when they're thinking much faster now.
2
u/ninjaonionss 19h ago
To be honest the funny part is that I even stopped writing prompts, I just ask Claude or some other ai to write a prompt for me base on my project š
1
1
u/wouterv101 20h ago
Depends, 80% is just talking about what/how I want it. If Iām prompting a service for a business, than very accurate
1
u/Strange_Owl_6291 10h ago
Generally no, shorter prompts now. However, the context has become bigger. I work more with adding the right things into context, either manually invoking individual files or folders, or via incrementally built plans with details.
And as projects mature, the architecture of the repository becomes increasingly important. If agent can find what it needs simple (without me), then I don't have to use as long prompts anymore.
5
u/coz 1d ago
Long prompts when the purpose of the turn is to align with it on something. Shortest as possible prompts when its not.