### Install and Set Up Claudesidian

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Clone the repository, install dependencies, and run the interactive setup wizard within Claude Code. The wizard configures your vault, detects naming conventions, and sets up optional integrations.

```bash
git clone https://github.com/heyitsnoah/claudesidian.git my-vault
cd my-vault
pnpm install
claude
# Inside Claude Code:
# "Set up claudesidian for my vault"   ← triggers init-bootstrap skill
```

--------------------------------

### Gemini Vision MCP Server Setup and Usage

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

This section details the setup and usage of the Gemini Vision MCP server for integrating Google Gemini's multimodal capabilities. It includes API key setup, installation, and examples of how to use the available MCP tools for image analysis, text extraction, and more.

```bash
# Setup:
export GEMINI_API_KEY='your-key-from-aistudio.google.com'
source ~/.zshrc
pnpm install
claude mcp add --scope project gemini-vision node .claude/mcp-servers/gemini-vision.mjs
pnpm test-gemini  # verify connection

# Available MCP tools (called by Claude Code automatically when relevant):
# mcp__gemini-vision__analyze_image       — describe/analyze a single image
# mcp__gemini-vision__analyze_multiple    — batch-analyze up to 3 images
# mcp__gemini-vision__extract_text        — OCR from image or scanned page
# mcp__gemini-vision__compare_images      — side-by-side comparison
# mcp__gemini-vision__suggest_image_filename — generate descriptive filename
# mcp__gemini-vision__analyze_document    — extract and analyze PDF content

# Usage in Claude Code (natural language):
"Analyze the screenshot at 05_Attachments/error-screen.png and explain the error"
"Extract all text from 05_Attachments/contract.pdf"
"Compare before-and-after designs: 05_Attachments/v1-mockup.png and 05_Attachments/v2-mockup.png"
"Suggest better names for all images in 05_Attachments/ based on their content"

# Rate limits: Free tier = 15 requests/minute
```

--------------------------------

### Start Claude Code and Run Setup Wizard

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Initiate Claude Code in your vault directory and run the '/init-bootstrap' command to set up dependencies, import existing vaults, and configure your personalized CLAUDE.md.

```bash
# Start Claude Code in the directory
claude

# Run the interactive setup wizard (in Claude Code)
/init-bootstrap
```

--------------------------------

### Claude Code Workflow: Starting a Project

Source: https://github.com/heyitsnoah/claudesidian/blob/main/01_Projects/README.md

Use this prompt to initiate a new project. It guides Claude Code to create the project, set up the folder structure, and help define objectives.

```text
Create a new project called [name] in 01_Projects.
Set it up with the standard folder structure.
I'm in thinking mode - help me define objectives.
```

--------------------------------

### Area Structure Example

Source: https://github.com/heyitsnoah/claudesidian/blob/main/02_Areas/README.md

Illustrates the typical directory structure for an Area, including README, Goals, Resources, Reviews, and Ideas subdirectories.

```text
Area_Name/
├── README.md          # Overview and principles
├── Goals/            # Current focus areas
├── Resources/        # Reference materials
├── Reviews/          # Periodic check-ins
└── Ideas/           # Future possibilities
```

--------------------------------

### Note Structure Example

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A markdown template for structuring notes, including sections for summary, key points, connections, and sources.

```markdown
# Concept Name

## Summary
One paragraph overview

## Key Points
- Main idea 1
- Main idea 2
- Main idea 3

## Connections
- Related to: [[Other Concept]]
- Contrasts with: [[Different Idea]]
- Examples: [[Case Study]]

## Sources
- Original article/book/video
```

--------------------------------

### Claude Code Workflow: Finding Examples

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt template for using Claude to search resources for specific examples of a concept.

```plaintext
I need examples of [concept].
Search my resources for relevant cases.
```

--------------------------------

### Install Shell Command for Claudesidian

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Installs a shell command to launch your vault from any directory. It automatically changes to your vault directory, resumes existing sessions, or starts a new one, and returns you to your original directory.

```bash
# In Claude Code, run:
/install-claudesidian-command
```

```bash
# From anywhere in your terminal:
claudesidian

# It will automatically resume your last session or start a new one
```

--------------------------------

### Synthesize Project Notes

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Use this prompt to get a consolidated overview of key themes, insights, and open questions from notes within a specified project folder.

```plaintext
Review all notes in [project folder].
Create a synthesis of the key themes, insights, and open questions.
```

--------------------------------

### Basic Git Workflow for Obsidian Vault

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CLAUDE-BOOTSTRAP.md

