How to Talk to AI

You are my assistant.

Role: [ROLE]
Goal: [GOAL]

Context:
[PASTE CONTEXT]

Output:
- Format: [FORMAT]
- Length: [LENGTH]
- Tone: [TONE]

Rules:
- If anything important is missing, ask me up to 7 questions before you answer.
- List the assumptions you are making.
- If you are unsure, say so. Do not make things up.
- Use plain English.
- When useful, give me 2 to 3 options and recommend one.
- If this depends on current facts, use current sources, link them, and include the date checked.
- If this would be better with a file, screenshot, or document, ask me for it.

Start by asking your questions. Then wait.

Before you answer, do this:

1. List any contradictions in my instructions.
2. List what is missing.
3. Rewrite my prompt to be tighter and clearer.
4. Ask me the questions you still need.

Then wait.

Respond from the perspective of a [primary role] with expertise in:
- [Specific qualification]
- [Specific experience]
- [Specific specialty]

What this role typically cares about:
- [Priority 1]
- [Priority 2]

Task: [specific task or question]

Instructions:
- Use the perspective, tradeoffs, and priorities of this role.
- Do not invent credentials, facts, or hidden knowledge.
- If experts in this role would disagree, say where they would disagree.
- If anything important is missing, ask me questions first.

Output:
- Terminology level: [professional | accessible]
- Tone: [tone]
- Format: [format]

Respond from the perspective of a clear, practical communication coach with expertise in writing firm but respectful emails.

What this role typically cares about:
- clarity
- respect
- getting to the point

Task: Write an email to my landlord about a leaking ceiling that needs repair.

Instructions:
- Use short sentences and plain English.
- Do not use hype.
- If anything important is missing, ask me questions first.

Output:
- Terminology level: accessible
- Tone: confident and respectful
- Format: subject line + email body + 3 alternate subject lines

Give me multiple expert perspectives on [problem].

Simulate a panel discussion with the following roles:
- Expert 1: [Specific role] with expertise in [domain]
- Expert 2: [Specific role] with expertise in [domain]
- Expert 3: [Specific role] with expertise in [domain]

Instructions:
- Base each perspective on common real world priorities for that role.
- Do not invent facts.
- If the answer depends on current facts, use sources and link them.

For each expert:
- State their perspective and priorities
- Analyze the problem from that viewpoint
- Propose a solution

Then provide:
- Where they agree
- Where they disagree
- What is uncertain
- A recommended path forward

Format as:
Expert 1:
[response]

You are a tireless researcher and fact checker.

Fact check the text below.
Analyze every factual claim, statistic, date, name, technical specification, and verifiable statement.

Use current sources when needed.

For each important claim, return:
- Claim
- Status: Verified / Unverified / Contradicted
- Source link
- Date checked
- Short note

Then include:
- Claims that still need verification
- Vague or misleading statements
- Internal contradictions
- What is confirmed vs inferred
- Overall risk level: low / medium / high

If you cannot verify something, label it Unverified.
Do not guess.

Text to fact check:
[PASTE YOUR TEXT HERE]

You are an expert in [domain] and an experienced teacher.

Create a step by step guide to accomplish [specific goal].

Instructions:
- If laws, policies, software, pricing, or product details may have changed, verify current information first.
- Ask questions if anything important is missing.
- Use plain language unless I ask for technical detail.

Structure your response as:

Requirements:
[what is needed]

Preparation:
[setup steps]

Instructions:
[step by step actions]

Troubleshooting:
[common issues and fixes]

Variations:
[alternate approaches]

Goal:
[specific objective]

You are an expert at government processes and navigating bureaucracy.

I need help with: [what you are trying to do]

Use current official sources and link them.
Prefer official agency websites.
Tell me which parts vary by jurisdiction.
If anything important is missing, ask me questions first.

My details:
- Who I am: [details]
- Goal: [goal]
- Agency or system: [if known]
- Jurisdiction: [country / state / city / institution]
- Current status: [what I have done]
- Constraints: [deadlines, missing documents, budget, legal issues]
- Dates and deadlines: [known dates]
- Special factors: [anything unusual]

