handrovermeulen/obsidian-dashboard — explained in plain English
Analysis updated 2026-05-18
Build a single-screen daily dashboard inside Obsidian showing project status, tasks, and calendar.
Turn Pinterest or Dribbble style references into a design system Claude Code can build a plugin from.
Set up one-click launchers for the Claude Code skills you use most often.
| handrovermeulen/obsidian-dashboard | 1061700625/github_vps | berliwu/world-cup-2026-match-prediction-engine | |
|---|---|---|---|
| Stars | 38 | 38 | 37 |
| Language | Shell | Shell | Shell |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 3/5 | 2/5 | 3/5 |
| Audience | vibe coder | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Obsidian, a Claude Code setup, MCP connections to your tools, and going through multiple planning and design phases.
This repository is a written guide, not ready made software, that walks a reader through building their own personal command center dashboard inside Obsidian, using Claude Code to do most of the technical work. Obsidian is a note taking app built around local markdown files, and the guide shows how to turn it into a single screen that surfaces whatever matters most in someone's day, such as live project status, a task queue, a calendar, a news feed, and meeting notes. The suggested way to use the guide is to paste its entire contents into a Claude Code session and ask Claude to walk through it step by step, answering a few planning questions first and waiting for the reader's answers before touching anything technical. The guide is written so the reader does not need to understand the technical details themselves, since Claude is meant to handle the actual coding. The core idea behind the design is that Obsidian acts as a middle layer rather than pulling data live from other tools. A separate background Claude script queries various tools through MCP connections and writes plain JSON files into the Obsidian vault, and the dashboard plugin simply reads those files and displays them. The more of someone's daily information already flows into files inside their vault, the more useful this dashboard becomes. The guide is organized into phases. The first phase has the reader answer three planning questions: what they want to see every day, where each piece of that data currently lives, and which frequently used actions should become one click buttons. The second phase covers getting Claude accessible from inside Obsidian, either through a terminal plugin or a dedicated chat plugin called Claudian. Later phases cover building a visual moodboard from reference images, feeding that moodboard into Claude's design tooling to generate a matching design system, and then scaffolding an actual Obsidian plugin, described as being built with Preact, TypeScript, Tailwind CSS, esbuild, framer motion, and lucide react, bundled so it works without an internet connection. The README also includes a short recruitment note from the author about an AI agency they run, inviting readers who enjoy this kind of work to apply. No license is mentioned in the visible portion of the README, and the guide text is described as continuing beyond what is captured here.
A step-by-step guide to building a personal Obsidian dashboard plugin, powered by Claude Code, that reads status data written into your vault as JSON.
Mainly Shell. The stack also includes Obsidian, Claude Code, Preact.
No license information is provided in the visible portion of the README.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly vibe coder.
This repo across BitVibe Labs
Verify against the repo before relying on details.