75 specialist agents, 78 skills, plus commands, hooks, and rules for Claude Code, Cursor, Codex, and Cowork.
I call it The Hive. Your coding assistant stops being one guy guessing and starts being a whole crew that already knows the job.
Want to know what will actually drive more revenue? OSPRY is the insight engine built for exactly that.
Your AI assistant is smart and has no memory. Every task starts the same way. You explain the stack. You repeat your standards. You name the tools you like. You remind it to check security, then you hope it did. Ten prompts later you are still typing the context you typed yesterday.
That tax never goes away on its own. You either pay it forever or you build the context once and make it permanent. The Hive is that context, built once and wired into four coding tools so it follows you around.
The point is not more AI output. Anybody can generate more code. The point is fewer wrong turns, fewer skipped checks, and work you can grade against something you wrote down.
get-started knowledge + the-beekeeper SHIP GATE
-stinger -> library -> routes work to -> security ->
(bootstrap) -stingers the right Bees quality ->
(build memory) | repo-health
| |
the-smoker you approve
drives a PRD to done the commit
Two orchestrators run the show. the-beekeeper routes a single task to the right specialists. the-smoker takes a whole PRD and drives it to a shippable PR. Everything either of them touches has to pass the same gate before it commits.
| Step | You run | What happens |
|---|---|---|
| 1. Set up the repo | get-started-stinger |
Inspects what exists, preserves it, lays down Library Schema v2, writes the README, gives you a setup report |
| 2. Build the memory | knowledge-stinger, then library-stinger |
Knowledge docs capture domain truth; PRDs turn ideas into goals, non-goals, and acceptance criteria in library/requirements/ |
| 3. Route a task | /the-beekeeper |
Picks the right Bees, arms each with its Stinger, runs them in parallel or sequence, verifies the output |
| 4. Ship a feature | /the-smoker on @library/requirements/backlog/prd-XXX |
Recon, execution ledger, delegates to workers, drives to a shippable PR |
| 5. Pass the gate | automatic close-out | security -> quality -> repo-health, reports written to library/, you approve the commit |
Open the repo you want to fix and give your assistant this:
Use get-started-stinger to set up this repository with the Library Schema v2 structure.
Inspect what already exists, preserve it, create only what is missing,
and give me the final setup report.
Read the report before you accept anything. It lists what got built and what still needs a human to decide.
After that, four folders do the heavy lifting:
| Folder | Holds | Who writes it |
|---|---|---|
library/knowledge/ |
Durable facts and domain truth | knowledge-stinger |
library/requirements/ |
Planned work (PRDs) | library-stinger |
library/issues/ |
Bugs and incidents (IRDs) | agents + you |
library/notes/ |
Scratch notes | humans only, read-only to agents |
Your agent reads those folders the way a new teammate reads a wiki, except it actually does.
Read the full getting started guide.
Every piece has one job. That is the whole design.
| Piece | Plain English | What it does |
|---|---|---|
| Bee | A specialist agent | Owns one domain and makes the calls in it |
| Stinger | The Bee's skill | The playbook, examples, templates, and research it reads first |
| Beekeeper | The router | Picks the right Bee and hands it the matching Stinger |
| Smoker | The closer | Drives a PRD through build, security, quality, and shipping |
| Rule | Always on | Boundaries every worker stays inside |
| Hook | The enforcer | Checks real actions before or after a tool runs |
The one rule that makes it work: every Bee is paired with exactly one Stinger. A Bee without its Stinger is a smart agent with amnesia, so a Bee dispatched without loading its skill is a failed dispatch and it starts over.
Three skills break that rule on purpose because they run the show instead of doing the work: beekeeper-suit routes, queen-bee-stinger forges new components, and get-started-stinger sets up repos. The full roster of all 75 pairs lives in the Asset Catalog.
This is my favorite part and the part most AI setups skip.
Before any code gets committed it runs security-stinger first, then quality-stinger, then github-repo-health-stinger. Each pass writes a real report into library/. Anything rated medium or worse gets fixed, then the whole thing gets re-checked, not spot-checked. You review the reports and you approve the commit. Not the agent. You.
Security runs before quality for a reason that took me a while to appreciate. A security fix changes the code, and changed code invalidates whatever quality just signed off on. Run them backwards and your QA report is a lie.
Claude Code. Everything lives in .claude/. Point it at the folder and go:
claude --plugin-dir .claudeThen use /the-beekeeper to route a task or /the-smoker to run the whole delivery line.
Cursor. Open the repo. That is it. The .cursor/ tree has 75 agents, 78 skills, 2 commands, 4 MDC rules, and hooks already in place.
Codex. A plain clone works with no install. .agents/skills/ has all 80 repo skills, .codex/agents/ has 75 native TOML agents, and the config and hooks are wired. Call the workflows directly:
$the-beekeeper route this task to the right specialists
$the-smoker execute these PRDs through verified completion
There is also an installable plugin at .codex/plugins/vibe-coding-tools/ for Codex CLI and the ChatGPT desktop app. The project adapter stays separate because installing a plugin does not install repo agent TOMLs.
Claude Cowork. Open Customize in the sidebar, go to Plugins, upload learn/packages/vibe-coding-tools-claude-code-1.0.0.zip. Same package format as Claude Code.
Prebuilt archives and SHA-256 checksums for all four are in learn/packages/.
Code tells you what the machine does right now. It does not tell you why anybody chose that, what it should do next, or what has to be true before you call it finished. That stuff lives in someone's head until they leave, and then it does not live anywhere.
So this system treats docs as working memory instead of homework. Knowledge files hold the domain truth that would otherwise die in a Slack thread. ADRs hold the reasoning behind expensive decisions so nobody relitigates them in six months. PRDs turn a vague idea into goals, non-goals, and acceptance criteria an agent can execute against. IRDs give a bug a traceable problem, cause, fix, and proof.
An agent with no context guesses well and confidently. An agent with your project knowledge and a written definition of done works like somebody who already had the meeting.
- Agents and Bees
- Skills and Stingers
- Commands
- Product Requirements Documents
- Library Structure
- Hooks
- Rules
- Model Selection
- Security and Secrets
- Harness Compatibility
- Troubleshooting
The .claude/ tree is the source of truth. Everything else is generated from it. Change an agent, skill, command, or hook, then run:
python learn/scripts/generate-harnesses.pyThat rebuilds the Cursor mirror, the Codex agents, the repo skills, the plugin skills, and the catalog. Do not hand-edit the generated trees. You will lose the change on the next build and spend an hour wondering why.
Want to add your own Bee and Stinger? queen-bee-stinger runs the seven stage forge: Topic, Research, Distillation, References, Guides, Skill File, Register. It does real research and archives the sources, so the skill you get is grounded instead of guessed. That is the same pipeline every skill in here went through.
Vibe Coding Tools is source-available software created by Mario Aldayuz and Legion Code Inc.
Use it personally, at work, in your business, and as a tool inside paid services. Do not sell the Work itself, do not strip the attribution, do not pass it off as yours. Full terms in LICENSE.md.
Built for vibe coders. Go ship something.
We are Legion. Vibe with Legion.