npx claudepluginhub devbrightraven/hiramekiObsidian vault knowledge management commands for Claude Code — daily rhythm, concept archaeology, thinking tools, and work logging
devBrightRavenObsidian vault knowledge management commands for Claude Code.
Hirameki is inspired by internetvin — specifically the workflow shown in this video by Greg Isenberg, CEO of Late Checkout and creator of Idea Browser:
How I Use Obsidian + Claude Code to Run My Life
The idea: your Obsidian vault is a goldmine of accumulated thinking. Hirameki gives Claude Code the commands to excavate, connect, and act on what's already there — rather than starting from scratch every time.
What is an Obsidian vault? Obsidian is a free note-taking app that stores everything as plain markdown files in a local folder — your "vault". No cloud lock-in, no proprietary format. Because it's just files, Claude Code can read and write directly to it.
# 1. Add the marketplace
claude /plugin marketplace add devBrightRaven/hirameki
# 2. Install the plugin
claude /plugin install hirameki@hirameki
Run /hirameki:__init once. It handles everything — vault detection, language, folder mapping, and copying reference docs into your vault.
Fastest path — open Claude Code from inside your vault:
cd /path/to/your/obsidian-vault
claude
/hirameki:__init
Vault is auto-detected. No path needed.
From anywhere else — run it wherever you are:
claude # anywhere
/hirameki:__init
__init reads Obsidian's app config to find your vaults automatically — no need to know the path. If you have multiple vaults, it shows a list to choose from.
Either way, the vault path is saved locally to ~/.claude/vault-local.md. After setup, every Hirameki command works no matter where you open Claude Code. If you sync ~/.claude/ across machines, vault-local.md should be gitignored — each machine runs /hirameki:__init once.
7 commands, grouped by when you reach for them.
/hirameki:catchup [days]
Use when: you're reopening the vault after time away and need to pick up the thread.
Progress catchup. Reads the last Wrap block from recent daily notes and all inbox items, then suggests 1–3 things to focus on today. Default: yesterday. Example: /hirameki:catchup 3 reviews the last 3 days.
/hirameki:wrap [description]
Use when: you're done for the day (or pausing a session) and want a record of what happened.
Progress snapshot. Scans session file activity, appends a timestamped block to today's daily note with: completed, in-progress, and next steps. Can run multiple times a day — each run appends a new block. Optional: describe the session focus to shape the summary.
/hirameki:pulse [week|patterns]
Use when: you want to know what's going on across your vault without diving in manually.
Three modes depending on what you need:
/hirameki:pulse — Immediate snapshot. Scans all content folders (depth 2) and the last 7 days of daily notes. Shows content topics per folder, recent file changes, and vault-wide counts. Good to run at session start.
/hirameki:pulse week — Weekly gap analysis. Compares what you said was a priority (from daily notes) against what you actually worked on (from file changes). Surfaces drift between intentions and effort. Requires at least 3 days of daily notes.
/hirameki:pulse patterns — Undercurrents and clusters. Surfaces recurring themes without dedicated articles (appears in 3+ files, no standalone write-up), and groups of notes converging on unnamed themes. Good for finding what's been quietly accumulating.
/hirameki:explore {input} [save]
Use when: you want to dig into a concept, find hidden connections, get a draft take in your voice, or pressure-test an argument.
One command that detects mode from the shape of your input:
| Input shape | Mode | What it does |
|---|---|---|
| Single concept | Arc | Tracks evolution of that concept across your vault — timeline from first mention to current state |
Two topics with and / 與 / と | Bridge | Finds hidden connections between the two — shared files, bridge notes, deep hypotheses |
Ends with ? | Ghost | Answers in your voice — extracts your existing stances and style, then drafts a response |
Starts with test: | Stress-test | Pressure-tests your arguments — finds contradictions, gaps, and unverified assumptions |
Development marketplace for Superpowers core skills library
Harness-native ECC skills, hooks, rules, MCP conventions, and operator workflows
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.