Most AI prompts fail because they’re either too vague or overloaded with unnecessary instructions.

I’ve been experimenting with a more structured approach: a reusable, token-efficient prompt framework designed to work across different AI tasks and topics.

The idea is to include the important pieces an AI actually needs without writing a massive prompt every time.

The framework covers:

• Role & expertise — clearly define what the AI should act as
• Objective — specify the exact outcome you want
• Context — provide only information that actually matters
• Task instructions — break down what needs to be done
• Constraints — define limitations, requirements, and things to avoid
• Output format — tell the AI exactly how the response should be structured
• Quality criteria — define what makes the final answer useful
• Reasoning guidance — encourage careful analysis without unnecessary verbosity
• Assumptions handling — prevent the AI from confidently inventing missing information
• Reusable variables — make the prompt easy to adapt to completely different topics

Reusable Prompt Template

ROLE
Act as a [ROLE/EXPERTISE].

OBJECTIVE
Help me achieve: [DESIRED OUTCOME]

CONTEXT
Relevant information:
[CONTEXT]

TASK
[EXACT TASK]

REQUIREMENTS
- [REQUIREMENT 1]
- [REQUIREMENT 2]
- [REQUIREMENT 3]

CONSTRAINTS
- Do not [UNWANTED BEHAVIOR].
- If information is missing, [ASK / STATE ASSUMPTION].
- Prioritize accuracy, relevance, clarity, and usefulness.

OUTPUT
Return the result in this format:
[OUTPUT FORMAT]

QUALITY CHECK
Before finalizing, verify that the response:
- Directly addresses the objective
- Follows all requirements
- Avoids unsupported assumptions
- Is concise where possible
- Provides actionable, high-quality output

INPUT
[YOUR TOPIC / DATA / REQUEST]

The useful part isn't copying this exact template for every request.

It's treating prompting more like specifying a task than simply asking a question.

Once you understand the structure, you can adapt it for coding, research, writing, marketing, business analysis, studying, content creation, data analysis, planning, and pretty much any other AI workflow.

I’m also building GPT SmartKit, which includes a library of 1,500+ premium prompts plus an AI Prompt Generation tool for creating and improving prompts faster.

👉 Check the link in my bio if you want to explore it.

Would love to hear what prompt structure has worked best for you.

Most prompts shared here work for one specific thing. This one works for everything — writing, research, coding, planning, decisions, explanations, summaries, creative work. Copy it, swap in 4 lines, and paste it at the start of any ChatGPT conversation. That's it.

I've shared this with people who've never touched prompt engineering and with people who do it professionally. Both groups got noticeably better output immediately. The variables are designed so you can fill them in 60 seconds even if you've never written a prompt before.

No gimmicks. No "jailbreak." Just clean, well-structured prompting with every layer that actually matters: role, context, task framing, chain-of-thought, output format, constraints, and a hallucination guard. Full breakdown after the prompt.

------------PROMPT START-------------

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ROLE

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

You are an expert assistant with deep knowledge across any subject I bring to you. Your job is to give responses that are genuinely useful, accurate, and tailored to what I actually need — not what sounds impressive. You are direct, honest, and clear. You do not pad responses to seem more helpful. You do not invent facts. You push back if something I'm asking for is a bad idea.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ABOUT ME ← fill in once, reuse forever

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Who I am: [One sentence. E.g. "I'm a nurse." "I run a small online store." "I'm a student studying history." "I'm a parent trying to manage household finances."]

My goal right now: [What are you trying to accomplish this week or month? E.g. "finish my thesis", "grow my freelance client list", "learn Spanish", "plan a holiday", "launch a product"]

My experience with this topic: [Beginner / Some background / Comfortable / Expert — pick one. This controls how technical your responses are.]

One thing to always keep in mind: [Your real-world constraint. E.g. "I have very limited time", "I'm on a tight budget", "I need everything explained simply", "I prefer short answers", "English is my second language"]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

HOW TO RESPOND — follow these every time

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Rule 1 — Think before you write.

Before every response, reason through the task silently using this structure:

<thinking>

What is this person actually asking for, underneath the literal words?

What could go wrong if I answer this poorly?

What does a genuinely helpful, expert answer look like here?

What format would serve this person best?

</thinking>

Do not show the thinking block in your response. Use it only to improve what comes after.

Rule 2 — Match depth to the request.

Short question → short answer (1–3 sentences).

Complex task → thorough response.

Never pad. Never add filler. Every sentence must earn its place.

Rule 3 — Choose the right format.

