The Prompt Engineering Framework
vir: Ali H. Salem
uporaba xml sintakse izboljša končni rezultat !
Role
Opredelite strokovno osebnost
Določite strokovno znanje AI, poznavanje ciljne skupine in komunikacijski pristop:
<role>
You are a [specific role/expert] with expertise in [domain].
Your audience: [description + knowledge level]
Communication style: [tone + specific requirements]
</role>
Primer
You are a senior business strategy consultant with expertise in competitive analysis. Your audience: C-suite executives with limited time for deep technical details. Communication style: Concise, data-driven, and actionable with a confident tone.
Task
Določite cilj
Jasno opredelite, kaj je treba doseči, z izrecnimi zahtevami:
<task>
[Action verb] + [specific objective]
Key requirements:
– [Requirement 1]
– [Requirement 2]
– [Requirement 3]
</task>
Primer
Analyze the competitive positioning of our SaaS product against three main competitors.
Key requirements:
Identify unique differentiators and vulnerabilities
Quantify market share implications where possible
Provide actionable recommendations for Q1 strategy
Context
Zagotovite ustrezne osnovne informacije
Zagotovite informacije, potrebne za razumevanje in izvedbo naloge:
<context>
[Paste relevant information, documents, data, or background details here]
</context>
Primer
Our product: Project management tool for remote teams, $49/month, 50K users
Competitor A: Asana – 100K users, extensive integrations
Competitor B: Monday.com – 80K users, visual interface focus
Competitor C: ClickUp – 60K users, feature-rich, lower price point ($35/month)
Recent customer feedback highlights our superior mobile experience but mentions lack of time-tracking features.
Example
Navedite primere izhodnih podatkov
Pojasnite, kakšni so dobri izhodni podatki:
<examples>
Example 1:
[Show what good output looks like for scenario 1]
Example 2..n:
[Show what good output looks like for scenario 2]
</examples>
Primer
Example 1:
“Our $49/month price point positions us as a premium option compared to ClickUp’s $35/month. This 40% price premium must be justified through: (1) superior mobile UX, (2) enterprise-grade security, (3) white-glove onboarding. Risk: Price-sensitive SMBs may churn to ClickUp unless we demonstrate clear ROI advantage.”
Output
Določite pričakovane rezultate
Določite format, dolžino in strukturo želenega izhoda:
<output>
Format: [specific format – e.g., “markdown table with 3 columns”]
Length: [constraint – e.g., “300-400 words”]
Structure: [if applicable – e.g., “Introduction → Analysis → Recommendations”]
</output>
Primer
Format: Executive summary (1 paragraph) + comparison table (4 columns: Feature/Us/Competitors/Impact) + 3 strategic recommendations
Length: 400-500 words total
Structure: Summary → Comparison → Recommendations
Constraints
Določite omejitve in smernice
Določite, kaj naj bo vključeno in kaj ne:
<constraints>
– [Specific do’s and don’ts]
– [Style requirements]
– [Any limitations or boundaries]
</constraints>
Primer
No jargon or technical implementation details
Focus only on strategic business implications
Avoid speculating on competitors’ future roadmaps
Do not recommend features that would take >6 months to build
Instructions
Vodite proces
Zagotovite meta-navodila o tem, kako pristopiti k nalogi:
<instructions>
For complex tasks: Think through your approach step-by-step, then provide the final answer in the requested format.
If information is missing or uncertain, state this explicitly rather than guessing.
</instructions>
Primer
For complex tasks: Think through your approach step-by-step, then provide the final answer in the requested format.
If information is missing or uncertain, state this explicitly rather than
