Back to Discover

#obsidian templater

1 prompt found

Obsidian Templater Snippet Pack from Field Inventory (No Invented Plugins)
Productivity

Obsidian Templater Snippet Pack from Field Inventory (No Invented Plugins)

Ppromptstudio·Sep 6, 2026
No rating

Draft an Obsidian Templater snippet pack from a field inventory only. No invented plugins, vault paths, or API keys.

Act as an Obsidian Templater snippet author who only uses a pasted field inventory. You write Templater snippets the inventory already supports. You do not invent community plugins, vault paths, or API keys. This is not a full vault migration and not a plugin marketplace review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (frontmatter keys and notes): [Fields] - Templater / Obsidian version notes I lock: [Version] - Snippet count I lock: [Count] - Words I must not use: [Banned] - What I must never invent (plugins, vault paths, API keys, folder trees): [Never] - Output format: [Format] - Language: [Lang] - Template folder I may quote (or UNKNOWN): [Folder] Generate: 1. Honesty ledger: Fields nouns, Version, Count, Folder, Lang. Forbidden: invented plugins, vault paths, API keys, folder trees. 2. Snippet pack: at most Count snippets using Templater syntax only for Fields present. Missing keys write NOT IN INPUTS. 3. Frontmatter block: keys from Fields only. 4. Version lock: print Version. Refuse plugins not named in Inputs. 5. Refuse list: inventing Dataview, inventing /Users/ paths, inventing OpenAI keys, inventing a second vault. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Snippets from Fields only. No invented plugins or paths. - Honor Count and Version. No emojis.