Adrien Lipari's personal Claude Code plugin. Skills, hooks, and a single command that encode the conventions of a one-person software studio operated entirely from a phone via Telegram.
This repo is published as documentation, not a product. You can install it as a Claude Code plugin, but most of its content is opinionated to a specific machine, vault, and workflow. The interesting parts are the patterns, not the configuration.
Plugin marketplace entry:
synodic-studio/synodic-kit. MIT-licensed.
15 skills under skills/. A skill loads on demand when its description matches what Claude is doing. The set covers the things I actually do day to day:
- Apple platform work:
apple-platform-dev,swift-quality,apple-release,testflight-ship,debug-builds - Cobalt vault (my Obsidian setup):
cobalt-sync,cobalt-replies,cobalt-links - Tooling:
pocketbase,openscad(scripted 3D modeling),beads-init,develop-preview,self-healing-errors,mochi(spaced-repetition flashcards),macro-kiwi(image generation, editing, vision, and OpenAI access)
Each skill is a single SKILL.md plus references. They are not generic tutorials. They contain the specific commands, anti-patterns, and recovery procedures I have learned the hard way.
9 lifecycle hooks under hooks/. The big one is pre_tool_use.py, which inspects every tool call before it runs. It blocks force-pushes to any branch, intercepts dangerous compound shell commands, and refuses to silently bypass test or signing steps. The others handle session start and stop, post-tool-use formatting, prompt submission, and pre-compaction snapshots.
One command: /open. Almost every other workflow lives in a skill instead, so commands are sparse on purpose.
No bundled MCP servers. What used to be the macro-kiwi MCP server is now the macro-kiwi skill: a self-contained CLI that runs through uv, no server to keep alive.
Add as a Claude Code plugin from the synodic-studio marketplace. The plugin manifest lives at .claude-plugin/plugin.json.
Two reasons. First, the patterns translate. The lifecycle-hook safety layer, the skill structure, the headless-first stance, the way I bind together vault and code workflows. Anyone building a similar setup can read the code instead of reinventing it.
Second, I write about the system on synodic.co, and a public repo is more useful than screenshots. If you read a post about how I run Claude Code from a phone and want to see the actual hook code, here it is.
- synodic.co/synodic-kit: a written tour of what each piece does and why it exists
- synodic.co/patchbay: the Telegram bridge that drives Claude Code from a phone, which is what synodic-kit is paired with
- synodic.co/ai-tooling/: related notes on plugins, skills, and personal AI tooling