Get started
Install bassclef and run the three commands that make up the core value journey.
Use this when
You have Claude Code installed and want to try bassclef in a real repo. You do not need to know what a hook or a skill is to get value from the three commands.
Skip this when
You want the reference catalog of every command. That lives under Skills. This page is the shortest path from zero to shipping your first thing.
The three steps
- Install — see the install page. Currently placeholder-then-refresh: the site shows a placeholder now and refreshes with the live command when v0.1.0 publishes.
- Run
/riff— sketch a UI idea from a paragraph. You type a paragraph. Claude comes back with three clickable mocks. - Pick one and run
/launch— Claude turns that mock into a buildable plan: a spec, user stories, and a migration plan. - Run
/build— Claude ships the plan. A Reviewer role signs off and a pull request opens on your branch.
What you get
By the end of the three steps, you have a pull request open on your own repo with code your reviewer can compare against the spec you agreed on. No slide deck. No feature request handoff. No demo that does not compile.
Next up: two workhorses
After the Tightest 3, you invoke /longrun and /sprint every
session — they drive the session shape. See
the workhorses.
Next steps
- The install page — install and version detail
- Skills catalog — every command bassclef ships
- When bassclef does something unexpected — read this before you rely on the framework in production
Coding agents know how to code. bassclef helps them know how to build.
A development substrate that sits between you and Claude Code. Turns coding capacity into shipped software that holds together — with product thinking, planning, standards, review, and learning as files you can read.
Supported systems
What bassclef runs on today. macOS is verified. Linux runs in CI under Docker on Debian 12. Direct Linux hosts, arm64, other distros, and WSL 2 are untested. Windows PowerShell native is not supported — use WSL 2.