Most of us start prompt engineering the same way: we type an instruction and hope the model behaves. “Write a 300-word product blurb for wireless earbuds. Mention noise cancelling and battery life.” “Write a 300-word product blurb for wireless earbuds. Mention noise cancelling and battery life.” That’s basic prompting: human designs the prompt, model executes. basic prompting human designs the prompt, model executes Meta-prompting flips the workflow. You ask the model to become the prompt designer. Meta-prompting flips the workflow. “Create a prompt that will make an LLM write a 300-word earbuds blurb, highlighting noise cancelling and battery life, with a punchy CTA.” “Create a prompt that will make an LLM write a 300-word earbuds blurb, highlighting noise cancelling and battery life, with a punchy CTA.” Now the output isn’t the blurb. The output is a prompt that reliably produces the blurb. prompt that reliably produces If normal prompting is “give me the fish,” meta-prompting is “build me a fishing rod… and label the parts.” Why Meta-Prompts Matter Meta-prompts are not here to replace your thinking. They’re here to remove your busywork. busywork 1) Lower the barrier for non-experts If you’re a primary school teacher in Manchester, you may know what you want (“Year 4 reading comprehension”), but not how to specify: text length
difficulty level
question mix
answer + explanation format text length difficulty level question mix answer + explanation format A meta-prompt lets you describe the goal and lets the model handle the prompt scaffolding. goal prompt scaffolding 2) Standardise quality across teams In organisations, prompt inconsistency is a silent killer. One person writes “Please help…”   Another writes “Return JSON only…” Then everyone wonders why outputs vary wildly. Meta-prompts help teams generate prompt families with the same structure, tone, and constraints—especially when you need 10 variations, not 1 masterpiece. prompt families 10 variations, not 1 masterpiece 3) Upgrade complex prompts For multi-step tasks—academic writing, data analysis, code refactors—humans often forget “obvious” constraints: structure (sections, headings)
evidence requirements
length limits
error handling
formatting rules structure (sections, headings) evidence requirements length limits error handling formatting rules Meta-prompts force those requirements into the prompt itself. 4) Adapt to dynamic contexts (parameterised prompts) If your prompt needs to change by audience (students vs managers vs customers), meta-prompts can generate parameterised prompts that “snap-fit” different inputs. parameterised prompts That’s how you stop rewriting the same prompt 30 times. The 4-Part Meta-Prompt Blueprint A strong meta-prompt usually contains four modules: Task definition — what the generated prompt should achieve
Constraints — format, content, style, forbidden items
Example — a reference prompt (optional, but powerful)
Optimisation guidance — how to make the prompt efficient and robust Task definition — what the generated prompt should achieve Task definition Constraints — format, content, style, forbidden items Constraints Example — a reference prompt (optional, but powerful) Example Optimisation guidance — how to make the prompt efficient and robust Optimisation guidance efficient and robust Think of it like a product spec for prompts. 1) Task definition: define the real job Bad: “Generate a prompt for writing a report.” Better: “Generate a prompt that helps an e-commerce ops analyst write a monthly performance report with KPIs, issues, and next steps.” Include: task type (write / analyse / code / summarise)
scenario (who, where, why)
expected result (structure, artefacts, success criteria) task type (write / analyse / code / summarise) scenario (who, where, why) expected result (structure, artefacts, success criteria) 2) Constraints: set rails, not cages Useful constraint categories: format: headings, bullet lists, JSON schema, tables
content: must-include points, required variables, sections
style: formal vs casual, technical vs plain English
don’ts: banned libraries, forbidden claims, no personal data format: headings, bullet lists, JSON schema, tables format content: must-include points, required variables, sections content style: formal vs casual, technical vs plain English style don’ts: banned libraries, forbidden claims, no personal data don’ts Constraints make the output predictable. Predictability is the whole point. 3) Example: reduce ambiguity with a single “golden sample” One good example is usually enough. But keep it aligned with the task. A mismatched example is worse than no example. aligned 4) Optimisation guidance: teach the model what “good” looks like This is where you “coach” the model’s prompt-writing behaviour: use direct verbs (“Write…”, “Return…”)
add placeholders and fallbacks
avoid vague phrasing (“try to…”)
specify output structure for readability use direct verbs (“Write…”, “Return…”) add placeholders and fallbacks avoid vague phrasing (“try to…”) specify output structure for readability Three Meta-Prompts You Can Copy Today Below are complete meta-prompts you can paste into any LLM.   I’ve tuned the examples for UK context (GBP, local workplace tone, etc.). UK context Scenario 1: Education Meta-prompt (copy/paste): Meta-prompt (copy/paste): You are a prompt engineer. Generate ONE high-quality prompt that instructs an LLM to create a Year 4 (UK) English reading comprehension exercise.
​
Requirements for the GENERATED prompt:
1) Output includes:
   - A 380–450 word narrative text about "school life" (e.g., class project, playground moment, teacher-student interaction).
   - 5 questions: 3 multiple choice (vocabulary meaning + detail recall), 2 short answer (paragraph summary + main message).
   - Answers + brief explanations (MCQ: why correct option; short answers: key points).