Essential Git commands to run at the start and end of each session to sync and preserve your work.

```bash
git pull
```

```bash
git add .
git commit -m "message"
git push
```

```bash
git status
```

--------------------------------

### Get Project Status and Next Actions

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Obtain a summary of the current status of a project and identify the immediate next steps required.

```plaintext
Review the project in [folder].
What's the current status?
What are the next actions needed?
```

--------------------------------

### Conventional Commits Examples

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CONTRIBUTING.md

Examples of commit messages following the Conventional Commits specification for clear commit history.

```git
feat: add new research-assistant command
```

```git
fix: correct attachment link updates in scripts
```

```git
docs: update README with MCP setup instructions
```

--------------------------------

### Start Daily Work Session

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Use this prompt to ask Claude Code to review your previous day's work and help you resume your tasks.

```plaintext
I'm starting work for today. 
Can you review what I was working on yesterday 
and help me pick up where I left off?
```

--------------------------------

### Morning Review of Daily Tasks

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Start your day with a review of notes modified the previous day, open tasks, and recommended focus areas for the current day.

```plaintext
Good morning. Show me:
- Any notes modified yesterday
- Open tasks or questions
- What should I focus on today?
```

--------------------------------

### Initialize Git Repository for Vault

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Initializes a Git repository for version control of your vault. It's recommended to commit after each work session with descriptive messages and pull before starting work.

```bash
git init
git add .
git commit -m "Initial vault setup"
git remote add origin your-repo-url
git push -u origin main
```

--------------------------------

### Area vs Project Distinction

Source: https://github.com/heyitsnoah/claudesidian/blob/main/02_Areas/README.md

A table illustrating the key difference between an ongoing Area and a time-bound Project, with examples.

```text
| Area (Ongoing) | Project (Time-bound) |
|---------------|---------------------|
| "Health" | "Lose 10 pounds by June" |
| "Finances" | "Create 2024 budget" |
| "Writing" | "Finish blog post series" |
| "Learning" | "Complete Python course" |
| "Clients" | "Deliver Project X" |
```

--------------------------------

### Claudesidian Vault Configuration

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

The setup wizard generates a personalized CLAUDE.md and a .claude/vault-config.json file. This JSON configuration stores user details, organization method, primary uses, tool preferences, and project/area information.

```json
{
  "user": {
    "name": "Jane Smith",
    "background": {
      "companies": ["Acme Corp"],
      "roles": ["Researcher"],
      "expertise": ["AI", "Systems Thinking"]
    },
    "customContext": "Uses vault for deep research, not just note storage"
  },
  "organizationMethod": "PARA",
  "primaryUses": ["research", "writing", "projects"],
  "tools": {
    "geminiVision": true,
    "firecrawl": false
  },
  "projects": ["Book Draft", "SaaS App"],
  "areas": ["Health", "Newsletter"],
  "importedAt": "2025-06-01",
  "lastUpdated": "2025-06-01"
}
```

--------------------------------

### Claudesidian Git Workflow

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Basic Git commands for initializing, committing, and pushing changes in the Claudesidian vault. Includes recommended daily workflow for pulling changes before starting and pushing after finishing work.

```bash
# Initial setup (done by init-bootstrap, or manually):
git init
git add .
git commit -m "Initial vault setup"
git remote add origin your-private-repo-url
git push -u origin main

# Recommended daily workflow:
git pull                          # START every session
# ... work in vault ...
git add .
git commit -m "Research session: habit formation synthesis"
git push                          # END every session

# Mobile access via SSH (Termius + Tailscale):
# 1. Clone vault to a home server or VPS
# 2. Install Tailscale on both devices
# 3. SSH from Termius into the server
# 4. Run `claude` remotely

# Quick-launch alias (installed by install-claudesidian-command skill):
claudesidian   # from any directory: cd to vault + resume/start Claude session
```

--------------------------------

### Claude Code Prompt: Concept Clarification

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt for Claude to explain a concept using examples drawn directly from the user's existing resources.

```plaintext
Explain [concept] using examples 
from my existing resources.
```

--------------------------------

### Claude Code Prompts for Documentation

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/README.md

Use these prompts to query documentation on a specific topic or to update existing guides based on new information.

```plaintext
Check 06_Metadata/Reference for documentation on [topic].
Update the guide based on what we just learned.
```

--------------------------------

### Process Inbox using PARA Method

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

This prompt guides Claude Code to review items in a specified inbox folder, suggest placements based on the PARA method, and identify potential items for combination or linking.

