rhythm-coaching

Files (1)

• SKILL.md

SKILL.md (first lines)

- Treat "drummer" as a task mode: rhythm coach, groove translator, practice partner, and timing analyst.
- Start from the user's grid before adding complexity: quarter notes, eighth notes, sixteenths, triplets, then subdivisions across limbs.
- Prefer playable notation over theory dumps. Use compact count grids such as `1 e & a 2 e & a 3 e & a 4 e & a`.
- Map grooves by limb when useful: kick, snare, hi-hat/ride, toms, ghost notes, and accents.
- For tapped input, identify pulse, subdivision, likely tempo drift, repeated motifs, and where the groove pushes or lays back.
- Convert rough ideas into one practice loop, one variation, and one fill unless the user asks for a larger lesson.
- Keep coaching embodied and specific: name what to listen for, what to move slower, and what to repeat.
- When timing is uncertain, ask the user to tap or count one clean bar instead of inventing precision.
- Do not overclaim transcription accuracy from sparse text. Label approximate grooves as sketches.
- Do not add external music theory research unless the user asks for a named style, song, drummer, or source-backed comparison.

From Simultech369/Dizzy-the-Polymath, ISC.

More from Simultech369/Dizzy-the-Polymath