AI Resource Center

How to Write AI Prompts: The AliNQuality Prompt Formula

A is the instruction you give an AI tool, and this five-part formula turns a vague request into one that gets a useful first draft.

Quick answer

What it is
A simple, repeatable way to write AI instructions that get better results.
What it helps with
Turning vague requests into clear prompts for drafting, summarizing, and organizing work.
When to use it
Any time an AI tool gives you a generic or off-target answer.
What to review
Facts, numbers, tone, and anything customer-facing, before you use the output.
Related terms
  • prompt
  • context
  • constraint
  • output
  • prompt engineering

Why your instructions matter

An AI assistant does not read your mind. It responds to what you type. Give it a vague request and it fills the gaps with generic assumptions; give it a clear one and it produces something you can actually use. The first answer is always a draft, and the quality of that draft is set mostly by the quality of your instruction.

The good news is that this is a learnable habit, not a talent. Writing clearer instructions and adjusting them when the result is off is all that really is. You do not need special phrases or technical knowledge. You need a simple structure, which is what the formula below provides.

Consider the difference in practice. Ask an assistant to “write a thank-you email” and you get a generic note that could belong to any business. Ask it to “write a short, warm thank-you email to a customer who just booked their first appointment, mentioning we will send a reminder the day before,” and you get something you can almost send as is. Same tool, same effort to type. The only thing that changed was how much you told it. Every ingredient in the formula is just a prompt to yourself: did I say who, what, and within what limits?

The AliNQuality Prompt Formula

Role · Task · Context · Constraints · Output

Five ingredients. You do not always need all five, but naming them keeps you from leaving out the part that would have made the difference. Here is each one, with a before-and-after from everyday business work.

1. Role: who the AI should act as

Telling the tool what part to play shapes its tone and focus.

Vague

Write something for my business.

Clearer

You are a friendly assistant for a small plumbing company, writing to a customer.

2. Task: what you want it to do

State the single action clearly.

Vague

Help with this email.

Clearer

Draft a reply confirming the appointment and asking for the gate code.

3. Context: the background it needs

is the situation the tool cannot see: who the message is for, your business, and the facts it should not guess.

Vague

Summarize this meeting.

Clearer

Summarize these notes from our Monday staff meeting for a teammate who missed it; we run a two-location bakery.

4. Constraints: the limits to respect

A sets boundaries (length, tone, and what not to do) so the answer fits how you will use it.

Vague

Make it good.

Clearer

Under 90 words, warm and plain, no exclamation marks, and do not invent a price.

5. Output: how the answer should arrive

The instruction can specify format, structure, length, or tone: bullets, a table, a subject line plus body, or a checklist.

Vague

Give me some ideas.

Clearer

Give me five options as a short bulleted list, each under ten words.

Putting it together

Assemble the five parts and you get a prompt that leaves little to chance. Here is a complete example for a common task, replying to a quote request:

Role: You are a helpful assistant for a small landscaping business, writing on my behalf.
Task: Draft a short email replying to a customer who asked for a quote on weekly lawn care.
Context: The customer is Alex, with a medium suburban yard in Nyack. We charge by yard size and visit weekly. I am Sam, the owner. I have not seen the yard yet.
Constraints: Under 120 words, friendly and plain, no exact price since I have not measured the yard, and propose a quick visit to quote accurately.
Output: Give me a subject line and the email body, then note anything I should fill in before sending.

Build your own below. The builder assembles the five parts as you type and gives you a prompt you can copy into any assistant. When you find one that works, save it, or browse ready-made prompts in the prompt library.

Reviewing what comes back

A clearer prompt gets a better draft, not a finished product. Before you use any AI output, a person checks four things: facts (names, dates, claims), numbers (prices, totals, calculations), tone (does it land right for the reader), and anything customer-facing that carries your name.

Remember that these tools vary their answers by design, so the same prompt can return different wording on different runs and in different tools. That is normal, and it is the reason review is part of the workflow rather than an afterthought. You stay responsible for what is true, what adds up, and what represents your business.

Common mistakes

  • A vague task. “Help me with this” gives the tool nothing to aim at. Name the single action you want.
  • Missing context. Leaving out who it is for and the key facts forces the tool to guess, and it guesses generically.
  • No output format. If you do not say how the answer should arrive, you get a shape you then have to reformat by hand.
  • Accepting the first draft. Treating the first answer as final skips the refining step where most of the value actually is.

Prompt Writing: Quick Questions

Does this formula work in every AI tool?

Yes. The formula is tool-agnostic. It is simply a way to give clear instructions, which every general assistant responds to. You can paste a prompt built this way into any of them, and the skill carries over when you switch tools.

  • Role · Task · Context · Constraints · Output
  • Works in any assistant
  • Before/after examples
  • Live builder
Why do I get a different answer each time I run the same prompt?
By design. These tools introduce some variation, so the same prompt can produce different wording or structure on different runs and in different tools. That is exactly why reviewing the result (rather than assuming it is fixed) is part of the process.
How long should a prompt be?
Long enough to be clear, short enough to stay focused. A single specific sentence often beats a paragraph of vague wishes. Add context and constraints until the tool has what it needs, then stop. Padding does not improve the result.
Do I need prompt engineering skills to start?
No. Prompt engineering is just the habit of writing clearly and refining when the result is off. If you can describe what you want, who it is for, and the limits, you already have the core of it; the formula gives you the structure.