Prompt Engineering Prompting Fundamentals Intermediate

Prompt Engineering Basics

Learn the foundations of prompt engineering, including how to structure prompts with Persona, Task, Context, and Format, and master techniques like Zero-Shot, Few-Shot, Step-Back, and Chain of Thought prompting to achieve precise, business-ready results from AI.

Best Model
ChatGPT GPT-5.5 Thinking / Claude Opus 4.7Prompt architecture
Brevity Mode
Detailed
Difficulty
Intermediate
Automation
Needs user context

Use This When

General business and marketing workflows.

Inputs Needed

Model/tool, objective, inputs, constraints, output format, examples, evaluation criteria.

Expected Output

Reusable prompt template with variables, instructions, examples, output format, validation tests.

The Workflow Prompt

Copy-paste ready. Replace [bracketed placeholders] with your specifics.
You are a prompt engineer and AI workflow architect.

Objective:
Prompt Engineering Basics

Context:
Learn the foundations of prompt engineering, including how to structure prompts with Persona, Task, Context, and Format, and master techniques like Zero-Shot, Few-Shot, Step-Back, and Chain of Thought prompting to achieve precise, business-ready results from AI.

Original task:
Supporting Notes for This LessonThis video introduces the core foundations of prompt engineering—the skill of designing clear, structured instructions that guide AI to deliver business-ready results.Key Takeaways:Stop treating AI like Google. Asking vague questions leads to vague answers.Think like a director, not just a user. Your job is to instruct, not just ask.The PTCF FrameworkPersona – Assign a role to the AI (e.g., “You are a senior marketing manager…”).Task – Use clear action verbs (e.g., create, summarize, rewrite, analyze).Context – Add the background info the AI needs (most prompts fail here).Format – Tell the AI exactly how you want the response (e.g., bullet points, table).Prompting Techniques CoveredZero-Shot Prompting: No examples needed—just a clear, structured prompt.Few-Shot Prompting: Include one or more examples to “show” the AI what good looks like.Step-Back Prompting: Start broad to help the AI gather relevant knowledge before narrowing in.Chain of Thought (CoT): Add phrases like “Let’s think step by step” to improve logic and reasoning.Choosing the Right AI for the JobStandard Models – Fast, great for simple tasks like summaries or rewrites.Reasoning Models – Better for multi-step problems and strategic tasks.Deep Research Models – Use for high-stakes, in-depth analysis (trade speed for depth).Best PracticesKeep prompts clear and simple—if it’s confusing to you, it’s confusing to the AI.Be specific about the output (length, style, format).Use instructions over constraints—tell the AI what to do, not just what to avoid.

Inputs I may provide:
Model/tool, objective, inputs, constraints, output format, examples, evaluation criteria.

Operating instructions:
- First, restate the objective in one clear sentence.
- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.
- Use a Detailed response style.
- Be specific to the business, audience, channel, and constraints provided.
- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.
- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.
- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.
- End with a short QA checklist that helps me verify the output.

Required output:
Reusable prompt template with variables, instructions, examples, output format, validation tests.

Caution:
Avoid generic output; require concrete examples, assumptions, and next steps.

QA Follow-Up Checklist

After the AI returns its output, verify against:

  1. Output is specific to the provided business/context.
  2. Assumptions are clearly labeled.
  3. No unsupported claims without source checks.
  4. Next actions are clear and usable.

Follow-Up Prompt

Run this next to refine the first output into a client-ready version.
Now turn the result for 'Prompt Engineering Basics' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.

Avoid / Cautions

Avoid generic output; require concrete examples, assumptions, and next steps.

How Different Verticals Use This Workflow

Restaurant & Hospitality

A regional taco chain operations lead learning prompt engineering builds a PTCF template for the weekly food cost report. Persona: senior restaurant CFO. Task: spot anomalies in COGS by location. Context: pasted invoice data + sales by SKU. Format: table of flagged variances + recommended action. Cuts a 2-hour Monday task to 12 minutes.

Retail & E-commerce

A DTC apparel ops manager learns prompt engineering to triage 800 customer service emails per week. Builds a few-shot prompt with 5 real classified examples (refund, sizing, shipping, defect, other), specifies JSON output with category + sentiment + suggested action. Cuts triage time from 9 hours/week to 90 minutes.

Professional Services & B2B

A junior associate at a 60-person consultancy learns prompt engineering by building a meeting prep template using PTCF. Persona: principal consultant. Task: prep brief for a Tuesday meeting with a CFO at a $200M company. Context: pasted LinkedIn profile + last earnings call. Format: one-page brief with 5 questions + 3 likely objections. Saves the principal 90 min/week and gets her promoted to the room.

Beauty & Personal Care

A salon owner with 4 chairs learns prompt engineering to draft response templates for negative Google reviews. Builds a chain-of-thought prompt that reasons through the complaint, identifies the operational fix, drafts a response that doesn't make legal claims, and flags whether the customer should be invited to call. Cuts review-response time from 40 min to 6 min per review.

Local & Trade Services

A residential GC with 12 jobs in progress learns prompt engineering to weekly summarize his project status notes for clients. PTCF: persona is a project manager, task is a 200-word client update, context is pasted voice memos transcribed, format is a numbered list with timeline + next steps + photos to attach. Cuts Sunday admin from 4 hours to 35 minutes.

Frequently Asked

What does PTCF actually look like in a working prompt?

Persona: 'You are a senior B2B SEO strategist who's done 200+ technical audits.' Task: 'Audit the following site for crawl waste and indexation issues.' Context: paste the site URL, last 3 months of GSC data, and the niche. Format: 'Return a table with: issue, severity, page count affected, fix.' Most prompts fail at context (people skip it) or format (they say 'be detailed' instead of specifying structure). Both are non-negotiable. Without them, you're playing 20 questions with a smart intern.

When should I use Few-Shot vs Zero-Shot vs Chain-of-Thought?

Zero-shot for tasks the model has clearly seen 10,000 times (summarize, translate, classify standard categories). Few-shot when the output format is custom or your brand voice is specific — give it 3-5 real examples. Chain-of-thought when the task requires reasoning (math, multi-step diagnosis, dependency mapping). Don't bolt CoT onto creative tasks; you'll get over-explained, defensive output. The mistake is using few-shot for everything because it 'feels safer.' It eats context window and slows you down.

Should I use ChatGPT 5.5 Thinking or Claude Opus 4.7 for learning prompt engineering?

Claude Opus 4.7 to learn the principles — it tells you when your prompt is ambiguous instead of guessing. ChatGPT 5.5 Thinking to test your prompts at scale because it's faster and most teams deploy on OpenAI. Practice on Claude, ship on ChatGPT or whatever the org already pays for. The principles transfer; the tool-specific quirks (system prompt position, JSON mode behavior, tool-calling syntax) you learn on the job.

What's the most common failure mode for beginners writing prompts?

Treating the prompt as a question instead of a brief. 'Write me a blog post about AI in marketing' is a question. 'Write a 1,200-word blog post for CMOs at $50M-$500M B2B SaaS companies, structured as 5 myths about AI in marketing with one paragraph of debunking each, ending with one tactical recommendation per myth, in a direct opinionated voice that's already used at companies like Stripe Press' is a brief. The second one gets you something usable on the first try. The first one gets you 6 regenerations.

Related Workflows

Copied to clipboard