Project Kits
What a Project Kit Is
A Project Kit is a one-click bundle that sets up your board for a specific project type. Instead of manually creating agents, wiring up workflows, and inventing a label scheme, you pick the kind of project you're building and VibeCodes configures everything for you in seconds.
The kit dialog is titled "Apply a Project Kit" and describes itself simply: "Choose a project type to set up agents, workflows, labels, and workflow triggers for this idea."
What a Kit Bundles
A kit sets up exactly four things — nothing more:
- AI Agents — a team of personas matched to the project type (for example Full Stack, UX, and QA agents).
- Workflow Templates — reusable multi-step processes such as Bug Fix or Feature Development.
- Board Labels — colored labels for categorization like Bug, Feature, and UX.
- Workflow Triggers — rules that tie a label to a workflow so the right process is auto-applied to a task when it gets that label.
Kits Never Touch Your Tasks
This is the most important thing to know about Project Kits: applying one is completely safe on an existing board. It only sets up the four building blocks above — it does not add, remove, move, or modify any of your tasks.
No tasks are added. This kit sets up your agents, workflows, labels and triggers only — your existing board tasks stay exactly as they are.
How to Apply a Kit
There are three entry points for applying a Project Kit:
- During onboarding — you pick a project type while describing your project, and the matching kit is applied automatically.
- From the board empty state — a fresh board offers to set itself up with a kit.
- From the Workflows tab — use the "Apply a Project Kit" button at any time.
In the dialog you pick a project-type card, preview what it includes, then click the apply button — labelled Apply {Kit Name} Kit (for example Apply Web Application Kit).
The Preview
Choosing a project-type card shows you a full preview before you commit, so you always know what a kit will set up:
- A Team section listing the agent role chips the kit will create.
- A Workflows — click to view steps section, where each workflow shows its step count. Click a workflow to expand its step chain.
- Steps that need sign-off show a lock for "Requires your approval".
- A legend notes "⚡ Labels auto-assign workflows" to explain how the triggers connect labels to workflows.
The "Custom" option starts from scratch — no kit is applied. Custom is not an applyable kit; it simply means you'll set up agents, workflows, and labels yourself afterwards.
Smart, Non-Destructive Application
Applying a kit is designed to be safe to run on a board that already has some setup. It de-duplicates as it goes:
- It skips agents whose role you already have.
- It skips labels that already exist.
- It imports each workflow template once.
- A partial failure on one item doesn't block the rest — the kit applies everything it can.
After wiring up the triggers, a kit also retroactively applies them to your existing labelled tasks. So a task that is already labelled bug gets the Bug Fix workflow attached automatically — without you having to re-label anything.
Via MCP / Claude Code
Kits are also available programmatically. Using the list_kits and apply_kit MCP tools, you — or an agent — can browse and apply a Project Kit at any time directly from Claude Code, without opening the dialog.
See the MCP Integration guide → for how to connect Claude Code to your boards.
Where to Go Next
A Project Kit is really a head start on two of the most powerful features in VibeCodes. Dig deeper here:
- Workflows guide → — how the bundled workflows and triggers actually run.
- AI Agent Teams guide → — the agents a kit creates for your board.