AiImported version
Prompt Structure Anthropic
/Users/fabien/Desktop/AI/PROMPTS/-ai/-prompting/optimization/-prompt-structure-anthropic.odt
Folder-ai/-prompting/optimization
Versions0
Imported2026-06-28
StatusActive
## The Anatomy of a Prompt — Structure & Examples
A 10-part structure for building strong prompts. Each part below shows how to use it (illustrated with a wind turbine AI inspection use case).
| # | Step | How to Use It (e.g., for a Wind Turbine AI) |
|---|---|---|
| 1 | **Task Context** | "You are an expert Structural Engineer and Drone Inspection Specialist." |
| 2 | **Tone Context** | "Professional, analytical, and safety-oriented. Use industry-standard terminology." |
| 3 | **Background Data** | Attach the high-res aerial images or previous inspection logs. |
| 4 | **Detailed Rules** | "If a crack exceeds 5cm, flag it as 'Critical'. Never speculate on internal damage without visual evidence." |
| 5 | **Examples** | Provide a `<example>` of a perfect report for a minor gelcoat erosion. |
| 6 | **Conv. History** | Reference the previous year's inspection to see if defects have progressed. |
| 7 | **Immediate Task** | "Analyze the attached image and generate a defect summary table." |
| 8 | **Deep Thinking** | Add "Think step-by-step about the potential cause of this blade delamination." |
| 9 | **Output Format** | "Output in a Markdown table with columns: ID, Type, Severity, and Recommendation." |
| 10 | **Prefilled Resp.** | Start the response with: "### Inspection Report for Turbine [ID]:" |
## The 10-Part Prompting Structure
1. **Task Context** – Define the role and overall task.
2. **Tone Context** – Set the communication style (professional, casual, etc.).
3. **Background Data** – Attach relevant files or supporting context.
4. **Detailed Task Description & Rules** – Expand on constraints and expectations.
5. **Examples** – Provide desired output samples using `<example>` tags.
6. **Conversation History** – Reference prior chats for continuity.
7. **Immediate Task Description** – State the specific action required now using clear verbs.
8. **Deep Thinking** – Trigger reasoning with phrases like "Think Deeply".
9. **Output Formatting** – Specify bullets, tables, prose, or structured layouts.
10. **Prefilled Response** – Optionally seed the beginning of the AI reply.
## Example Prompt (User Input)
You will be acting as an AI career coach named Joe created by the company AdAstra Careers. Your goal is to give career advice to users. You will be replying to users who are on the AdAstra site and who will be confused if you don't respond in the character of Joe.
You should maintain a friendly customer service tone.
Here is the career guidance document you should reference when answering the user:
```
<guide>{{DOCUMENT}}</guide>
```
Here are some important rules for the interaction:
- Always stay in character, as Joe, an AI from AdAstra careers
- If you are unsure how to respond, say "Sorry, I didn't understand that. Could you repeat the question?"
- If someone asks something irrelevant, say, "Sorry, I am Joe and I give career advice. Do you have a career question today I can help you with?"
Here is an example of how to respond in a standard interaction:
```
<example>
User: Hi, how were you created and what do you do?
Joe: Hello! My name is Joe, and I was created by AdAstra Careers to give career advice. What can I help you with today?
</example>
```
Here is the conversation history (between the user and you) prior to the question. It could be empty if there is no history:
```
<history>{{HISTORY}}</history>
```
Here is the user's question:
```
<question>{{QUESTION}}</question>
```
How do you respond to the user's question?
Think about your answer first before you respond.
Put your response in `<response></response>` tags.
**Assistant (prefill):**
```
<response>
```
## The Anatomy of a Prompt (Template)
**[Task]** I want to [TASK] so that [SUCCESS CRITERIA]. First, read these files completely before responding:
- [filename.md] — [what it contains]
- [filename.md] — [what it contains]
- [filename.md] — [what it contains]
**[Context Files]** Here is a reference to what I want to achieve:
- [Upload reference file as markdown, or paste it here]
**[Reference]** Here's what makes this reference work:
- [Paste your reverse-engineered blueprint — the patterns, tone, structure, and rules you extracted from the reference. Format each one as a rule starting with "Always" or "Never."]
**[Success Brief]** Here's what I need for my version:
SUCCESS BRIEF
- Type of output + length: [Contract, memo, report, proposal, landing page, post?]
- Recipient's reaction: [What should they think/feel/do after reading?]
- Does NOT sound like: [What to avoid — generic AI, too casual, formal, jargon-heavy?]
- Success means: [They sign? They approve? They reply? They take action?]
**[Rules]** My context file contains my standards, constraints, landmines, and audience. Read it fully before starting. If you're about to break one of my rules, stop and tell me.
**[Conversation]** DO NOT start executing yet. Instead, ask me clarifying questions (use 'AskUserQuestion' tool) so we can refine the approach together step by step.
**[Plan]** Before you write anything, list the 3 rules from my context file that matter most for this task.
**[Alignment]** Then give me your execution plan (5 steps maximum). Only begin work once we've aligned.