/riff
Produce 2 or 3 clickable mock variants. Each pins a luminary lens. Three modes — full, local, scratch. Full uses git, gh, and screenshots. Local writes to disk only. Scratch uses a tmp dir with no git.
/riff/riff full/riff local/riff scratchType it bare, or paste it with loose context after — Claude figures out the rest.
Design work gets one variant. No comparison. The operator picks blind. Rework is heavy.
Two or three mocks per surface. Each mock pins a luminary lens. Cold adopters see a result in five minutes.
Takes in
- A UI surface intent or design goal
Returns
- 2-3 clickable mock variants
- Luminary lens per variant
What it does
You get 2-3 clickable mock alternatives for a UI surface. Each mock uses a different luminary lens. You pick the one that fits.
The picker picks a marketing variant. The writer picks a direction before building.
Read the full skill
The complete instructions live at .claude/skills/riff/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Clickable mock alternatives per luminary lens.
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.
- luminary
- A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- 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
/requirement
Produce Cockburn use cases plus INVEST user stories for a feature in one pass. The writer produces formal use cases for a spec. The picker produces INVEST stories for a backlog. You get both from one operator input. Combines /use-case + /user-stories.
/spec
Turn a canvas or issue into a structured spec. Names the What, the Why, and the acceptance list. Downstream skills read the spec as source-of-truth.