Creating Templates

Templates are just markdown files stored in your vault’s templates folder. There’s no special format to learn — if you can write a markdown note, you can create a template.

Where Templates Live

Templates are stored in:

<vault>/templates/

Any .md file in this folder is recognized as a template by Atlas. You can create subfolders to organize templates by category if you have many.

Creating a Template

Create a new .md file in the templates/ folder with your desired structure. You can do this:

• In the Files tab — navigate to the templates folder and create a new file
• Via chat — “Create a new template called meeting-notes.md with sections for Attendees, Agenda, Discussion, and Action Items”
• Directly in your file system — create the file in any text editor and save it to the templates folder

A Simple Example: Meeting Notes Template

# Meeting Notes — {{title}}

**Date:** {{date}}
**Time:** {{time}}

## Attendees

-

## Agenda

1.

## Discussion

## Action Items

- [ ]

## Notes

Save this as templates/meeting-notes.md and it’s immediately available to Atlas.

What You Can Include

Templates support everything a regular markdown note can have:

• Headings (#, ##, ###)
• Lists (bullet and numbered)
• Tasks (- [ ] checkboxes)
• Tables
• Frontmatter (YAML at the top between --- delimiters)
• Code blocks
• Links (including [[wikilinks]] to other vault notes)
• Placeholders ({{variable}} syntax for dynamic values)

Using Placeholders

Placeholders are replaced with real values when Atlas creates a note from the template. Use double curly braces: {{variable_name}}.

Built-in placeholders are replaced automatically. Custom placeholders (anything you define yourself, like {{client_name}}) are replaced if you provide the value when requesting the note, or left as-is for you to fill in manually.

See Template Variables for the full list of built-in placeholders.

Tip

Keep placeholder names short and descriptive. {{project}}, {{client_name}}, and {{meeting_type}} are easy to remember and obvious when you’re filling them in later.

Updating a Template

Edit the template file directly — changes take effect immediately the next time the template is used. Atlas always reads the template file at creation time, so there’s no cache to clear.

Organizing Templates

As your template library grows, consider using subfolders:

templates/
  meetings/
    1on1.md
    team-sync.md
    client-call.md
  reviews/
    weekly-review.md
    monthly-retro.md
  projects/
    project-plan.md
    sprint-planning.md

Atlas can list and use templates from subfolders — just tell it which one you want: “create a note from the client-call template.”

---

Next: Template Variables