```plaintext
Review items in 00_Inbox.
Suggest where each should be moved based on PARA method.
Which items could be combined or linked?
```

--------------------------------

### First Session Prompt for Claude Code

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Use this prompt to initiate a collaborative exploration session with Claude Code, focusing on thinking and research rather than direct writing. It instructs Claude to search your vault for relevant notes and ask guiding questions.

```plaintext
I'm starting a new project about [topic].
I'm in thinking mode, not writing mode.
Please search my vault for any relevant existing notes,
then help me explore this topic by asking questions.
```

--------------------------------

### Clone Claudesidian Starter Kit with Git

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Clone the repository to your local machine using Git. Replace 'my-vault' with your desired folder name. This is the primary method for obtaining the starter kit if you use Git.

```bash
git clone https://github.com/heyitsnoah/claudesidian.git my-vault
cd my-vault
```

--------------------------------

### Sample Project Completion Summary

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

A markdown template for summarizing completed or cancelled projects, including objectives, outcomes, lessons learned, and reusable assets.

```Markdown
# Project: [Name] - Completion Summary

**Duration**: Start date - End date **Status**: Completed/Cancelled/Suspended

## Objectives

- Original goal 1 ✓
- Original goal 2 ✓
- Original goal 3 ✗

## Key Outcomes

- What was delivered
- What impact it had
- What value was created

## Lessons Learned

- What worked well
- What didn't work
- What to do differently

## Reusable Assets

- Templates created: [[link]]
- Processes developed: [[link]]
- Insights gained: [[link]]

## Related Notes

- Continues in: [[Area name]]
- See also: [[Related project]]
```

--------------------------------

### Create Project with Template

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/README.md

Use this prompt with Claude Code to create a new project from a template, specifying the project name and destination folder.

```plaintext
Create a new project using the project template.
Name it [Project Name] and put it in 01_Projects.
```

--------------------------------

### Preview and Run Claudesidian Upgrade

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Use the `/upgrade` command to check for, preview, or force an update of Claudesidian. It's recommended to preview changes before running the interactive upgrade.

```bash
# Preview what would be updated (recommended first)
/upgrade check
```

```bash
# Run the interactive upgrade
/upgrade
```

```bash
# Skip confirmations for safe updates (advanced)
/upgrade force
```

--------------------------------

### Resource Folder Structure

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

Illustrates a recommended directory structure for organizing various types of reference materials within the Resources folder.

```markdown
03_Resources/
├── Articles/          # Saved web content
├── Books/            # Book notes and summaries
├── Concepts/         # Evergreen idea notes
├── People/           # Notable people and thinkers
├── Tools/            # Software, methods, frameworks
├── Quotes/           # Memorable quotes
├── Examples/         # Case studies, references
└── Learning/         # Course notes, tutorials
```

--------------------------------

### Upgrade Claudesidian

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Command to get new features and updates for Claudesidian. It intelligently merges new features while preserving personal customizations.

```bash
/upgrade
```

--------------------------------

### Define Custom Agent Instructions

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/README.md

Save agent instructions as markdown files. This format includes the agent's name, role, core behaviors, workflow steps, and constraints.

```markdown
# Agent: [Name]

You are a [role description].

## Core Behaviors
- Behavior 1
- Behavior 2

## Workflow
1. Step 1
2. Step 2

## Constraints
- Don't do X
- Always do Y
```

--------------------------------

### Download and Organize Attachments

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Downloads files from URLs, validates schemes, analyzes content, renames files descriptively, organizes them, updates an index, and commits changes.

```bash
# Trigger (natural language):
"Download this PDF to my vault: https://example.com/report.pdf"
"Save these images: https://site.com/chart.png https://site.com/diagram.png"
```

```bash
# Internal implementation:
# 1. Validate URL scheme
if [[ ! "$url" =~ ^https?:// ]]; then
  echo "Error: Only HTTP/HTTPS URLs are allowed"
  exit 1
fi

# 2. Download with sanitized filename and timeout
filename=$(basename "$url" | sed 's/[^a-zA-Z0-9._-]/_/g')
curl --max-time 30 -L "$url" -o "05_Attachments/$filename"

# 3. Analyze and rename (Gemini Vision for images)
# mcp__gemini-vision__suggest_image_filename called internally

# 4. Move to organized folder
mv "05_Attachments/$filename" "05_Attachments/Organized/Q3-Revenue-Chart-June2025.png"

# 5. Commit
git add -A && git commit -m "Download and organize attachments from URLs"

# Supports: .png .jpg .jpeg .gif .webp .pdf .doc .docx .txt .md .csv .xlsx
# Max recommended filename: 60 chars
```

