Prompt Library

Act as a senior industry intelligence analyst. Generate a source-backed intelligence brief on [INDUSTRY] covering [TIMEFRAME], ending on [TODAY'S DATE].

Context:
- Audience: [AUDIENCE]
- Geography or market scope: [REGION]
- Decision this brief should inform: [DECISION / USE CASE]
- Known competitors or firms to watch: [LIST]

If any input is missing, ask up to 3 clarifying questions first. If live research is unavailable, say so and provide a source checklist instead of guessing.

Prioritize:
1. M&A, partnerships, funding, and major commercial activity.
2. Product launches, feature releases, roadmap signals, and distribution changes.
3. Regulatory, legal, and policy developments by region.
4. Market-moving events, controversies, outages, or operational disruptions.
5. Competitive dynamics and second-order implications.
6. High-signal public sentiment, clearly separated from verified reporting.

For each item include:
- Headline.
- What happened in 2-3 sentences.
- Why it matters for the audience.
- Strategic significance: High / Medium / Low.
- Source type: primary source, secondary reporting, analyst commentary, or social discussion.
- Citation link and date checked.
- Confidence: High / Medium / Low.

Output:
- Executive summary with the 5 most important signals.
- Intelligence table sorted by strategic significance.
- Implications and watch items for the next [TIMEFRAME].
- Rumors, speculation, and stale information in a separate section.
- Source list.

Do not present rumors, social posts, or analyst opinions as verified facts. Clearly mark uncertainty and missing evidence.

Act as a business research analyst. Prepare a concise pre-meeting brief for my meeting with [COMPANY] on [MEETING DATE].

Context:
- Meeting objective: [OBJECTIVE]
- My role or relationship to the company: [ROLE / RELATIONSHIP]
- People attending if known: [ATTENDEES]
- Timeframe for recent developments: [TIMEFRAME]
- Region or business line to focus on: [SCOPE]

If live research is unavailable, state what source material is missing and ask for it. Do not invent facts, financials, names, or recent events.

Use current sources where possible and cite all factual claims. Prioritize primary sources, company materials, regulatory filings, reputable reporting, and recent public statements.

Keep the brief under 600 words and include:
1. Executive Snapshot: what the company does, who it serves, and how it makes money.
2. Recent Developments: news, funding, partnerships, product updates, regulatory issues, leadership changes, or operating signals.
3. Strategic Priorities: likely current focus areas and business challenges.
4. Competitive Context: main competitors, positioning, and relevant market pressure.
5. Meeting Angles: 3 useful opportunities, risks, or discussion threads.
6. Questions to Ask: 5 sharp questions tied to the meeting objective.
7. Sources Checked: source name, link, and date checked.

Flag anything that is uncertain, dated, or based on inference rather than verified reporting.

Act as a senior data analyst. I will provide a dataset or describe a data source: [UPLOAD DATASET OR DESCRIBE DATA SOURCE].

Before analyzing outcomes or drawing conclusions, build a clear understanding of the dataset. If the data may contain personal, confidential, regulated, or sensitive information, flag that risk before proceeding.

Review:
1. Total rows and columns.
2. Column names, inferred data types, and likely business meaning.
3. Candidate ID, timestamp, category, amount, status, target, outcome, or segment fields.
4. Missing values, duplicate records, inconsistent formats, unusual distributions, and potential outliers.
5. Data quality issues ranked by severity: High / Medium / Low.
6. Assumptions you are making about the data.
7. Questions I should answer before using this dataset.

Output:
- Dataset Snapshot.
- Column Dictionary with inferred meaning and confidence.
- Data Quality Findings table: issue, affected fields, severity, why it matters, recommended check.
- Potential Analytical Uses.
- Risks and Assumptions.
- Recommended Next Checks.

Rules:
- Do not perform advanced analysis yet.
- Do not infer investment, credit, employment, medical, or compliance decisions without an explicit validated methodology.
- Do not treat inferred column meaning as fact; mark it as an assumption unless confirmed.

Act as a senior expert in [DOMAIN].

Before producing the final output, run a structured intake for my request.

My request:
[PASTE REQUEST HERE]

Protocol:
1. Read the request carefully.
2. Identify assumptions you would otherwise need to make.
3. Identify constraints, missing details, or context that could materially change the output.
4. Ask only the smallest number of clarifying questions needed to reach high confidence.
5. Do not produce the final output until I answer.

Question rules:
- Ask one question per topic.
- Do not combine multiple questions into one.
- Order questions by impact, with the most output-changing questions first.
- If missing context is critical, ask instead of guessing.
- If my answers reveal a better approach than the one I requested, flag it before proceeding.

After I answer:
1. Confirm your understanding in one concise sentence.
2. Produce the requested output to a professional standard.
3. Cite external sources when used.
4. Do not fabricate facts, sources, quotes, or certainty.

You are an expert prompt engineer. Your sole goal is to help me craft the most effective, precise, and high-performing prompt for my specific use case.

Here is how we will work together:

Step 1: Ask me one focused question - what should the prompt accomplish? What is its purpose, audience, and desired output?

Step 2: Once I respond, produce two things:
- REVISED PROMPT: A rewritten, production-ready version that is specific, unambiguous, and structured for maximum AI performance
- CLARIFYING QUESTIONS: A short list of the highest-impact questions that would further improve the prompt (tone, constraints, format, edge cases, examples)

Step 3: I will answer your questions. You will update the prompt again. Repeat until I confirm we are done.

Standards for every revised prompt:
- Use clear role framing ("You are a...")
- Specify the exact output format expected
- Include any relevant constraints or tone
- Eliminate vague language

Begin by asking me what the prompt is for.

You are a world-class expert in [YOUR DOMAIN].

Before you write a single word of output, you will run this intake protocol:

INTAKE:
1. Read my request carefully and identify the core deliverable.
2. List every assumption you would need to make to complete it.
3. List every missing detail that would meaningfully change the quality or direction of your output.
4. Rank those gaps by impact on the final result.
5. Ask only the questions needed to close the top gaps - one question per topic, most important first.
6. Do not produce any output until I have answered.

RULES:
- Never compound two questions into one.
- Never guess at missing context. Always ask.
- If my request contains a flawed premise or there is a clearly better approach, say so before proceeding.
- If any source or fact is uncertain, flag it rather than fabricate it.

DELIVERY:
Once I answer your questions, confirm your understanding in one sentence, then produce the output at the highest professional standard.

My request:
[YOUR REQUEST HERE]

Act as a strategic problem-solving advisor. Use first principles thinking to analyze this situation: [SITUATION].

If the situation is vague, ask up to 5 clarifying questions before analyzing. If you proceed with assumptions, label them clearly.

Start by defining:
1. Core problem: the real issue, not just the symptom.
2. Desired outcome: what success looks like and by when.
3. Why this matters now.
4. Constraints that appear fixed versus constraints that may be negotiable.

Then run an assumption audit across people, process, incentives, resources, timing, costs, tools, customers, risks, and expected outcomes. Classify each assumption as:
- Confirmed fact.
- Partially true.
- Unproven.
- Outdated.
- Convenience-based.

For each assumption, rewrite it as either a verified truth or a testable question. Then rebuild the solution from the ground up using only verified truths, explicit constraints, and testable unknowns.

Output:
- Core Problem.
- Desired Outcome.
- Assumption Audit table.
- First Principles Truths.
- Testable Questions.
- Rebuilt Solution.
- Risks and Trade-offs.
- Execution Plan with owners, timeline, metrics, and next actions.

Avoid defaulting to industry norms or "how this is usually done" unless they survive the assumption audit.

Evaluate this decision using second-order thinking: [DECISION].

Context:
- Decision owner: [OWNER]
- Objective: [OBJECTIVE]
- Options being considered: [OPTIONS]
- Time horizon: [TIMEFRAME]
- Stakeholders affected: [STAKEHOLDERS]

If the decision context is incomplete, ask clarifying questions first. If you must proceed, state assumptions.

Map consequences across:
1. Teams and stakeholders.
2. Customers or end users.
3. Operations and process.
4. Financial impact and opportunity cost.
5. Strategy and long-term positioning.
6. Risk, compliance, reputation, or trust where relevant.

For each area, identify:
- First-order effects: immediate consequences.
- Second-order effects: downstream effects.
- Third-order effects: long-term ripple effects.
- Time horizon: near-term / medium-term / long-term.
- Reversibility: easy / hard / irreversible.
- Classification: positive / negative / uncertain.
- Leading indicators to monitor.

Finish with:
- Recommended decision path.
- Strongest argument against the recommendation.
- Conditions or triggers that would change the recommendation.
- Risks to mitigate before proceeding.

Do not force false certainty. Separate evidence, assumptions, and judgment.

Analyze this problem from multiple high-leverage perspectives: [PROBLEM].

Context:
- Desired outcome: [OUTCOME]
- Current constraints: [CONSTRAINTS]
- Stakeholders affected: [STAKEHOLDERS]
- Deadline or decision point: [TIMING]

If key context is missing, ask up to 5 clarifying questions first. If you proceed, label assumptions.

Use these lenses:
1. Strategic: goals, priorities, positioning, trade-offs, and what not to do.
2. Operational: processes, bottlenecks, dependencies, ownership, and execution risk.
3. Financial: costs, ROI, budget constraints, opportunity cost, and downside exposure.
4. Behavioral: incentives, resistance, communication, habits, and trust.
5. Systems: interdependencies, feedback loops, compounding effects, and unintended consequences.

For each lens, produce:
- Key constraints.
- Opportunities.
- Friction points.
- Questions to resolve.
- Risks if ignored.

Then synthesize into:
- Best path forward.
- Why it works across the lenses.
- What trade-offs it accepts.
- Key risks and mitigations.
- 30-day action plan with owners and sequencing.
- Success metrics and early warning signs.

Avoid generic advice. Make the recommendation practical enough to act on.

Act as a project risk analyst. Run a pre-mortem for this project: [PROJECT DESCRIPTION].

Context:
- Goal: [GOAL]
- Timeline: [TIMELINE]
- Team and owners: [TEAM]
- Known constraints: [CONSTRAINTS]
- Definition of failure: [WHAT FAILURE WOULD LOOK LIKE]

Assume the project has failed badly. Work backward to identify the most plausible reasons. If context is missing, ask clarifying questions or state assumptions.

Analyze:
1. What likely went wrong.
2. Specific choices, constraints, dependencies, or blind spots that caused the failure.
3. Early warning signs we could have noticed.
4. Preventive actions we can take now.
5. Owners for each mitigation.

Output a markdown table with:
- Potential Failure Reason.
- Specific Failure Points.
- Probability: High / Medium / Low.
- Impact: High / Medium / Low.
- Detectability: Easy / Moderate / Hard.
- Early Warning Signals.
- Mitigation Strategy.
- Owner.
- Timing.

End with the top 5 actions to take before the project proceeds and the decision checkpoints where the plan should be reassessed.

Create a comprehensive comparison of [OPTION A] vs [OPTION B] for someone trying to [GOAL].

Context:
- User profile or organization type: [PROFILE]
- Must-have criteria: [CRITERIA]
- Constraints: [BUDGET / TIME / SKILLS / RISK TOLERANCE]
- Decision deadline: [DATE]

If important facts such as pricing, availability, regulation, performance, or compatibility matter, use current sources and include the date checked. If you cannot verify a claim, mark it as unverified.

Include:
1. Decision criteria and suggested weights.
2. Side-by-side comparison table.
3. Pros and cons of each option.
4. Situations where each option is strongest.
5. Total cost of ownership: money, time, switching cost, complexity, maintenance, training, support, and lock-in.
6. Key risks, failure modes, and hidden trade-offs.
7. Recommendation by user profile or scenario.
8. Questions to answer before committing.

Output a clear recommendation, but separate facts, assumptions, and judgment. Do not overstate certainty when evidence is incomplete.

Act as a pattern extraction specialist. Reverse-engineer this success into repeatable principles.

Context:
- Success: [DESCRIBE THE SUCCESS]
- Timeline: [KEY PHASES]
- Team/resources: [DETAILS]
- Your theory for why it worked: [YOUR THEORY]
- Differentiators: [WHAT WAS DIFFERENT]
- Evidence available: [RESULTS / DATA / FEEDBACK]

If the context is thin, ask clarifying questions before analyzing. Do not confuse correlation, luck, or timing with a repeatable cause.

Analyze:
1. Break the success into 3-5 phases.
2. Identify the 2-4 key decisions in each phase.
3. Explain the conditions that made each decision work.
4. Separate deliberate choices from lucky timing, market conditions, personal relationships, or context-specific advantages.
5. Identify what likely would have happened if the opposite decision had been made.
6. Separate non-repeatable factors from transferable mechanisms.
7. Identify warning signs that the pattern would not transfer elsewhere.

Output:
- Phase-by-phase breakdown.
- Causal mechanism map.
- Transferable principles.
- Non-repeatable factors.
- Repeatable Success Protocol as a checklist.
- 2-3 adaptation scenarios.
- Near-miss lessons.

Avoid generic advice. Focus on mechanisms that can be reused.

Act as a productivity consultant specializing in realistic weekly planning and executive-level scheduling.

Inputs:
- Task list: [TASK LIST]
- Fixed commitments: [MEETINGS / APPOINTMENTS / DEADLINES]
- Core working hours: [WORKING HOURS]
- Energy patterns: [WHEN I AM SHARPEST / LOWEST ENERGY]
- Non-work commitments or constraints: [CONSTRAINTS]
- Must-finish outcomes this week: [OUTCOMES]

If the task list is too vague or too large, ask clarifying questions before building the plan.

Build a realistic weekly plan by considering urgency, deadline, importance, energy level, focus required, and available capacity. Include focused work blocks, admin time, personal errands, buffer time, and recovery space.

Output:
- Capacity Check: total available hours versus estimated workload.
- Weekly Schedule table with day, time block, task or focus, priority, energy fit, and notes.
- Deferred / Delegated / Shortened / Removed list if the workload is too high.
- Risk areas where the plan may break.
- Daily shutdown reminder or next-day setup action.

Rules:
- Do not overload the calendar.
- Protect high-energy windows for the most cognitively demanding work.
- Add buffers after meetings and before deadlines.
- If information is missing, mark it rather than inventing it.

Act as a deep work schedule architect. Build a weekly schedule that protects my best cognitive hours for my most important work.

First ask me for:
1. My current weekly schedule.
2. My peak energy and focus windows.
3. Non-negotiable commitments.
4. Work that requires deep focus.
5. Shallow work, admin, and meeting load.
6. Target deep work hours per week.
7. Constraints that make focus difficult.

After I answer, design:
- Peak Cognitive Hours.
- Deep Work Blocks of 90 minutes to 4 hours.
- Shallow Work and Admin Blocks outside peak focus time.
- Meeting Windows.
- Buffer and recovery blocks.
- Weekly Template.

For each deep work block include:
- Objective.
- Duration.
- Required preparation.
- Distraction boundary.
- Definition of done.

Rules:
- Schedule deep work only during realistic peak-focus windows.
- Protect at least [TARGET HOURS] of deep work per week if capacity allows.
- Identify what must be moved, shortened, delegated, or declined if the calendar is too crowded.
- Keep the schedule sustainable for low-energy days.

Act as a deep work environment architect. Design a physical and digital environment that makes focused work easier and distraction harder.

First ask me for:
1. Current workspace setup.
2. Available space and equipment.
3. Biggest physical distractions.
4. Biggest digital distractions.
5. Type of work I need to focus on.
6. Budget or constraints.
7. Whether this is for home, office, or hybrid work.

Then create:
- Physical Environment Design: desk layout, lighting, sound, seating, visual cues, and items to remove.
- Digital Environment Design: apps, notifications, file setup, browser setup, communication boundaries, and focus tools.
- 2-Minute Entry Ritual: a short sequence to start deep work.
- Distraction Friction Plan: how to make interruptions harder to access than the work.
- Reset Checklist: what to reset daily and weekly.
- Minimum Viable Setup: the smallest version for low-motivation or travel days.

For each recommendation, explain the purpose and the first action to take. Keep the system practical, low-friction, and realistic.

Act as my end-of-day executive assistant and productivity reviewer.

I will paste notes, tasks, conversations, meeting summaries, ideas, and updates from today: [PASTE NOTES].

Analyze everything and create a clear close-of-day review. If details are missing, mark them as unclear instead of inventing them.

Identify:
1. What was completed.
2. What progressed but remains open.
3. Unfinished tasks and open loops.
4. Pending decisions, blockers, and follow-ups.
5. Items that can wait until tomorrow.
6. Anything important that may have been forgotten.
7. Risks created by missed deadlines or unclear ownership.

Prioritize remaining work by urgency, importance, momentum, dependency, and realistic next action.

Output:
- Executive Summary.
- Completed Today.
- In Progress.
- Open Loops and Follow-Ups table: item, owner, next action, due date, status.
- Can Wait Until Tomorrow.
- Blockers or Decisions Needed.
- Suggested Priorities for Tomorrow Morning.
- One shutdown note: what I can stop thinking about tonight.

Do not create fake owners, deadlines, or decisions. Mark unknowns clearly.

Act as a professional meeting documentation assistant.

I will provide raw notes, bullet points, brainstorms, or a transcript: [PASTE MEETING NOTES OR TRANSCRIPT].

Transform the material into a clean, executive-ready summary. Remove filler and repetition while preserving decisions, nuance, risks, dissent, and unresolved issues.

Extract:
- Executive Summary.
- Key Decisions Made.
- Main Discussion Points.
- Action Items.
- Responsible Owners.
- Deadlines or Timelines.
- Risks or Blockers.
- Unresolved Questions or Follow-Ups.

For action items, output a table with:
Task | Owner | Due Date | Source / Context | Status

Rules:
- If an owner, deadline, or decision is unclear, write "Unclear" instead of inventing it.
- Separate confirmed decisions from proposals or opinions.
- Preserve important caveats and disagreements.
- Keep the final summary concise and useful for someone who missed the meeting.

When summarizing meetings, conversations, or collaborative work: attribute ideas to the person who introduced them, not just the person who agreed with them last. Treat problem framing, constraint identification, and exploratory questions as equal contributions to declarative conclusions. Do not weight assertive communication styles over analytical ones. For each key idea or decision, identify who introduced the underlying concept, not only who endorsed it.

You are starting a new project. Create three files in this folder:

1. AGENTS.md
   Single source of truth for this project. Include: project purpose, folder
   structure, key files and their roles, writing or coding style rules, content
   or data model, change workflow, and any constraints a collaborator must
   respect before touching anything. Write it so a tool starting cold could pick
   up the project without asking a clarifying question.

2. CLAUDE.md
   Claude's session entrypoint. It should contain only this:

   # Claude Context
   Read AGENTS.md before doing anything in this folder.
   Before working on this project, read:
   - AGENTS.md

3. HANDOFF.md
   Session coordination log. Start with this structure:

   # Handoff Log

   ## Last session summary
   [What was completed]

   ## In progress
   [What is partially done and where it stands]

   ## Decisions made
   [Any choices that affect future work]

   ## Next step
   [Exactly what the next session should start with]

Both Claude Code and CODEX should read AGENTS.md for project context and
HANDOFF.md to see where the last session left off. Update HANDOFF.md at the
end of every working session before closing.

Act as an execution strategist focused on realistic workload design.

Help me plan my upcoming week.

Inputs:
- Top objectives this week: [OBJECTIVES]
- Recurring commitments: [MEETINGS / ROUTINES / FIXED TIME BLOCKS]
- Biggest productivity challenges: [CHALLENGES]
- Energy patterns: [PEAK / LOW ENERGY TIMES]
- Hard deadlines: [DEADLINES]
- Available work hours: [HOURS]

If there are too many objectives for the available capacity, identify the conflict before building the plan.

Design a day-by-day plan where each day has exactly one primary outcome supported by 2-4 high-leverage tasks. Include realistic duration estimates, time-blocking suggestions, grouped task types, and buffer time.

Output:
- Weekly Overview.
- Capacity and Trade-Off Check.
- Daily Plan table: day, primary outcome, supporting tasks, estimated time, energy fit, buffer.
- Deferred or Reduced Items.
- Risk Points and Mitigations.
- Weekly Review Framework: progress, bottlenecks, learnings, and next-week priorities.

Rules:
- One primary outcome per day means one real priority, not a renamed task list.
- Keep the plan flexible enough to survive interruptions.
- Do not schedule more work than the stated available time supports.

Create a copy-paste-ready weekly executive meeting agenda for a [MEETING LENGTH] meeting.

Context:
- Team or group: [TEAM]
- Current priorities: [PRIORITIES]
- Metrics to review: [METRICS]
- Strategic initiatives: [INITIATIVES]
- Open questions: [OPEN QUESTIONS]
- Carry-forward actions from last meeting: [ACTIONS]

If meeting length or priorities are missing, ask clarifying questions first.

Build a timed agenda with:
1. Quick Wins and Headlines.
2. Carry-Forward Action Review.
3. Metrics Review.
4. Product or Workstream Progress.
5. Strategic Initiatives.
6. Team and Operations.
7. Risks, Blockers, and Decisions Needed.
8. Open Floor.
9. Action Items, Ownership, and Decision Log.

For each section include:
- Time allocation.
- Purpose.
- Questions to answer.
- Expected output.

End with two tables:
Task | Owner | Deadline | Status
Decision | Owner | Rationale | Follow-up Needed

Keep the formatting clean for direct use in Google Docs or a meeting notes tool. Do not invent owners or deadlines.

Act as a case study research assistant. I want to understand [TOPIC/SKILL] and how it has been applied in real organizations.

Context:
- My industry or use case: [CONTEXT]
- Preferred sectors or company types: [SECTORS]
- Timeframe or recency requirement: [TIMEFRAME]
- Depth required: [QUICK / DETAILED]

Find or construct a selection of case studies across different companies, sectors, or contexts. If factual or current claims are included, cite sources. If sources are unavailable, clearly label the case as illustrative.

For each case study include:
- Organization or context.
- Source type: verified source / secondary reporting / illustrative example.
- Situation and challenge.
- Approach or solution.
- Outcome and measurable impact where available.
- Why the example matters.
- Transferable lesson.
- Limits of transferability.

End with:
- Common patterns across cases.
- Mistakes or limitations to watch for.
- 3 practical ideas I could test in [MY CONTEXT].
- Source list with links and dates checked.

Do not fabricate company results, metrics, or quotes. Separate verified examples from constructed illustrations.

Act as a world-class presentation creator. Create a complete slide-by-slide presentation on [TOPIC] for [AUDIENCE].

Context:
- Presentation goal: [GOAL]
- Desired length: [NUMBER OF SLIDES OR TIME LIMIT]
- Tone: [TONE]
- Audience knowledge level: [LEVEL]
- Desired action after the presentation: [ACTION]
- Source material or facts to use: [SOURCES / NOTES]

If the goal, audience, or desired action is unclear, ask clarifying questions before building the deck.

Build a clear narrative flow with:
1. Title slide.
2. Opening hook.
3. Problem or context.
4. Key arguments or insights.
5. Supporting examples, data, or stories.
6. Visual suggestions for each major slide.
7. Audience takeaways.
8. Closing call to action.

For each slide include:
- Slide title.
- Slide objective.
- Main message.
- 3-5 bullets or talking points.
- Suggested visual.
- Speaker note or transition.
- Source placeholder if data, quotes, or factual claims are needed.

Do not invent statistics or research. Mark where evidence should be added.

Explain [TOPIC] using a structured visual-thinking approach.

Context:
- Audience: [AUDIENCE]
- Current knowledge level: [BEGINNER / INTERMEDIATE / ADVANCED]
- Desired use: [LEARN / TEACH / DECIDE / PRESENT]
- Preferred format: [FRAMEWORK / TIMELINE / PROCESS / SYSTEM MAP / COMPARISON]

If the topic is broad, ask clarifying questions or narrow it into a useful scope.

Make the topic easy to understand, remember, and mentally visualize. Use text-based diagrams, frameworks, timelines, systems maps, comparisons, and step-by-step structures where useful.

Include:
1. Simple foundation.
2. Key components and how they connect.
3. Cause-and-effect relationships.
4. Process flow if relevant.
5. System inputs, outputs, dependencies, and feedback loops if relevant.
6. Analogies or visual metaphors for abstract ideas.
7. Common misunderstandings.
8. Practical example in [MY CONTEXT].

Use clean spacing, arrows, hierarchy, concise labels, and plain language. End with a "mental snapshot" summary that compresses the topic into one memorable framework.

If factual accuracy matters, flag claims that should be verified.

Act as an expert note-taking and study assistant.

I will provide rough notes about [TOPIC]: [PASTE NOTES].

Clean up the notes, correct clarity issues, and organize them into structured study material. Preserve the original meaning. Clearly mark assumptions, added context, and points that need verification.

Include:
- Clean section headings.
- Polished bullet points.
- Key terms and definitions.
- Examples or analogies where helpful.
- Important takeaways.
- Gaps, unclear points, or possible inaccuracies.
- Questions for review.
- Short final summary.

Rules:
- Do not add unsupported facts as if they were in the notes.
- Keep source ideas traceable to the original notes where possible.
- If the notes conflict or seem incomplete, flag the issue instead of smoothing it over.
- Make the final output useful for studying, teaching, or revisiting later.

I am going to paste raw, unstructured notes below. They may include scattered thoughts, half-formed ideas, bullet fragments, and stream-of-consciousness writing.

Your job is to process this material and return a structured knowledge summary. Here is exactly what I need:

1. THEMES: Identify the 3 to 5 core themes running through the notes. Name each one clearly.
2. ACTIONS: Extract every actionable item. Rewrite each as a concrete next step starting with a verb.
3. TOP IDEAS: Surface the 3 highest-leverage ideas. For each, explain why it matters and what it unlocks.
4. HIDDEN CONNECTIONS: Identify non-obvious links between ideas that I likely did not notice myself. Be specific.
5. MASTER SUMMARY: Write a clean, scannable summary I can use as a reference document. Use headers and short paragraphs - no bullet soup.

Do not add ideas that are not in the notes. Do not editorialize. Reflect back what is there, but make it clear and organized.

Here are my notes:
[PASTE NOTES HERE]

You are a learning strategist who specializes in helping people study smarter, not harder. You use evidence-based methods from cognitive science and educational psychology.

I want to understand how I learn best and build a personalized study system around that.

Here is my context:
- What I am trying to learn: [SUBJECT OR SKILL]
- My current approach: [HOW YOU ARE STUDYING NOW]
- What is not working: [YOUR FRUSTRATIONS OR BLOCKERS]
- Time available per week: [HOURS PER WEEK]
- My deadline or goal: [WHEN AND WHAT YOU WANT TO ACHIEVE]

Run me through a diagnostic. Ask me 5 to 7 targeted questions to identify my strongest learning modalities (visual, auditory, reading/writing, kinesthetic, social, solitary) and my biggest retention bottlenecks.

After I answer, deliver:

1. LEARNING PROFILE: My dominant and secondary learning styles based on my answers, explained in plain language
2. WHAT I AM DOING WRONG: The specific mismatches between my current approach and how I actually learn best
3. MY CUSTOM STUDY SYSTEM: A concrete weekly routine built around my profile, available time, and goal
4. 3 HIGH-LEVERAGE TECHNIQUES: The specific methods most likely to accelerate my progress given my style

Start with your diagnostic questions.

Act as a document analyst. Read the full document before forming conclusions: [UPLOAD DOCUMENT OR PASTE TEXT].

If the document is long, still account for appendices, tables, footnotes, exhibits, and definitions where they affect meaning. If content is missing or unreadable, say so.

Analyze:
1. Document type.
2. Intended audience.
3. Primary objective.
4. Key ideas, arguments, decisions, or outcomes.
5. Major sections or themes.
6. Most important takeaway.
7. Evidence used to support the document's claims.
8. Open questions, missing information, assumptions, or ambiguities.

Output:
- Document Snapshot.
- Plain-Language Executive Summary.
- Section-by-Section Overview.
- Key Takeaways.
- Evidence and Support table: claim, source section, strength of support.
- Risks, Gaps, or Ambiguities.
- Most Important Message.
- Questions to Ask Next.

Keep the summary clear enough for a non-expert. Do not skip details that change the interpretation.

Act as a learning coach and intellectual historian. Analyze the public thinking style of [HISTORICAL FIGURE / EXPERT / THINKER] and translate it into practical exercises I can use.

Context:
- My problem or domain: [MY PROBLEM OR DOMAIN]
- What I want to learn from this thinker: [GOAL]
- My current level: [LEVEL]

Do not claim to know their exact private thought process. Base the analysis on public work, documented methods, decisions, writings, interviews, or widely accepted interpretations. If sources are needed, cite them or mark source needs clearly.

Include:
1. Core principles of their public thinking style.
2. How they approached problems.
3. Evidence or examples supporting each principle.
4. Strengths and blind spots of that approach.
5. 5 practical exercises to practice similar habits.
6. A checklist for applying the style to [MY PROBLEM OR DOMAIN].
7. Warning section: where this style may fail, mislead, or not transfer.

Keep the advice practical, grounded, and honest about uncertainty.

Act as a writing enhancement specialist and communication strategist.

Improve this text: [PASTE TEXT].

Context:
- Intended audience: [AUDIENCE]
- Purpose: [PURPOSE]
- Preferred tone: [TONE]
- Format: [EMAIL / MEMO / POST / REPORT / SCRIPT]
- Length or style constraints: [CONSTRAINTS]

Before rewriting, briefly identify:
1. The text's apparent purpose.
2. The intended reader.
3. The main message.
4. What is unclear, too long, unsupported, or tonally off.

Then rewrite the text to improve clarity, structure, concision, tone, and persuasive flow while preserving all original facts and essential meaning.

Output:
1. Improved version.
2. Brief notes on the most important changes.
3. Optional stronger headline, subject line, or opening if relevant.

Rules:
- Do not add new facts or unsupported claims.
- Preserve the author's position and intent.
- Avoid filler, vague claims, excessive polish, and robotic language.
- If a claim needs support, flag it instead of strengthening it artificially.

Act as a professional editor.

Rewrite the following text to correct grammar, punctuation, structure, and clarity while preserving the original meaning: [PASTE TEXT].

Editing preferences:
- Tone: [TONE]
- Format: [FORMAT]
- Edit intensity: light cleanup / moderate rewrite / strong rewrite
- Audience: [AUDIENCE]

Output:
- Revised text.
- 3-5 short notes explaining meaningful edits.
- Any unclear wording or unsupported claims that should be checked.

Rules:
- Do not add new facts.
- Do not change the author's position.
- Do not make claims stronger than the source text supports.
- Keep terminology that is important to the original meaning.

Act as an AI copyeditor with strong judgment about clarity, tone, and reader engagement.

Review this draft: [PASTE COPY].

Context:
- Intended reader: [READER]
- Desired action or response: [ACTION]
- Tone to preserve: [TONE]
- Channel or format: [CHANNEL]

Before rewriting, identify:
- Intended reader.
- Main message.
- Current tone.
- What is unclear, wordy, generic, unsupported, or weak.

Then improve the copy by:
1. Simplifying jargon and complex phrasing.
2. Removing unnecessary words.
3. Improving flow and structure.
4. Strengthening specific examples or story elements where useful.
5. Preserving the original meaning and voice.

Output:
- Revised copy.
- Key edits made.
- Optional alternative opening or closing.
- Claims or details that need evidence.

Do not add facts, exaggerate benefits, or make the copy sound unlike the intended voice.

Act as a content adaptation editor. Repurpose this source material for different channels while preserving the original message and avoiding hype: [PASTE SOURCE CONTENT].

Context:
- Audience: [AUDIENCE]
- Tone: [TONE]
- Channels needed: [CHANNELS]
- Primary message to preserve: [MESSAGE]
- Claims or facts that must not be changed: [FACTS]

Create a channel-native version for each channel listed in [CHANNELS]. If [CHANNELS] was left blank, default to: short professional post, concise thread or multi-part explainer, internal update or newsletter blurb, and short video or presentation script.

For each version include:
- Channel.
- Intended use.
- Final copy.
- What changed from the original and why.
- Any claims that need source support.

Rules:
- Preserve the original meaning.
- Do not add claims, statistics, or promotional language unsupported by the source.
- Adapt structure and tone to the channel instead of copying the same wording everywhere.
- Keep it useful, accurate, and audience-appropriate.

Act as a life strategist and performance coach. Help me run a structured life audit.

Context:
- Age: [AGE]
- Current role or life situation: [ROLE OR SITUATION]
- Biggest frustrations or challenges: [LIST 3-5]
- Desired outcome: [OUTCOME]
- Constraints: [TIME / MONEY / HEALTH / FAMILY / WORK]

First, ask focused diagnostic questions across:
1. Physical health and energy.
2. Mental clarity and emotional state.
3. Skills and career trajectory.
4. Income and financial stability.
5. Relationships and social environment.
6. Daily habits and routines.
7. Physical, digital, and work environment.
8. Long-term direction and values.

After I answer, identify patterns, bottlenecks, and blind spots. Prioritize the top 3 highest-leverage areas for improvement using impact, urgency, feasibility, and compounding benefit.

Then create a realistic 90-day plan with:
- Monthly themes.
- Weekly actions.
- Daily habits.
- Simple tracking metrics.
- Likely obstacles and fallback versions.

Important: Do not present this as medical, mental health, legal, or financial advice. If risks appear serious or outside coaching scope, recommend qualified professional support.

Context:
- What's causing the stress: [SITUATION]
- Type of stress: [OVERWHELM / ANXIETY / ANGER / GENERAL]
- Where I am right now: [HOME / OFFICE / PUBLIC SPACE]

Give me a clear 5-minute stress relief routine tailored to this context.

Structure it as a real-time guided script with approximate timing:
1. 0:00-1:00: One simple breathing exercise with exact timing.
2. 1:00-3:00: One grounding practice using the senses.
3. 3:00-4:15: One short calming thought or mental reframe suited to the situation.
4. 4:15-5:00: A gentle closing step for returning to the next task.

Use simple, calm, beginner-friendly language. Make the instructions easy to follow without special equipment. Avoid jargon and avoid overpromising.

Include:
- A short version for when I only have 60 seconds.
- A gentle reminder that this is not medical treatment.
- A brief note to seek qualified help or immediate support if symptoms feel severe, unsafe, or persistent.

Keep the tone steady, practical, and non-judgmental.