/personas
Load, list, and manage user personas — the bassclef WHO record. Downstream skills (value-prop-canvas, synthetic-user, user-stories, jtbd-tasks) read from its output. Defaults to operator when no personas exist.
/personasType it bare, or paste it with loose context after — Claude figures out the rest.
Product decisions get made for a nameless user. Downstream skills invent personas per session.
One record of the WHO the product serves. Every skill reads the same personas.
Takes in
- Manage command — list or add or edit or delete
Returns
- Persona list with names and jobs
- Loaded into session for downstream skills
What it does
The WHO building block for bassclef. Load personas from a repo's persona directory, list them with summary, get one by slug, or fall back to a minimal operator-default when no personas exist.
Downstream skills read personas via the file-system convention below — not via an in-memory API. The "interface" is a directory shape + a schema, not a function signature. That keeps the primitive compatible with every agent session regardless of runtime.
Read the full skill
The complete instructions live at .claude/skills/personas/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Also relevant in: Design.
Why this phase: Persona definitions loaded before Design-phase JTBD or empathy-map work.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- primitive
- A building block of bassclef — a skill, a rule, a hook, a luminary, or an agent. Adopters compose primitives into workflows. The lite tier ships one primitive of each kind (except luminaries — lite ships 4, standard adds more, ultra loads the full 96). See: /docs/config/tier-system
- INVEST
- Bill Wake's checklist for well-formed user stories — Independent, Negotiable, Valuable, Estimable, Small, Testable. `/ticket` enforces all six for stories. Epics only need V (Valuable) + N (Negotiable) since they break I/E/S/T by definition.
- whereami
- The authoritative project-state snapshot — current phase, active goals, subsystem status, gate progress, session recap history. Read at session-start; updated at session-end. The one file every new session should read first to know where the project stands. See: /docs/skills/whereami
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
- bassclef-upstream
- The private repo where bassclef substrate is authored. Ships to a public `bassclef` npm package + a public `bassclef-web` docs site. Adopters read the public tier; the operator maintains upstream.
Shipped by @kingofrock · Read the essays
/luminary
Browse and preview luminary files. Filter by discipline (ux, visual, architecture, product), by claiming agent (designer, architect), or preview a specific luminary by slug. Catalog analog to /skills.
/skills
Browse the skill catalog live. Every skill grouped by discovery cluster with descriptions, modes, and key chains. Reads SKILL.md frontmatter directly so the catalog explains itself.