AiTechWorlds
AiTechWorlds
Five elements — Role, Context, Task, Format, Constraints — consistently separate a great prompt from a mediocre one, across ChatGPT, Claude, and Gemini alike.
Think of briefing a new freelance contractor by phone versus handing them a written spec sheet. The phone call leaves gaps they have to guess at; the spec sheet tells them who they're building for, what's expected, how to deliver it, and what to avoid. A prompt missing any of these five pillars is the phone call — the model fills the gaps with guesses. Master all five and you will get better results than 95% of AI users.
The single most impactful change you can make to any prompt is assigning a role to the AI.
Why it works: LLMs are trained on billions of texts from every domain. When you assign a role, you activate a specific cluster of knowledge, tone, and approach. "You are a cardiologist" pulls different patterns than "You are a fitness blogger" — even for the same question about heart health.
Without role: "Explain machine learning"
→ Gets a textbook-style, generic explanation
With role: "You are a senior ML engineer at Google who
explains complex concepts to junior developers using
real-world analogies and practical code examples."
→ Gets an accessible, practical explanation with codePower roles to try:
Context is the background information the AI needs to give you relevant answers. Without context, the model guesses — and guesses wrong.
Without context: "Write a marketing email"
→ Gets a generic template
With context: "I run a B2B SaaS company selling project management
software to construction companies with 50-500 employees. Our
average deal size is $15K/year. Our main competitor is Procore.
Write a cold outreach email targeting construction project managers."
→ Gets something you could actually sendWhat to include in context:
The task is the actual instruction — and precision here matters enormously.
Weak task words: "Write about", "Tell me", "Help with"
Strong task words: "Analyze and identify", "Write a [specific type] that [specific goal]", "Create a [format] with [specific elements]", "Compare X and Y across [specific dimensions]"
Weak: "Help me with my resume"
Strong: "Review my resume for a senior product manager role
at a Series B fintech startup. Identify: (1) three specific
weaknesses, (2) two achievements that need stronger metrics,
(3) whether my summary matches a PM profile. Format as a
numbered list with specific suggested rewrites."Explicitly specifying format is one of the most underused tactics in prompt engineering. The AI has no idea what format serves you — unless you tell it.
Common format specifications:
"Return the analysis as a JSON object with this exact structure:
{
'strengths': ['string', 'string', 'string'],
'weaknesses': ['string', 'string'],
'recommendation': 'string',
'confidence': number // 0-100
}"This is especially critical when you're feeding AI output into other systems or code.
Constraints tell the AI what NOT to do — and they're just as important as telling it what to do.
Common constraints:
Write a product description for noise-canceling headphones.
Constraints:
- Do NOT use "revolutionary", "game-changing", or "amazing"
- Do NOT use superlatives
- Maximum 100 words
- Focus only on sound quality and comfort
- Target audience: commuters who value focusCombining all five pillars:
You are [ROLE] with expertise in [DOMAIN].
Context: [Background information]
Task: [Specific request with action verb]
Format: [How the output should look]
Constraints:
- [Rule 1]
- [Rule 2]
- [Rule 3]Take any task you regularly use AI for and rebuild the prompt using all five pillars. Compare the result with your old prompt. The difference will be immediate and significant.
Example transformation:
Before: "Write a blog post about productivity"
After: "You are a productivity writer for busy tech professionals. Context: My audience are software engineers who work remotely and struggle with context-switching. Task: Write a 700-word blog post about the 'time-blocking' technique with a specific implementation guide for developers. Format: Introduction hook, 3 main sections with H2 headers, practical tips section, strong CTA. Constraints: No generic advice, use developer-specific examples, avoid the word 'simply'."
In the next lesson, we dive deep into Role-Based Prompting — the single most powerful individual technique.
Get this course's notes on Telegram!
Free cheat sheets, summaries & practice exercises