Consolidating Claude

I spent a few hours today consolidating my sprawling Claude Code files into a Claude Plugin which is published in a personal marketplace. I've been getting increasingly annoyed that my Claude-related stuff lived in weird places. My globally available agents were in their own repo, cloned into . My global slash commands, hooks and were in my dotfiles repo, symlinked from in the same way all my other dotfiles are. My css-expert skill was in yet another repo. And so on. Which felt messy af... particularly as I'm not using Claude Code for much more than just programming. I now have a single claude-marketplace repo which anyone can add with: I currently have two plugins available there, which can be installed with . Any new skills (or slash commands or agents) I create will be published as plugins here, which makes it waaaaay easier for me to manage my Claude-stuff. And also makes everything available to other people in a sane way. If you want my CSS expert skill, you can just install it. My Personal Plugin I resisted the urge to turn my existing commands & agents into a bunch of small specialised plugins because most of them are designed specifically for me – the only reason to publish them as a plugin is my own ease-of-management. So I've ended up with a personal plugin, which is essentially a replacement for the stuff that was in (or symlinked from) . Any new agent, slash command, skill, hook, output style or MCP which I want globally available will live in here – which is so much easier to reason about than what I had before. So long as I have installed, I have access to all that stuff. This plugin currently consists of five directories... 1. agents/ Most of these were written before I really understood how best to use agents. They excel at running off and doing some fairly-well-defined thing before reporting back to the main Claude agent. By far my most used agent (apart from ) is , because it prefers to audit and report. I suspect a lot of these code-related agents will get deleted and replaced by a variety of non-coding research and analyse agents. | Agent | Description | | ----------------------- | --------------------------------------------------------------- | | | Analyzes code for structural improvements and technical debt | | | Writing in Danny's conversational, substantive voice | | | Visual design and frontend development (React/Next.js/Tailwind) | | | Information verification using SIFT method | | | Security audit specialist (OWASP Top 10) | | | Technical documentation (READMEs, API docs) | | | User-facing documentation in plain language | 2. commands/ I mostly think of slash commands as bash scripts on crack. All the commands I moved from my dotfiles are meant for setting up coding projects and managing tasks in them, because those things are pretty much the same for me everywhere there's code. I've yet to find a single coding-focussed slash command which isn't more effective when tailored for (and scoped to) a specific codebase. | Command | Description | | -------------------------------- | ------------------------------------------------------- | | | Prime session with project context | | | Initialize AI assistant boilerplate files | | | Initialize task management system | | | Create new unprioritized task | | | Create task from GitHub issue | | | Renumber prioritized tasks | | | Update documentation based on recent changes | 3. hooks/ If you haven't got hooks pinging noisy OS notifications whenever Claude needs you, you're missing out. Or perhaps you haven't got the same ADHD as me. This is all I use hooks for. 4. output-styles/ Currently empty, but it's here with a in it because the more I use Claude Code for non-coding stuff the more interested I am in these. 5. skills/ Also empty. I'm excited about agent skills, but so far I've only used the two I've built and a few of Anthropic's. And the two I made belong in their own plugins (taskdn & css-expert). MCPs The only MCP I have globally is Context7, and I should probably find a way to have it only load in coding projects. What's left in dot claude? So if I've moved all this into plugin, what's left in my ? Answer: very little I care about, which is as it should be. Claude is free to write and overwrite whatever it wants in there now. The two files still under version control are and , and I made a bunch of tweaks to them today... Global CLAUDE Here's mine as of 2026-01-03 A few comments: - Claude has finally stopped telling me I'm absolutely right. This is probably down to Opus 4.5 but I'm leaving that line in there forever. - Claude still peppers my planning docs with "Estimate: 4-5 weeks" 🤷‍♂️. - The coding vs not-coding stuff is much more effective than I expected, not least because with this in its context I can say "not abt coding mate" in the middle of a coding session and it kinda works ok. Global settings.json This is basically a massive list of default-allow and default-deny permissions. Blacklisting dangerous operations is kinda mandatory, but I'm increasingly whitelisting certain tool calls globally in here - my general rule is: Read whatever but no writing/mutating anything without asking first That's all folks.