Public
code-review-kit
by community · 6 artifacts
Versioned AI capabilities your whole team can install.
Artifacts are the versioned units of AI agent configuration. Kits bundle them so your team installs everything with one command.
01
Six building blocks
Prompts, skills, rules, MCP servers, subagents and hooks — everything you standardize.
02
A real marketplace
Use community Kits as they are, or fork them into something yours.
03
Portable by design
The same Kit installs on every supported tool. No rewrites.
What is an AI Artifact?
An AI Artifact is a versioned, reusable unit of AI agent configuration. Every Artifact has an owner, a version history and a visibility scope, and any of them can be installed on its own or bundled into a Kit. There are six types.
01 / 06
Prompts
Reusable instructions your team has already proven work — system prompts, review prompts, refactor prompts. Versioned, so improving one improves it for everyone.
02 / 06
Skills
Packaged procedures an agent can invoke for repeatable work: run the migration checklist, write the changelog entry, prepare the release.
03 / 06
Rules
Conventions and constraints the agent must always follow — the content of files like CLAUDE.md, .cursorrules and AGENTS.md, kept in one place instead of in everyone's dotfiles.
04 / 06
MCP servers
Model Context Protocol servers that give an agent access to tools and data: your issue tracker, your database, your internal APIs.
05 / 06
Subagents
Specialized agents you delegate focused tasks to, each with its own instructions, tools and model — a reviewer, a test writer, a migration agent.
06 / 06
Hooks
Automations that fire around the agent's lifecycle: before a tool call, after an edit, on session start. Where policy becomes enforcement.
What is a Kit?
Bundle any combination of Artifacts into a Kit, then distribute it to a team or to the whole organization. One command installs everything, identically, on every machine.
Artifacts
Kit
frontend-kit
5 artifacts
How does an Artifact reach a developer's machine?
The path an Artifact takes is always the same, whether it's one rule or a full Kit.
- 01
Create
Write the hook, rule or skill once — the way your team wants it done.
- 02
Package
Bundle related Artifacts into a Kit and version it so changes are traceable.
- 03
Distribute
Assign the Kit to a team or the whole organization from the dashboard.
- 04
Update
Ship a new version and every machine picks it up on the next sync.
Where do teams find Artifacts and Kits?
Browse Kits and Artifacts built by the community or by your own company. Use them as they are, or fork them to make them yours.
Private
acme-security
by Acme Inc. · 4 artifacts
Public
ts-fullstack
by community · 9 artifacts
Public and private, side by side.
Public Kits are visible across companies. Private Kits are scoped to your organization — only its members can see and use them.
Which AI tools do Kits work with?
Kits install the same on any supported tool. Switch providers — or run several at once — without rewriting your standards.
- Claude Code
- Cursor
- Codex
- Antigravity
- Copilot
See how it all connects.
Each piece of HubBound builds on the others. Pick where you want to go next.