Smart Templates

Build reusable prompt requests in Core and generate reviewed output in Pro from one Smart Templates reference. Pro controls remain visible beside the Core clipboard workflow.

In this guide

Build and copy AI prompts from Obsidian templates

Smart Templates combines current work, reusable Markdown templates, and request-specific instructions. Core copies the assembled prompt without requiring an API or generation model.

The Template Context flow combines selected note context with a reusable template before the prompt is copied.

Open template context

Run Smart Templates: Open template context to open the shared context-first modal.

Use the current note as the seed

The active note is added as the starting context when there is no editor selection override.

Use an editor selection as the seed

Highlighted editor text replaces the current-note seed for that invocation.

Why did selected text replace the whole note?

Editor selection is the intentional higher-priority context seed.

Add and review context

Add more sources or blocks through the embedded Smart Context workflow before selecting the final templates.

Select one or more templates

The selected-template state makes the active reusable structure visible before prompt assembly.

Select one or more trusted Markdown templates from the template suggestion scope.

Combine multiple templates

Multiple selected templates are merged in stable selection order before prompt assembly.

What order are multiple templates merged in?

The stable order in which they were selected.

Add request instructions

Add request-specific instructions without modifying the reusable template files.

Copy the completed prompt

Copy prompt assembles and copies one ready-to-run prompt.

No API or configured generation model is required.

Do I need Smart Templates Pro to copy a prompt?

No. Clipboard-first prompt assembly is the Core workflow.

Expand `{{vault_tags}}`

{{vault_tags}} is expanded before prompt assembly in templates or instructions that use it.

Commands and entry points

The command, ribbon, and supported file-menu action open the same shared modal.

Command list

Main command:

Command	Behavior
`Smart Templates: Open template context`	Opens the shared Template Context modal.

Does Pro use a different open command?

No. Core and Pro use the same command; Pro adds controls inside the modal.

Command visibility

The main command is available while the plugin is enabled.

Feature-specific eligibility is resolved inside the modal rather than through several legacy command variants.

Command prerequisites

The plugin and Smart Environment must be loaded.

A current note is optional; without seeded context the modal starts in context-suggestion mode.

Hotkey candidate

The main command is the preferred hotkey target because Core and Pro share it.

Ribbon action

The ribbon icon opens the same shared modal as the main command.

File-menu action

Right-click a supported Markdown or text file and choose Open template context.

The clicked file becomes the initial context seed even when another file is active.

Why did the file-menu action use a note that was not active?

The clicked file intentionally becomes the seed for that invocation.

Template Context modal

The modal combines context selection, template selection, instructions, and Core or Pro output controls.

Open the modal

Open the shared Template Context modal from the Command Palette, ribbon icon, or supported file-menu entry.

Initial context seed

The active note is the default context seed.

Selection override

When editor text is selected, the selection replaces the whole note as the initial context item.

Context workspace

The left side of the modal contains the current Smart Context workspace and suggestion flow.

Request panel

The right side owns request state:

selected template keys
user instructions
preferred output target

Template suggestions

When seeded context exists, template suggestions open immediately.

With no context, the modal starts in context-suggestion mode.

Why did the modal open to template suggestions instead of context suggestions?

It already had seeded context from the current note, selected text, or clicked file.

Select or unselect templates

Enter or Right Arrow toggles the highlighted template.

Left Arrow returns to context suggestions.

How do I return from template selection to context selection?

Press Left Arrow in the template suggestion scope.

Instructions

Add optional user instructions in the request panel.

Instructions are combined with the selected context and templates when the prompt is built.

Copy prompt

Core exposes Copy prompt.

The action assembles one prompt from current context, selected templates, and instructions, then writes it to the clipboard.

Pro Generate controls

Pro extends the same modal with:

Generate
per-request model selector
configurable primary-action shortcut

The model override applies to the current request and does not need to change the saved default.

Does Pro use a separate configurator modal?

No. The shared Template Context modal already owns context, templates, instructions, model override, and output action.

Troubleshooting Smart Templates Clipboard

Confirm Smart Templates and Smart Environment are loaded; clear selection when the whole note should seed; use the file-menu action for a non-active file; review multi-template order; confirm variables are supported; retry clipboard copy with the destination focused.

Generate from templates inside Obsidian

Smart Templates Pro adds in-Obsidian generation to the same context, template, and instruction request used by the clipboard workflow. Output opens for review before insertion or note creation.

Availability and model requirements

Generate requires Smart Templates Pro and a compatible chat-completion model configured through Smart Environment.

Generate from the Template Context modal

Smart Templates Pro adds Generate to the shared Template Context modal. The request uses the current context, selected templates, optional instructions, and selected model.

Why is Generate missing?

Generate requires Smart Templates Pro and a configured chat model.

Understand model resolution

Smart Templates resolves the model in this order:

current request override
Smart Templates Generate model setting
Smart Environment default chat model

Override the model for one request

Choosing a model in the request or output modal changes only that request. It does not replace the saved default.

Does a per-request model change my default?

No. It applies only to the current request.

Review generated output

Generate opens a dedicated output modal and streams the response into a review surface.

Copy generated output

Use the copy icon to copy the generated text without closing the output modal.

Can I copy without inserting?

Yes. Use the copy action in the output modal.

Regenerate with another model

Change the model when needed and select Regenerate. The same context, selected templates, and instructions are used again.

Insert into the current note

Use Insert to place the reviewed output into the active editor. Check the destination before inserting generated text into a trusted note.

Create a new note

Enter a filename and choose Create note to save the reviewed output as a new note.

Review before promoting generated content

Generated text is not trusted note content until it has been checked. Correct the output, the context set, or the template before inserting it into a canonical note.

Troubleshooting Smart Templates Generate

Confirm a model is configured, review context and templates when output drifts, use a one-request model override for comparison, confirm an active editor before Insert, choose a valid filename before Create note, or use Core Copy prompt when in-Obsidian generation is unnecessary.