2) Difficulty: Year 4 UK, avoid rare vocabulary (no GCSE-level words).
3) Format: use Markdown headings:
   - # Text
   - # Questions
   - # Answers & Explanations
4) Do NOT lock the story to one specific event (e.g., not always sports day). Keep it flexible.
5) Robustness: if the story doesn’t naturally include a good vocabulary word, the LLM may adjust one MCQ into a detail-recall question.
​
Output ONLY the generated prompt. You are a prompt engineer. Generate ONE high-quality prompt that instructs an LLM to create a Year 4 (UK) English reading comprehension exercise.
​
Requirements for the GENERATED prompt:
1) Output includes:
   - A 380–450 word narrative text about "school life" (e.g., class project, playground moment, teacher-student interaction).
   - 5 questions: 3 multiple choice (vocabulary meaning + detail recall), 2 short answer (paragraph summary + main message).
   - Answers + brief explanations (MCQ: why correct option; short answers: key points).
2) Difficulty: Year 4 UK, avoid rare vocabulary (no GCSE-level words).
3) Format: use Markdown headings:
   - # Text
   - # Questions
   - # Answers & Explanations
4) Do NOT lock the story to one specific event (e.g., not always sports day). Keep it flexible.
5) Robustness: if the story doesn’t naturally include a good vocabulary word, the LLM may adjust one MCQ into a detail-recall question.
​
Output ONLY the generated prompt. Why it works: it forces the model to produce a prompt that’s structured, age-appropriate, and reusable. Why it works: Scenario 2: Workplace Meta-prompt (copy/paste): Meta-prompt (copy/paste): Generate ONE prompt that helps an operations analyst write a monthly department update for a UK-based company.
​
The GENERATED prompt must:
- Produce a report framework (NOT a fully filled report).
- Structure:
  1) Key outcomes (with KPIs)
  2) Issues + root causes
  3) Next month plan (goals + actions)
- Require KPI placeholders using GBP and UK spelling:
  - Revenue (GBP): £____
  - Conversion rate: ____%
  - Active users: ____
  - Customer support tickets: ____
- Tone: professional and concise (avoid slang, avoid “we smashed it”).
- Word count target: 800–1,000 words, but allow placeholders.
- If a section is not applicable, include “No material updates this month” rather than inventing content.
- Output format: Markdown with H2 headings for each section and bullet points inside.
​
Output ONLY the generated prompt. Generate ONE prompt that helps an operations analyst write a monthly department update for a UK-based company.
​
The GENERATED prompt must:
- Produce a report framework (NOT a fully filled report).
- Structure:
  1) Key outcomes (with KPIs)
  2) Issues + root causes
  3) Next month plan (goals + actions)
- Require KPI placeholders using GBP and UK spelling:
  - Revenue (GBP): £____
  - Conversion rate: ____%
  - Active users: ____
  - Customer support tickets: ____
