Library
Saved prompts
Keep the requests that work — with fill-in-the-blank fields, kept private or shared with a team, and inserted into any task with a slash.
The prompt that got you exactly the right weekly update is worth more than the update. Saved prompts are where those live, so you are not searching March’s tasks for a message you wrote once.
Find them in the Library, under the Prompts tab.
Writing one
A saved prompt is a title and a body. The title is how you will find it later — Weekly status update, Vendor contract review — so name it after the job, not the technique.
If you would rather start from a sketch, Draft with AI turns a title and a rough idea into a first version you then edit.
A prompt can be up to 10,000 characters, which is far more than a good one needs.
Fill-in-the-blank fields
Put {{double braces}} around anything that changes each time:
Write a status update for {{client}} covering {{period}}.
Lead with risks. Under 200 words. No preamble.When you use the prompt, Dhanu asks for each field before inserting it — Client, Period — and fills them in. One prompt then covers a whole category of request instead of being rewritten every week.
Leave a field blank and the placeholder stays in the text, so you can fill it in yourself.
Private or shared
Every prompt lives in one of two places, chosen when you save it:
| Visibility | Who can use it |
|---|---|
| Private | Only you |
| A team | Everyone on that team |
Sharing the good ones is the point. A team prompt is how a way of asking spreads without anyone writing a style guide about it.
Using one
In a task composer, type / and pick the prompt by name — yours are marked My
prompt, your teams’ as Shared prompt. It is inserted into the message, fields
filled, and you can edit it before sending.
The same / menu also reaches your staff, your apps, other tasks, your files and
your templates, so a prompt sits alongside everything else you might want to pull
into a message.
Keeping them useful
Save it the moment it works. The best time is right after a reply that was exactly right — copy that message, generalise the specifics into fields, save.
Generalise the specifics, keep the constraints. The client name becomes a field; “no preamble, under 200 words” stays hard-coded, because that is the part that made it good.
Prune them. Twenty prompts nobody can choose between is worse than five everyone uses. Delete the ones that stopped matching how you work.
Know when it should be a staff member instead. A prompt you run every Monday against the same sources is a job, not a message — see Hire your first AI staff member.