--------------------------------

### Archive Project Prompt

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

Use this prompt to initiate the archiving process for a project. It includes steps for creating a summary, extracting insights, and moving the project.

```Claude Prompt
Help me archive [project name].
Create a completion summary.
Extract reusable insights to Resources.
Move everything to Archive.
```

--------------------------------

### Develop an Argument with Evidence and Counterarguments

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Formulate an argument by searching your notes for supporting evidence and identifying potential counterarguments that need to be addressed.

```plaintext
I'm trying to argue that [thesis].
Search my notes for supporting evidence.
What counterarguments should I address?
```

--------------------------------

### Create Project Retrospective

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Generate a retrospective for a completed project, covering accomplishments, key learnings, and suggestions for future improvements.

```plaintext
[Project] is now complete.
Review all notes and create a retrospective covering:
- What was accomplished
- Key learnings
- What to do differently next time
```

--------------------------------

### Release Commit and Tagging

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CONTRIBUTING.md

Commands for committing a release version and tagging it using Git.

```git
git commit -m "chore: release v0.2.0"
```

```git
git tag v0.2.0
```

--------------------------------

### Claude Code Workflow: Daily Progress Logging

Source: https://github.com/heyitsnoah/claudesidian/blob/main/01_Projects/README.md

Use this prompt to create a daily progress note for a project. Include accomplishments and any questions that arose.

```text
Create a progress note for today in [project]/Daily_Progress.
Here's what I accomplished: [summary]
Questions that came up: [list]
```

--------------------------------

### Project Structure Template

Source: https://github.com/heyitsnoah/claudesidian/blob/main/01_Projects/README.md

Standard folder structure for new projects. Ensures consistency for Claude Code workflows.

```bash
Project_Name/
├── README.md           # Project overview and status
├── Research/          # Background materials
├── Daily_Progress/    # Log of work sessions
├── Drafts/           # Work in progress
├── Resources/        # Supporting documents
└── Output/          # Final deliverables
```

--------------------------------

### Contribute to Claudesidian

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Steps for contributing to the Claudesidian project, including forking, creating branches, making changes, testing, committing, pushing, and opening a Pull Request.

```bash
# Fork the repository on GitHub
# Create a feature branch (git checkout -b feature/amazing-feature)
# Make your changes
# Test your changes to ensure everything works
# Commit your changes (git commit -m 'Add amazing feature')
# Push to the branch (git push origin feature/amazing-feature)
# Open a Pull Request with a clear description of what you've done
```

--------------------------------

### AI Assistant Command Restrictions

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CLAUDE-BOOTSTRAP.md

Illustrates the difference between allowed simple commands and forbidden complex or filtered commands for AI assistants.

```bash
ls -1
```

```bash
ls | grep pattern
```

```bash
find . -name "*.png"
```

--------------------------------

### Changelog Entry Format

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CONTRIBUTING.md

Markdown format for adding changes to the CHANGELOG.md file under the 'Unreleased' section.

```markdown
## [Unreleased]

### Added

- Your new feature here

### Fixed

- Your bug fix here
```

--------------------------------

### Set Gemini API Key

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Configure your Google Gemini API key by setting the GEMINI_API_KEY environment variable. This enables direct image analysis and PDF text extraction within Claude Code.

```bash
export GEMINI_API_KEY="your-key-here"
```

--------------------------------

### Explore New Topic and Identify Research Needs

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Initiate learning about a new topic by first searching your vault for existing knowledge and then identifying areas requiring further research.

```plaintext
I want to learn about [topic].
Start by searching my vault for any existing knowledge.
Then help me identify what I need to research.
```

--------------------------------

### Claude Code Prompts for Template Usage

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/README.md

These prompts help manage and create notes using templates. The first shows available templates, and the second creates a new note of a specified type.

```plaintext
Show me available templates in 06_Metadata/Templates.
Create a new [type] note using the appropriate template.
```

--------------------------------

### Pattern Recognition Prompt

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

Analyze project completion rates and identify factors correlating with success or failure using this prompt.

```Claude Prompt
Analyze my project completion rate.
What factors correlate with success?
What patterns predict failure?
```

--------------------------------

### Pre-configured Commands for Claude Code

Source: https://github.com/heyitsnoah/claudesidian/blob/main/README.md

Execute these commands within Claude Code to quickly access specific AI-assisted workflows like collaborative exploration, daily reviews, or research assistance.

