English
Inspiration
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.
Install
# 1. Add the marketplace
claude /plugin marketplace add devBrightRaven/hirameki
# 2. Install the plugin
claude /plugin install hirameki@hirameki
Setup (one time)
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, __init writes a split configuration: your vault's folder structure goes into <vault>/AGENTS.md (agent-neutral — it travels with the vault and any AI agent can read it), and per-machine values (vault path, language) go into ~/.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.
Codex compatibility
Claude Code remains the command-native surface for Hirameki. The repository also includes a Codex adapter at codex/skills/hirameki/: one umbrella SKILL.md plus 20 same-name workflow references. Codex users keep the same Hirameki vocabulary (wrap, journal, handoff, mekiki, etc.) while avoiding 20 always-visible skill entries.
The Codex adapter prefers ~/.codex/hirameki-local.md for per-machine vault settings, with ~/.claude/vault-local.md as a migration fallback. Claude-specific features are adapted where possible: __init writes Codex-local config, and critique uses only the reviewers available from a Codex session.
Commands
20 commands, grouped by how you use them.
Orchestrators
Guided flows that bundle related primitives into a single interactive sequence. Each step shows a full draft — save, skip, or edit before moving on. The underlying primitives all work standalone.
/hirameki:triage
Use when: you're wrapping up a session and want to capture everything in one go.
End-of-session bundle. Walks through wrap → journal → handoff in sequence. Each step shows a full draft with save / skip / edit before the next begins. Shares a single session-state scan across all three sub-flows. Run once at session end. No arguments.
/hirameki:lens <concept>
Use when: you want to deeply understand how a concept lives in your vault — its history, your positions on it, how it connects to something else, and where the arguments might be weak.
Topic understanding flow. Four steps in sequence: arc → position extraction → bridge → challenge. Bridge auto-suggests a related topic from the arc step; you can accept or change it. Each step can be saved or skipped individually. Saves to {research}/lens/.
/hirameki:compose <topic>
Use when: you want to write something grounded in your vault, and want to validate the idea before fully committing.
Topic creation flow. Two steps: voice (writes a response in your style, drawing on your vault positions) → frame (runs the five-question validation test). Standalone — does not require running /hirameki:lens first. Each step can be saved or skipped. Saves to {research}/compose/.
/hirameki:mekiki <input>
Use when: you want to capture an external resource — a GitHub repo, a web article, or a piece of text — and integrate it into your vault.
External resource capture. Auto-detects input type:
