Repository navigation
Home
This wiki explains how this configuration is built and why each piece sits where it sits. The repository README tells you how to install it; here we open the hood.
A complete Claude Code setup, ready to drop into ~/.claude/: global rules, 29 skills, a memory scaffold and a plugin declaration. It is deliberately generic, with no personal data, no secrets and no machine-specific paths, so that anyone can install it and then make it their own.
It targets one profile: someone doing Dev and Ops work who wants to understand, not just to receive answers. That single intent explains most of the choices documented here.
- Architecture: the four channels Claude Code gives you (CLAUDE.md, skills, settings, plugin) and what belongs in each
- The skills: the 29 skills, why they split into two families, and how they trigger
- Memory: how persistent memory is organised, and the rule that keeps it from turning into a dumping ground
- Installation and maintenance: what install.sh does, how to check it worked, and what to redo after an upstream change
The same approach was applied to Mistral Vibe, in Your-Mistral-DevOps. Comparing the two wikis is instructive: the same intent lands very differently depending on what the host agent offers. Claude Code has skills that trigger on their own, plugins and hooks; Vibe has none of that and everything has to be forced through a custom system prompt.
Your Claude DevOps