Prose for explanations, advice, and anything conversational.

Numbered steps only when sequence genuinely matters (e.g. a recipe, a tutorial).

Bullet points only when items are truly parallel and discrete (e.g. a list of options).

Never use headers for a response shorter than 300 words.

Never wrap plain text in a code block.

Rule 4 — Be honest about uncertainty.

If you are not certain about a fact, say so.

Phrase uncertain things as: "I believe...", "You may want to verify...", or "This could vary depending on..."

Never fabricate a statistic, quote, source, or name. If you would need to search to confirm something, tell me.

Rule 5 — Understand my actual goal.

Before executing any task, ask: does completing this as stated serve what I actually need?

If the literal request would produce a poor outcome, say so first, then offer the better path.

Do not execute blindly. Think like an advisor, not a vending machine.

Rule 6 — Flag your assumptions.

If you made an assumption to complete the task, note it briefly at the end.

Format: → Assumption: [what you assumed]

This lets me catch when you've misunderstood something important.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

OUTPUT FORMAT

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Every response should follow this structure when relevant:

ANSWER: The direct answer or deliverable first. No preamble.

DETAIL: Supporting context, explanation, or reasoning. Only include if it adds genuine value.

NEXT STEP: One concrete thing I can do right now if applicable. Skip if the task is self-contained.

FLAG: Any assumption, uncertainty, or thing worth verifying. Skip if nothing applies.

For simple conversational exchanges, ignore the labels and just respond naturally.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

CONSTRAINTS — always active

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

× Do not start responses with "Great question!", "Certainly!", "Of course!", "Absolutely!", or any filler affirmation.

× Do not summarise what you're about to do before doing it.

× Do not add a closing line like "I hope this helps!" or "Let me know if you need anything else!"

× Do not use bold for decoration — only bold something if the reader genuinely needs to notice it.

× Do not repeat the question back to me before answering.

× If my request is vague, make one reasonable interpretation and state it, rather than asking 5 clarifying questions.

× Respect the experience level I provided above. Adjust vocabulary and depth accordingly.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

MEMORY — within this conversation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Remember everything I've told you in this conversation.

If I establish a preference ("keep it short", "use simple words", "give me bullet points"), apply it for all future responses without me repeating it.

If we have established a style, format, or vocabulary preference, maintain it.

---------------PROMPT END----------------

Why each section exists — every design decision explained

Role block -> Sets the baseline behavior for the entire conversation. Telling the model to be direct, honest, and willing to push back on bad ideas is the single most effective antidote to generic, sycophantic responses. Without this, the model defaults to agreeing with everything you say.

About Me block -> Context is the highest-leverage part of any prompt. The model doesn't know if you're a nurse or a student or a retiree. Without this, it guesses — and it usually guesses "generic professional." Four lines of real context transforms output depth, vocabulary, and relevance instantly.

<thinking> block -> Chain-of-thought reasoning before output. Research from 2024–2025 shows that asking the model to reason through a task before writing — even silently — improves accuracy on complex questions by a meaningful margin. Hidden reasoning means no clutter in the output, but better quality underneath it.

Rule 2: depth calibration -> Eliminates padded, bloated responses. The default model behavior is to write as much as possible to seem thorough. This rule inverts that: the model must earn every sentence. Short answers for short questions. Long answers only when genuinely needed.

Rule 3: format logic -> Stops inappropriate formatting. Without guidance, the model turns almost everything into bullet points — even when prose would be far more useful. This rule matches the format to what the content actually needs, not what looks like a thorough answer.

Rule 4: honesty guard -> The single most important safety rule. AI models hallucinate. Explicitly instructing the model to flag uncertainty — rather than sound confident about wrong things — meaningfully reduces fabricated facts. Not perfect, but a real, measurable improvement.

Rule 5: goal understanding -> Makes it act like an advisor, not a vending machine. If you ask "write me a cover letter for a job I'm underqualified for," a vending machine writes the letter. An advisor says "here's the letter, but you should know you're missing 3 of the 5 required qualifications — here's what to do about that."

ANSWER / DETAIL / NEXT STEP / FLAG format -> Predictable structure on every response. The direct answer always comes first — not after 2 paragraphs of preamble. Supporting detail only appears when it adds value. Next steps are concrete, not vague. Flags catch hidden assumptions before they cause problems.

Constraints block -> Kills the filler patterns trained into every AI. "Great question!" "Certainly!" "I hope this helps!" — these responses are trained in because users historically upvoted them. They add zero value. Explicitly banning them strips the output back to pure content.

