Riff
- Updated May 9, 2026
- junjzhang/riff
Riff is a Claude Code plugin that runs structured brief, learn, explain, and design workflows so developers can review rich HTML planning artifacts before implementing changes.
About
Riff is a Claude Code marketplace plugin for structured human-agent collaboration during development tasks. Four slash commands—brief, learn, explain, and design—produce self-contained HTML documents in a per-task .workspace folder you open in a browser to review problem breakdowns, code insights, mechanism explanations, and architecture proposals. Reach for it when you want a repeatable pre-implementation ritual instead of ad-hoc chat: research an issue, deep-dive code, explain a mechanism, or propose a design before writing patches.
- Four workflows: brief, learn, explain, design
- Self-contained HTML outputs in .workspace per task
- Tokyo Night themed visual documents, no external CSS deps
- Typical flow: brief → learn → design → implement
Riff by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add junjzhang/riffAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | May 9, 2026 |
|---|---|
| Repository | junjzhang/riff ↗ |
How do I turn messy exploration into reviewable briefs, code learnings, explanations, and design docs with an agent?
Run structured brief/learn/explain/design workflows that output browser-reviewable HTML docs before you implement a change.
Who is it for?
Developers who want a repeatable human-agent ritual before touching code on tickets, modules, or architectural changes.
Skip if: Teams that only need one-off answers in chat and do not want per-task HTML workspace artifacts.
What you get
Browser-openable HTML files land under .workspace/{task}/ for brief, learn, explain, and design reviews.
Recommended Marketplaces
FAQ
What commands does Riff provide?
Four slash skills: /Riff:brief, /Riff:learn, /Riff:explain, and /Riff:design, each writing a self-contained HTML file.
Where do outputs go?
Each task gets a git-ignored folder under .workspace/{task}/ with brief.html, learn.html, explain-*.html, or design.html.
What is the recommended sequence?
Typical flow is brief → learn → design → implement; explain is standalone for deep dives on one mechanism.