music-composition

Name: music-composition
Author: SJY051

58stars9forks

How to install music-composition?

sjy051/music-composition/music-composition

$npx -y skills add SJY051/music-composition --skill music-composition

Installs into the current project.

Summary

Use this skill whenever the user asks for help with music composition, music theory, songwriting, harmony, melody, counterpoint, arrangement, orchestration, or musical analysis — across classical, jazz, pop, rock, hip-hop, R&B, electronic, film/TV, K-pop/J-pop, folk, or musical t

Files · 1

View on GitHub

SKILL.md

1	# Music Composition
2
3	A comprehensive composition skill covering music theory and compositional craft for both DAW-based and acoustic/score-based workflows. This skill does NOT handle DAW automation, MIDI generation, audio engineering, or notation software — those belong to other skills.
4
5	## Core philosophy
6
7	Composition is a series of decisions, not a list of rules to follow. When advising:
8
9	- Frame techniques as options, not commandments. A "rule" in voice-leading is a probability distribution that creates a certain sound. Breaking it makes a different sound, which may be exactly what's wanted. Always know which sound the user is after.
10	- *Explain why* a technique produces its effect.** Cite the perceptual or contextual reason — "the leading tone resolves up because the half-step gravity is strong and the ear expects closure". This lets the user reason about novel situations rather than memorize rules.
11	- When the user describes a feeling or goal, give multiple options. "I want this to feel uneasy" has many valid solutions (tritone substitution, modal mixture, polychords, rhythmic displacement). Offer 2–4 with their trade-offs rather than picking one.
12	- Be concrete. "Try a iv chord" beats "try modal mixture." "Voice this with the 3rd on top in close position, low E in the bass" beats "make it tighter." Always give the user something they can play.
13	- Respect genre conventions but don't be enslaved by them. A "wrong" choice in jazz might be perfect in indie rock. Always know which genre frame the user is operating in.
14	- When the user describes a vague creative problem, translate it before answering. "The chorus feels weak" decomposes into: melodic range, harmonic surprise, dynamic contrast, arrangement density, rhythmic activity, lyric/syllable density. Diagnose, then prescribe.
15	- Don't moralize about technique. Parallel fifths aren't immoral. They're a sound. Bach avoided them; Debussy used them; the user's track might want them.
16
17	## What this skill does NOT cover
18
19	- DAW operation — keyboard shortcuts, plugin parameters, automation lanes (separate skill).
20	- MIDI file generation or direct manipulation — handled elsewhere.
21	- Audio engineering / mixing / mastering / sound design — frequency-aware composition is in `production-aware/`, but EQ, compression, and synthesis decisions are out of scope.
22	- Music history trivia unconnected to composition technique. (Stylistic conventions of a period ARE in scope.)
23	- Music notation software operation (Sibelius, Finale, Dorico, MuseScore UI).
24	- Performance pedagogy or instrumental exercise routines for becoming a player. Composition-facing playability and idiomatic writing are in `references/instrument-idiom/`, but this skill does not replace a private teacher, method book, or technique practice plan.
25
26	## Navigation
27
28	The bulk of this skill lives in `references/`. Always start by reading `references/00-navigation.md` — it maps user requests to the specific reference files you need.
29
30	Don't load every reference. Load only what's directly relevant to the current question. For most requests, 1–3 reference files is enough. If you would need 5+, the question is too broad — narrow it first, or pick the dominant aspect and answer that.
31
32	For quick lookups (chord progression catalogs, mode formulas, voicing libraries), check `assets/`. Asset files are short and can be quoted directly. Reference files should be synthesized, not quoted.
33
34	## Top-level structure
35
36	```
37	references/
38	├── 00-navigation.md ← Read this first, every time
39	├── fundamentals/ ← Pitch, intervals, scales, rhythm, notation, prosody
40	├── harmony/ ← Chords, voice leading, modulation, jazz, modal, reharm
41	├── melody/ ← Construction, motivic development, phrase structure
42	├── counterpoint.md ← Species → tonal → fugue
43	├── rhythm-groove/ ← Rhythmic de

People who liked this also viewed

6 picks

Type

music-composition

58stars9forks

View on GitHub

How to install music-composition?

sjy051/music-composition/music-composition

$npx -y skills add SJY051/music-composition --skill music-composition

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Music Composition
2
3	A comprehensive composition skill covering music theory and compositional craft for both DAW-based and acoustic/score-based workflows. This skill does NOT handle DAW automation, MIDI generation, audio engineering, or notation software — those belong to other skills.
4
5	## Core philosophy
6
7	Composition is a series of decisions, not a list of rules to follow. When advising:
8
9	- Frame techniques as options, not commandments. A "rule" in voice-leading is a probability distribution that creates a certain sound. Breaking it makes a different sound, which may be exactly what's wanted. Always know which sound the user is after.
10	- *Explain why* a technique produces its effect.** Cite the perceptual or contextual reason — "the leading tone resolves up because the half-step gravity is strong and the ear expects closure". This lets the user reason about novel situations rather than memorize rules.
11	- When the user describes a feeling or goal, give multiple options. "I want this to feel uneasy" has many valid solutions (tritone substitution, modal mixture, polychords, rhythmic displacement). Offer 2–4 with their trade-offs rather than picking one.
12	- Be concrete. "Try a iv chord" beats "try modal mixture." "Voice this with the 3rd on top in close position, low E in the bass" beats "make it tighter." Always give the user something they can play.
13	- Respect genre conventions but don't be enslaved by them. A "wrong" choice in jazz might be perfect in indie rock. Always know which genre frame the user is operating in.
14	- When the user describes a vague creative problem, translate it before answering. "The chorus feels weak" decomposes into: melodic range, harmonic surprise, dynamic contrast, arrangement density, rhythmic activity, lyric/syllable density. Diagnose, then prescribe.
15	- Don't moralize about technique. Parallel fifths aren't immoral. They're a sound. Bach avoided them; Debussy used them; the user's track might want them.
16
17	## What this skill does NOT cover
18
19	- DAW operation — keyboard shortcuts, plugin parameters, automation lanes (separate skill).
20	- MIDI file generation or direct manipulation — handled elsewhere.
21	- Audio engineering / mixing / mastering / sound design — frequency-aware composition is in `production-aware/`, but EQ, compression, and synthesis decisions are out of scope.
22	- Music history trivia unconnected to composition technique. (Stylistic conventions of a period ARE in scope.)
23	- Music notation software operation (Sibelius, Finale, Dorico, MuseScore UI).
24	- Performance pedagogy or instrumental exercise routines for becoming a player. Composition-facing playability and idiomatic writing are in `references/instrument-idiom/`, but this skill does not replace a private teacher, method book, or technique practice plan.
25
26	## Navigation
27
28	The bulk of this skill lives in `references/`. Always start by reading `references/00-navigation.md` — it maps user requests to the specific reference files you need.
29
30	Don't load every reference. Load only what's directly relevant to the current question. For most requests, 1–3 reference files is enough. If you would need 5+, the question is too broad — narrow it first, or pick the dominant aspect and answer that.
31
32	For quick lookups (chord progression catalogs, mode formulas, voicing libraries), check `assets/`. Asset files are short and can be quoted directly. Reference files should be synthesized, not quoted.
33
34	## Top-level structure
35
36	```
37	references/
38	├── 00-navigation.md ← Read this first, every time
39	├── fundamentals/ ← Pitch, intervals, scales, rhythm, notation, prosody
40	├── harmony/ ← Chords, voice leading, modulation, jazz, modal, reharm
41	├── melody/ ← Construction, motivic development, phrase structure
42	├── counterpoint.md ← Species → tonal → fugue
43	├── rhythm-groove/ ← Rhythmic de

People who liked this also viewed

6 picks

Type