Archives
Trending
Support
Login
clear text
XML
Django
JavaScript
MATLAB
C
C++
C#
Python
SQL
Shell
Bash
Markdown
YAML
JSON
HTML
CSS
PHP
Java
Ruby
Go
Rust
Swift
Kotlin
Arduino
TypeScript
Perl
Autohotkey
Lua
SQF
R
Scala
Haskell
Groovy
Dart
Clojure
VB.NET
Objective-C
PowerShell
Bash
CoffeeScript
Verilog
--- name: log-to-daily-note description: Logs conversation activity and outcomes to the daily note in the Obsidian vault. Use when wrapping up tasks, after completing work, or when the user asks to update the daily note. ---
Capture and log conversation activity to the current day's daily note in the Obsidian vault at `MY OBSIDIAN PATH`. This ensures all work sessions are documented for future reference and maintains continuity across sessions.
1. Determine today's date and construct the daily note path: `00 Daily/YYYY/YYYYMMDD.md` 2. Read the existing daily note (or create if it doesn't exist) 3. Summarize the conversation activity into appropriate sections 4. Append or update the daily note with new content
**Daily note location:** `00 Daily/YYYY/YYYYMMDD.md` - Example: `00 Daily/2025/20251125.md` for November 25, 2025 **Daily note template:** ```markdown --- date: YYYY-MM-DDTHH:MM tags: [Daily] cssclasses: [daily, Weekday] --- # DAILY NOTE ### *Weekday, Month DDth, YYYY* ## Journal [Summary of the day's activities] --- ## [Topic/Project Sections] [Detailed notes organized by topic] --- ## Ongoing Tasks - [ ] Task items --- ## Reflections [Optional end-of-day reflections] --- ## Files Created Today [Obsidian wiki links to any files created during this session] ```
**Step 1: Identify today's daily note** - Get current date - Construct path: `/Users/jameschristian/Sync/Cerebro/00 Daily/YYYY/YYYYMMDD.md` **Step 2: Read existing content** - If file exists, read current content - If file doesn't exist, create with template frontmatter **Step 3: Analyze conversation for loggable content** Identify: - Meetings held or scheduled - Decisions made - Tasks completed or created - Projects progressed - Emails sent or received - Strategic insights - Next steps identified - **Files created during this session** (new documents, incubation ideas, project files) **Step 4: Structure the update** - Add new sections for distinct topics/projects - Update existing sections if adding to prior content - Add/update task items in Ongoing Tasks section - Include links to related project files where relevant - **Add "Files Created Today" section at the end** with Obsidian wiki links to any new files **Step 5: Write the update** - Preserve existing content - Append new sections in logical order - Use consistent formatting (headers, bullet points, checkboxes)
**Section headers:** Use `## Section Name` for main topics **Project/meeting sections:** ```markdown ## Project Name - Brief Description **Key details in bold** - Bullet points for details - Use checkboxes for action items: `- [ ]` or `- [x]` **Status:** Current status **Next steps:** What happens next ``` **Linking to project files:** - Reference related files: `Project file: \`02 Projects/Project Name.md\`` - Use Obsidian wiki links where appropriate: `[[Project Name]]` **Tables for summaries:** ```markdown | Item | Status | Value | |------|--------|-------| | Entry | Status | €X | ```
Logging is complete when: - [ ] Today's daily note exists at correct path - [ ] Frontmatter is valid and up-to-date (correct date, tags, cssclasses) - [ ] All significant conversation activity is captured - [ ] Content is organized into logical sections - [ ] Related project files are linked - [ ] Task items are captured with checkboxes - [ ] Formatting is consistent with existing vault style - [ ] **"Files Created Today" section exists** with wiki links to any files created during this session
**Required format for Files Created Today:** ```markdown --- ## Files Created Today - [[PAST-SHAPE Plugin Pack Idea]] - Framework monetization concept - [[Some Other File]] - Brief description ``` **Rules:** - Use Obsidian wiki link syntax: `[[File Name]]` (without path or extension) - Add brief description after each link - Include ALL files created during the conversation (incubation ideas, project docs, resources) - Place at the very end of the daily note as an appendix
Mark as private (unlisted)
for 30 minutes
for 6 hours
for 1 day
for 1 week
for 1 month
for 1 year
everlasting (like CCCP)