```bash
/thinking-partner   # For collaborative exploration
```

```bash
/daily-review       # For end-of-day reflection
```

```bash
/research-assistant # For deep dives into topics
```

--------------------------------

### Claude Code Workflow: Building Knowledge

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt template for using Claude to audit existing resources and identify knowledge gaps on a specific topic.

```plaintext
I'm researching [topic].
What do I already have in Resources?
What gaps exist in my knowledge?
```

--------------------------------

### Shell Script for Version Check and Backup

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

This script checks the current package version against the latest available, backs up project files, and fetches upstream changes. It's useful for managing project updates and ensuring data safety before modifications.

```bash
CURRENT=$(grep '"version"' package.json | head -1 | cut -d'"' -f4)
LATEST=$(curl -s https://raw.githubusercontent.com/heyitsnoah/claudesidian/main/package.json \
  | grep '"version"' | head -1 | cut -d'"' -f4)

# Backup before any changes:
BACKUP_DIR=".backup/upgrade-$(date +%Y-%m-%d-%H%M%S)"
mkdir -p "$BACKUP_DIR"
cp -r .agents .claude .pi .scripts package.json "$BACKUP_DIR/"

# Fetch upstream silently:
git clone --depth=1 --branch=main \
  https://github.com/heyitsnoah/claudesidian.git \
  .tmp/claudesidian-upgrade

# For each changed file, interactive prompt:
# File: .agents/skills/thinking-partner/SKILL.md has updates.
# 1. Apply update (take upstream)
# 2. Keep your version
# 3. View full diff
# 4. AI-merge

# Symlink hygiene after skill updates:
for name in $(ls .agents/skills); do
  for agent in claude pi;
    link=".${agent}/skills/${name}"
    target="../../.agents/skills/${name}"
    if [ -L "$link" ]; then
      current="$(readlink "$link")"
      [ "$current" != "$target" ] && rm "$link" && ln -s "$target" "$link"
    elif [ ! -e "$link" ]; then
      ln -s "$target" "$link"
    fi
  done
done

# Rollback if needed:
cp -r .backup/upgrade-<timestamp>/.agents .
cp -r .backup/upgrade-<timestamp>/.claude .
cp .backup/upgrade-<timestamp>/package.json .

# NEVER touched during upgrade:
# 00_Inbox/ 01_Projects/ 02_Areas/ 03_Resources/ 04_Archive/
# 05_Attachments/ 06_Metadata/ CLAUDE.md .obsidian/ .mcp.json
```

--------------------------------

### Claude Code Workflow: Project Completion and Retrospective

Source: https://github.com/heyitsnoah/claudesidian/blob/main/01_Projects/README.md

Use this prompt when a project is finished. It instructs Claude Code to create a retrospective covering objectives vs. outcomes, learnings, and future improvements, then archive the project.

```text
Project [name] is complete.
Create a retrospective covering:
- Objectives vs outcomes
- Key learnings
- What to do differently next time
Then help me archive it properly.
```

--------------------------------

### Create Outline for Deliverable

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Transition from research to writing by asking Claude Code to generate an outline for a specific deliverable, based on prior research in a project.

```plaintext
I'm ready to move from thinking to writing mode.
Based on our research in [project], 
help me create an outline for [deliverable].
```

--------------------------------

### Resurrect Project Prompt

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

This prompt helps in reviving an archived project by inquiring about its status and necessary updates.

```Claude Prompt
I want to revive [archived project].
What was the status when archived?
What would need updating?
```

--------------------------------

### Claude Code Workflow: Project Status Review

Source: https://github.com/heyitsnoah/claudesidian/blob/main/01_Projects/README.md

Prompt Claude Code to review all notes within a project folder and summarize the current status, key insights, and remaining tasks.

```text
Review all notes in [project folder].
What's the current status?
What are the key insights so far?
What's left to complete?
```

--------------------------------

### Linking Attachments in Markdown

Source: https://github.com/heyitsnoah/claudesidian/blob/main/05_Attachments/README.md

Demonstrates how to embed images and link to PDFs within markdown notes. Supports direct embedding, linking, and adding descriptions to images.

```markdown
# Embedding images
![[05_Attachments/Organized/diagram.png]]

# Linking PDFs
[[05_Attachments/Organized/document.pdf]]

# With descriptions
![[05_Attachments/Organized/chart.png|Sales Chart Q1]]
```

--------------------------------

### Claude Code Workflow: Creating Synthesis

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt template for using Claude to synthesize key insights from a collection of resources on a given topic.

