Guides
For people using Magus plugins.
Getting set up
- Installing Magus — install claudeup, add a marketplace, enable plugins
- Teams and profiles — share one setup through a committed manifest
- Advanced Usage — global and project-scoped installation, version pinning, plugin updates, and custom configuration
- How skills get found — why some skills Claude picks up on its own, why some you have to name, and why one can quietly stop firing
- Troubleshooting — what to check when a plugin does not load, a hook does not fire, or the marketplace goes missing
Doing the work
One guide per job. What you type, what it asks, which options change the outcome.
- Building a feature —
/dev:dev, its depth ladder, and presets - Fixing a bug —
/dev:fix, reproduced first and reviewed twice - Designing before you build —
/dev:architect, plan mode, and handing the design straight to the builder - Understanding code —
/dev:investigate, read-only - Documentation —
/dev:docand its four modes - Isolated worktrees —
/dev:worktree, with database branching
Bringing in other tools
- multimodel — a blind vote across models, or handing a whole task to one
- code-analysis — asking questions about code you didn't write
- bunjs — one command, and the eight skills behind it
Looking for what a specific plugin does? See the plugin catalog.