battle-tested · 1B+ tokens · ~1000 hours · 20+ repos status · alpha source · github.com/sunj-labs/bassclef license · apache-2.0 maintainer · one
A markdown add-on for Claude Code — for one person running six projects at once.
the agent band that backs your solos.
An opinionated add-on for Claude Code — every session starts loaded with your rules and context.
request early access →Five things that happen at every Claude Code session — plain outcomes, not architecture. "You" = you the operator; "Claude" = the agent working on your behalf.
You write your project conventions once in markdown files inside your repo. Claude reads them at every session start. You never re-explain them.
At session-end, Claude writes a short paragraph summarizing what happened. At session-start, Claude reads that paragraph back. Open a project three weeks later and both of you know where to pick up — context recovery is the primary thing bassclef does.
Substrate in .claude/. Your code stays in src/. No IDE switch, no migration, no proprietary format. If bassclef stops shipping, your files stay yours.
You invoke /luminary cockburn when you want a use case. Claude channels Cockburn's methodology from a markdown profile it loads on demand. Same for Rams's visual restraint, Cooper's persona check, Norman's affordance review. The reasoning is in the profile file — you can read it — not hidden in the model.
You dictate a paragraph from your phone. Claude reads it, picks luminary perspectives, generates variant HTML files, serves them locally, and hands back a preview URL. This landing page was generated that way — Sunday morning, walking the dog.
bassclef isn't a framework with hidden magic. It's six named building blocks, each doing one obvious thing. The five outcomes above? They're what these six blocks add up to when Claude reads them at session start.
/onboard-repo; Claude executes it. A "chronicle" is a paragraph Claude writes at session-end summarizing what happened — you read it (or Claude reads it back at the next session-start via /whereami).
Your project conventions as markdown. You write them once. Claude reads them at every session start.
Stops you re-explaining conventions every session.
Named slash-commands. You type /onboard-repo, /sprint, /verify; Claude executes.
One verb per skill. Composable — chain them.
Shell scripts that fire automatically at Claude Code lifecycle points. Gates, checks, formatters.
Every agent action gets a check or a confirmation.
Session-end paragraphs Claude writes summarizing what happened. Claude reads them back at the next session-start.
The chart survives closing your laptop.
82 markdown profiles of named practitioners. You invoke /luminary don-norman; Claude channels the profile.
Reasoning is in the file, not the model.
Typed JSON per schema — chronicles, whereami, iteration bets. All plain files.
If bassclef dies, your files stay yours.
shipped, not theoretical · 43 skills · 24 hooks · 82 luminaries · 6 sibling repos in production
Three fields. Every one has a reason. If we're a fit we send you a signed link to the tarball for your OS.