Free practical resource
Twenty-four copy-ready prompts built for real work. Replace the bracketed details, add relevant context, and check the output before using it.
Use prompts responsibly
A strong prompt improves the process, but it does not guarantee a correct answer. Add real context, protect private information, and verify current facts, quotations, figures, medical, legal, and financial claims.
Showing 24 prompts
Turn a topic into a focused article plan.
Act as an experienced content strategist. Create a practical content brief about [TOPIC] for [AUDIENCE]. The reader's main problem is [PROBLEM]. Include: search intent, one clear promise, a suggested title, an H1, a logical H2/H3 outline, questions the article must answer, evidence or examples needed, internal-link opportunities, and one useful call to action. Avoid generic filler and explain any assumptions.
Write a credible article without sounding generic.
Help me write an article about [TOPIC] using this real experience: [EXPERIENCE]. The audience is [AUDIENCE]. Lead with the practical problem, use the experience as evidence, explain what worked and what did not, and finish with clear next steps. Keep the tone [TONE]. Do not invent results, quotes, statistics, or personal details. Mark anything that needs verification.
Improve a draft while preserving the author's voice.
Edit the draft below for clarity, structure, and credibility while preserving my voice. Remove repetition, vague claims, hype, and unnecessary jargon. Strengthen transitions and make the practical takeaway obvious. Do not add facts that are not in the draft. Return: 1) the revised draft, 2) the five most important edits, and 3) any claims that need evidence. Draft: [PASTE DRAFT]
Create several useful formats from one source.
Repurpose the source below into: one LinkedIn post, one Instagram caption, a five-slide carousel outline, a short email, and three FAQ answers. Preserve the original meaning and facts. Adapt the opening and call to action for each format instead of copying the same text. Source: [PASTE ARTICLE]
Identify the evidence needed before searching.
Create a research plan for this question: [QUESTION]. Separate the question into sub-questions, identify which claims need current data, list the best primary source types, define inclusion and exclusion criteria, and provide a simple evidence table template. Flag likely uncertainty, bias, or regional differences. Do not answer the question yet.
Resolve agreements and conflicts between sources.
Compare the sources below. For each source, record its date, authority, method, relevant claim, limitations, and whether it directly supports the conclusion. Then show where the sources agree, conflict, or leave gaps. Prefer primary and recent sources. Clearly separate verified facts from reasonable inference. Sources: [PASTE LINKS OR EXCERPTS]
Turn a long document into actionable information.
Analyze the document below and extract only: confirmed decisions, deadlines, owners, required actions, unresolved questions, risks, and exact figures. Do not treat proposals as decisions. Present the result as a concise action table, followed by a short list of items that require confirmation. Document: [PASTE TEXT]
Pressure-test a plan or recommendation.
Critically review this argument or proposal: [PASTE TEXT]. Identify unsupported assumptions, missing evidence, alternative explanations, operational risks, and the strongest counterargument. Then suggest the minimum additional research needed before making a decision. Be constructive and specific.
Create an executable sequence with priorities.
Turn this goal into a realistic project plan: [GOAL]. Context: [CONTEXT]. Deadline: [DATE]. Available people or tools: [RESOURCES]. Create phases, deliverables, dependencies, owners, estimated effort, risks, and a definition of done. Separate must-have work from optional improvements and identify the first three actions.
Compare options using explicit criteria.
Help me decide between [OPTION A] and [OPTION B]. My priorities are [PRIORITIES], constraints are [CONSTRAINTS], and time horizon is [TIME HORIZON]. Build a weighted comparison, show trade-offs and risks, state what information is still missing, and make a recommendation that explains why. Do not assume every criterion has equal importance.
Find likely failure points before work begins.
Imagine this project failed six months from now: [PROJECT]. List the ten most plausible reasons, early warning signs, impact, and one prevention action for each. Rank them by likelihood and severity. Finish with the three risks that should be monitored weekly.
Convert updates into next-week priorities.
Using the notes below, prepare a weekly review with: completed work, work in progress, delays, decisions, risks, metrics, and the three highest-priority actions for next week. Separate confirmed facts from items that need checking. Notes: [PASTE NOTES]
Review one page for clarity, conversion, and search.
Audit this webpage for its target audience and search intent. URL or content: [URL OR PAGE TEXT]. Target customer: [AUDIENCE]. Primary goal: [ACTION]. Review message clarity, information hierarchy, mobile usability, trust signals, internal links, title, meta description, headings, image alt text, and call to action. Rank findings as critical, important, or optional and give exact replacement copy where useful.
Choose a useful page type for a search topic.
Analyze the likely search intent behind [KEYWORD] in [LOCATION OR MARKET]. Identify primary intent, secondary questions, suitable page type, audience stage, related terms, local modifiers, and content that would genuinely satisfy the search. Avoid keyword stuffing and distinguish research assumptions from verified search data.
Create accurate titles and descriptions.
Write five SEO title and meta-description pairs for this page: [PAGE SUMMARY]. Primary topic: [TOPIC]. Location if relevant: [LOCATION]. Keep titles concise, descriptions accurate, and the value clear. Do not use clickbait or make unsupported claims. Show approximate character counts and recommend the strongest pair.
Connect related content meaningfully.
Create an internal-link plan using these pages: [PAGE LIST]. For each source page, recommend the destination page, a natural anchor phrase, why the link helps the visitor, and where it should appear. Prioritize important service or resource pages and avoid repetitive exact-match anchors.
Investigate before changing code.
Diagnose this software issue before proposing a fix. Expected behavior: [EXPECTED]. Actual behavior: [ACTUAL]. Reproduction steps: [STEPS]. Relevant code or logs: [PASTE]. List the most likely causes in order, the evidence for each, the smallest checks that would confirm or reject them, and then propose the lowest-risk fix. Do not rewrite unrelated code.
Define changes, risks, and tests first.
Create an implementation plan for this feature: [FEATURE]. Current stack and constraints: [STACK]. Identify affected files or components, data flow, edge cases, security and accessibility considerations, migration needs, tests, rollback approach, and definition of done. Prefer the smallest maintainable change.
Find correctness and maintenance risks.
Review the code below as a production change. Focus on correctness, security, accessibility, performance, error handling, type safety, and maintainability. Rank findings by severity, cite the relevant code, explain the real impact, and provide minimal fixes. Do not comment on style unless it affects quality. Code: [PASTE CODE]
Cover the user flow and important failures.
Create a focused test plan for [FEATURE OR FLOW]. Include happy path, validation, permissions, mobile behavior, accessibility, network or API failure, empty states, boundary cases, regression risks, and production verification. Mark which tests should be automated and which need manual visual review.
Create a concise message with a clear ask.
Write a professional email to [RECIPIENT] about [SUBJECT]. Context: [CONTEXT]. My requested action is [ACTION]. Desired tone: [TONE]. Include a warm opening, only the necessary background, a clear request, any deadline, and an easy closing. Do not invent names, dates, prices, or commitments.
Separate discussion from commitments.
Convert these meeting notes into: decisions made, action items with owners and due dates, unresolved questions, risks, and the next meeting agenda. Do not infer ownership or deadlines that were not stated; mark them as confirmation needed. Notes: [PASTE NOTES]
Document a repeatable process for another person.
Create a simple SOP for this process: [PROCESS]. Intended user: [ROLE]. Include purpose, trigger, prerequisites, numbered steps, decision points, quality checks, common mistakes, escalation path, and completion record. Use plain language and make every step observable.
Reduce repetitive work without losing control.
Analyze this workflow: [DESCRIBE WORKFLOW]. Identify repeated work, handoff delays, duplicate data entry, approval bottlenecks, and error risks. Propose a simpler future workflow, what should remain manual, what could be automated, required data fields, and a phased rollout starting with the lowest-risk improvement.