
Live product
snipvaultapp.vercel.app
My role
Product strategy · Design · Engineering
Why I built it
Developers repeatedly lose valuable code to browser tabs, chat histories, and disconnected note apps. I built SnipVault as a durable personal memory layer: save a snippet once, retrieve it by title, language, tag, or code content, then pipe the raw result directly into the next command.
It also captures terminal work sessions, making complex deployment and debugging work reviewable later without sending private command history to a third party.
Why it's next-generation
Local-first ownership
No account, cloud database, telemetry, or lock-in. Data stays in portable JSON files the developer controls.
AI-native engineering
The repository includes agent instructions, portable skills, a test-guardian subagent, and a hook that blocks AI access to private vault data.
Zero-runtime delivery
Self-contained binaries and one-line installers put the same tool on Windows, macOS, and Linux without a Python setup.
Composable workflow
Pipe-friendly output and per-project vaults make it useful inside existing shells, scripts, and automation.
$ snipvault search auth
7 jwt decode python api, auth
$ snipvault show 7 | clip
Single-file
local data ownership
Five core
commands to learn
Zero
runtime dependencies


