Write Better Prompts

Better prompts usually come from clarity, not complexity.

Start with One Clear Job

A strong prompt usually does one thing well.

Good:

• Rewrite this to sound more professional.
• Turn this into three action items.
• Translate this into plain German.

Weaker:

• Rewrite this, shorten it, make it funny, add strategy advice, and turn it into a sales pitch.

If you want several different outcomes, split them into separate prompts.

Tell TypeBoost What Good Looks Like

If the results feel vague, add more direction:

• the tone you want
• the length you want
• the structure you want
• what to avoid

Example:

Rewrite the text to sound warm and professional. Keep it under 120 words. Keep the main point. Do not add extra explanation.

That gives the AI a much better target.

Use a Simple Prompt Structure

You do not need a complicated framework. For prompts you plan to reuse, cover four things:

1. Task: What should the action do?
2. Context: What does it need to know about the reader or situation?
3. Constraints: What must it preserve, include, avoid, or limit?
4. Output: What should the final result look like?

Example:

• Task: Turn the selected notes into a project update.
• Context: The reader knows the project but not the technical details.
• Constraints: Preserve every date, owner, and commitment. Do not invent progress.
• Output: Use a short summary followed by bullets for completed work, blockers, and next steps.

You can write that as one natural instruction. The labels simply help you notice what is missing.

Split Complex Work into Steps

One prompt can contain several related steps, but the result becomes harder to check when the jobs are unrelated.

For a larger workflow, separate the stages:

1. Organize the source material.
2. Create the first draft.
3. Review the draft for a specific audience or constraint.

This gives you a visible result at each stage. It is easier to correct an outline before it becomes a full document than to repair the complete output afterward.

Use Examples Only When You Need Them

Many prompts work with one clear instruction.

Examples help when you need:

• a very specific tone
• a specific format
• more consistency across repeated runs

In TypeBoost, those examples usually live in the extra user and assistant messages inside the prompt.

Use them when they help. Do not feel forced to add them to every prompt.

Improve a Prompt Through Real Use

The fastest way to improve a prompt is to test it on real work.

When a result is close but not right, edit the prompt and try again.

Small changes are usually enough:

• make the tone clearer
• limit the length
• say “return only the final text”
• add one useful example

Keep a short note about the input you tested and the problem you changed. If two saved prompts now solve the same job, keep the clearer one and retire the duplicate. A small library you understand is more useful than a large collection you cannot trust.

Use Learn the Right Way

Learn is for cases where the AI result is close, but you still need to improve it.

Edit the result inside TypeBoost first.

After you change the output, Learn can save:

• the original input
• your improved output

TypeBoost stores that as a user and assistant example pair inside the prompt.

That gives the prompt a better example to follow on similar inputs later.

What Learn means:

• it saves a corrected example for that prompt
• it works like a few-shot example

What Learn does not mean:

• model training
• changes to the AI model itself

So use Learn after you improve a result and want the prompt to learn from that correction.

Keep Prompt Writing Practical

If a prompt works well in daily use, it is a good prompt.

Do not optimize for theory. Optimize for whether it makes your work faster and more consistent.

Next: Instant Actions on Mac