Form Filling
asgeirtj/system_prompts_leaks
Fill out online forms (Google Forms, Typeform and similar) or PDF, Word and DocuSign forms; prepare a reviewable draft and get approval before submitting or sending.
Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus.
MITAuto-check passed
Install Mc Form
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-form --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .claude/skills/mc-form && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .claude/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-formType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-form --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .agents/skills/mc-form && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .agents/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-form --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .cursor/skills/mc-form && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .cursor/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jtydhr88/music-composition-skills.git --path plugins/music-composition/skills/mc-form--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-form --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .gemini/skills/mc-form && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .gemini/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jtydhr88/music-composition-skills mc-formInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .github/skills/mc-form && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .github/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/music-composition-skills --skill mc-form -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-form --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/music-composition/skills/mc-form .opencode/skills/mc-form && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mc-form" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-form into .opencode/skills/mc-form/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-form", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mc-form- GitHub stars
- 151
- Token cost
- ~2.2k tokens
- SKILL.md length
- 604 words
- Files
- 2
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus.
- Works in 8 steps: 段落术语对照 → 标准模板 → 开头怎么进 → …
- Laying out a song
- SKILL.md covers 按任务读哪几节, 边界, 1. 段落术语对照 and 2. 标准模板, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mc Form is an agent skill from jtydhr88/music-composition-skills. Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus. The Japanese section vocabulary mapped onto Anglo-American terms (and the two that are routinely mistranslated), the two broad families sorted by chorus position, the royal-road template with its repetition-omission rule, ternary form and the recapitulation principle, EDM and club variants, lead-in options, and the classical Chinese/Russian period-and-phrase apparatus for when pop…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
The repository describes itself as: Professional agent skills for composing and arranging popular music. The licence is MIT.
When your agent uses it
- Laying out a song
- Sections blur together
- Deciding how many verse-chorus cycles
- A bridge is needed
Example prompts
- “/mc-form”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7adca0c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mc Form loads about 2.2k tokens when it runs. Until then it costs about 186 tokens; SKILL.md has 604 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jtydhr88/music-composition-skills at commit 7adca0c, republished under its MIT licence (© jtydhr88). 604 words, ~2,237 tokens.
Download SKILL.mdSave it as
.claude/skills/mc-form/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- mc-form
- description
- Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus. The Japanese section vocabulary mapped onto Anglo-American terms (and the two that are routinely mistranslated), the two broad families sorted by chorus position, the royal-road template with its repetition-omission rule, ternary form and the recapitulation principle, EDM and club variants, lead-in options, and the classical Chinese/Russian period-and-phrase apparatus for when pop terms run out. Use when laying out a song, when sections blur together, when deciding how many verse-chorus cycles, when a bridge is needed, or when filling the form table of an ARR-SPEC. 曲式、段落、结构、主歌副歌、桥段、乐段、再现、A メロ、サビ。
曲式与段落（Form）
这个 skill 管"这首歌由哪些块组成、每块多长、按什么顺序"。
它和 mc-arrangement-arch 的分工是本库最容易混的一处：
mc-form管曲式是什么（乐理与惯例）；mc-arrangement-arch管这首歌为什么这么切（决策与非对称）。
具体说："副歌通常 8 小节"归 form；"这首歌的第二段主歌要 14 小节因为要打破整数"归 arrangement-arch。
按任务读哪几节
| 任务 | 读 |
|---|---|
| 排一首歌的结构 | §2 模板 → §5 倒着设计 |
| 段落术语对不上 | §1 对照表（★ 有两个常被译错） |
| 段落之间糊成一片 | §4 ＋ mc-arrangement-arch §4 |
| 要不要加 C 段/桥 | §5 的构成选择 |
| 做 EDM / 俱乐部音乐 | §2.5 |
| 开头怎么进 | §3 |
| 流行术语不够用了 | §6 古典曲式装置 |
| 填 ARR-SPEC 的 form 表 | §7 |
边界
| 不归这里 | 归哪 |
|---|---|
| 为什么这段要 14 小节而不是 16（非对称设计） | mc-arrangement-arch §4 |
| 能量曲线、进退场事件 | mc-arrangement-arch |
| 动机怎么发展成乐句、一段拿旧材料做什么 | mc-development；乐句内部的切分与呼应仍在 mc-melody §7 |
| 段落之间怎么转调 | mc-modulation |
| 副歌的和声怎么配 | mc-harmony |
| 某风格的典型曲式 | mc-style-*（L3） |
| 影视配乐的结构（跟画面不跟曲式） | 出库 → 配乐库 |
| 古典曲式的完整分类与谱例 | reference.md |
1. 段落术语对照
日式（J-POP）术语与英美术语不是一一对应的，分析或沟通前先理清。
| 日式 | 中文／英美 | 功能 |
|---|---|---|
| A メロ | 主歌（Verse，平歌） | 引入段。音域窄、时值短、"語り"式演唱；歌词讲具体故事、铺场景 |
| B メロ | 预副歌（Pre-chorus） | ★ 日本特有的"第二主歌"：介于 A メロ与サビ之间、性格不同的一段，音区逐步抬高、堆积期待 |
| サビ | 副歌（Chorus） | 全曲高潮所在的乐节：音区最高、密度最大、最好记；承载核心信息 |
| C メロ / D メロ | 第三发展段（桥的位置） | 2 番之后出现的全新旋律/和声/节奏，制造"意外发展" |
| 大サビ | ≈ 英美的 bridge / middle eight | ★★ 不是"更大的サビ"！ 性格更接近"第二个 B メロ"：内省、收敛，常带半速感；它后面一定跟一个サビ |
| 頭サビ | 以副歌开场 | 第一秒就是サビ，直接抢占记忆 |
| 落ちサビ | "落下"的副歌 | 同一条サビ旋律突然换成极稀薄的编制（如只剩钢琴+人声），靠落差打动人 |
| キメ | 齐奏重音 / 收尾句 | 接在サビ末尾约 2 小节的插旗句，伴奏骤停或打标志性节奏，唱出主题词 |
| イントロ | 前奏 | |
| 間奏 | 间奏 | 英文叫 Second Introduction——"第二轮主副歌的前奏" |
| アウトロ／後奏 | 尾奏 | 器乐化的尾声 |
| ヴァンプ | 律动段 | 不奏旋律、只提示节奏型的段落（可以只有打击乐，或加贝司/吉他） |
| コーダ | 尾声 | 最后一轮节结束后追加的演唱段落 |
| 1 番 / 2 番 | 第一轮 / 第二轮 | 一轮主副歌 = 一个"节"；同旋律 + 不同词 + 编制微变——几代人提炼出的防腻装置 |
| ブレイク | Break | 伴奏完全停止、只剩人声的瞬间 |
| フィル | Fill | 段落接缝处的鼓填充，提前点燃期待 |
★★ 两个最容易译错的：
- 大サビ ≠ 大副歌，它是 bridge
- 日文"平行調" = 关系大小调，不是英文的 parallel key（那是"同主調"）——见
mc-modulation§2
旋律法的层级：部分动机 → 动机 → 小乐节 → 乐节 → 节 → 全曲。
サビ 的旋律法定义：在"节"这个大单位内充当高潮的那个乐节。 每一层级上高潮的大小，与那一层块的大小成正比。
2. 标准模板
2.1 按副歌位置分两大类
| 类 | 形状 | 说明 |
|---|---|---|
| 末広がり型（越往后越开阔） | [A→B→サビ] 或 [A→サビ] | サビ 以外的段落都是"铺台面"。现代 J-POP 绝大多数属于这一类 |
| 循環解決型 | [A→サビ→A] 或 [サビ→B→サビ] | 末尾回到开头的旋律（三部性，再现原则）。1960 年代、演歌/歌谣曲/爵士标准曲常见，今天越来越少 |
2.2 王道全曲模板（末広がり型）
Intro → 1A → 1B → 1サビ → (间奏1)
→ 2A → 2B → 2サビ → 间奏2
→ Cメロ(大サビ) → 3サビ(可转调) → (3サビ2) → 尾奏要点：
- A−B−サビ 三段构成是日本流行最常见的形式（旋律法：a−b−c 的纯三段构成 = 起 − 换个视角 − 综合解决）
- 为什么有"2 番"：同旋律 + 音响略变 + 完全不同的歌词，防腻装置
- 2 番之后插 C メロ/桥（可以全新旋律、和声、节奏）继续防腻并推高，再给一遍サビ
- ★ 省略重复规则：第 1 节
A−A'−B−C→ 第 2 节A−B−C→ 第 3 节可以直接从サビ开始 - 全曲通常 2–3 个节、3–5 分钟；慢歌减节数，快歌加节数（BPM 差 3 倍以上靠节数平衡）
唯一真正的标准：听众既不因为太长而腻，也不因为太短而觉得亏，听完是满足的。
2.3 三部曲式模板（サビ 在中间）
A(melo) → B(サビ) → A'(melo) ×2–3 节- 支柱是再现原则：B 把 A 的内容更情绪化地展开（或从更宽的视角叙述）， 回到 A 带来"深切的领悟与怅惘"
- A 与 B 的连续性通常比 Verse=Chorus 型更强
- 扩展形 A−A'−B−A'' = 经典的起承转合构成
- 稀见变体 A−B−C：末段不再现 A，而是做成"反复落在同一个音上、边收边静"的旋律，听起来仍像回家
2.4 其他形式速查
| 形式 | 结构 |
|---|---|
| 二部曲式 | A（主歌）− B（副歌）：西方流行/摇滚的基本形 |
| 插桥形 | A −（短桥）− サビ：不写完整的第二主歌，只插一小段连接（抬音区、加热） |
| 复三部 | [A−B−A]−[C−D−C]−[A−B−A] |
| 混合形 | A−B−サビ−A（Verse=Chorus 之后再现主歌） |
| 单段构成 | 只有副歌／只有主歌：数え歌、叙事民谣、循环型舞曲 |
| 广告曲 | 把 A/B/サビ 塞进 15/30 秒；发展必须极其清楚；用变拍子做"长度调整" |
2.5 EDM / 俱乐部音乐变体
在比歌曲类音乐长得多的时间尺度上堆积强度：
four-on-the-floor 底鼓起
→ 加 hi-hat
→ 加钢琴之类的持续伴奏（以 8+ 小节为单位重复）
→ 正式前奏 → A メロ → サビ
→ 回到只有鼓的段落 → 循环……- 特征：旋律可有可无；结构长而大；有只剩鼓或只剩 pad 的段落， 所以厚度落差极其尖锐；以鼓为中心来编
- 这个结构成立的两个理由：(1) 慢慢堆更适合跳舞；(2) 只有鼓的段落方便 DJ 接下一首
- ★ 在家里听觉得啰嗦无聊的结构，在舞池上极其有效——目的决定形式
- 舞曲的节构成常是 A−A−A−…−A'−B：主歌把一个动机重复很多次 + 一个短副歌
- 极端形：节内只有一个动机（a a a a）。重复渗进无意识，唤起半不随意的身体反应—— 即使没有大高潮，重复本身就构成了堆积
3. 开头怎么进
在正歌之外、曲子最顶端加一个引入乐节，两大类形式都能用：
| 方式 | 做法 |
|---|---|
| 朗读式前段（安静导入） | 中音区 + 音高几乎不动 + 简单节奏 + 和声静止的伴奏，甚至自由速度——从"介于朗读与歌唱之间"的状态开始，平滑地把听众领进作品的世界（歌剧与音乐剧极常见）。形式：D(引子) − [A−B−サビ] − [A−B−サビ] |
| 高扬型导入（反过来） | 引子以高扬的乐节开始（跳进 + 高音区），制造与日常的巨大落差，一把把听众拽进来 |
| 頭サビ | 引子直接用サビ——最常见的选项。C−[A−B−C]−[A−B−C]（Verse=Chorus）；B−[A−B−A]（三部）。★ 两种打法：原样演奏 = 炫目的开场；薄伴奏 + 慢速 + 自由速度 = 平滑的叙述式导入 |
4. 段落之间要有对比
段落糊成一片的根因是相邻两段在太多维度上相同。 对比的具体手段在 reference.md §1，这里只给判据：
自检动作：把相邻两段在这六项上打勾—— 音区 / 节奏密度 / 和声节奏 / 编制厚度 / 演唱方式 / 乐句长度。 少于两项不同，这两段就会被听成同一段。
Show full SKILL.md (263 more words)Show less
5. ★ 倒着设计：从副歌往回推
设计原则永远是"以サビ为中心倒推"。
| 构成 | 怎么设计 |
|---|---|
| A 构成（单乐节） | 不换性格，朴素简单。舞曲重复同一 riff 时，节内动机甚至只有一个（a a a a） |
| A−B 构成（Verse=Chorus 基本形） | 二段构成原则；欧美摇滚/R&B 常见，抓耳力强。已有サビ → 倒推"什么样的 A 能领进它"；已有 A → 想它该接什么样的サビ。★ サビ 不只开头要有冲击，后半也必须有足够的高潮 |
| A−B−C 构成（日式王道） | ★ 先想サビ(C) 和引入段 A，定中间部分的方案，B 最后写 |
| A−B−A 构成（三部） | 在乐节末尾上演"深切的怅惘"或"解决的开阔"。★ 要让再现效果充分兑现，标准做法是让 B 的性格剧变 |
B 段的两种写法（A−B−C 构成里）：
- B 当桥：收敛的 A → 强调节奏的短动机重复、音区逐级上台阶的 B → 有律动的 C
- B 当第二主歌：轻的 A → 内省安静的 B → 靠落差把高扬感加倍的 C （B 的后半个小乐节可以做成往上堆、领出 C 的短桥）
5.1 ★ 扩展警告
在
A−B−C → A−B−C−D这样加元素之前，先考虑用"乐节重复"来扩展。 元素太多 → 通往サビ的路弯弯绕绕、焦点发散。
这是个先后顺序的判据，不是"不许加段落"：先看能不能靠上表里已经列出的手法（比如 A 构成里 riff 的整段重复、A−B−C 里 B 段末尾自带的短桥）把篇幅撑够，撑不够、对比也做不出来了再考虑加新元素。加不加最终还是服从 §8 的时长预算：多一个元素通常意味着多几个小节，超出 3–5 分钟就要说得出理由。
5.2 加キメ
任何构成都可以在乐节末尾或サビ内部加一段约 2 小节的キメ。 ★ 觉得歌曲"缺乏起伏（メリハリ）"时，先考虑这个，而不是加段落。
这是应对"缺乏起伏"的两条处方之一，另一条是 §5.1 的乐节重复扩展；两条都比加新段落轻，所以排在前面试。キメ 本身怎么编排（齐奏、留白还是加花）跟位置、风格强相关，属于编曲执行层，不在曲式这一节铺开。
6. 流行术语不够用时：古典曲式装置
做影视配乐、器乐曲、或需要更细的结构分析时，流行那套"A/B/サビ"不够用。 中文/俄式体系提供了更细的刻度：
| 装置 | 用处 |
|---|---|
| 乐段（Period） | 比"段落"更严格的单位。分一个乐句、两个乐句、三个及以上乐句结构 |
| 复乐段 | 两个乐段构成的更大单位 |
| 开放乐段 | 结束在非主和弦上的乐段——★ 对应 mc-melody reference §5 的终止开放度 5–8 档 |
| 乐段前后的引子与补充 | 结构外的附加部分。★ 解释了"为什么这段是 17 小节不是 16" |
| 单二部曲式 | 有再现 / 没有再现两类 |
| 单三部、复三部、回旋、变奏、奏鸣 | 见 reference.md §3 |
★ 作为独立曲式的乐段，与作为曲式一部分的乐段，特征不同—— 这条区分对判断"这到底是一段还是一首"很有用。
本库的用法：写流行歌用 §1–§5 的术语； 走
mc-style-cinematic或需要做结构分析（mc-case-studies）时，切到这一套。 两套不要混着说，否则交接会乱。
6.1 ★ 段落在做什么：五种陈述方式与六种结构功能（李吉提）
§1 到 §5 用的是段落的名称，这一套用的是段落的行为，填的是名称与功能之间的空白（李吉提《曲式与作品分析》p0022–0024）。
| 陈述方式 | 特征 | 一句话 |
|---|---|---|
| 显示性 | 调性稳定、材料统一、句法完整 | 把东西摆出来 |
| 展开性 | 陈述与和声调性都不稳定且越来越动荡，结构分裂，转调频繁，没有完整句法 | 把东西拆开 |
| 过渡性 | 承前启后：先补充前面的乐思 → 转调 → 引出新乐思，或停在一个期待性和弦上 | 搭桥 |
| 收束性 | 旋律片断化、调性稳定、强调终止式或主持续音 | 只答不问 |
| 导入性 | 提示后面的调性、速度、织体、旋律概要 | 只问不答 |
六种结构功能：引子（导入性；也有"结论式引子"，《国际歌》就是）、开始（显示性）、中间（★ 即使引入新主题用的是显示性陈述，功能仍是对比）、 连接（过渡性，大型作品里兼"先展开前面的未尽之言"）、再现（恢复显示性，但目的变成强调主要乐思与恢复平衡；渗入展开因素就是动力再现）、 尾声（收束性；大型作品可在尾声开头先做一次补充性再展开）。
用法：给规格单里每一段写上它是哪种陈述方式。副歌写成了展开性、桥段写成了显示性，就是段落功能错位，换名字救不了。
6.2 再现部的五种形态（李吉提 p0066、p0070）
| 形态 | 做法 |
|---|---|
| 完全（静止）再现 | 原样 |
| 变化再现 | 改织体或配器，材料不动 |
| 动力再现 | 动机再加工、不稳定节奏、和声介入、织体加厚、力度加强，常导致结构扩充甚至成为全曲总高潮 |
| 综合再现 | 同时把中部或引子的材料一起再现 |
| 减缩再现 | 只再现一部分 |
末段副歌"怎么变"的答案就在这张表里，lw-structure §6.0 的末段微变是它在词那一侧的对应。
★ 再现不必在主调上：巴赫的再现时常在属调或下属调，只要段落各部分与呈示段相对应就叫再现（赵晓生 p0232）。
6.3 乐思怎么发展，曲式怎么组合（李吉提）
乐思怎么发展（加工处理、展衍、对比三路，与十种手法的对应）归 mc-development §5.1；曲式怎么组合仍在本 skill §2 与 reference §4。
7. 与 ARR-SPEC 的字段对应
| 字段 | 本 skill |
|---|---|
form[].id | §1 的术语体系（I/A1/B1/C1/D/O） |
form[].name | ★ 用英美术语（Intro/Verse/Pre-Chorus/Chorus/Bridge/Instrumental/Outro），因为它直接映射后端的段落标签。日式术语只在笔记和沟通里用 |
form[].bars | §2 的模板给默认值；打破默认归 mc-arrangement-arch |
form[].start_bar | 首尾相接（lint #2） |
| 段落数 | §2.2 的 2–3 个节 |
★ 一个映射陷阱：大サビ 要映射成 Bridge，不是 Chorus。
映射错了，后端会在那个位置给你一个高能量副歌，而它本该是内省的。
8. 写完后必过
- 术语用的是英美那套填
form[].name，日式术语只在注释里 - 大サビ 映射成了 Bridge，不是 Chorus
- 全曲 2–3 个节，时长 3–5 分钟（或说得出为什么不是）
- 用了省略重复规则（第 2 节省掉开头重复）
- 相邻段落在六项对比里至少有两项不同
- 是从サビ倒推设计的，不是从头往后排
- 想加段落之前，先试过乐节重复
- サビ 的后半也有高潮，不只是开头有冲击
- 若用三部曲式，B 的性格是剧变的
附：来源
- 日式包
jp-song-structure——§1–§5 主干。 已移出的部分：段落对比的具体技法 → reference.md； hook 设计与高潮/结尾 →mc-arrangement-arch§7、§8； 反予定調和清单 →mc-melody§8。 - 吴祖强《曲式与作品分析》——§6 古典曲式装置的主干。
- 伦纳德/论曲式、 中央音乐学院曲式例集——谱例来源。
- 李吉提《曲式与作品分析》（中央音乐学院远程教育丛书，十六讲；）—— 中国传统音乐的组织逻辑与西方的"再现原则"根本不同，提纲见 reference.md §5。
© jtydhr88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/music-composition/skills/mc-form of jtydhr88/music-composition-skills.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 7adca0c
Compare with similar skills
Mc Form next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mc Form this skilljtydhr88/music-composition-skills | 151 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Form Fillingasgeirtj/system_prompts_leaks | 69k | — | ~400 | Automated safety check: Pass | CC0-1.0 | |
| Form Validationthedaviddias/Front-End-Checklist | 74k | — | ~633 | Automated safety check: Pass | MIT | |
| Formstrycompai/comp | 2k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Form Httpsthedaviddias/Front-End-Checklist | 74k | — | ~552 | Automated safety check: Pass | MIT | |
| Telemetry Standardssupabase/supabase | 111k | — | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Form Validation
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Validate forms accessibly.
Forms
trycompai/comp
A skill your agent uses when building forms - covers React Hook Form, Zod validation, and form patterns
Form Https
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing HTML forms, fetch/XHR calls, and form action attributes to ensure data is submitted exclusively over HTTPS.
- Official
Telemetry Standards
supabase/supabase
PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.
Cpp Coding Standards
affaan-m/ECC
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io).
More from jtydhr88/music-composition-skills
All 29 skills in this repoMc AI Tell Audit
jtydhr88/music-composition-skills
The post-generation AI-tell audit (AI 味诊断). An agent skill from jtydhr88/music-composition-skills.
Mc Arrangement Arch
jtydhr88/music-composition-skills
Arrangement architecture (编曲结构学) - the shape of a track over time rather than its notes.
Mc Case Studies
jtydhr88/music-composition-skills
The corpus layer (语料层) - how real recordings are made to testify for or against the textbook rules.
Mc Development
jtydhr88/music-composition-skills
Thematic development (乐思发展层) - what the theme is and what each section does with it.
Mc Melody
jtydhr88/music-composition-skills
Melody writing (旋律法) - what a melodic line expresses and how to make it singable.
Mc Progressions
jtydhr88/music-composition-skills
Chord progression lookup library (和弦进行速查库) - the eight famous named progressions with their variants and what each one actually does, a mood reverse-lookup, the eight variation techniques that turn…
Questions about Mc Form
What does Mc Form do?
Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus. Mc Form is an agent skill from jtydhr88/music-composition-skills. Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus.
When should I use Mc Form?
Mc Form fits situations like: laying out a song; sections blur together; deciding how many verse-chorus cycles; A bridge is needed.
How do I install Mc Form in Claude Code?
Run `npx skills add jtydhr88/music-composition-skills --skill mc-form -a claude-code`. Or copy the skill folder (plugins/music-composition/skills/mc-form in jtydhr88/music-composition-skills) into .claude/skills/mc-form in your project. Claude Code loads it when a task matches its description.
How do I install Mc Form in Codex?
Run `npx skills add jtydhr88/music-composition-skills --skill mc-form -a codex`. Or copy the skill folder (plugins/music-composition/skills/mc-form in jtydhr88/music-composition-skills) into .agents/skills/mc-form in your project. Codex loads it when a task matches its description.
Can I use Mc Form in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jtydhr88/music-composition-skills --skill mc-form -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mc-form, .gemini/skills/mc-form, .github/skills/mc-form and .opencode/skills/mc-form in your project.
What does Mc Form need to run?
SKILL.md names no scripts, command-line tools or credentials: Mc Form is instructions for the agent only.
Does Mc Form access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mc Form safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mc Form use?
Mc Form is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mc Form use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mc Form?
Skills that share tags, products or a category with Mc Form: Form Filling (asgeirtj/system_prompts_leaks, 69k stars), Form Validation (thedaviddias/Front-End-Checklist, 74k stars), Forms (trycompai/comp, 2k stars) and Form Https (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mc Form?
jtydhr88 (a GitHub user) maintains it in jtydhr88/music-composition-skills, which has 151 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on September 22, 2026.
Source: jtydhr88/music-composition-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.