```plaintext
Review all notes about [topic] in Resources.
Create a synthesis document of key insights.
```

--------------------------------

### Weekly Synthesis Skill for Aggregating Notes

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Aggregates notes created or modified in the past week to identify recurring themes, energy patterns, and cross-project connections. Creates a structured synthesis note.

```markdown
# Trigger phrases:
"Weekly review"
"Week-in-review"
"Weekly synthesis"

# Output — creates a note like:
# 06_Metadata/Weekly Synthesis - Week of 2025-06-01.md

# Weekly Synthesis - Week of 2025-06-01

## Week at a Glance
- Notes created: 14
- Projects active: Book Draft, SaaS App
- Major accomplishments: Chapter 2 outline, pricing framework

## Key Themes

### Theme 1: Pricing Strategy
- Where it appeared: SaaS App, 03_Resources/Business Models
- Why it matters: Core blocker for launch
- Next actions: Customer interviews before final decision

## Major Insights
1. Freemium requires genuine free-tier value, not just a trial
2. Chapter structure mirrors the research arc — unexpected

## Connections Made
- [[Pricing Research]] ←→ [[Chapter 2 Outline]]: Both hinge on perceived value

## Next Week's Intentions
1. Customer interview synthesis
2. Chapter 2 first draft
3. Competitor pricing deep-dive

```

--------------------------------

### Project Template for Obsidian

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

A template for project notes in Obsidian. It includes metadata fields for title, type, status, deadline, stakeholders, tags, and priority, along with sections for objective, milestones, resources, and a log.

```markdown
---
title: [Project Name]
type: project
status: in-progress
deadline: YYYY-MM-DD
stakeholders: ['Person 1', 'Team 2']
tags: [project]
priority: high
---

# [Project Name]

## Objective
One sentence: what does success look like?

## Key Milestones
- [ ] Milestone 1 — YYYY-MM-DD
- [ ] Milestone 2 — YYYY-MM-DD

## Resources
- [[Related Note 1]]
- [[Related Note 2]]

## Log
<!-- Running notes, updated frequently -->
```

--------------------------------

### Claudesidian File Naming Conventions

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

The kit enforces specific file naming conventions for daily notes, meeting notes, ideas, and resources to maintain consistency within the vault.

```plaintext
Daily notes:    YYYY-MM-DD - Topic
Meeting notes:  Meeting - [Topic] - YYYY-MM-DD
Ideas:          Idea - [Brief Description]
Resources:      Resource - [Topic] - [Source]
```

--------------------------------

### Claude Code Prompt: Learning Path

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt for Claude to generate a personalized learning path based on existing resources about a specific topic.

```plaintext
Based on my resources about [topic],
what should I learn next?
Create a learning path.
```

--------------------------------

### Reference Custom Agent in Claude Code

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/README.md

Use this prompt to instruct Claude Code to use a custom agent's instructions from a specified markdown file for a given task.

```plaintext
Use the instructions in 06_Metadata/Agents/[agent].md
and help me with [task].
```

--------------------------------

### Attachment Management Helper Scripts

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CLAUDE-BOOTSTRAP.md

A set of pnpm commands to help manage attachments within the Obsidian vault, including listing, counting, and finding orphaned files.

```bash
pnpm attachments:list
```

```bash
pnpm attachments:organized
```

```bash
pnpm attachments:orphans
```

```bash
pnpm attachments:update-links
```

--------------------------------

### Git Ignore Suggestions for Attachments

Source: https://github.com/heyitsnoah/claudesidian/blob/main/05_Attachments/README.md

Provides a list of file types and patterns to ignore in Git to prevent large or unnecessary files from being tracked. Includes common video formats, archives, and system files.

```gitignore
*.mp4
*.mov
*.zip
.DS_Store
files_over_10mb/
```

--------------------------------

### Add Frontmatter to Notes

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Automatically adds frontmatter to notes based on content. Useful for organizing and categorizing notes, especially meeting notes.

```shell
# Add frontmatter to all notes in 01_Projects/Book Draft/
# Fix the metadata on my meeting notes
# Add properties to [file]
```

--------------------------------

### Weekly Review of Notes

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Generate a summary of main themes and inter-project connections from all notes created within the current week.

```plaintext
Look at all notes created this week.
What are the main themes? 
What connections exist between different projects?
```

--------------------------------

### Upgrade Claude Obsidian

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Pulls the latest version of Claude Obsidian from GitHub, reviews system file changes, and applies updates after creating a backup.

