name: design-session-logger
description: Log design work sessions to your note-taking system. Use when user says "log" or "exit" to save session progress, document design work, or create session summaries. Works with Obsidian, Notion, Confluence, Apple Notes, or any markdown-based system. Trigger on session logging, save progress, design documentation, exit commands, or when user wants to document their work.

Design Session Logger

A flexible skill for logging design sessions to any note-taking system (Obsidian, Notion, Confluence, Apple Notes, etc.).

First-time Setup

Check for config file at ~/.design-session-logger.json.

If config exists: Read settings and use them.

If config doesn't exist: Ask the user:

1. "Where should I save design logs?"
2. Get the full path (e.g., /Users/you/Documents/Obsidian Vault/Design Sessions)

3. For Notion/Confluence users, suggest a local folder they can import from

4. "What's your preferred structure?" Offer these presets:

5. Project folders (recommended): {project}/{page} - {date}.md
6. Flat structure: {project} - {page} - {date}.md
7. Date-based: {date}/{project} - {page}.md

8. Custom: Let them define their own pattern

9. Ask about Notion sync (optional):

10. "Do you want to also sync to Notion automatically?"
11. If yes: "I'll need your Notion integration token and parent page ID"

12. If no: Set notion.enabled to false

13. Create the config file:

{
  "save_location": "/path/to/notes",
  "folder_pattern": "{project}",
  "file_pattern": "{page} - {date}.md",
  "title_format": "# {project} - {page}",
  "date_format": "MMMM DD, YYYY",
  "sections": [
    "What we built",
    "Design decisions",
    "Components changed",
    "Potential next steps",
    "Notes"
  ],
  "notion": {
    "enabled": false,
    "integration_token": "",
    "parent_page_id": ""
  }
}

Save this to ~/.design-session-logger.json and confirm with the user.

When User Says "log" or "exit"

Step 1: Load Configuration

Read ~/.design-session-logger.json to get settings.

Step 2: Gather Context

From the current conversation, extract:
- Project name: The Figma project or design system being worked on
- Page name: The specific page/canvas within that project
- Current date: Format according to date_format from config
- Session content:
- What was built (components, layouts, features)
- Design decisions made (approach, rationale, tradeoffs)
- Components changed (what was created, modified, or removed)
- Potential next steps (what's planned or suggested)
- Notes (any important context, blockers, or observations)

Step 3: Build File Path

Use the config patterns to construct the path:
- Replace {project} with project name
- Replace {page} with page name
- Replace {date} with formatted date
- Combine: {save_location}/{folder_pattern}/{file_pattern}

Example: /Users/you/Documents/Obsidian Vault/Design Sessions/Agentic workflow/MCP test - March 12, 2026.md

Step 4: Check for Existing File

If working on the same project-page-date:
- UPDATE the existing file (merge new content with existing)
- Preserve existing content, add new work

If new day or new project-page:
- CREATE a new file

Step 5: Format Content

Use the title format and sections from config. Example:

# {project} - {page}

## What we built
- [Bullet points of components, layouts, features created]

## Design decisions
- [Key choices made, rationale, approach]

## Components changed
- [What was created, modified, updated]

## Potential next steps
- [ ] [Checkbox list of future work]

## Notes
- [Context, blockers, observations]

Important formatting rules:
- Use sentence case for all section headings (from config)
- Keep content simple and flat with bullet points
- No complex formatting or nested structures
- Focus on high-level decisions and changes, not minutiae

Step 6: Write the File

Create any necessary folders, then write the file to Obsidian.

Step 7: Sync to Notion (if enabled)

Check if config.notion.enabled is true.

If Notion sync is enabled:
1. Find or create project folder page:
- Search for a child page with title matching {project} under the parent page
- If not found, create it using Notion API:
bash curl -X POST https://api.notion.com/v1/pages \ -H "Authorization: Bearer {token}" \ -H "Content-Type: application/json" \ -H "Notion-Version: 2022-06-28" \ --data '{"parent": {"page_id": "{parent_page_id}"}, "properties": {"title": [{"text": {"content": "{project}"}}]}}'
- Extract the id from response and save as project_page_id

1. Find existing session log page:
2. Search for a child page under project_page_id with title {page} - {date}

3. If found, this is an update scenario

4. Convert markdown content to Notion blocks:

5. ## Heading → heading_2 block
6. - Item → bulleted_list_item block
7. - [ ] Todo → to_do block (unchecked)
8. Regular text → paragraph block

9. Limit to first 100 blocks (Notion API restriction)

10. Create or update the page:

11. If page exists: Append new blocks to existing page using PATCH /v1/blocks/{page_id}/children
12. If new page: Create page with blocks using POST /v1/pages

Example creation:

python3 << 'PYTHON' | curl -X POST https://api.notion.com/v1/pages \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -H "Notion-Version: 2022-06-28" \
  --data @-
[Python script to convert markdown to JSON blocks]
PYTHON

Step 8: Confirm and Continue

• If user said "log": Confirm saves to both Obsidian and Notion (if enabled), continue session
• If user said "exit": Confirm saves and say goodbye

Platform-Specific Notes

Obsidian

Files are saved directly as .md and will appear immediately in Obsidian.

Notion

Automatic sync (if enabled in config):
- Logs are automatically created/updated in Notion via API
- Maintains same folder structure: project pages contain session logs
- Works alongside Obsidian logging (dual sync)

Manual import (if Notion sync disabled):
- Save as .md files to the configured location
- User can drag-and-drop into Notion or use Notion's import feature

Setup for automatic sync:
1. Create integration at https://www.notion.so/my-integrations
2. Copy integration token
3. Share target page with the integration
4. Add token and page ID to config

Confluence

• Generate markdown files
• User can copy-paste content into Confluence pages
• Preserve markdown formatting for easy conversion

Apple Notes

• Save as .txt or .md files
• User can copy-paste into Notes
• Alternatively, use AppleScript to create notes directly (if user wants automation)

Other Systems

• Save as plain text or markdown
• Provide clear file location so user can import/copy as needed

Updating Configuration

User can edit ~/.design-session-logger.json anytime to change:
- Save location
- Folder/file structure
- Section names
- Date format
- Title format
- Notion integration settings (enable/disable, token, parent page)

Or ask you to update it for them by saying "update my design log config".

Examples

Example 1: Obsidian with project folders

Config:
{
  "save_location": "/Users/you/Documents/Obsidian Vault/Design Sessions",
  "folder_pattern": "{project}",
  "file_pattern": "{page} - {date}.md"
}

Result: Design Sessions/Agentic workflow/Dashboard - March 12, 2026.md

Example 2: Flat structure for Notion import

Config:
{
  "save_location": "/Users/you/Desktop/Design Logs",
  "folder_pattern": "",
  "file_pattern": "{project} - {page} - {date}.md"
}

Result: Design Logs/Agentic workflow - Dashboard - March 12, 2026.md

Example 3: Date-based organization

Config:
{
  "save_location": "/Users/you/Documents/Notes",
  "folder_pattern": "{date}",
  "file_pattern": "{project} - {page}.md"
}

Result: Notes/March 12, 2026/Agentic workflow - Dashboard.md

Troubleshooting

Config file missing or corrupted: Walk through setup again.

Path doesn't exist: Create the directories as needed.

Can't determine project/page: Ask user to clarify what project and page they're working on.

First time in session: If no design work has happened yet, ask user if they want to log configuration changes or skip logging this session.