626Labs · Claude Code plugin

Bootstrap the file agents stand on.

vibe-keystone produces a production-grade CLAUDE.md for any repository — inventorying first, interviewing you for your actual conventions, then writing a structured file every downstream agent can stand on. Works for any org, not just 626Labs.

v0.2.1·1 command·tenant-aware·MIT

Includes2 skills

ValidatedBootstrapped the CLAUDE.md across every 626 Labs work repo and the main repo.

keystone ~
> /keystone
[keystone] Inventorying repo...
git log: 14 commits, active main
stack: Next.js 15, TypeScript, Tailwind v4
CLAUDE.md: not found — clear to draft
 
Four questions before I write anything:
1. Whose repo is this? 2. Where do decisions log?
3. Persona: inherit / override / none? 4. Work mode?
 
> Acme Corp · docs/decisions.md · inherit · code platform
 
Writing CLAUDE.md... 9 sections, 0 placeholders
01 · What it does

One command, one load-bearing file.

Before writing a line, /keystone inventories your stack and asks four targeted questions — then produces a CLAUDE.md future agents actually stand on, not a template dressed up with your repo name.

/keystone

Bootstrap a CLAUDE.md.

Inventories the repo (git state, layout, stack files, existing .claude/ config), interviews you for tenant identity and conventions, then writes a structured CLAUDE.md adapted to that context. Shows a diff and confirms before overwriting an existing file.

(follow-ups)

Proposes the scaffold.

After the file, it proposes .claude/agents/, .claude/rules/, and .claude/hooks/ candidates tailored to the repo — but never auto-creates anything. You decide what to keep.

02 · How it's different

It refuses to write blind.

Most bootstrapping tools generate a template and call it done. vibe-keystone treats blind writes as a bug: it inventories the repo first — git log, package.json, workflow files, existing .claude/ structure — then asks one round of targeted questions before drafting anything. The produced file is specific to your stack, your decision-tracking surface, and your org's voice rules.

The skill adapts its output to repo type. A code platform gets a tech-stack section and infrastructure guardrails. A marketing site gets voice rules and a design-system reference. A writing repo gets a persona-override clause and citation discipline. Sections that don't apply are dropped, not left as placeholders that rot.

It will not overwrite an existing CLAUDE.md without a diff and explicit confirmation.
03 · Get it

Install.

Stable marketplace

Or drop the SKILL into ~/.claude/skills/keystone/ to run it as /keystone.

/plugin marketplace add estevanhernandez-stack-ed/vibe-Keystone
/plugin install vibe-keystone@vibe-keystone

Surfaces as /keystone (user skill) or /vibe-keystone:keystone (plugin).