Find a prompt. Adapt it. Try it.

Act as a practical planning coach. I will share my tasks, deadlines, available hours, and energy levels. Create a realistic weekly plan, group similar tasks, identify the three highest priorities, and include buffer time. Present the result as a day-by-day table.

Rewrite the text below in clear language for a general audience. Preserve every important fact, remove jargon, shorten long sentences, and flag anything that remains ambiguous. Return: 1) revised text, 2) key changes, and 3) questions that need clarification. Text: [paste text]

Teach me [topic] at a beginner level. First explain it with one simple analogy. Then give me a five-part lesson, ask one question after each part, and wait for my answer before continuing. Correct misunderstandings gently and finish with a short review quiz.

Help me prepare for a meeting about [topic]. My goal is [goal], the other participants are [people], and the main constraint is [constraint]. Create an agenda, likely objections, concise responses, five questions to ask, and a follow-up email template.

Act as a careful debugging partner. Review the code and error below. Do not rewrite everything immediately. First identify the most likely causes, then propose the smallest diagnostic checks, explain what each result would mean, and finally provide a minimal fix with tests. Code: [paste code] Error: [paste error]

Generate 12 ideas for [project]. Divide them into three groups: safe, distinctive, and experimental. Make every idea different in audience, mechanism, or format—not merely a renamed version. For each idea include the core concept, intended audience, and first test.

Turn the notes below into an action plan. Separate decisions, tasks, open questions, and risks. For every task suggest an owner, priority, and reasonable next step. Do not invent missing deadlines or commitments; mark them as needing confirmation. Notes: [paste notes]

Draft a concise email about [subject] for [recipient]. My goal is [goal]. Use a warm, professional tone, put the request near the top, include only necessary context, and end with a clear next step. Provide a subject line and keep the body under 150 words.

Act as a constructive reviewer. Evaluate the plan below for unclear assumptions, missing dependencies, operational risks, and measures of success. Rank the issues by impact and likelihood. Then suggest the three smallest changes that would reduce the most risk. Plan: [paste plan]

Turn the requirements below into a test plan. Include happy paths, boundary cases, invalid inputs, permissions, failure recovery, and accessibility checks. For each test provide setup, action, and expected result. Highlight requirements that are not testable as written. Requirements: [paste requirements]