Unit 2 / 12

Good Prompt Anatomy: Role, Context, Task, Format, Example, Constraint

Gains:

  • List the six basic components of an effective prompt and explain the function of each.
  • You can strengthen a weak prompt step by step with these components
  • Can make conscious decisions about what components are needed for a task

The quality of the response you get from the AI depends largely on the quality of the instructions you give it. Telling the same model to "write an email" and giving a well-structured instruction produces completely different results. In this unit, we will learn the six basic components, or "anatomy", of an effective prompt. If you know these six pieces, you can build a powerful instruction for any task in your business, and if you don't like what's going on in the output, you can quickly find which piece is missing.

What is Prompt?

A prompt is an instruction or question you give to the AI. A good prompt tells the model what you want clearly, completely and without any room for misunderstanding. A bad prompt, on the other hand, forces the model to fill in the gaps with its own assumptions and often produces generic, inaccurate answers. The purpose of learning anatomy is to consciously close these gaps.

Six Essential Components

You can think of a powerful prompt as consisting of six building blocks. Not all of them are needed for every task; But knowing these means having a checklist in your hand.

1. Role (Persona)

Tell the model from which perspective she will speak. Role; determines the terminology, tone and depth to be used. When you say, “Act like an experienced financial advisor,” the model gives a more technical and careful answer to the same question than a student. (We will cover the role in depth in unit 9.)

2. Context

It is the background information needed for the model to understand the situation. For whom, for what purpose, under what conditions? If the context is missing, the model remains in the air and produces a generic text. The sentence “This email is going to a valued corporate customer who has been 3 months behind on their payment but has been with us for a long time” gives the model critical information to set the tone.

3. Task

Tell it with a clear action exactly what you want it to do. Use concrete verbs such as "write", "summarize", "compare", "classify", "list". The task is the heart of the prompt; A fuzzy task verb blurs the entire output.

4. Format

Specify what you want the output to look like: bullet list, table, paragraph, how many words, with what headings? If you don't say this, the model will apply its own preference, which usually won't fit your business. (We will detail format forcing in unit 7.)

Example 5

If possible, show an example similar to the output you want. Saying "I want something like this" is often more effective than describing at length because the model mimics the example. (We will see this technique in depth in unit 5.)

6. Constraint (Limits)

State what you don't want done and limits: "Don't use technical jargon", "Don't promise prices", "150 words maximum", "Just rely on the information I give you, it's fictitious". Constraints are guardrails that prevent the output from straying in wrong directions and are the most valuable component that many people skip.

Seeing the Components Together

The following table compares a weak and strong prompt:

component

Weak Prompt

Powerful Prompt

Role

(none)

"Act like an experienced customer relations expert"

Context

(none)

"To a valuable, 4-year old corporate customer whose payment is delayed"

Quest

"Write an email"

"Write a polite but clear payment reminder email"

Format

(none)

"120 words maximum, 3 short paragraphs, formal but warm tone"

example

(none)

"Solution oriented as in our previous successful reminders"

constraint

(none)

"Using threatening statements; mentioning legal process"

Step by Step: Strengthening a Weak Prompt

You have this: “Write a blog post.” Now let's add the components in order.

  1. Clarify the task: “Write a blog post about our cloud accounting software.”
  2. Add role: “Write like a finance content editor writing for small businesses.”
  3. Add context: "Readers are SME owners who do not understand accounting; the goal is to sign up for the trial version."
  4. Add format: "700-800 words, 4 subheadings, a question at the beginning, a one-sentence appeal at the end."
  5. Add restriction: "Don't name a rival brand; don't use exaggerated promises; plain Turkish."
  6. Add an example: "Similar in tone to this paragraph: [sample paragraph]."

With each step, the output gets closer to what you have in mind. That's the power of anatomy: instead of trying randomly, you add the missing component on purpose.

Four Copiable Templates

1) General purpose frame:

Role: Act as someone experienced in [expertise].Context: [for whom, for what purpose, in what situation].Task: [single clear verb] ...Format: [length, structure, headings].Constraint: [do what, what limits].

2) Writing an email:

Role: Corporate communications specialist.Context: Recipient [who], relationship [situation], purpose [what].Task: Write [information / reminder / apology / offer] email.Format: No more than [X] words, [tone] tone, with a clear closing sentence.Constraint: Promise, exaggeration; Just rely on the information I give you.

3) Text summarization:

Task: Summarize the following text.Format: Maximum [X] items; Each item is a decision/action. Restriction: Do not add any information that is not in the text; add comment.Context: This summary will be used for [who], for [purpose].Text:[text]

4) Comparison table:

Task: Compare [A] to [B].Format: Markdown table; columns: Criteria | A | B.Context: Decision maker [who], priority [what].Constraint: Exact price/figure fitting; When you're not sure, write "uncertain."

Weak Prompt / Strong Prompt

Weak:

Prepare an agenda for the meeting.

Strong:

Role: Act as an experienced project manager.Context: 45-minute weekly team meeting; 6 people; The topic is new product launch delay.Task: Prepare an agenda with time box (minutes allocated for each item).Format: Table; columns: Topic | Duration | Responsible | Expected output.Constraint: Total time should not exceed 45 minutes; There should be a maximum of 6 items.

Three Mini Cases

Case 1 — Sales. A sales team was constantly receiving cold texts with the "write offer email" prompt. When role, context, and format were added, the initial response rate increased significantly according to the team's own measurement; What changed was not the model, but the instruction.

Case 2 — Legal assistant. A law firm assistant did not add constraints when requesting a contract summary, and the model sometimes added comments. After adding the restriction "Based only on what is written in the article, do not make inferences", the summaries became ready for audit and the lawyer's correction time was reduced by approximately half.

Case 3 — Education. When a corporate trainer said "write a presentation plan," he was getting messy 20-slide drafts. When I fixed the format as "8 slides, title + 3 articles + 1 example on each slide", the drafts became directly usable.

Tip: When you don't like the output, ask: "What component was missing?" The answer is usually context or constraint; because most people write the task and format but skip these two.
Attention: Adding components does not mean "longer prompt is always better". The goal is clarity, not length. Unnecessary, contradictory or irrelevant details may confuse the model. Let every sentence have a purpose.

Common mistakes

  • Just write the task. Saying "write an email" and skipping the role, context, format and constraint; This is the most common mistake.
  • Forget the constraint. Not saying what is not wanted. The model adds whatever it deems "safe" because it doesn't know.
  • Conflicting ingredients. Giving self-contradictory instructions such as "It's very short but includes all the details."
  • Mistaking the context for duty. Writing pages of background information and not explaining clearly what to do.
  • Choosing the sample of poor quality. The model imitates the sample; bad example produces bad output.

In summary

  • Six components of a strong prompt: role, context, task, format, example, and constraint.
  • The role determines the point of view, the context determines the background, the task determines what to do, the format determines the format, the example determines the desired result, and the constraint determines the boundaries.
  • Not all of them are needed for every task; The more important and specific the result, the more ingredients you add.
  • The constraint component that most people skip is the most valuable part that protects the output from straying in wrong directions.
  • The goal is clarity, not length; Let each sentence have a function.

Application task

Choose a task you do frequently at work and write the weak one-sentence version first. Then reinstall the prompt by adding the six components one by one; Reproduce the output as you add each component and note which addition makes the biggest jump. Save the resulting powerful prompt for next time.

checklist

  • [ ] I can recite the six components (role, context, task, format, example, constraint).
  • [ ] I can explain with an example how each component affects the output.
  • [ ] I can strengthen a weak prompt with components step by step.
  • [ ] I'm adding the constraint component on purpose.
  • [ ] I focus on clarifying the prompt rather than making it longer.