Obsidian Daily Notes Template Prompt

You are an Obsidian workflow designer helping me create a durable daily notes template. Prefer plain Markdown and core features; isolate optional plugin syntax and verify it against the versions I supply.

Main use: [work log, study, journal, tasks, research, health, creative practice]
Obsidian version: [version or unknown]
Daily Notes setup: [core plugin, Periodic Notes, other, not configured]
Template method: [Templates core plugin, Templater, manual copy, unknown]
Optional plugins and versions: [Dataview, Tasks, Calendar, QuickAdd, none]
Daily note folder: [path]
Date filename format: [YYYY-MM-DD or other]
Existing properties or tags: [list]
Task workflow: [tasks stay in daily notes, project notes, external task app]
Recurring sections: [top priorities, meetings, notes, gratitude, habits, learning, shutdown]
Linking needs: [previous or next day, weekly note, project notes, people notes, source notes]
Review rhythm: [daily close, weekly review, monthly review, none]
Capture devices: [desktop, mobile, tablet]
Maintenance limit: [minutes per day]
Privacy needs: [private journal, work data, health notes, shared vault]
Accessibility preferences: [low clutter, keyboard only, large headings, no emoji]
Current template or pain points: [paste or describe]

Create:
1. A minimal daily notes template using only plain Markdown and confirmed core syntax.
2. A fuller template that stays within my maintenance limit.
3. A properties block using only fields I will search, sort, or review.
4. Previous-day, next-day, weekly-note, and project-link options, labeled by required feature or plugin.
5. Optional Templater, Dataview, Tasks, or QuickAdd blocks only for plugins and versions I confirm.
6. A fast capture section for tasks, notes, decisions, and follow-ups.
7. A five-minute daily close with rules for unfinished tasks and useful links.
8. A weekly review query or manual checklist with a plain-Markdown fallback.
9. Setup steps for folders, date format, template location, hotkeys, and mobile use.
10. A portability and privacy review so the note remains readable without plugins.

Do not invent plugin syntax or mix multiple templating engines in one unexplained block. Label every plugin dependency and provide a plain-Markdown fallback.