← ClaudeAtlas

song-structurelisted

Plans or edits song form, including section order, bar counts, hook timing and runtime. Use when the user asks where sections should go, what to cut, or how to meet a target duration.
Vocaler-AI/music-skills · ★ 3 · AI & Automation · score 77
Install: claude install-skill Vocaler-AI/music-skills
# Song Structure Architect Plans the form of a song bar by bar: when the chorus hits, how energy rises and where a bridge or drop earns its place. ## When to use - Planning a song before writing it. - A song feels long, flat or slow to get going. - Adapting a song to a target length (radio edit, 60-second short, extended mix). ## What to look for in the request - Genre and listening context, tempo, meter and the note value counted by the BPM. - Existing sections or timestamps, including any pickup, count-in or tail that counts toward runtime. - Target duration, hook deadline, required sections and any tempo or meter changes. Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely. Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of. Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree. ## Workflow 1. For an edit, map the c