Blog: guides for developers
Practical guides for developers, starting with Claude Code plugins. 9 posts.
- Claude Code plugins explained: skills, commands, agents, hooks and MCP (29 September 2026): What a Claude Code plugin is, the five building blocks inside one, and how a plugin gets from a GitHub repo into your coding session.
- How to install, update and remove Claude Code plugins (29 September 2026): A practical guide to marketplaces, installing plugins in the terminal or VS Code, scopes, updates, sharing plugins with your team, and fixing common errors.
- superpowers: a brainstorm, plan, test-first workflow for Claude (29 September 2026): superpowers teaches Claude a disciplined engineering process: clarify the idea, plan, build test-first and verify before claiming done. Here is how it works and how to use it.
- frontend-design: distinctive UI instead of generic defaults (29 September 2026): frontend-design gives Claude design guidance so the interfaces it builds have a clear direction instead of looking templated. What it does and when to use it.
- context7: current library docs inside Claude (29 September 2026): context7 lets Claude look up current documentation for the libraries you use, so answers match your versions instead of old training data.
- code-review: automated pull request review (29 September 2026): code-review runs several review passes over a pull request and returns only the findings worth acting on. How it works and how to run it.
- code-simplifier: tidy code without changing behavior (29 September 2026): code-simplifier is an agent that cleans up recently changed code, improving naming and structure while keeping behavior identical.
- claude-mem: memory that carries across sessions (29 September 2026): claude-mem records what happens in your Claude Code sessions and brings the relevant history back later. How it captures memory and how to search it.
- context-mode: keep big outputs out of the context window (29 September 2026): context-mode runs large commands in a sandbox and returns only the relevant part, so long logs and test runs don’t fill up Claude’s context window.