- Tone: professional and concise (avoid slang, avoid “we smashed it”).
- Word count target: 800–1,000 words, but allow placeholders.
- If a section is not applicable, include “No material updates this month” rather than inventing content.
- Output format: Markdown with H2 headings for each section and bullet points inside.
​
Output ONLY the generated prompt. Why it works: it prevents hallucinated numbers, forces a report skeleton, and keeps the style “UK corporate.” Why it works: Scenario 3: Tech Here’s a slightly different twist from the usual “sales A/B” example:   we’ll chart weekly ticket volumes for two support queues. weekly ticket volumes Meta-prompt (copy/paste): Meta-prompt (copy/paste): You are a senior Python developer. Generate ONE prompt that instructs an LLM to write Python 3.10+ code using pandas + matplotlib ONLY.
​
Goal for the GENERATED prompt:
- Read a CSV named "tickets_weekly.csv" with columns:
  - week (YYYY-MM-DD)
  - platform_queue
  - app_queue
- Plot a line chart with week on X-axis and ticket counts on Y-axis.
- Add: title, axis labels, legend, grid, and rotate x-ticks.
- Save as "ticket_trend.png" (dpi=300).
- Include error handling:
  - file not found -> print helpful message and exit
  - missing columns -> print which columns are missing
- Provide clear inline comments.
- Do NOT use seaborn or plotly.
​
Output ONLY the generated prompt. You are a senior Python developer. Generate ONE prompt that instructs an LLM to write Python 3.10+ code using pandas + matplotlib ONLY.
​
Goal for the GENERATED prompt:
- Read a CSV named "tickets_weekly.csv" with columns:
  - week (YYYY-MM-DD)
  - platform_queue
  - app_queue
- Plot a line chart with week on X-axis and ticket counts on Y-axis.
- Add: title, axis labels, legend, grid, and rotate x-ticks.
- Save as "ticket_trend.png" (dpi=300).
- Include error handling:
  - file not found -> print helpful message and exit
  - missing columns -> print which columns are missing
