Why Builder OS

The future of work is humans co-creating with AI. The teams that thrive will be the ones who sharpen this skill together, day after day, compounding what they learn.

Every time someone on the team discovers a better way to work with AI, that insight should propagate to everyone. Not through a wiki page or a meeting, but in the most AI-native way possible: as a skill that AI itself can use. That is why Builder OS exists.

The four layers of AI-augmented work

Productive AI collaboration is shaped by four layers. Each has a different owner, a different pace of change, and a different scope of impact. They stack: every layer adds context without replacing the one above it.

Organization
Shared skills and playbooks that encode how your organization works. Spec writing, experiment briefs, code review, release processes. The same standards for everyone, maintained collectively.
Role
Your role's way of thinking. A PM approaches problems through specs and user outcomes. An engineer approaches them through code and system design. The role layer shapes how AI reasons alongside you.
Project
Long-lived product context. What the product does, who uses it, what constraints matter, what has been tried before. One workspace per product, accumulating knowledge over time.
Personal
Your individual productivity. Communication style, domain expertise, preferred shortcuts. This layer learns and adapts to you automatically as you work.
· · ·
The knowledge flywheel

Individual learning becomes organizational knowledge. The more your team works with AI, the smarter the entire organization gets. This is the loop that makes it happen.

Use daily work Discover useful pattern Codify /builder-distill Release ships to everyone everyone gets smarter "I keep doing this..." PR + review weekly release plugin update

Your personal memory catches what works for you.
Builder OS captures what works for everyone.
The flywheel connects them.

· · ·
Where things live in Claude
Layer Claude Code Desktop / Web What it means for you
Organization Plugin via marketplace Upload .zip via Customization One-time install. Updates come through the weekly release. No action needed unless a new version ships.
Role ~/.claude/CLAUDE.md Settings > Profile > Custom Instructions Set once during onboarding. Evolves when your role or responsibilities change.
Project .claude/CLAUDE.md in repo Claude Project instructions You maintain this. Add product context, architecture notes, and constraints. The richer it gets, the more useful AI becomes.
Personal Claude memory (automatic) No setup. Claude learns your style as you work. Just be yourself.
· · ·
Four things to remember
Role in Profile,
not in Projects

Put your role persona in personal settings so it works across all conversations. Projects are for product context.

One Project
per product

Not per task, not per sprint. A long-lived Project accumulates context and becomes your team's shared brain for that product.

"I keep doing this"
= a skill

If you find yourself repeating instructions to AI, say "I want to create a skill" and builder-distill turns it into a shared skill for the whole team.

Memory is yours,
skills are ours

AI memory stores your preferences. Builder OS skills store the team's best practices. Both compound, at different scales.

Skill Catalog Agent Catalog Community Home GitHub

Builder OS — Carousell Group