Structure
Role
Role
Meaning
A description of the perspective or job the model should adopt.
When to use it
Use it to establish relevant expertise, audience, and tone.
Practical example
Act as a Korean technical editor for beginner developers.Generative AI Engineering
Learn how roles, instructions, context, examples, output schemas, multi-step workflows, and advanced reasoning patterns shape reliable AI responses.
18 matching terms
Structure
Role
A description of the perspective or job the model should adopt.
Use it to establish relevant expertise, audience, and tone.
Act as a Korean technical editor for beginner developers.Structure
Instruction
A direct statement of the task the model should perform.
Use an explicit verb and a clear deliverable to reduce ambiguity.
Summarize the report into five decision-ready bullet points.Structure
Context
Background information the model needs to interpret the task correctly.
Provide audience, goals, constraints, source material, and definitions that affect the answer.
Context: the readers are first-time users and the feature launches next week.Structure
Constraint
A boundary on content, length, style, tools, or allowed actions.
Use it to make acceptance criteria visible and testable.
Use only the supplied policy, stay under 150 words, and do not infer missing dates.Structure
Delimiter
A marker that separates instructions, examples, and source data.
Use XML-like tags, headings, or fenced blocks when the prompt contains multiple sections.
Summarize only the text inside <source>...</source>.Examples
Zero-shot prompting
Requesting a task without providing a worked example.
Start here for common tasks that the model already understands well.
Classify each review as positive, neutral, or negative.Examples
Few-shot prompting
Providing a small set of input-output examples before the actual task.
Use it to teach a specific label policy, tone, edge case, or output pattern.
Input: delivery was fast. Output: logistics-positive. Now classify: the box arrived damaged.Reuse
Prompt template
A reusable prompt with placeholders filled by variables at runtime.
Use it for repeated workflows that require consistent instructions.
Summarize {{document}} for {{audience}} using {{format}}.Output
Structured output
A response constrained to a predictable machine-readable shape.
Use it when another program will parse or validate the result.
Return an object with title, summary, risk_level, and source_ids.Output
JSON Schema
A formal description of allowed JSON fields, types, and required values.
Use supported schema constraints to reduce parsing failures in automated workflows.
Require status as an enum and due_date as a nullable ISO date.Workflow
Task decomposition
Breaking a complex request into smaller, verifiable subtasks.
Use it when research, transformation, checking, and final synthesis require different steps.
First extract requirements, then identify conflicts, then draft and verify the answer.Workflow
Prompt chaining
Passing the output of one model step into a later model step.
Use it when intermediate results should be inspected, transformed, or approved.
Errors can propagate across steps, so validate important intermediate outputs.
Extract claims -> retrieve evidence -> verify each claim -> write the final brief.Advanced reasoning patterns
Step-back prompting
Starting with a broader principle, definition, or decision framework before answering a specific question.
Use it when the specific case is easy to misread without first identifying the governing concepts or constraints.
The broader step can still be wrong or irrelevant, so verify it against authoritative sources.
First identify the policy principles that govern refund eligibility. Then apply them to this case and cite the supporting clauses.Advanced reasoning patterns
Least-to-most prompting
Solving simpler dependent subproblems first and using their verified results to address the harder overall task.
Use it when later conclusions depend on several prerequisite calculations, facts, or decisions.
An early error can propagate through later steps; validate prerequisite outputs before reuse.
1. Extract the contract dates. 2. Calculate each notice period. 3. Compare the periods with the termination clause. 4. Report the conclusion with evidence.Advanced reasoning patterns
Self-consistency
Generating multiple independently sampled candidate solutions and selecting an answer supported by agreement or a separate verification rule.
Use it selectively for difficult tasks where multiple valid solution paths can be compared and the additional cost is justified.
Agreement does not prove correctness, correlated errors can agree, and multiple samples increase latency and cost.
Generate five independent candidate totals, compare the final values, and accept one only if the source rows and deterministic calculation verify it.Advanced reasoning patterns
Critique-and-revise
Producing a draft, evaluating it against explicit criteria and evidence, and revising the identified weaknesses.
Use it when the output has a reviewable rubric such as completeness, source support, format, tone, or policy compliance.
A model can overlook its own mistakes; high-impact results still need independent checks or human review.
Draft the answer. Critique it against required facts, citations, prohibited claims, and length. Revise only the failed items, then return the final answer.Advanced reasoning patterns
Plan-and-execute
Separating task planning from execution so dependencies, tools, checkpoints, and completion criteria are defined before work proceeds.
Use it for multi-step work where order, permissions, resource limits, or intermediate validation matter.
Treat the plan as revisable; do not continue blindly when new evidence invalidates it.
Return a concise action plan with dependencies and approval points. Execute each approved step, record evidence, and replan when an assumption fails.Advanced reasoning patterns
Verifier pattern
Using a distinct verification step to check a candidate answer against rules, evidence, schemas, or deterministic tools before acceptance.
Use it when important claims, calculations, citations, structured outputs, or tool arguments can be checked independently.
A verifier that shares the same missing evidence or flawed assumptions may repeat the generator's error.
Generator: produce the invoice summary with source row IDs. Verifier: recompute totals, validate the schema, and reject unsupported claims.Select a pattern only when the task structure and evaluation evidence justify the additional steps, tokens, latency, and complexity.
| Need | Pattern to consider |
|---|---|
| Identify governing principles before applying them to a case | Step-back prompting |
| Solve prerequisite subproblems in dependency order | Least-to-most prompting |
| Compare several candidate solutions when additional sampling is justified | Self-consistency plus independent verification |
| Improve a draft against explicit review criteria | Critique-and-revise |
| Coordinate dependencies, tools, and approval checkpoints | Plan-and-execute |
| Reject unsupported claims, invalid schemas, or wrong calculations | Verifier pattern |
No. Prefer a concise answer, checkable intermediate results, cited evidence, assumptions, calculations, and validation outcomes. Some reasoning models perform internal thinking automatically, and a long visible rationale is not proof that the answer is correct.
No. Their effect varies by model, task, prompt, sampling, and evaluation method. They can also add latency, token cost, correlated errors, and failure propagation. Compare them with a simple baseline on representative cases.
Critique-and-revise improves a draft through review and editing. A verifier acts as an acceptance gate that checks a candidate against evidence, rules, schemas, or deterministic tools and may reject it without rewriting it.
Official guidance on structured prompting, reasoning, planning, validation, agentic workflows, and model-specific thinking behavior.
Primary research introducing self-consistency as sampling diverse reasoning paths and selecting the most consistent answer.
Extend a prompt into a controlled context containing evidence, history, state, and reusable material.
Design requests that combine text with images, documents, audio, or video.
Compare prompt variants with repeatable cases, metrics, and regression checks.
Version, approve, deploy, observe, roll back, and retire production prompts.
Apply query rewriting, evidence-only answers, abstention, citations, synthesis, and source-conflict handling.