bassclef

An opinionated add-on for Claude Code, for the person running six software projects at once.

opinionated

Defaults tested through 1B+ tokens of production use. No config file to argue with; override anything.

auto-guided builds

Every session starts loaded. Every session ends charted.

expert lenses

Beck, Cockburn, Rams, Norman on call. Reasoning in markdown.

Request early access → click. two minutes. no forms until we're a fit.

Where this fits, in five short answers

market category
Agent substrate. Sits under Claude Code, over your repo. Not an IDE, not a CI, not a workflow tool.
who it's for
The solo builder running six or more initiatives in parallel, around a day job and family. Larger teams may borrow it; methodology leans solo.
who it's not for
Teams of ten with a PM, an assignment router, a cross-team dependency graph. Different problem, different tool.
unique attribute
Three primitives: context that persists across every session, expert lenses on demand (Cockburn, Norman, Rams), and lifecycle hooks that keep momentum, guardrail every step, and enforce discipline. All from files you can read, not from model weights.
proof
Dozens of skills and hooks (growing every day). 82 luminary profiles. Running in daily production on 6 sibling repos. apache-2.0. Repo private for now; opens publicly at v1.0.

what it's made of

Six building blocks. That's the whole thing.

Not just markdown. Everything bassclef is made of. Markdown for the plans you write. Shell scripts for the guardrails at every Claude Code lifecycle event. JSON schemas for the state that persists. Plus tests to keep it honest. All files, all in your repo, all yours to modify.

block · rule

Rules

Markdown files with your project conventions. Loaded via SessionStart.

block · skill

Skills

Named slash-commands. /onboard-repo, /sprint, /verify. Composable.

block · hook

Hooks

Shell scripts at Claude Code lifecycle points. Gates, checks, formatters.

block · chronicle

Chronicles

Session-end paragraphs pinned to state. Read via /whereami.

block · luminary

Luminaries

82 practitioner profiles. Reasoning in the file, not the model.

block · state

State spine

Typed JSON per schema. Plain files, browsable.

Three reasons this isn't hand-waving.

Status: alpha, in daily production on 6 sibling repos

License: apache-2.0

Cost: free (you'll need Claude Code; that's a separate subscription)

Repo: private for now. Comes with your invite. Goes public at v1.0.

Maintainer: Sunjay Pandey — 20 years across Amazon (AWS, Alexa), Capital One, BP, and bootstrapped startups. LinkedIn ↗

Get on the list

One email a week. What shipped, what to install, and one thing I learned running bassclef this week. Sunday evenings. Unsub anytime.

So I know which OS you're on when I write about tooling. Windows adopters usually use the Linux path via WSL.
Where the weekly note lands. Reply-to comes straight to me.
Helps me write about the things you'd actually use. Skip if you'd rather not say.
one email a week · reply-to-me · unsub anytime

About the maintainer

Solo operator running six or more software projects in parallel around a day job and family. Started bassclef because thirty minutes of context reconstruction per Claude Code session, times six projects, was eating my Saturday mornings.

Two decades across Amazon (AWS, Alexa), Capital One, BP, and bootstrapped startups: cloud infrastructure, consumer tech, regulated finance, industrial, solo-builder. bassclef distills what actually holds across that range. I'm carrying the learnings into the day job, not away from it.

The substrate is one person's opinionated solution. In daily use, growing every day. Shared with a considered early cohort, one operator at a time.

Sunjay on LinkedIn ↗ · maintainer@bassclef.dev