Templates

Template library

Reusable prompts extracted from real use cases. Read the scene, then paste the template into your own agent.

Show me first; do not send on your own

When to use it：When the task might send mail, submit a form, sign into payment, or do something you cannot undo

You may research and prepare a draft, but if the next step is sending, submitting, opening a payment account, or anything irreversible, stop and show me the full text. Do not submit until I have clearly said you may.

Three questions at most, then three options

When to use it：Posters, covers, layouts, and other work that needs a style choice first

Before you start making anything, ask at most three decisive questions. Then offer three distinct directions, each in three sentences covering mood, where it fits, and its limits. Wait until I pick one, then produce the sizes I need.

If a figure is not in the files, leave it blank

When to use it：Taxes, claims, reconciliations, and any work that must match the files exactly

Use only the files I handed you. List missing fields as “needs confirmation”. Do not estimate, fill gaps, or invent figures. Name the files you relied on in the output.

Stop at the last confirm button and list the consequences

When to use it：Cancelling a subscription, asking for a refund, placing an order, or filing an official form

Walk the flow up to, but not through, the final confirm button. List the end date, amounts, and what happens if I confirm. Press it only after I say so. When you finish, split out what is done and what you could not complete.

Give me a list first; change nothing until I agree

When to use it：Cleaning up overlapping automations, routines, files, or tasks

First list every overlapping or duplicate item, how you would merge or remove it, and the exact steps you would take. Change or delete nothing until I agree. When you are done, give me a list of what remains.

Read the shared notes first, then write back when you finish

When to use it：Several agents taking turns on the same project

Before you start, read and follow the shared notes in this repository (conventions, recent decisions, unfinished work). When you finish, commit what you decided and what is still open. Leave unrelated files alone, and never commit secrets.

Send a card when you are unsure; do not guess and continue

When to use it：A person has stepped away and the job is still running in the background

Ping me with a Feishu or desktop card only when you need a choice or a secret, or when the next step would delete data, spend money, message the outside world, or cannot be undone. Otherwise keep going, and say in the card what is done and where you are stuck.

Plan and pre-fill, but do not place the order

When to use it：Travel, lodging, or appointments that would charge a card or lock a date

Search and compare options, build the itinerary, and pre-fill the forms I choose. Do not pay or make a final submission until I have checked the price, dates, and cancellation terms. Show me everything first.

Save a new file; leave the original as it is

When to use it：Editing Word, Excel, PowerPoint, or another existing document

Make the changes I asked for, but save the result as a new file with the name I give you. Do not overwrite the original, and list every change when you are done.

Name the file behind every answer

When to use it：Answering meeting questions or knowledge-base queries from local files

Answer only from the folder I specify. Every suggestion must name the file it comes from. If that folder has no basis for an answer, say you do not know — do not invent one. Keep the work on this machine, and ask before installing software.

If you want it to tidy the structure, say it is responsible for this codebase

When to use it：When a stronger coding model is editing an existing repo, and you do not want it to pile another copy beside the code that is already there

You are responsible for this codebase from here: you decide how it should be structured, and you will keep working on it. Merge duplicated logic when you see it, and fix nearby problems that would block the change I asked for. Do not change behavior I did not ask for; if you think you must, list it and wait. When you finish, name every structural change in your summary. I will review the full diff, not only that summary.

Work through ordinary obstacles; stop only at a real blocker

When to use it：When a long or unattended agent run stops halfway to ask whether it should continue

Do not stop while the work I asked for is still doable. If you hit an error, a timeout, an empty result, or a flaky tool, diagnose it and try another safe path: retry, fix the request, or use another tool you already have access to. Do not pause only to ask whether you should continue. Stop and tell me plainly when the next step needs a decision from me, or when you would have to touch a file I marked off-limits, use access I withheld, or do something risky or irreversible — then wait. While you report progress, keep going on any part that does not depend on my answer.