Memory instruction -> Builds on the conversation instead of resetting every message. Within a single chat, the model remembers your preferences if you tell it to. Without this line, it often forgets a preference you stated 5 messages ago. With it, preferences accumulate through the session.

Three mistakes that kill this prompt's effectiveness

Vague About Me fields. "I'm a professional who works in business" tells the model nothing it doesn't already assume. "I'm a freelance graphic designer with 2 clients, trying to get to 5" gives it everything it needs. The specificity of your 4 lines directly controls the specificity of every response you get back.

Asking vague questions after a detailed prompt. The prompt sets up a great assistant. You still need to give it a real task. "Help me with my email" is not a task. "Write a follow-up email to a client who hasn't responded in 2 weeks about a project proposal" is a task. The prompt improves the response — it doesn't replace the question.

Starting a new chat for every single question. This prompt is designed for a session — a block of related work. Start a chat, paste the prompt, then ask everything related to that work in the same conversation. The model builds context. A new chat wipes it. For completely unrelated topics, start a fresh chat and paste the prompt again.

If you want more structured prompts like this — with the variables and the reasoning written out — I built a premium prompts library check my bio for link, There's also a Chrome extension that lets you run prompts like this from inside any AI chat without copying and pasting every session.

Most "productivity prompts" I see shared here are single-line task instructions. Those work. But the thing that actually changed how I use ChatGPT day-to-day was treating it less like a search engine and more like a briefed assistant who knows my context upfront.

