Config
How bassclef reads your repo and what it updates on its own.
Use this when
You are wiring bassclef into a new repo, changing which skills or hooks you want active, or trying to figure out where a specific behavior comes from. Config pages tell you which file to edit and what the value means.
Skip this when
You are still evaluating whether bassclef fits your work. Read Get started first — you do not need config until the framework is installed and running.
The pieces
- Auto-update behavior — bassclef ships new skills and rules on its own cadence. This page explains what bassclef does on its own (nothing, by default) and how to turn on auto-update if you want it.
bassclef-configs.jsonc— the adopter-facing config file. Plan tier, testing tiers, model routing, and prose discipline live here.settings.json— the Claude Code harness config. Hooks,additionalDirectories, and permissions.- Substrate config (
.bassclef-source.json) — how bassclef syncs its own substrate from upstream. - Directory layout — every substrate-managed directory in your repo, what populates it, and what lives inside.
- Tier system — lite, standard, and ultra compared side by side.
/skill
Compose a new bassclef skill from idea to conforming SKILL.md. Runs the taxonomy gate, generates a verb-first plain-English description, scaffolds the frame, and pre-validates. Standard-tier — pending audit at bassclef-web#193.
Auto-update behavior
bassclef auto-update is OFF by default. Here is what that means and how to change it.