AI Prompt Engineer

The Prompt

You are an specialist prompt engineer with deep knowledge of:

Models: GPT-4, Claude, Gemini, LLaMA, Midjourney, DALL-E, Stable Diffusion
Techniques: Few-shot learning, chain-of-thought, role-playing, constraints
Optimization: Token efficiency, response quality, consistency
Applications: Text generation, image creation, code writing, data analysis
Testing: A/B testing prompts, quality metrics, refinement strategies

When engineering prompts:
1. Analyze the task requirements and constraints
2. Select optimal prompting techniques
3. Structure prompts for clarity and effectiveness
4. Include examples and edge cases
5. Iterate based on output quality

Provide:
- Multiple prompt variations to test
- Explanation of techniques used
- Expected outputs and quality metrics
- Refinement strategies
- Cross-model compatibility notes

How to Use This Prompt

1. Replace placeholder text with your specific productivity requirements
2. Provide detailed context and examples for best results
3. Iterate on the output to refine and improve
4. Save successful prompts for future use
5. Combine with other prompts for comprehensive solutions

When This Prompt Is Most Useful

Use this prompt when you need help with ai engineer but do not want a generic answer. It works best for founders, managers, consultants, and teams making practical business decisions who already have some context and want the AI to organize it into a decision memo, options analysis, operating plan, risk register, or next-step checklist. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.

This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.

Inputs to Prepare

Before running the prompt, gather:

• The real goal or decision you are trying to support
• The audience, customer, learner, stakeholder, or user involved
• Any source material the AI should use instead of guessing
• Constraints such as deadline, format, budget, word count, platform, or policy
• Examples of good and bad outputs if you have them
• The exact tone you want the final answer to use

For this page, the most important context is: business model, customer segment, current constraint, data available, decision deadline, and options already considered. If you leave that out, the model may still respond, but the result will usually be generic.

Example Input

Company: B2B SaaS at $35k MRR. Problem: onboarding drop-off. Goal: choose the next two experiments.

How to Review the Output

Do not use the first answer blindly. Check whether it:

• defines the decision before recommending actions
• compares options instead of forcing one answer
• turns strategy into measurable next steps
• makes assumptions visible instead of hiding them in confident language
• gives you something you can act on, test, or revise within the same work session

If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.

Common Failure Modes

• Too little context: the AI fills gaps with generic advice.
• No review criteria: the output sounds polished but is hard to judge.
• Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
• Overclaiming: the model may invent certainty when the source material is weak.

The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.

Practical Variations for AI Prompt Engineer

• Diagnosis mode: Ask whether the real constraint is demand, positioning, operations, pricing, distribution, or execution.
• Options mode: Request three options with cost, upside, downside, risk, and evidence needed.
• Execution mode: Ask for a 30-day plan with owner, metric, checkpoint, and rollback condition.

Follow-Up Prompts

Use these after the first answer:

• “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
• “Give me a conservative version, a direct version, and a version optimized for speed.”
• “Create a final review checklist I can use before I publish, send, ship, or present this.”

What Makes This Page Different

This page is useful when you are working on ai engineer and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.