Vibe Plugins.
A coordinated family of Claude Code plugins — installed independently, composed when present. Plan it, ship it, iterate it, document it, test it, secure it.
Fourteen plugins, one playbook.
Each ships on its own. Each composes with the others when they share a repo.
The thinking behind it.
Every Vibe plugin follows the same architectural playbook — an Apache-licensed spec that makes the claims checkable, not aspirational.
A plugin should be more useful on its tenth run than on its first — not because the user learned it, but because it learned the user.
The Self-Evolving Plugin Framework is three disciplines stacked on top of each other: self-repair, self-teach, self-evolve. A plugin that can fix itself when it breaks, teach itself what the user actually wanted, and rewrite its own guidance when the pattern repeats. Each discipline earns its rung on a five-level maturity ladder — sixteen named patterns across the climb, one Apache-licensed spec, and a scorecard so the claims are checkable, not aspirational.
Vibe Cartographer sits at Level 3.5 right now — the highest rung any public plugin has reached — and every new plugin we ship gets benchmarked against the same ladder. The framework isn't marketing. It's how we keep the work honest when nobody's watching.
From legitimate to sustainable.
A builder's doctrine for vibe-coded software that lasts. Five tenets — Legitimacy, Discipline, Quality, Trust, Coherence — for native builders shipping AI-built artifacts to real users.