Skills › Compound Engineering › ce-riffrec-feedback-analysis › install-riffrec.md
install-riffrec.md
27 lines · skills/ce-riffrec-feedback-analysis/references/install-riffrec.md at 3449230
1# Setup: Add Riffrec to a project
3Use this path when the user has no recording yet and wants to start capturing product feedback with [Riffrec](https://github.com/kieranklaassen/riffrec).
5Riffrec is a browser-based capture tool that records the screen, microphone audio, console output, network requests, and DOM events into a single `riffrec-*.zip` bundle. The bundle is what this skill consumes downstream.
Setup: Add Riffrec to a project
Use this path when the user has no recording yet and wants to start capturing product feedback with Riffrec.
Riffrec is a browser-based capture tool that records the screen, microphone audio, console output, network requests, and DOM events into a single riffrec-*.zip bundle. The bundle is what this skill consumes downstream.
7## What to tell the user
91. Riffrec lives at <https://github.com/kieranklaassen/riffrec>. Refer them to the README for the current install command — it is the source of truth and may change.
102. The general shape of integration:
11 - Add the Riffrec capture script or package to the project's web app.
12 - Wire a "Record feedback" affordance somewhere accessible during real use (a bug report button, a dev-only floating recorder, or a keyboard shortcut).
13 - Confirm a sample session ends with a downloadable `riffrec-*.zip`.
143. Once a zip exists, the user runs this skill again with the zip path. The skill will pick the **quick bug report** or **extensive analysis** path automatically based on length and content.
What to tell the user
- Riffrec lives at <https://github.com/kieranklaassen/riffrec>. Refer them to the README for the current install command — it is the source of truth and may change.
- The general shape of integration:
- Add the Riffrec capture script or package to the project's web app.
- Wire a "Record feedback" affordance somewhere accessible during real use (a bug report button, a dev-only floating recorder, or a keyboard shortcut).
- Confirm a sample session ends with a downloadable
riffrec-*.zip. - Once a zip exists, the user runs this skill again with the zip path. The skill will pick the quick bug report or extensive analysis path automatically based on length and content.
16## Recommended capture habits
18Surface these to the user during setup so the recordings they share later are easy to analyze:
20- Speak the issue out loud while reproducing it. The transcript is the single highest-signal artifact.
21- Click the affected UI even when it does nothing — failed clicks are the strongest signal in event extraction.
22- Keep recordings focused. Many short clips beat one long one when issues are unrelated.
23- Note when a step is intentional vs. accidental ("oops, that wasn't what I meant"). The analyzer cannot infer intent.
Recommended capture habits
Surface these to the user during setup so the recordings they share later are easy to analyze:
- Speak the issue out loud while reproducing it. The transcript is the single highest-signal artifact.
- Click the affected UI even when it does nothing — failed clicks are the strongest signal in event extraction.
- Keep recordings focused. Many short clips beat one long one when issues are unrelated.
- Note when a step is intentional vs. accidental ("oops, that wasn't what I meant"). The analyzer cannot infer intent.
25## After install
27When the user returns with their first zip, route to `references/quick-bug-report.md` or `references/extensive-analysis.md` per the SKILL.md routing rules. Do not run the analyzer in the setup path — there is nothing to analyze yet.
After install
When the user returns with their first zip, route to references/quick-bug-report.md or references/extensive-analysis.md per the SKILL.md routing rules. Do not run the analyzer in the setup path — there is nothing to analyze yet.