BBMstack is a multi-source AI coding workspace bootstrapper for Claude Code and Codex.
It solves a common onboarding failure mode: new developers open Claude Code or Codex, burn context teaching the agent how to work, and still end up with inconsistent workflows. BBMstack gives them a repeatable install, stable command surface, public workflow sources, optional private packs, and project-level activation.
BBMstack is not another skill marketplace.
It is the composition layer above:
- public workflow sources such as
gstackandsuperpowers - BBMstack-native public packs such as
seo - optional private company packs such as
bbmstack-fleksa - optional integrations such as
tmux-ideand GitNexus-style repo intelligence
That means a team can clone one repo, run setup once, activate a project config, and start working with a sane agent workflow instead of re-explaining everything in every session.
git clone https://github.com/MishraBhushan/BBMstack.git ~/Dev/BBMstack
cd ~/Dev/BBMstack
./setupRequires:
- Claude Code
- Git
- Bun v1.0+
./setup links BBMstack into both ~/.claude/skills and ~/.codex/skills, syncs enabled sources, and activates packs for the current project if .bbmstack.json exists.
- Install BBMstack:
cd ~/Dev/BBMstack && ./setup- Create a project config:
cp ~/Dev/BBMstack/examples/bbmstack.json .bbmstack.json- Sync sources and activate packs:
bbmstack source sync
bbmstack activate
bbmstack check- Restart Codex if needed, then start using:
/plan/debug/qa/review/ship
BBMstack supports three source types:
bundled: shipped inside the repogit: public or private git repositories synced into~/.bbmstack/sources/local: a local path on disk
List the resolved sources for a project:
bbmstack source listSync enabled sources:
bbmstack source syncProject configuration lives in .bbmstack.json.
Public example:
{
"sources": {
"gstack": { "enabled": true, "ref": "main" },
"superpowers": { "enabled": true, "ref": "main" }
},
"packs": ["seo"],
"integrations": {
"gitnexus": false,
"tmux_ide": true
},
"browse": {
"default_url": "http://localhost:3000"
}
}Private-source example:
{
"sources": {
"gstack": { "enabled": true, "ref": "main" },
"superpowers": { "enabled": true, "ref": "main" },
"fleksa": {
"enabled": true,
"private": true,
"type": "git",
"git": "git@github.com:MishraBhushan/bbmstack-fleksa.git",
"ref": "main"
}
},
"packs": ["seo", "fleksa"]
}Private sources are config-driven. They are not required submodules of the public BBMstack repo, so public installs still work even when a user does not have access to your company packs.
See:
examples/bbmstack.jsonexamples/bbmstack.private.jsonschemas/bbmstack.config.schema.jsondocs/configuration.mddocs/usage.mddocs/team-onboarding.md
Public BBMstack ships:
- core workflow skills
- public integrations such as
tmux-ide - public packs such as
seo - a pack template for your own extensions
- source syncing and project activation
Private company knowledge should live in separate private sources, not in the public repo.
bbmstack source list [path]
bbmstack source sync [path]
bbmstack activate [path]
bbmstack check [path]
bbmstack status [path]
bbmstack vendor <path>
bbmstack update
bbmstack update --selfseo— SEO audits, strategy, and structured data_template— starter template for your own pack
Create a new pack by copying packs/_template/ and adding skills plus pack.json.
Vendor BBMstack into a repo:
bbmstack vendor ~/path/to/projectTeammate flow:
cd .claude/skills/bbmstack
./setupThis keeps the onboarding surface small:
- install once
- sync sources once
- activate packs for the repo
- start using the same commands everywhere
BBMstack is designed to compose multiple public ecosystems instead of replacing them.
- Built on top of bundled
gstackby Garry Tan - Designed to work alongside
superpowersby Obra Studio
Please preserve upstream licenses and attribution when vendoring or redistributing BBMstack.
See also: