ObsidianTemplates

Files (2)

• SKILL.md
• SKILL.yaml

SKILL.md (first lines)

# ObsidianTemplates

Manages the Obsidian template lifecycle: authoring templates across the two template trees, maintaining frontmatter schema conventions, and keeping the Templater plugin config in sync.

## Template Architecture

Two top-level trees, split by execution model:

| Tree | Role | Syntax |
|------|------|--------|
| `Templates/` | Standard templates — the agent copies schemas from here when creating typed notes | Plain markdown; Journals-plugin placeholders (`{{date}}`, `{{title}}`) allowed |
| `Templater/` | Dynamic templates — executed in-app by the Templater plugin (folder templates, hotkeys, journals) | `<% %>` blocks, moment.js, `tp.*` |

The agent never pastes `<% %>` syntax into a note; `Templater/` files are for in-app execution only. A template may exist in both trees: body structure (sections, embeds, query blocks) must be identical, only dynamic field expressions differ.

## Tree Layout

```
Templates/               standard
  Blocks/  Charts/  Domains/  Journal/  Library/  Maps/  Projects/  Zettelkasten/
  Default.md
Templater/               dynamic (in-app)
  Blocks/  Journal/  Library/  Processors/  Projects/
  Default.md
```

Folder mirrors destination: `Templates/Library/Book.md` → notes in `Library/Books/`, `Templates/Journal/Daily.md` → `Journal/Daily/`.

### Plugin syntax comparison

| Feature | Core Templates | Journals plugin | Templater |
|---------|---------------|-----------------|-----------|
| Title | `{{title}}` | `{{title}}` | `<% tp.file.title %>` |
| Date | `{{date:FORMAT}}` | `{{date:FORMAT}}` | `<% tp.date.now("FORMAT") %>` |
| Date offsets | Not supported | `{{date-1d:FORMAT}}`, `{{date+1d:FORMAT}}` | `moment().add()` |
| Week number | Not supported | `{{date:YYYY-[W]ww}}` | `moment().format("YYYY-[W]ww")` |
| JavaScript | Not supported | Not supported | `<%* ... %>` blocks |
| Include | Not supported | Not supported | `<% tp.file.include("[[...]]") %>` |

### Cascading with `tp.file.include()`

Reusable logic blocks live in `Templater/Blocks/`. Templates include them via:

```
<% tp.file.include("[[Block Name]]") %>
```

Templater resolves `<%* tR += %>` blocks through includes — cascading works. Use this for personal content (Key Results injection, habit trackers), query blocks shared across templates, and any logic that varies per-user.

**Pitfalls:**

- **Ambiguous file resolution**: `tp.file.find_tfile("Name")` resolves by basename — fails silently when multiple files share the same name. Use `app.vault.getAbstractFileByPath("full/path/to/File.md")` for explicit resolution.
- **Arrow functions in `<% %>`**: Templater's parser cannot handle `=>` inside `<% %>` tags (`Unexpected token '>'`). Use `<%* %>` execution blocks for multi-line logic.
- **Whitespace from includes**: `tp.file.include()` preserves leading/trailing whitespace from the included file. Use `.trim()` on `tR +=` output to prevent extra blank lines.
- **Linter reformats frontmatter**: After rendering, the Obsidian Linter may reformat quotes, field order, and timestamps. When editing rendered notes programmatically, use full-overwrite writes instead of incremental edits to avoid stale-content errors.

## Frontmatter Schema Registry

### Universal Fields (all templates)

```yaml
title:
aliases: []
tags:              # system/structural only (type/*, note/*)
keywords:          # wikilinks for topics/categories
  - "[[Topic]]"
description:
icon:              # Lucide icon name (LiCalendarFold, LiUser, etc.) — never emoji
image:
cssclasses:
created:           # YYYY-MM-DD HH:mm Z (empty in standard, Templater fills in dynamic)
updated:
related:
  - "[[Note]]"
collection:        # parent collection wikilink
root:              # parent hierarchy wikilink
```

### Tag Conventions

Primary tag: `type/<noun>` — what the note IS.
Secondary tag: `note/<category>` — zettel provenance (optional, for notes in the knowledge pipeline).

```
type/journal    note/daily | note/weekly | note/monthly | note/quarterly | note/yearly
type/contact    (no secondary — reference data, not zettel)
type/project    (no secondary)
type/book       note/literature
type/event      (no secondary)
type/collection (no secondary)
type/skill      (no secondary)
type/item       note/permanent
type/topic      note/permanent
type/repository note/literature
type/exercise   note/literature
```

DEPRECATED — do not use in new templates:
- `file/*` (use `type/*`)
- `schema/*`, `process/*`, `project/*`, `book/*` (use frontmatter fields for status/metadata)
- `lang/*` (remove — language is obvious from content)

### Category-Specific Schemas

**Journals**

```yaml
journal: Daily | Weekly | Monthly | Quarterly | Yearly
timeframe: YYYY-MM-DD
```

**Contacts**

```yaml
contact.email:
contact.linkedin:
contact.phone:
contact.website:
location.address:

From N4M3Z/forge-obsidian, EUPL-1.2.

More from N4M3Z/forge-obsidian