By mjrskiles
Domain-specific code auditors: Klaus (embedded), Librodotus (docs), Shawn (education)
Invoke Klaus for firmware quality audit (memory|timing|safety|style|full)
Invoke Librodotus for documentation quality audit (readme|code|architecture|freshness|full)
Invoke Shawn for educational review (onboarding|concepts|examples|depth|full)
Embedded firmware quality auditor. Invoke after major changes, before releases, or to audit codebase quality. A pedantic expert who demands best practices. Usage - specify audit type: memory, timing, safety, style, or full.
Documentation quality auditor. Invoke to audit docs, README, code comments, or overall documentation health. Values clarity, brevity, and unix-like usefulness. Usage - specify audit type: readme, code, architecture, freshness, or full.
Educational mentor who evaluates projects as learning resources. Asks "what makes this teachable?" Balances accessibility with appropriate challenge. Usage - specify review type: onboarding, concepts, examples, depth, or full.
A collection of Claude Code plugins for hacking, development workflows, and greenfield projects.
| Plugin | Description | Use Case |
|---|---|---|
| greenfield-mode | Prevent backwards-compatibility cruft | Prototype projects |
| primer | Context priming on session start | Any project |
| planning | ADRs, FDPs, Action Plans, Reports, Roadmap | Structured planning |
| expert-agents | Klaus, Librodotus, Shawn | Code audits |
# Add the vibe-hacker directory as a marketplace
/plugin marketplace add /path/to/vibe-hacker
# Install individual plugins
/plugin install greenfield-mode@vibe-hacker
/plugin install primer@vibe-hacker
/plugin install planning@vibe-hacker
/plugin install expert-agents@vibe-hacker
Prevents backwards-compatibility cruft in prototype projects.
Hooks:
Config: greenfield_mode, greenfield_strict, greenfield_patterns
Context priming - automatically load project files on session start.
Hooks:
Config: priming.files, priming.globs, priming.instructions
Structured planning documents with protected paths.
Features:
Hooks:
Config: planning, protected_paths
Domain-specific code auditors with unique personalities.
Commands:
/klaus - Embedded systems auditor/librodotus - Documentation quality auditor/shawn - Educational mentorConfig: None (stateless)
All plugins read from .claude/vibe-hacker.json:
{
"greenfield_mode": true,
"greenfield_strict": false,
"greenfield_patterns": ["deprecated", "legacy", "@deprecated"],
"priming": {
"files": ["README.md"],
"globs": ["docs/planning/action-plans/*.md"],
"instructions": "Focus on active work."
},
"planning": {
"version": "0.2.1",
"subdirs": {
"adr": "decisions",
"fdp": "designs",
"ap": "action-plans",
"report": "reports"
}
},
"protected_paths": {
"planning_root": "docs/planning",
"rules": [
{"pattern": "docs/planning/*/archive/**", "tier": "readonly"}
]
}
}
Each plugin reads only its relevant keys:
greenfield-mode reads: greenfield_mode, greenfield_strict, greenfield_patternsprimer reads: priming, greenfield_mode (for display)planning reads: planning, protected_pathsexpert-agents reads: nothing (stateless)vibe-hacker/
├── plugins/
│ ├── greenfield-mode/ # Cruft prevention
│ ├── primer/ # Context priming
│ ├── planning/ # Planning documents
│ └── expert-agents/ # Code auditors
├── docs/
│ └── planning/ # This project's planning docs
├── templates/
└── README.md
MIT
Michael Skiles ([email protected])
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub mjrskiles/vibe-hacker --plugin expert-agentsPrevent backwards-compatibility cruft in prototype projects
Context priming - load project files on session start
Structured planning documents (ADRs, FDPs, Action Plans) with protected paths
Helps Claude read a planning document and explore related files to get familiar with a topic. Asking Claude to prepare to discuss seems to work better than asking it to prepare to do specific work. This is followed by Plan, then Execute.
Interactive feature audit for vibe-coded projects. Finds dead code, unused features, and experiments through conversation with the developer.
Structured implementation planning, interactive annotation review, and autonomous plan execution
Planning mode guidelines and context injection
Autonomous Claude + Codex review loop. Plan a feature with adversarial pushback, or audit code, all in one window.
Opinionated workflow guides and best practices - the preacher's proven patterns for Claude Code projects