Part 0 / 7
Background
A few quick questions to help us understand your context.
Q1 How often do you use AI coding assistants (Claude Code, Codex CLI, etc.)?
Less than 2 hours / week 2–5 hours / week 5–10 hours / week More than 10 hours / week
Q2 Before CWB, how often did you listen to music while coding?
Rarely / Never Sometimes Often Almost every session
Q3 How long have you been using CWB?
Less than 1 week 1–2 weeks 2–4 weeks More than 1 month
Part 1 / 7
Flow & Focus
Rate each statement: 1 = Strongly disagree → 5 = Strongly agree
Q4 After using CWB, I feel less need to interrupt my coding to adjust music.
1 2 3 4 5
Strongly disagree Strongly agree
Q5 Music responses make my coding rhythm feel more continuous.
1 2 3 4 5
Strongly disagree Strongly agree
Q6 Compared to before, I get interrupted less often by the need to switch to a music app.
1 2 3 4 5
Strongly disagree Strongly agree
Q7 During long AI coding sessions, CWB helps me maintain my working state.
1 2 3 4 5
Strongly disagree Strongly agree
Q8 Overall, CWB improves my sense of immersion while coding.
1 2 3 4 5
Strongly disagree Strongly agree
Part 2 / 7
Emotional Resonance & Vibe Matching
This is the core design goal of CWB — please answer thoughtfully. 1 = Strongly disagree → 5 = Strongly agree
Q9 The music style CWB recommends usually matches my coding state (focused, debugging, celebrating, etc.).
1 2 3 4 5
Strongly disagree Strongly agree
Q10 When tests fail, the music response makes me feel "understood" or accompanied.
1 2 3 4 5
Strongly disagree Strongly agree
Q11 When tests pass or a commit succeeds, the music feedback amplifies my sense of achievement.
1 2 3 4 5
Strongly disagree Strongly agree
Q12 DJ Buddy's facial expressions and mood changes accurately reflect my coding emotions.
1 2 3 4 5
Strongly disagree Strongly agree
Q13 Music helps me stay emotionally stable during frustrating debug sessions.
1 2 3 4 5
Strongly disagree Strongly agree
Q14 When did you feel CWB's emotional response most strongly? (select all that apply)
Session start Repeated errors / debug struggle Tests all-green / successful commit Late-night long coding sessions Deep focus / writing code quietly Didn't notice any particular moment
Part 3 / 7
Companion Mode — Proactive Check-ins
DJ Buddy proactively reaches out at key emotional moments. Rate your experience. 1 = Strongly disagree → 5 = Strongly agree
Q15 DJ Buddy's proactive greetings / check-ins feel warm and welcome, not intrusive.
1 2 3 4 5
Strongly disagree Strongly agree
Q16 The timing of companion messages (session start, repeated failures, commit success, close) feels natural.
1 2 3 4 5
Strongly disagree Strongly agree
Q17 Companion mode makes CWB feel more like a "coding buddy" than just a tool.
1 2 3 4 5
Strongly disagree Strongly agree
Q18 The 15-minute cooldown means companion messages appear at a comfortable frequency.
1 2 3 4 5
Strongly disagree Strongly agree
Q19 Which companion trigger moments feel most valuable? (pick up to 2)
Session start greeting After repeated failures — care check Victory celebration after commit / green tests Silent period idle check-in Session close farewell I prefer it stays quiet
Q20 Preferred companion message tone?
More concise and restrained Current balance feels right Warmer and more expressive
Part 4 / 7
Music Discovery & Quality
1 = Strongly disagree → 5 = Strongly agree
Q21 The quality of smart search results meets my expectations.
1 2 3 4 5
Strongly disagree Strongly agree
Q22 The scene categories (Lofi, Focus, Synthwave, etc.) point to the right kind of music.
1 2 3 4 5
Strongly disagree Strongly agree
Q23 Through CWB I discovered music I wouldn't have found on my own.
1 2 3 4 5
Strongly disagree Strongly agree
Q24 Having ~15 results per search gives me enough choice variety.
1 2 3 4 5
Strongly disagree Strongly agree
Q25 Which scene skills do you use most often? (select all that apply)
🎧 Lofi 🧠 Focus 🔥 Hype ☕ Jazz 🌆 Synthwave 🌅 Relax 🎹 Classical 💙 Sad 🏮 Chinese 🌙 Sleep
Part 5 / 7
Interaction & Usability
1 = Strongly disagree → 5 = Strongly agree
Q26 The /cwb command syntax feels natural — I don't have to memorize it.
1 2 3 4 5
Strongly disagree Strongly agree
Q27 Describing music with natural language (e.g. "something for late-night debugging") gives ideal results.
1 2 3 4 5
Strongly disagree Strongly agree
Q28 The statusline lets me see playback state at a glance without breaking focus.
1 2 3 4 5
Strongly disagree Strongly agree
Q29 The installation was simple and didn't add unnecessary setup friction.
1 2 3 4 5
Strongly disagree Strongly agree
Q30 The system runs stably — I rarely encounter errors or unexpected interruptions.
1 2 3 4 5
Strongly disagree Strongly agree
Part 6–7 / 7
Overall Rating & Open Feedback
Last section — your open feedback is the most valuable part. 🙏
Q31 Overall satisfaction with CWB
⭐ ⭐⭐ ⭐⭐⭐ ⭐⭐⭐⭐ ⭐⭐⭐⭐⭐
Q32 How likely are you to recommend CWB to other AI coding assistant users?
0 1 2 3 4 5 6 7 8 9 10
Not at all Definitely yes
Q33 Compared to before using CWB, your overall coding experience has:
Improved significantly Improved slightly No noticeable change Slightly worse Noticeably worse
Q34 In one sentence, describe the biggest change CWB made to your coding experience.
Q35 What is the one biggest problem or improvement you'd most like to see?
Q36 Was there a specific moment that surprised or delighted you? (optional)
Q37 Your email (optional — only if you'd like a follow-up)

We won't share your email. Leave blank to stay anonymous.

(•ᴗ•) ♪ ♫ ♪

## Thanks for your feedback!

Your responses have been recorded and will help shape the future of Coding with Beat. Stay in flow. 🎧

→ Star CWB on GitHub