Library
Templates
Upload a document or deck you already use as your house format, describe how it should be followed, and the assistant writes new material to match it.
A saved prompt captures what to ask for. A template captures what the result should look like — your proposal layout, your board deck, your report structure — by giving the assistant the real file to work from.
Find them in the Library, under the Templates tab.
Adding one
Upload a document or a presentation you already use. Accepted formats:
| Type | Formats |
|---|---|
| Document | PDF, Word (.doc, .docx, .dotx) |
| Presentation | PowerPoint (.ppt, .pptx, .potx) |
Up to 50 MB. Dhanu works out which type it is from the file itself.
After the upload, the template is briefly Extracting while Dhanu reads it and generates a preview, then Ready. If it fails, the file was unreadable — export it again and re-upload.
The instructions are the important half
Every template carries a name and an instructions field: how should the AI use this? This is where the value is.
Follow the section order exactly. Keep the cover page and the disclaimer verbatim. One page per topic. Use the client’s name in the header. Do not add sections that are not in the template.
A template with no instructions gives the assistant a format to imitate. A template with good instructions gives it rules to follow — which is the difference between “roughly like ours” and “ours”.
Using one
In a task composer, type / and pick the template by name, or start a task from
a template directly from the Library. The assistant gets both your instructions
and the file itself as a reference, and writes the new document or deck to match.
You can then keep working on the result exactly as with any other document or deck — the template shapes the first version, it does not lock the file.
Private or shared
Like prompts, a template is either private to you or shared with a team. House formats belong to a team: that is how “our deck” stays one deck.
Templates are never project-scoped. They stay personal or with a team on purpose, so archiving a project cannot take your proposal format with it.
Working with it well
Upload the good example, not the empty shell. A filled-in past proposal teaches tone and depth as well as structure; a blank skeleton teaches only headings.
Write the instructions as rules, not description. “Keep the disclaimer verbatim” is enforceable. “Professional tone” is not.
One per real format. Two templates that differ by a logo will produce two inconsistent families of document. Keep the number small enough that choosing is obvious.
Refresh them when the format changes. A template is a standing instruction like any other — the rebrand that nobody applied here will keep coming out of the assistant for months.