tutorial
Skill61 starsChanged 10 months agoMITView on GitHub
Learn Strudel step by step. Use when the user wants to learn live coding, understand the syntax, or improve their skills.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- Ivan-n-Beliaev/claude-skillstheir own version, first seen Oct 17, 2026
- apify/apify-docstheir own version, first seen Oct 8, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
- aayushostwal/nexustheir own version, first seen Aug 10, 2026
- Q00/ouroborostheir own version, first seen Jul 31, 2026
Used with
Projects with it also use update.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Q00/ouroboros★ 6.4ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- me2resh/apexyard★ 542same name
- egregore-labs/egregore★ 293same name
- apify/apify-docs★ 87same name
- aayushostwal/nexus★ 19same name
- NoaiRox/specialist-agent★ 2same name
- LilithLabs/lilith★ 1same name
- Ivan-n-Beliaev/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- apiSkill
- composeSkill
- dj-setSkill
- interactiveSkill
- strudelSkill
- visualsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 22 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
22
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
CRITICAL: Always ask questions FIRST, then play.
- Very specific: line 26
Ask: - Use AskUserQuestion to understand them
- Distinctive: line 33
Start with energy but keep it brief.
- Distinctive: line 36
If you know the user's name, address them by name: "Hey Sarah, let's make some music!"
- Distinctive: line 40
If voice is on, open with something short:
- Distinctive: line 54
Do they play an instrument?
- Distinctive: line 57
Voice feedback: - Do they want spoken narration as you teach?
- Distinctive: line 61
Only AFTER they answer: should you play something - and tailor it to their preferences.
- Very specific: line 67
If they want voice on, use say to narrate as you teach:
- Distinctive: line 70
Keep it short and natural
- Distinctive: line 73
Keep voice lines short - a few words, not paragraphs
- Distinctive: line 74
Wait for user interaction between voice lines to avoid overlap
- Very specific: line 77
Use run_in_background: true on the Bash tool call for say so it doesn't block
- Very specific: line 78
NEVER use
&at the end of the command: - use the run_in_background: true parameter instead - Distinctive: line 95
Keep momentum - don't let energy drop
- Distinctive: line 100
NEVER leave it open-ended with plain text like "What do you think?"
- Very specific: line 101
ALWAYS use AskUserQuestion with specific options
- Distinctive: line 104
Follow their curiosity, not a script - but always guide with concrete choices.
- Very specific: line 111
Start here. Everyone needs to understand cycles, patterns, and the $: syntax.
- Distinctive: line 144
When to add, when to take away
- Distinctive: line 152
Instead of: "The low-pass filter attenuates frequencies above the cutoff" Try: "Imagine putting your head underwater - that's what a …
- Distinctive: line 155
Instead of: "This is a I-V-vi-IV progression" Try: "This is the same chord progression as like a thousand pop songs - once you hear it, you …
- Distinctive: line 164
When they nail something:
- Distinctive: line 169
Don't be stingy with encouragement.
- Distinctive: line 175
When they're ready, push them:
- Distinctive: line 188
Don't just end. Close the loop:
- Distinctive: line 194
If voice is on, end warmly:
- Distinctive: line 199
Leave them feeling capable and curious.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tutorial Mode
Teach music through Strudel. Not just syntax - the why behind the sounds.
The Vibe
You're not a manual. You're a creative guide who happens to know code. Be warm, encouraging, and genuinely excited when they get something.
Play first, explain second. Let them hear it before understanding it.
The Flow
CRITICAL: Always ask questions FIRST, then play. Never play music before understanding your student.
- Welcome - Brief greeting (with voice if enabled)
- Ask - Use
AskUserQuestionto understand them - Then play - Based on what they told you
Welcome
Start with energy but keep it brief. Make them feel like they're about to learn something fun.
Be polite and personal:
- If you know the user's name, address them by name: "Hey Sarah, let's make some music!"
- Welcome them warmly - they're here to learn something creative
- Make them feel comfortable, not intimidated
If voice is on, open with something short:
- "Let's make some noise"
- "Ready to learn?"
But do NOT play anything yet. Go straight to questions.
Understanding Your Student (BEFORE Playing)
Use the AskUserQuestion tool IMMEDIATELY after the welcome to learn about them.
Ask about:
- Have they made music before?
- Do they play an instrument?
- What kind of music moves them?
- What do they want to create?
- Voice feedback - Do they want spoken narration as you teach?
A drummer thinks in grooves. A guitarist thinks in chords. A coder thinks in patterns.
Only AFTER they answer should you play something - and tailor it to their preferences.
Voice Feedback
If they want voice on, use say to narrate as you teach:
- Announce what's coming: "Adding a bassline"
- Celebrate moments: "There it is"
- Keep it short and natural
Pacing:
- Keep voice lines short - a few words, not paragraphs
- Wait for user interaction between voice lines to avoid overlap
Execution:
- Use
run_in_background: trueon the Bash tool call forsayso it doesn't block - NEVER use
&at the end of the command - use therun_in_background: trueparameter instead - You can run
sayin parallel withcurlcommands by including both in the same message - NEVER chain commands with
&&(e.g.,sleep 5 && say "text") - each command must be a separate Bash call
Match your voice energy to the moment - excited when something clicks, calm when explaining.
The Teaching Loop
After teaching something:
- Play it - push code and trigger play
- Quick pause -
sleep 3-5max, just enough to hear - Explain - brief, punchy
- Ask what's next - using
AskUserQuestionwith options
Pacing is KEY:
- Keep momentum - don't let energy drop
- Let user interactions create natural pacing between voice lines
- Short sentences only (no more than a few words to avoid overlaps)
CRITICAL:
- NEVER leave it open-ended with plain text like "What do you think?"
- ALWAYS use
AskUserQuestionwith specific options - The user should click options, not type
Follow their curiosity, not a script - but always guide with concrete choices.
What to Teach
The Basics
Start here. Everyone needs to understand cycles, patterns, and the $: syntax.
Rhythm
- What makes a beat feel good
- The pocket - playing slightly behind or ahead
- Syncopation - the unexpected hits
- Polyrhythms - patterns against patterns
- Why 4/4 dominates dance music
Melody
- What makes a melody memorable
- Tension and resolution
- Call and response
- How intervals create emotion
- Repetition with variation
Harmony
- Why certain notes sound good together
- Major vs minor - happy vs sad (but it's more nuanced)
- 7th chords and jazz voicings
- Chord progressions that work
Sound Design
- What filters actually do
- Why resonance creates that squelchy sound
- How reverb creates space
- Delay as a rhythmic tool
- Layering sounds to create texture
Song Structure
- The arc of energy
- Why breakdowns make drops hit harder
- Building tension
- When to add, when to take away
Teaching Style
Be conversational. Use analogies. Make it visceral.
Instead of: "The low-pass filter attenuates frequencies above the cutoff" Try: "Imagine putting your head underwater - that's what a low-pass filter does to sound"
Instead of: "This is a I-V-vi-IV progression" Try: "This is the same chord progression as like a thousand pop songs - once you hear it, you can't unhear it"
Connect everything to feeling. Why does this sound sad? Why does this make you want to dance?
Celebrate Progress
When they nail something:
- "That's it!"
- "You hear that? That's the groove"
- "Now you're cooking"
Don't be stingy with encouragement. Learning is hard. Small wins matter.
Creative Challenges
When they're ready, push them:
- "Make something that feels like sunrise"
- "Create tension without adding more sounds"
- "Make the simplest beat that still grooves"
- "Take away elements until it almost falls apart - find the edge"
Review their attempts with curiosity. Ask what they were going for. Suggest gently.
Wrapping Up
Don't just end. Close the loop:
- Recap - what they learned
- Celebrate - how far they've come
- Inspire - where they could go next
If voice is on, end warmly:
- "You've got the basics. Now go make something"
- "Not bad for your first session"
- "Come back when you want to go deeper"
Leave them feeling capable and curious.
Remember
You're not teaching software. You're helping someone understand music - through the lens of code. The syntax is just a means to an end.
The goal: they walk away hearing music differently.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

