Productive— faster every day
For your professionTeachersStudentsManagersMarketingDevelopersFreelancersParents

Prompt library · AI · 11 prompts

Prompts from the guide

Which tools have an MCP connector, and what you can actually do with them

11 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.

Read the full guide →

In Claude Code, from the command line

I want to add an MCP server to Claude Code [name / URL or
command to launch it]. I've never done this before. Write me:

1. The exact command and what each of its parameters means
2. Whether it's remote or local, and what that means for me
   in practice (where the data flows, what runs on my machine)
3. What I need to have ready beforehand (account, permissions,
   environment)
4. A query I can use after install to confirm it's working
5. How to remove it again if it doesn't work out

Don't assume I can code. Where there's a risk, say so up
front, not at the end.

Buffer: a scheduler the model can see into

Put together a batch of posts from this source material:

[paste the article text or a link]

Channels: [LinkedIn, Instagram, Facebook page].
Period: [14] days starting [date]. Frequency: [LinkedIn 3x a
week, Instagram 2x, Facebook 2x].

For each post, write:
- copy tailored to that channel (LinkedIn longer and
  substantive, Instagram shorter with emphasis on the first
  line, Facebook medium length)
- a suggestion for what the image should show (description
  only, don't generate the image)
- a proposed day and time with a reason
- one extra opening-line variant so I have something to
  choose from

It must not be the same text just shortened — each channel
should get its own angle on the source material. Don't claim
anything the source material doesn't say.

Don't create anything in Buffer yet, just list it out in the
chat.

Evaluation: what worked and what just looked good

Pull my post metrics from Buffer for [the last 3 months]
for channel [channel] and break it down:

1. The ten best-performing and ten worst-performing posts —
   date, first 80 characters, and key metric for each
2. What the successful ones have in common: topic, format,
   length, type of opening line, day and time, presence of
   an image
3. The same for the weak ones
4. Which differences are a real pattern and which could just
   be noise from a small sample size
5. Three changes for next month and how I'll know they worked

Be careful with point 4: when a claim is based on fewer than
[10] posts, say so explicitly instead of drawing a conclusion.
Work only from metrics you actually pulled.

Canva: working with your designs, not generating from nothing

Find my brand template [name] in Canva and produce a series
of designs from it based on this table:

[paste the data — e.g. heading / subheading / name / date
for each item, one row = one design]

Rules:
- insert the text verbatim, don't rephrase or shorten
  anything
- if text doesn't fit a field, don't create that design and
  tell me how many characters over it is
- name the designs following the pattern
  [project]-[sequence number]
- save them into folder [folder name]
- at the end, give me a list with links and status for each
  one

Don't publish or share anything externally.

Adobe: image editing, video, and Express

Folder [path] has [50] product photos. Process them like this:

1. Remove the background from each one
2. Crop to content and add a uniform [8] percent border
3. Standardize to [1600 x 1600] px, product centered
4. Save as [PNG with transparency] into folder [destination],
   keep the filename and add a -clean suffix

Before you start, do the first three and show them to me —
once I approve those, run the rest. Where background removal
doesn't come out clean (hair, transparent materials, fine
detail), skip the file and put it on a list for manual
finishing.

Lucid: diagrams you don't draw by hand

Turn this process description into a flowchart in Lucid:

[paste the process description — plain paragraphs are fine,
however it was originally written]

- each step as a block, decision points as diamonds
- name the role that does each step in the block, under the
  step's title
- label the branches at each decision (yes/no or the specific
  condition)
- where the description has a gap — a step that doesn't lead
  anywhere, or a decision missing a second branch — insert a
  block that says “UNRESOLVED: [what's missing]” instead of
  guessing
- name the diagram [name], save it into folder [folder], and
  at the end list everything you flagged as unresolved

Google Analytics: official, local, and read-only

Look at my GA4 property [name or ID] and answer this for the
period [July 1-31, 2026] versus [the previous month]:

1. What changed in traffic — total and by channel (organic,
   direct, referral, paid, social), both in percentages and
   absolute numbers
2. Which pages gained the most and lost the most, ten and
   ten, with numbers
3. For the three biggest changes, write which explanations
   are plausible and how I'd verify them with another query
   against the data

Rules:
- don't state a percent change for numbers under [100]
  visits, give absolute values instead
- distinguish what's your conclusion from what's directly in
  the data
- where a metric is missing, say so instead of estimating

Notion, Drive, and Supabase: where the rest of the answers live

Put together a monthly report for [client] covering [month]:

1. From GA4 property [name]: total traffic and traffic by
   channel, the ten most-visited pages, conversions on
   [event] — all versus last month
2. From Notion, from page [name]: what we launched or changed
   this month, with dates
3. For each significant change in the numbers, note whether
   it lines up in time with anything from point 2

Format: two pages, a five-sentence summary first, then the
numbers, then what it means for next month.

Don't mistake a coincidence in timing for a cause — where
something lines up, write “coincides with,” not “caused.”
State where each number comes from.

Keeping an eye on spend

I want to process [task description — e.g. generate
illustrations for 200 articles / classify 5,000 comments]
through the Gemini API.

Estimate the cost for me:
1. Which billing type applies to this task (tokens / per
   image / per second of video)
2. An estimate of volume — for text, estimate the token count
   for input and output and say what the estimate is based on
3. The price under standard processing and under batch
4. How the price changes if I use a cheaper model, and what
   I'd actually lose by doing that
5. Three ways to cut the volume without losing the result

Use the prices from the price list I'm giving you: [paste the
current price list]. Don't work from prices in your memory —
they may have changed.

Route A: a script on top of an API key

Work inside this project's folder. I want a script that uses
the Gemini API to [task description — e.g. generate an
illustration for every article / transcribe audio files in a
folder].

Requirements:
- the API key is read EXCLUSIVELY from environment variable
  [name]; if it's missing, the script exits with a clear
  error message
- the key is never printed to a log or to output
- inputs come from folder [path], outputs are saved to [path]
- an item that already has output gets skipped
- with no arguments it processes everything; with arguments,
  only the specified items
- a call counter with a cap of [50]; it stops if that's
  exceeded
- if one item fails, it keeps going and prints a summary at
  the end: how many done, how many skipped, how many failed
- nothing gets published or sent anywhere — output only goes
  to the folder

At the top of the file, add a comment explaining how to run
the script and what it needs configured. Comment the code in
English. When you're done, explain what each part does as if
I don't know how to code.

When a connector fails or comes back empty

The previous answer doesn't look right to me — [it's empty /
the numbers don't match what I see in the tool]. Before you
try again, describe:

- which connector and which of its capabilities you used
- with what parameters (period, account, property, folder,
  filter)
- how many records it returned and whether anything got
  truncated
- what in the answer comes from the data you pulled and what
  is your own conclusion

Then suggest what to change in the request. Don't repeat the
query until we've agreed on what went wrong.

All prompts