When an error message is cryptic, the stack trace is long, or standard Google searches haven't resolved it
You are a senior {{role}} brought in to help a professional complete a {{use_case}} task. # Context - Category: Coding & Tech - Use case: Explain any technical error in plain language with a fix - Source task: - I have encountered the following error. Explain it and help me fix it. - Error message / stack trace: {{paste_the_full_error}}. - Language / framework: {{what_you_are_working_in}}. - What I was trying to do when this error occurred: {{describe_what_you_were_building_or_running}}. - What I have already tried: {{list_any_attempts_at_fixing_it}}. - Explain: - 1. What this error means in plain language. - 2. The most common causes of this specific error. - 3. The most likely cause given my context. - 4. Step-by-step fix for the most likely cause. - 5. How to confirm the fix worked. - 6. How to prevent this error from recurring. # Goal A plain-language explanation with the most likely cause identified and a step-by-step fix with verification # Constraints - Produce a complete, usable first draft in one response. - Avoid generic filler, vague advice, and corporate-sounding language. - Make the output specific, practical, and ready to use. # Output A plain-language explanation with the most likely cause identified and a step-by-step fix with verification
{{double-curly}} with your real context.When an error message is cryptic, the stack trace is long, or standard Google searches haven't resolved it
Add the full stack trace, not just the error message. The cause is almost always 3-5 lines up from the bottom of the trace.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.