What I want:
1. A simple overview of how the system works
2. A numbered action plan for my situation
3. Required forms, documents, IDs, and evidence
4. Expected fees
5. Decision points and bottlenecks
6. Common mistakes and how to avoid them
7. A realistic timeline
8. Questions the agency is likely to ask me
9. A script for calling or emailing the agency
10. A backup plan if the main path stalls

You are an experienced teacher, coach, and interviewer in [field].

Help me prepare for [role / exam / conversation / topic].

Do the following:
1. Ask me for the relevant materials first.
2. Review the materials and identify focus areas.
3. Create a structured practice session with questions of varying difficulty.
4. After each answer, score me briefly on:
   - clarity
   - completeness
   - credibility
5. Tell me whether I should expand, clarify, or move on.
6. End with a summary of strengths and the top improvements I should make.

Start by asking for my materials.

You are excellent at following directions.

I am giving you a strict output template with [PLACEHOLDERS].

Rules:
- Output must match the template exactly.
- Do not add extra sections.
- Do not invent facts.
- If a field is missing, either ask me for it or mark it as [MISSING].

Template:
[PASTE TEMPLATE HERE]

Apply this template to:
[YOUR REQUEST]

Research this topic using current sources:
[TOPIC]

Instructions:
- Use current sources.
- Link each major claim.
- Include the date checked.
- Separate what is confirmed from what is inferred.
- If sources conflict, say so.
- If you cannot verify something, label it Unverified.

Output:
1. Short answer
2. Key findings with source links
3. What is confirmed
4. What is inferred
5. Open questions or uncertainty

I am uploading a document or PDF.

First:
1. Summarize what the document is.
2. List any ambiguities, missing pages, or unreadable parts.

Then do this task:
[TASK]

Rules:
- Answer from the document first.
- If you use outside knowledge, label it clearly.
- Quote or cite the part of the document you are relying on when possible.
- If the file is not enough to answer fully, tell me what is missing.

I am uploading an image or screenshot.

First:
1. Describe exactly what you see.
2. List any ambiguities or things you cannot read clearly.

Then do this task:
[TASK]

Rules:
- Separate observation from interpretation.
- If text is visible, extract the text first.
- If you are inferring something, label it as inference.
- If the image alone is not enough, tell me what else you need.

Compare these sources on:
[TOPIC]

Sources:
- [SOURCE 1]
- [SOURCE 2]
- [SOURCE 3]

Output:
1. What all sources agree on
2. Where they conflict
3. Which source appears strongest and why
4. What is still uncertain
5. Your best current conclusion

Rules:
- Link the sources.
- Prefer primary or official sources when possible.
- Separate evidence from interpretation.

Return the answer in [JSON | table] format.

Schema or columns:
- [FIELD 1]
- [FIELD 2]
- [FIELD 3]

Rules:
- Use null for unknown values.
- Do not invent missing values.
- If the schema is unclear, ask me questions first.
- Keep all field names exact.

Task:
[YOUR REQUEST]

Return the answer in JSON format.

Schema:
- company_name
- product_name
- category
- target_customer
- pricing_notes
- source_url
- confidence

Rules:
- Use null for unknown values.
- Do not invent missing values.
- Keep all field names exact.

Task:
Research the top embedded DevOps tools vendors and return the results in this schema.

Goal:
[What I want completed]

Allowed actions:
- [Browse / inspect files / write code / create a document / use a tool / other]

Boundaries:
- Do not publish, send, delete, purchase, or make external changes without asking me first.
- Do not expose private information.
- Stay within these files, apps, or systems: [BOUNDARIES]

Inputs:
[Paste notes, links, files, screenshots, examples, or constraints]

Work style:
- Start by checking the relevant context.
- Make a short plan.
- Do the work.
- Verify the result.
- Tell me what changed, what you checked, and what still needs human review.