This took about 3 months of daily iteration. The version below is what stuck. Copy it exactly, fill in the variables (they're in all-caps brackets), and paste it as your Custom Instructions system prompt, or as the first message in a fresh chat.

One rule: fill in every variable with real specifics about you. The more specific your values, the more specific the output. "marketing manager at a B2B SaaS startup" beats "professional" every time.

--------------PROMPT START--------------

## ROLE

You are [YOUR_ROLE] — a highly capable professional assistant with deep expertise in [YOUR_DOMAIN]. You think like a senior practitioner in this field: precise, opinionated where appropriate, and honest about uncertainty. You are not a yes-machine — push back on weak ideas, flag gaps, and ask one clarifying question if something is genuinely underspecified.

## CONTEXT — read before every response

About me: [YOUR_PROFESSIONAL_CONTEXT]

Current active projects: [YOUR_CURRENT_PROJECTS]

Today's date: [TODAY_DATE]

Key constraint to respect always: [YOUR_MAIN_CONSTRAINT]

## OPERATING RULES — follow these on every response

1. Before responding, reason through the task in a private <thinking> block (2–5 sentences). Consider: what is actually being asked, what are the 1–2 ways this could go wrong, and what would a senior practitioner in this field do first. Then respond outside the tags.

2. Default output format is structured prose — NOT bullet point soup. Use bullets only when the output is genuinely a list of discrete parallel items. Use headers only when the response is long enough to need navigation.

3. Calibrate depth to the request. A quick question gets a direct answer (1–3 sentences). A complex task gets a thorough response. Never pad to seem more helpful.

4. If you are unsure about a fact, say so explicitly. Do not hallucinate sources, statistics, or quotes. If you would need to search to verify something, flag it as "worth verifying."

5. When I give you a task, identify the actual goal underneath the task. If completing the task as stated would not serve that goal well, say so before doing it.

6. Match my energy and register. If I write casually, respond conversationally. If I'm in formal-document mode, match that.

## HOW TO HANDLE DAILY TASK REQUESTS

When I share a task or to-do item:

— First: restate what I'm actually asking in one line (no echoing my exact words — synthesize it)

— Then: identify whether this is a creation task, an editing task, a decision task, or a planning task

— Then: produce the output in the most useful format for that task type:

• Creation → draft the thing directly, don't ask 5 questions first

• Editing → show the change, explain why, preserve my voice

• Decision → give me your actual recommendation first, then the reasoning

• Planning → give me a numbered sequence with real first steps, not abstract phases

## OUTPUT FORMAT RULES

When producing structured content, use this hierarchy:

LEVEL 1 — a single bolded outcome statement ("What this gives you:")

LEVEL 2 — the actual content or deliverable

LEVEL 3 — (optional) a one-line note at the end flagging any assumption made or thing worth verifying

Never wrap a plain-text response in a code block. Never add "I hope this helps" or similar closers.

## MEMORY ACROSS THIS CONVERSATION

Track any decisions made or constraints added during our conversation. If I say "always do X" or "never do Y," apply it for the remainder of the session without me repeating it. If we've established a format or voice preference, maintain it.

-------------PROMPT END--------------

Common mistakes when using this

Don't fill in generic values. "I am a professional working in business" produces generic output. The specificity of the variables determines the specificity of everything that follows. If you're embarrassed about how specific you're being, you're at the right level.

Don't add 20 more rules. I've seen versions of this with 40 operating rules. The model starts to weight-average and everything regresses to generic. Six focused rules outperform twenty scattered ones.

Don't skip the thinking block. The <thinking> instruction is the highest-leverage single line in this whole prompt. If you strip it for "cleaner output," you lose the quality improvement it drives on complex reasoning tasks.

Drop your improvements in the comments. I'll update the prompt with whatever actually works and credit you.

If you want more prompts structured like this one — with the variables and the reasoning written out, not just a copy-paste block — I keep a library of them check link in my bio.

I built a free prompt library with 100+ optimized prompts (no fluff, just results)

I’ve been using AI tools daily for coding, writing, and building projects… and one thing kept frustrating me:

Most prompts online are either too generic or just don’t give good output.

So instead of searching every time, I started building my own prompt collection — and eventually turned it into a proper library.

Now it has 100+ prompts across different use cases like:

* Writing & content (blogs, ads, emails)

* Coding & debugging

* Business & marketing

* Learning & research

* Productivity & planning

* Creative writing

* AI prompt engineering itself

What makes it different:

* Prompts are structured (not random sentences)

* Designed to get clear, useful output (not vague answers)

* Actually tested while building real projects

* Covers practical use cases, not just theory

I’ve been using it myself while building apps and content, and it saves a lot of time.

It’s completely free, no signup needed.

If you’re someone who uses AI regularly, this might help you get better results faster.

👉 Prompt Library

I’ve been using AI tools daily for coding, writing, and building projects… and one thing kept frustrating me:

Most prompts online are either too generic or just don’t give good output.

So instead of searching every time, I started building my own prompt collection — and eventually turned it into a proper library.

Now it has 100+ prompts across different use cases like:

• Writing & content (blogs, ads, emails)
• Coding & debugging
• Business & marketing
• Learning & research
• Productivity & planning
• Creative writing
• AI prompt engineering itself

What makes it different:

• Prompts are structured (not random sentences)
• Designed to get clear, useful output (not vague answers)
• Actually tested while building real projects
• Covers practical use cases, not just theory

I’ve been using it myself while building apps and content, and it saves a lot of time.

It’s completely free, no signup needed.

If you’re someone who uses AI regularly, this might help you get better results faster.

👉 Prompt Library

I use AI daily for coding, writing, and problem-solving, and honestly… most prompts online just don’t work that well.

They’re either too vague or too “fancy” without improving results.

So I built a free prompt library (80+ prompts) that I personally use in real projects.

Instead of dumping random prompts, I focused on:

clear structure → better outputs

real-world use cases → not theoretical

reusable formats → easy to tweak

What’s inside

I organized everything into categories so you don’t waste time searching:

Writing & Content

Coding & Development

Business & Marketing

Analysis & Research

Creative Writing

Education & Learning

Productivity & Planning

Persona & Roleplay

Example (coding prompt I use often)

Act as a senior software engineer.

Purpose:

Help me debug and improve my code with clean, production-ready solutions.

Context:

- Language: [JavaScript / Python / etc]

- Problem: [describe the issue]

- Code:

[Paste your code here]

Instructions:

1. Identify the root cause of the issue

2. Explain it in simple terms (no jargon)

3. Provide a fixed version of the code

4. Suggest improvements for performance and readability

5. Mention any edge cases I should handle

Output:

- Clear explanation

- Updated code block

- Optional improvements

Why I made this

Most prompts online:

feel robotic

aren’t structured

don’t actually improve output quality

I wanted something that genuinely helps you get better results, faster.

If you’re into building with AI, this might save you a lot of time.

👉 Prompt Library

I used to struggle learning new coding topics because I’d ask things like:

“Explain closures”

“Teach me async/await”

And I’d get decent answers… but not something I could actually learn from step by step.

Then I switched to structured prompts (XML-style), and it completely changed how I learn.

Instead of asking vaguely, I guide the AI like a tutor:

<Purpose> Teach me a coding topic in a structured, beginner-friendly way </Purpose>

<Topic> JavaScript Closures </Topic>

<Context> Skill Level: beginner to intermediate What I know: variables, functions, basic JavaScript Goal: understand concept deeply and apply it in real projects </Context>

<Teaching_Method>

<Step_by_Step> Start from intuition → then definition → then technical explanation </Step_by_Step>

<Examples> Provide simple examples first, then real-world use cases </Examples>

<Code> Include clean, well-commented code snippets </Code>

<Practice> Give 2–3 small exercises to test understanding </Practice>

</Teaching_Method>

<Output> - Clear explanation (no jargon overload) - Code examples with comments - Real-world analogy - Practice tasks at the end </Output>

<Constraints> - Avoid skipping steps - Don’t assume advanced knowledge - Keep explanations simple but not shallow </Constraints>

<Style> Friendly, like a mentor explaining patiently Focus on clarity and understanding </Style>

Why this works so well:

You’re not just asking for info — you’re defining a learning system

It forces structured teaching instead of random explanations

You actually retain concepts instead of just reading them

Big realization for me:

If you want better answers, stop asking better questions…

Start designing better prompts.

Disclaimer: You can generate and organize structured XML prompts like this using GPT SmartKit — a free lightweight Chrome extension.

Most outreach emails fail for one simple reason: they sound generic.

I used to write them the same way — decent wording, but no replies.

Then I started using structured prompts (XML-style), and it changed how the emails came out. Way more targeted, way more human.

Here’s the exact kind of prompt I use now:

<Purpose>

Write a personalized cold outreach email to a potential client

</Purpose>

<Context>

Sender: freelance frontend developer

Service: building modern, responsive websites and UI improvements

Goal: get a reply or book a short call

Platform: email or LinkedIn DM

</Context>

<Target_Prospect>

Type: small business owner / startup founder

Situation: likely has an outdated or poorly optimized website

Pain_Points:

- low conversion rate

- slow website performance

- outdated UI/UX

</Target_Prospect>

<Personalization>

Mention that you reviewed their website or product

Highlight 1 specific observation (keep it realistic, not fake praise)

</Personalization>

<Offer>

Suggest a quick improvement idea (e.g., redesign section, speed optimization)

Keep it low-commitment and helpful, not salesy

</Offer>

<Output>

- Subject line (if email)

- Opening line (personalized)

- Short body (3–5 sentences max)

- Clear CTA (reply or quick call)

</Output>

<Constraints>

- Avoid generic phrases like "I hope you're doing well"

- No long paragraphs

- No hard selling

- Keep it under 120 words

</Constraints>

<Style>

Natural, human, slightly informal

Confident but not pushy

Feels like a real person, not a template

</Style>

Why this works better:

- You’re forcing real personalization, not fake fluff

- The AI focuses on outcome (reply), not just writing nicely

- It naturally avoids spammy patterns

- You can reuse it across niches just by changing context

The biggest shift?

You stop asking “write an email” and start defining how it should think.

---

If you’re doing cold outreach and not getting replies, your prompt structure might be the real problem.

---

Disclaimer: You can generate and organize structured prompts like this using GPT SmartKit — a free lightweight Chrome extension.

I use ChatGPT a lot, and over time I noticed the same problems:

• writing good prompts takes too much effort
• I keep repeating the same prompts
• long chats get messy fast
• useful outputs get lost

So I built a lightweight extension to fix this for myself.

GPT SmartKit - AI Prompts, ChatGPT Tools & Utilities

What it adds

Better prompts without overthinking

• simple prompt builder (form style)
• improves your prompts automatically
• lets you save and reuse them
• can run step-by-step prompt flows

AI help anywhere (not just ChatGPT)

• works inside text inputs on any website
• rewrite, improve, or expand what you write
• select any text → get instant suggestions or summaries

Cleaner chat experience

• collapse long chats into sections
• export chats when needed
• small UI improvements that make it easier to use daily

Why I like it:

It doesn’t try to do everything.
It just removes friction and makes ChatGPT more practical to use.

Also kept it super lightweight (~200KB), so it doesn’t slow anything down.

Thanks for reading

I’ve been using ChatGPT a lot lately, and a few things kept slowing me down.

Writing good prompts takes more effort than it should.
Long chats get messy fast.
And I keep repeating the same prompts again and again.

So I started building a small tool for myself to fix this.

It helps you:

• build prompts using a simple form
• improve prompts with suggestions
• save and reuse them
• run step-by-step prompt flows

It also adds AI features outside ChatGPT, which I found really useful:

• works in text inputs on any website to rewrite or improve content
• lets you select any text and instantly get suggestions or summaries

Plus a few small things like making long chats easier to navigate and exporting them.

It will be available for you soon and it is completely free

what’s the most annoying part of using ChatGPT for you right now?

Thanks for reading