I kept solving the same problems differently every session. So I built a system.
Six Claude Code plugins that turn ad-hoc prompting into structured, repeatable workflows. Planning, branding, design, development, content, and task management — each handled by a plugin that knows its job.
The problem with Claude Code sessions
Every session starts from scratch. You explain the same context, set up the same patterns, and hope you remember what worked last time. Plans live in your head. Quality depends on how much you feel like typing today.
Multi-file changes? Hope your agents don't overwrite each other. Verification? You read the diff and squint. Session handoffs? Copy-paste some notes and pray.
This isn't a tooling problem. It's a workflow problem. And workflows need structure.
Six plugins, each owns a domain
Use one, use all six, or build your own
How it works
Install the plugins
Clone the repo, point Claude Code at the plugins directory. Each plugin auto-registers its skills, commands, hooks, and agents.
Run a workflow
Slash commands invoke structured workflows. /plan:create breaks a task into waves. /dev:run decomposes and dispatches. /brand:create builds a brand from scratch.
Everything persists
Plans, decisions, brand guidelines, design tokens — all stored as YAML files that survive session boundaries. Next session picks up where you left off.
What you actually get
Verification, not vibes
Every task passes a verification gate before it's marked done. Implementing agents never grade their own work. A separate reviewer checks against the original spec.
Parallel agents, zero conflicts
File-ownership boundaries mean multiple agents work simultaneously without overwriting each other. The system assigns exclusive file access per agent.
Contradiction detection
herold compares Jira ticket descriptions against their comments and flags inconsistencies before you start coding the wrong thing.
Cross-session memory
State files, session handoffs, and context snapshots mean you don't start from zero every time. The compact gate protects context during long sessions.
110+ skills across six plugins
Framework knowledge, content strategy, SEO, copywriting, marketing psychology — patterns, anti-patterns, and real-world examples. Reference material that agents use during implementation.
Brand-to-code pipeline
From brand strategy through visual identity to design tokens to Tailwind config. Every step produces structured output the next step consumes.
Try it
It's open source. Clone it, install it, run /plan:create on something you're building. If it doesn't save you time in the first session, it's not for you.