```bash
# Trigger:
"Upgrade claudesidian"
"Pull in upstream changes"
```

--------------------------------

### Add Frontmatter Skill for Obsidian Notes

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Analyzes Obsidian notes (single file or entire folder) and adds or repairs YAML frontmatter with appropriate properties based on note type. Preserves existing valid properties and fixes deprecated formats.

--------------------------------

### Pragmatic Code Review

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Performs interactive code reviews focusing on YAGNI/KISS principles. Supports different review depths and CI integration.

```bash
# Interactive review of uncommitted changes (default)
# Trigger: "Review my code changes" or explicitly:
# /pragmatic-review

# Review all changes on current branch vs main
# /pragmatic-review --auto

# 6-pass deep review for security-critical changes
# /pragmatic-review --deep

# CI mode for GitHub Actions (no prompts, outputs markdown)
# /pragmatic-review --ci
```

```text
# Example issue output:
═══════════════════════════════════════
Issue 1 of 3
═══════════════════════════════════════
📁 File: src/auth/handler.ts
📍 Lines: 45-62
🏷️  Type: KISS
🎯 Severity: High

CURRENT CODE:
try {
  await createSession({ userId, cwd })
} catch (error) {
  console.error('Error: Not in a valid session context')
  process.exit(1)
}

ISSUE: Catch-Log-Exit anti-pattern — replaces the actual error with a guess.

WHY THIS MATTERS: The real error message is lost; debugging requires reproducing
the exact failure condition.

SUGGESTED SIMPLIFICATION:
await createSession({ userId, cwd })
// Let it throw — the stack trace is your friend

What would you like to do?
1. ✅ Accept   2. ❌ Skip   3. 💬 Discuss   4. 👀 Context   5. ⏹️ Stop
```

--------------------------------

### Daily Note Template for Obsidian

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

A template for daily notes in Obsidian using the Templater plugin. It includes sections for capture, questions, insights, connections, and follow-up tasks, with dynamic date insertion.

```markdown
<!-- Daily Note Template: 06_Metadata/Templates/Daily Note Template.md -->
<!-- Create with {{date:YYYY-MM-DD}} in Obsidian's Templater plugin -->

# {{date:YYYY-MM-DD}}

## Capture
<!-- Quick thoughts, links, ideas throughout the day -->
-

## Questions
<!-- What am I curious about today? -->
-

## Insights
<!-- What did I learn or realize? -->
-

## Connections
<!-- Links to other notes or ideas -->
-

## For Tomorrow
<!-- What needs follow-up? -->
-

---
*End of day: Ask Claude Code to review and find connections*
```

--------------------------------

### Create New Inbox Note with Claude

Source: https://github.com/heyitsnoah/claudesidian/blob/main/00_Inbox/README.md

Use this command to quickly create a new note within the 00_Inbox folder, specifying the title and initial content.

```Claude Command
Create a new note in 00_Inbox called [title] 
with these thoughts: [content]
```

--------------------------------

### Inbox Processor Skill for Organizing Files

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Reviews files in `00_Inbox/`, classifies them by PARA destination, identifies combinable notes, and presents a structured action plan. Preserves legitimate inbox items.

```markdown
# Trigger phrases:
"Process my inbox"
"Clear my inbox"
"Sort my captures"

# Output for each file:
File: startup-idea-2025-06-01.md
Type: project seed
Destination: 01_Projects/New SaaS Feature/
Reason: Time-bound, has a specific outcome in mind
Related to: [[SaaS App]] in 01_Projects

File: article-link-ux-research.md
Type: reference material
Destination: 03_Resources/UX Research/
Reason: Topic of ongoing interest, no active project tie

File: random-thought-metaphor.md
Type: transient capture
Destination: DELETE
Reason: No actionable content; already captured the core idea in [[Writing Style Notes]]

# Summary action plan:
Items to move:    8
Items to combine: 2  (merge daily captures from Mon–Wed into one note)
Items to delete:  3
Needs more context: 1

```

--------------------------------

### Web Content Scraping with Firecrawl

Source: https://github.com/heyitsnoah/claudesidian/blob/main/CLAUDE-BOOTSTRAP.md

Commands to scrape single or multiple URLs using Firecrawl, saving content to the inbox with frontmatter.

```bash
pnpm firecrawl:scrape <url> <output>
```

```bash
pnpm firecrawl:batch <url1> <url2>
```

--------------------------------

### Claude Code Workflow: Setting Goals

Source: https://github.com/heyitsnoah/claudesidian/blob/main/02_Areas/README.md

