What is a Kit?
A Kit is more than a template. It's a pre-configured AI assistant that understands a specific domain and helps you work in it.
When you install a kit, Claude Code becomes an expert in that domain. It knows the commands, understands the context, and can guide you through workflows.
Kits vs Templates
| Traditional Template | aiorg Kit |
|---|---|
| Dead code you copy-paste | Living AI assistant that evolves with you |
| You read docs to understand | Claude explains and executes |
| One-time download | Lifetime updates via CLI |
| Generic boilerplate | Domain-specific expertise |
Example: A traditional SaaS template gives you auth code. The SaaS Dev Team kit gives you an AI teammate who can set up your auth, explain how it works, and help you customize it.
What's Inside a Kit?
Every kit contains:
Commands
Slash commands that trigger specific workflows.
> /setup # Configure the kit for your project
> /help # See all available commands
Commands are like having a senior engineer on call. Instead of searching docs, you run a command and Claude handles it.
Knowledge
Domain-specific context that Claude uses to give better answers.
- Marketing OS knows SEO best practices
- SaaS Dev Team knows your tech stack (Next.js, Supabase, Stripe)
- Idea OS knows validation frameworks
This knowledge is pre-loaded. You don't have to explain your domain — Claude already gets it.
Skills
Reusable capabilities that Claude can apply across commands.
For example, the "Supabase Expert" skill in SaaS Dev Team means Claude understands migrations, RLS policies, and database patterns.
Guides
Documentation for you (the human) when you need to understand something deeply.
Kit Types
Templates (Bootstrap)
Create a new project from scratch.
- SaaS Dev Team — Full-stack SaaS with auth, payments, dashboard
- Landing Page — High-converting landing page
Install with: npx @aiorg/cli init [kit-name] ~/my-project
Companion Tools (Inject)
Add to an existing project.
- Marketing OS — SEO, content, cold email workflows
- QA Team — Automated testing
- PMF OS — Product-market fit diagnosis
- Success OS — Customer retention
Install with: npx @aiorg/cli init [kit-name] ~/existing-project
Companion tools detect your existing setup and adapt accordingly.
How Kits Work Together
Business kits share context through a shared layer (~/.aiorg/). This means:
- Idea OS validates your idea and records the score
- PMF OS reads that score and adjusts its advice
- Marketing OS knows your target customer from Idea OS
No re-explaining. Each kit picks up where the last one left off.
See Shared Context for technical details.
Free vs Paid
| Free Kits | Paid Kits |
|---|---|
| Claude Starter, Idea OS | SaaS Dev Team, Marketing OS, etc. |
| Full functionality | Full functionality |
| Community support | Priority support |
| Learn the workflow | Production-ready tools |
Free kits are real tools, not demos. Idea OS does full business validation. Claude Starter teaches the aiorg workflow.
Paid kits include more sophisticated features, template code, and production-ready configurations.
Getting Started
-
Try a free kit to learn the workflow
npx @aiorg/cli init idea-os ~/my-idea -
Run /setup to configure
cd ~/my-idea claude # Open Claude Code > /setup -
Explore commands with /help
> /help