No prompts match your search.
Product launch announcement You are a marketing copywriter for [Company name], which sells [what you sell] to [target customers].
Write a launch announcement for [product or feature name]. It solves this problem: [problem it solves].
Include:
- A headline under 10 words
- Two short paragraphs on the problem and how the product solves it
- Three bullet points with concrete benefits
- A clear call to action: [call to action]
Tone: [tone, e.g. friendly and confident]. Avoid hype words like "revolutionary" and "game-changing".
Social media post series Create [number] social media posts for [platform] for [Company name].
Audience: [target audience]
Goal: [goal, e.g. drive sign-ups to the free trial]
Key message: [key message]
For each post give: the hook (first line), the post text, a suggested image idea and up to 3 relevant hashtags. Vary the formats: tip, question, behind the scenes, customer problem, and offer.
SEO blog outline Act as an SEO content strategist. Create a detailed outline for a blog post targeting the keyword "[main keyword]" for readers who are [audience].
Include:
- 3 title options under 60 characters
- A meta description under 155 characters
- H2 and H3 headings that answer the main questions people search for
- Where to use related terms: [related keywords]
- 4 FAQs with one-line answers
Do not invent statistics. Mark any place where a real figure or source is needed with [SOURCE NEEDED].
Cold email to a prospect Write a cold email from [your name] at [Company name] to [prospect name], the [prospect's role] at [prospect company].
What we offer: [your offer]
Why them: [a specific reason this prospect may need it]
Proof: [one real result or client type, or leave out]
Rules: under 120 words, no buzzwords, one clear question as the call to action, and a subject line under 6 words. Give 2 versions.
Follow-up after no reply Write a follow-up email to [prospect name] who has not replied to my email about [topic] sent [days] days ago.
Add something useful: [a resource, insight or idea relevant to them].
Keep it under 80 words, friendly, and end with an easy yes/no question. Do not guilt-trip or say "just checking in".
Proposal summary Summarise this proposal for [decision-maker's role] at [client company] who has 2 minutes to read it.
Proposal details:
[paste proposal or key points]
Structure: the problem in one sentence, what we will deliver, timeline, price, and the next step. Use plain language and keep it under 200 words.
Reply to an unhappy customer You are a customer support agent for [Company name]. Write a reply to this customer message:
"[paste customer message]"
What we can do: [solution, refund, replacement or next step]
Acknowledge the problem without excuses, explain the fix and timeline clearly, and end with how they can reach us. Keep it under 150 words. Tone: warm and professional.
FAQ from support tickets Here are recent customer questions for [product or service]:
[paste questions]
Group similar questions, then write an FAQ with the 8 most common ones. For each, give a short clear answer based only on this information: [paste policies or product facts]. If the information is missing, write [ANSWER NEEDED] instead of guessing.
Chatbot system prompt You are the support assistant for [Company name], which [what the company does].
Help visitors with: [topics the bot should handle].
Do not: give legal, medical or financial advice; make up prices, policies or delivery dates; promise anything not written below.
If you don't know the answer or the visitor is upset, offer to connect them with a human at [contact method].
Facts you can use:
[paste key facts, prices and policies]
Keep answers short, friendly and in the visitor's language.
Rewrite for clarity Rewrite the text below so a [audience, e.g. busy business owner] understands it on first read.
[paste text]
Keep the meaning and all facts. Use short sentences, everyday words and active voice. Cut anything that repeats. Show the rewritten text first, then list the 3 biggest changes you made.
Meeting notes to action items Turn these meeting notes into a clear summary:
[paste notes]
Output:
1. Decisions made
2. Action items as a table: task, owner, due date (write "not set" if missing)
3. Open questions
Do not add anything that is not in the notes.
Professional email reply Write a reply to this email:
"[paste email]"
What I want to say: [your main points]
Tone: [tone, e.g. polite but firm]
Keep it under [number] words and end with a clear next step.
Code review Review this [language] code as a senior engineer:
```
[paste code]
```
Context: [what the code is supposed to do]
List issues in order of severity: bugs, security problems, performance, then readability. For each, quote the line, explain the problem and show the fix. Skip style nitpicks unless they hide a bug.
Explain an error I am getting this error in my [language/framework] project:
```
[paste error and stack trace]
```
Relevant code:
```
[paste code]
```
Explain what the error means in plain words, the most likely cause, and how to fix it. If more information is needed, tell me exactly what to check.
Write unit tests Write unit tests for this [language] function using [test framework]:
```
[paste function]
```
Cover the normal case, edge cases (empty input, limits, invalid values) and expected errors. Use clear test names that describe the behaviour. Do not change the function.
Technical spec from an idea Turn this feature idea into a technical specification for a [type of app, e.g. Laravel web app]:
Idea: [describe the feature]
Users: [who will use it]
Include: user stories, acceptance criteria, data model changes, API endpoints, edge cases, and questions to answer before building. Keep it practical and avoid gold-plating.
Standard operating procedure Write a standard operating procedure (SOP) for [process name] at [Company name].
Who does it: [role]
How often: [frequency]
Current steps (rough notes): [paste notes]
Format: purpose, scope, tools needed, numbered steps, checks at the end, and what to do if something goes wrong. Write it so a new team member can follow it without help.
Find automation opportunities Here is a description of how our team handles [process or department]:
[describe the daily and weekly tasks]
Identify the tasks that could be automated or helped by AI. For each, explain: what would be automated, the type of tool needed (e.g. a script, an integration, an AI assistant), rough effort (low/medium/high), and the risk if it goes wrong. Rank them by value for effort.
Compare vendors Help me compare these options for [what you are buying]: [option A], [option B], [option C].
Our needs: [key requirements]
Budget: [budget]
Create a comparison table with criteria that matter for our needs, then list the questions I should ask each vendor. Do not invent prices or features; mark unknowns as [CHECK WITH VENDOR].
Job description Write a job description for a [job title] at [Company name], a [company description] based in [location / remote].
Responsibilities: [main responsibilities]
Must-have skills: [skills]
Nice-to-have: [skills]
What we offer: [benefits, salary range if public]
Use inclusive, plain language. Keep must-haves to what is truly required. End with how to apply.
Interview questions Create interview questions for a [job title] role. The most important skills are: [skills].
Give 8 questions: 3 about past experience, 3 practical or scenario questions, and 2 about how they work with others. For each, add what a strong answer should include.
Analyse a spreadsheet export Here is data from [source, e.g. our sales report for Q3]:
[paste CSV or table]
Analyse it and tell me: the 3 most important trends, anything unusual, and 3 questions I should investigate. Show any calculations you did. Do not make assumptions about columns you do not understand; ask instead.
Customer feedback themes Here are customer reviews / survey answers for [product or service]:
[paste feedback]
Group them into themes. For each theme give: a short name, how many comments mention it, 2 representative quotes, and whether it is positive or negative. Finish with the top 3 things to improve.