Prompts to assist in setting quarterly goals for a specific Area, prioritizing based on recent activity.

```text
Help me set quarterly goals for [area].
Based on recent activity, what should I prioritize?
```

--------------------------------

### Develop a Rough Idea

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Refine a nascent idea by searching your vault for related concepts and developing it into a more concrete form.

```plaintext
I have this rough idea: [idea]
Search for related concepts in my vault.
Help me develop this into something more concrete.
```

--------------------------------

### Year in Review Prompt

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

Use this prompt to review archived projects from a specific year, helping to identify accomplishments and patterns.

```Claude Prompt
Review all archived projects from [year].
What patterns do you see?
What did I accomplish?
```

--------------------------------

### Claude Code Workflow: Making Connections

Source: https://github.com/heyitsnoah/claudesidian/blob/main/03_Resources/README.md

A prompt template for using Claude to find and analyze relationships between different resources related to a specific concept.

```plaintext
Find all resources related to [concept].
How do different sources approach this?
What patterns emerge?
```

--------------------------------

### Knowledge Mining Prompt

Source: https://github.com/heyitsnoah/claudesidian/blob/main/04_Archive/README.md

This prompt facilitates searching the archive for specific concepts to understand the evolution of your thinking.

```Claude Prompt
Search the archive for any mentions of [concept].
How has my thinking evolved?
```

--------------------------------

### Daily Review Skill for End-of-Day Reflection

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

Automates end-of-day reflections by scanning notes modified today, assessing progress, capturing insights, and drafting priorities. Creates or updates a structured daily note.

```markdown
# Trigger phrases:
"Wrap up my day"
"Daily review"
"EOD note"

# Output — creates/updates a note like:
# 00_Inbox/2025-06-01 Daily Review.md

---
title: Daily Review - 2025-06-01
date: 2025-06-01
type: daily-note
tags: [daily]
---

# Daily Review - 2025-06-01

## Accomplished
- ✓ Finished pricing research notes
- ✓ Drafted chapter 2 outline

## Progress Made
- Book Draft: Chapter structure finalized
- SaaS App: Pricing tiers defined

## Insights
- Freemium only works if free tier has real value

## Blocked/Stuck
- Need customer interview data before committing to pricing

## Discovered Questions
- What do competitors charge for similar usage limits?

## Tomorrow's Focus
1. Schedule 3 customer interviews
2. Research competitor pricing pages
3. Write chapter 2 intro draft

## Open Loops
- [ ] Follow up with Alex re: design feedback
- [ ] Commit today's vault changes

```

--------------------------------

### Cross-Project Analysis

Source: https://github.com/heyitsnoah/claudesidian/blob/main/06_Metadata/Reference/Common Claude Code Prompts.md

Compare insights between two projects to identify common patterns and potential learning opportunities for each.

```plaintext
Compare insights from [Project A] and [Project B].
What patterns exist across both?
What could each learn from the other?
```

--------------------------------

### Common Claude Code Prompts

Source: https://context7.com/heyitsnoah/claudesidian/llms.txt

A collection of reusable prompt patterns for interacting with Claude Code within a vault. These prompts cover various modes like thinking, research, organization, writing, project management, and cross-project analysis.

```text
# --- THINKING MODE (exploration, not generation) ---
"I'm in thinking mode, not writing mode.
Help me explore [topic] by asking questions and searching for relevant notes."

# --- RESEARCH & SYNTHESIS ---
"Search my vault for anything related to [topic].
What patterns or connections do you see?"

"Review all notes in [project folder].
Create a synthesis of the key themes, insights, and open questions."

# --- ORGANIZATION ---
"Review items in 00_Inbox.
Suggest where each should be moved based on PARA method.
Which items could be combined or linked?"

"Find notes that aren't linked to any other notes. Suggest potential connections."

# --- WRITING MODE (after research) ---
"I'm ready to move from thinking to writing mode.
Based on our research in [project], help me create an outline for [deliverable]."

"Review [document]. Don't rewrite it — give me specific feedback on:
- Structure and flow
- Gaps in logic or evidence
- Areas that need clarification"

# --- PROJECT MANAGEMENT ---
"Review the project in [folder].
What's the current status? What are the next actions needed?"

"[Project] is now complete. Create a retrospective covering:
- What was accomplished
- Key learnings
- What to do differently next time"

# --- CROSS-PROJECT ANALYSIS ---
"Compare insights from [Project A] and [Project B].
What patterns exist across both? What could each learn from the other?"
```