- Provide clear inline comments.
- Do NOT use seaborn or plotly.
​
Output ONLY the generated prompt. Meta-Prompting, But Make It Reusable: Parameterised Templates If you do this more than twice, you’ll want placeholders. Here’s a meta-prompt template you can keep in a notes app: Create ONE prompt for an LLM to perform the task: {TASK}.
​
Context:
- Audience: {AUDIENCE}
- Scenario: {SCENARIO}
​
The prompt MUST include:
- Output format: {FORMAT}
- Must-include points: {MUST_INCLUDE}
- Constraints: {CONSTRAINTS}
- Forbidden items: {FORBIDDEN}
​
Robustness:
- If required data is missing, ask for it using a short checklist.
- If uncertain, make assumptions explicit and label them.
​
Return ONLY the generated prompt. Create ONE prompt for an LLM to perform the task: {TASK}.
​
Context:
- Audience: {AUDIENCE}
- Scenario: {SCENARIO}
​
The prompt MUST include:
- Output format: {FORMAT}
- Must-include points: {MUST_INCLUDE}
- Constraints: {CONSTRAINTS}
- Forbidden items: {FORBIDDEN}
​
Robustness:
- If required data is missing, ask for it using a short checklist.
- If uncertain, make assumptions explicit and label them.
​
Return ONLY the generated prompt. How to use it: replace the braces with your values, paste, and go. How to use it: A Tiny Prompt-Generator Script If you’re building internal tooling, you can generate meta-prompts programmatically. Below is a minimal JavaScript example that assembles a meta-prompt from inputs (note: this doesn’t call an API—it just generates the meta-prompt text): function buildMetaPrompt({
  task,
  audience,
  scenario,
  format,
  mustInclude = [],
  constraints = [],
  forbidden = [],
}) {
  return `You are a prompt engineer. Generate ONE high-quality prompt for the task below.
​
Task: ${task}
Audience: ${audience}
Scenario: ${scenario}
​
The GENERATED prompt must:
- Output format: ${format}
- Must-include: ${mustInclude.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
- Constraints: ${constraints.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
- Forbidden: ${forbidden.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
​
Robustness rules:
- If required info is missing, ask 3–6 targeted questions.
- Don’t invent numbers, names, or sources.
- Keep instructions direct (“Write…”, “Return…”).
​
Output ONLY the generated prompt.`;
}
​
// Example (UK-flavoured)
console.log(
  buildMetaPrompt({
    task: "Create a product listing description for a winter waterproof jacket",
    audience: "UK shoppers browsing on mobile",
    scenario: "Outdoor commuting in rain and wind",
    format: "Markdown with short sections and bullet points",
    mustInclude: ["waterproof rating", "breathability", "size range", "care instructions"],
    constraints: ["200–260 words", "include a single call-to-action", "avoid exaggerated health claims"],
    forbidden: ["US spellings", "prices in USD"],
  })
); function buildMetaPrompt({
  task,
  audience,
  scenario,
  format,
  mustInclude = [],
  constraints = [],
  forbidden = [],
}) {
  return `You are a prompt engineer. Generate ONE high-quality prompt for the task below.
​
Task: ${task}
Audience: ${audience}
Scenario: ${scenario}
​
The GENERATED prompt must:
- Output format: ${format}
- Must-include: ${mustInclude.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
- Constraints: ${constraints.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
- Forbidden: ${forbidden.map(x => `\n  - ${x}`).join("") || "\n  - (none)"}
​
Robustness rules:
- If required info is missing, ask 3–6 targeted questions.
- Don’t invent numbers, names, or sources.
- Keep instructions direct (“Write…”, “Return…”).
​
Output ONLY the generated prompt.`;
}
​
// Example (UK-flavoured)
console.log(
  buildMetaPrompt({
    task: "Create a product listing description for a winter waterproof jacket",
    audience: "UK shoppers browsing on mobile",
    scenario: "Outdoor commuting in rain and wind",
    format: "Markdown with short sections and bullet points",
    mustInclude: ["waterproof rating", "breathability", "size range", "care instructions"],
    constraints: ["200–260 words", "include a single call-to-action", "avoid exaggerated health claims"],
    forbidden: ["US spellings", "prices in USD"],
  })
); Five Common Meta-Prompt Mistakes 1) Vague task definition → prompt drifts Fix: use task + scenario + output shape in one sentence. Fix: task + scenario + output shape 2) Weak formatting rules → messy outputs Fix: lock the structure (headings, bullet lists, schema) and require it. Fix: 3) Wrong example → model learns the wrong thing Fix: only include examples that match the task exactly. Fix: exactly 4) No optimisation guidance → “valid” but low-quality prompts Fix: add explicit rules like “use direct verbs,” “include placeholders,” “don’t invent data.” Fix: 5) Ignoring audience cognition → prompts feel unusable Fix: specify the audience’s knowledge level and vocabulary boundaries (Year 4 vs university vs exec). Fix: A Practical Workflow That Actually Scales If you want meta-prompting to be more than a novelty: Start with a baseline meta-prompt (4 modules).
Generate the prompt.
Test the prompt on the real task.
Patch the meta-prompt based on failures.
Save your best meta-prompts as templates. Start with a baseline meta-prompt (4 modules). Start with a baseline meta-prompt Generate the prompt. Generate the prompt Test the prompt on the real task. Test the prompt Patch the meta-prompt based on failures. Patch the meta-prompt Save your best meta-prompts as templates. Meta-prompting becomes genuinely powerful when it turns into a library:   a shelf of “prompt generators” you can reuse across projects. Final Thought The endgame isn’t “perfect prompts.”   It’s repeatable outputs with less effort and fewer surprises. repeatable outputs Meta-prompts are one of the cleanest ways to get there.

Harmony

Keep

Meta-Prompting: From “Using Prompts” to “Generating Prompts”

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

A Developer's Guide to Merging AI with the Spring Ecosystem

The Noonification: How Often Do NFTs Pass The Howey Test? (1/13/2023)

Darwin's Hybrid Intelligence to Align AI & Human Goals for Startups & VCs

The Noonification: White Man (11/26/2022)

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

A Developer's Guide to Merging AI with the Spring Ecosystem

The Noonification: How Often Do NFTs Pass The Howey Test? (1/13/2023)

Darwin's Hybrid Intelligence to Align AI & Human Goals for Startups & VCs

The Noonification: White Man (11/26/2022)

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps