Smart Templates

Smart Templates combines the current note or selection, optional supporting context, one or more reusable Markdown templates, and a request-specific instruction.

Core copies the completed prompt. Templates Pro can generate inside Obsidian, open the result for review, and then copy, insert, create a note, or regenerate.

Choose the output path

Path	Use when	Completion
Copy prompt	You want to use ChatGPT, Claude, Gemini, Smart Chat, or another AI interface.	The pasted prompt contains the intended context, template, and instructions.
Generate	You use Templates Pro and want generation and review to stay inside Obsidian.	A reviewed result is copied, inserted, used to create a note, or regenerated deliberately.

The preparation flow is shared:

current note or selection -> context -> template -> instructions

Only the output action changes.

In this guide

Build and copy AI prompts from Obsidian templates

Open Template Context

Run:

Smart Templates: Open template context

The ribbon opens the same shared modal. In the file navigator, right-click a Markdown or text file and choose Open template context to seed that file even when another note is active.

Core and Pro use the same open command and preparation modal. Pro adds output controls after the request is ready.

Start from the current note or selection

Opening from the editor uses the active note as the context anchor. When supported text is selected first, the selection becomes the starting context instead of the whole note.

If a selection unexpectedly replaced the note, close Template Context, clear or adjust the selection, and reopen it. If a file-menu action used the wrong note, invoke the action from the intended file rather than relying on the editor's active note.

Add and review context

Choose Add context only when the current note or selection does not contain enough evidence. Opening the chooser does not add a source by itself.

Review every included source before generating or copying. When the assignment needs a deliberately composed or reusable package, build it first with Smart Context, then open that context in Smart Templates.

Select one or more templates

Choose Select, or Change when a template is already selected. Smart Templates can use:

built-in templates
templates from configured folders
the Obsidian Templates folder
notes marked with smart template: true
notes matching configured filename rules
matching headings inside notes

Built-in defaults allow a first workflow before vault-specific configuration.

When you select multiple templates, Smart Templates combines them in selection order. Review the finished request when order affects section sequence or instruction priority.

Use {{vault_tags}} in a template when the workflow should expand the vault's current tags. Verify the expansion in the finished prompt before sending it.

Add request-specific instructions

Templates should hold reusable structure. The instruction should describe what is unique about this run.

For example:

Focus on the unresolved decision, strongest evidence, and next reversible action.

Avoid repeating the complete template in the instruction. Shorter, discriminating constraints are easier to inspect and reuse.

Before choosing an output action, check:

the starting note or selection
any added context
the selected templates and their order
the request-specific instruction
the visible size or scope estimate
the destination you intend to use

Template suggestions and context suggestions are separate modes. Use the mode control to return to the source type you need. Selecting or clearing a template should update the request panel before you continue.

Templates Pro does not use a separate configurator. It adds Generate and model controls to the shared flow.

Copy the completed prompt in Core or Pro

Choose Copy prompt after reviewing the request. Paste into a clean composer or temporary note and verify:

the intended context is present
unrelated sources are absent
the selected template structure is recognizable
the request-specific instruction is included
source material and instructions are clearly separated

Core does not require an API key because it stops at the clipboard. Content leaves Obsidian when you paste or send it into another application or provider.

Generate and review output in Pro

Availability and model requirements

Templates Pro adds Generate to the same context-first workflow. It requires one compatible configured model.

If Generate is missing:

confirm Templates Pro is installed, enabled, and active
confirm a compatible model is configured and available
reopen Template Context from the intended note or selection
review edition or account access in Browse Smart Plugins

Do not replace the Pro workflow with the Core copy path merely because one model or account state is unavailable. Fix the prerequisite or use Core intentionally.

Generate from Template Context

Prepare the request exactly as you would for Core, then choose Generate.

Templates Pro sends the reviewed context, templates, and instruction through the selected model and opens the result in a review surface. Generation does not automatically promote the output into a trusted note.

Choose a default or per-request model

Templates Pro supports:

a default Generate model in settings
a per-request model override in Template Context or the review flow

Use the saved default for routine work. Override it when the task needs a different capability, cost, privacy boundary, or comparison. A per-request choice does not change the saved default.

Review generated output

Compare the result with:

the source context
the selected template structure
the task-specific instruction
the intended note or destination

Then choose the appropriate action:

Action	Use when
Copy	The result belongs in another composer, note, or application.
Insert	The reviewed output belongs at the intended position in the current note.
Create note	The result should become a separate note.
Regenerate	The request is sound but another model or pass may improve the result.

You can copy without inserting. Insert and Create note should follow review, not replace it.

Regenerate deliberately

Before regenerating, identify what should change. Improve the instruction or context when the first result lacked evidence or misunderstood the goal. Change the model when the same request merits a capability comparison.

Repeated generation without changing the request can produce variation, but it does not resolve a missing requirement.

Review before promoting trusted content

Generated output remains a draft until you inspect its claims, omissions, structure, and fit. Insert only material that belongs in the trusted note. When the output reveals a recurring problem, improve the source note or template so the next request starts stronger.

Troubleshooting Smart Templates

What happened	Try first
No templates appear	Check the template folder, Obsidian Templates fallback, flags, filename rules, and heading detection in settings.
The wrong source is seeded	Close the modal, clear the editor selection, and reopen from the intended note or file.
The request is too large	Remove optional sources or build a narrower Smart Context package.
Copy prompt appears incomplete	Recheck context, template selection, and instructions independently, then copy and paste again.
Generate is missing	Confirm Templates Pro access and one compatible configured model.
Generation fails	Test or switch the model, reduce the context, and retry from the reviewed request.
The output format drifts	Make the template more explicit, simplify the instruction, and regenerate.
Insert would overwrite trusted work	Copy the result or create a new note, then merge manually after review.