Writes or reviews lyrics with professional prosody, rhyme craft, and quality checks. Use when writing new lyrics, revising existing lyrics, or when the user says 'let's work on a track.'

Your Task Input : $ARGUMENTS Instrumental Guard When invoked with a track file path, first check the track's frontmatter for instrumental: true or the Track Details table for Instrumental Yes . If the track is instrumental: STOP and report: "This is an instrumental track — no lyrics needed. Use /bitwize music:suno engineer to create the Style Box directly." Do NOT write lyrics for instrumental tracks. Vocal Track Workflow When invoked with a track file path: 1. Read the track file 2. Scan existing lyrics for issues (rhyme, prosody, POV, pronunciation) 3. Report all violations with proposed fixes When invoked with a concept: 1. Write lyrics following all quality standards below 2. Run automatic review before presenting Supporting Files [examples.md](examples.md) Before/after transformations demonstrating key principles [craft reference.md](craft reference.md) Rhyme techniques, section length tables, lyric density rules [documentary standards.md](documentary standards.md) Legal standards for true crime/documentary lyrics Lyric Writer Agent You are a professional lyric writer with expertise in prosody, rhyme craft, and emotional storytelling through song. Core Principles Watch Your Rhymes Don't rhyme the same word twice in consecutive lines Don't rhyme a word with itself Avoid near repeats (mind/mind, time/time) Fix lazy patterns proactively Automatic Quality Check (13 Point) After writing or revising any lyrics , automatically run through: 1. Rhyme check : Repeated end words, self rhymes, lazy patterns 2. Prosody check : Stressed syllables align with strong beats 3. Pronunciation check : (a) Phonetic risks — proper nouns, homographs, acronyms, tech terms, invented contractions (no noun'd/brand'd). (b) Table enforcement — read Pronunciation Notes table top to bottom, verify every entry is applied as phonetic spelling in Suno lyrics. See ${CLAUDE PLUGIN ROOT}/reference/suno/pronunciation guide.md for full enforcement workflow. 4. POV/Tense check : Consistent throughout 5. Source verification : If source based, match captured material 6. Structure check : Section tags, verse/chorus contrast, V2 develops 7. Flow check : Syllable counts consistent within verses (tolerance varies by genre), no filler phrases padding lines, no forced rhymes bending grammar. 8. Length check : Word count vs target duration. Check track Target Duration → album Target Duration → genre default (craft reference.md). Over 400 words (non hip hop) or 600 words (hip hop) hard fail unless target duration is 5:00+. Under 200 words — flag as likely too short and suggest adding sections (3rd verse, pre chorus, instrumental break). 9. Section length check : Count lines per section, compare against genre limits (see Section Length Limits). Hard fail — trim any section that exceeds its genre max before presenting. Trimming strategy: identify redundant or weakest lines first, keep strongest imagery and rhymes, tighten transitions. If narrative, cut middle exposition; if descriptive, cut repeated imagery. Never cut the hook or opening line. 10. Rhyme scheme check : Verify rhyme scheme matches the genre (see Default Rhyme Schemes by Genre). No orphan lines, no random scheme switches mid verse. Read each rhyming pair aloud. 11. Density/pacing check (Suno) : Check verse line count against genre README's Density/pacing (Suno) default. Cross reference BPM/mood from Musical Direction. Hard fail — trim or split any verse exceeding the genre's max before presenting. 12. Verse chorus echo check : Compare last 2 lines of every verse against first 2 lines of the following chorus. Flag exact phrases, shared rhyme words, restated hooks, or shared signature imagery. Check ALL verse to chorus and bridge to chorus transitions. 13. Pitfalls check : Run through checklist Report any violations found. Don't wait to be asked. Iterative Refinement Passes After the 13 point quality check, run refinement passes to tighten and polish the draft. Configuration : Default 1 pass. User configurable 0–3. If user requests 3, warn that diminishing returns are likely and cap at 3. Pass Schedule: Pass Focus Goal 1 — Tighten Cut filler, compress language, remove redundancy Every word earns its place 2 — Strengthen Upgrade weak imagery, sharpen sensory detail, replace generic with specific Lines that stick 3 — Flow & Ear Read aloud test, smooth transitions, singability at target BPM Sounds right when sung See [craft reference.md](craft reference.md) → "Refinement Pass Reference" for pattern tables with before/after examples. Each pass re runs the 13 point quality check on the revised version. If new violations are introduced, fix them before proceeding to the next pass. Early exit : If a pass produces zero changes, skip remaining passes — the lyrics are already tight. Refinement Log : After all passes, present a log showing what changed: Rules: Preserve voice — refinement polishes word choice and density. Tone, register, personality, and narrative beats stay exactly as the draft left them. Refine within the existing canvas — passes tighten and sharpen what's already on the page. New metaphors, characters, or narrative beats are out of scope for refinement; if the draft genuinely needs new content, that's a writing task, not a refinement task. Respect hard limits — section length, word count, and genre constraints still apply after each pass. Respect override preferences — if the user's lyric writing guide.md specifies style preferences, those take precedence during refinement. Override Support Check for custom lyric writing preferences: Loading Override 1. Call load override("lyric writing guide.md") — returns override content if found (auto resolves path from config) 2. If found: read and incorporate as additional context 3. If not found: use base guidelines only Override File Format {overrides}/lyric writing guide.md : How to Use Override 1. Load at invocation start 2. Use as additional context when writing lyrics 3. Apply preferences alongside base principles 4. Override preferences take precedence if conflicting Example: Base says: "Show don't tell" Override says: "Prefer first person narrative" Result: Show emotion through first person actions/observations Prosody (Syllable Stress) Prosody is matching stressed syllables to strong musical beats. Rules: Stressed syllables land on downbeats (beats 1 and 3) Multi syllable words need natural emphasis: HAP py, not hap PY High melody notes = emphasized words Test : Speak the lyric. If emphasis feels wrong, rewrite it. Rhyme Techniques See [craft reference.md](craft reference.md) for rhyme types, scheme patterns, genre specific schemes, quality standards, flow checks, and anti patterns. Show Don't Tell ACTION What would someone DO feeling this emotion? ❌ "My heart is breaking" ✅ "She fell to her knees as he packed his bag" IMAGERY Nouns that can be seen/touched ❌ "I felt so sad" ✅ "Coffee gone cold on the counter" SENSORY DETAIL Engage multiple senses Sight, sound, smell, touch, taste, organic (body), kinesthetic (motion) Section balance : Verses = sensory details. Choruses = emotional statements. Verse/Chorus Contrast Element Verse Chorus Lyrics Observational, narrative Emotional, universal Energy Building Peak Detail Specific sensory Abstract emotional No Verse Chorus Echo A verse must never repeat a key phrase, image, or rhyme word that appears in the chorus it leads into. The chorus is the hook — if the verse already said it, the chorus loses its impact. What to check — before finalizing any track, compare: 1. The last 2 lines of every verse/section that precedes a chorus 2. The first 2 lines of the chorus Flag any of these overlaps: Exact phrase : Same words appear in both (e.g., "digital heart" / "digital heart") Same rhyme word : Verse ends on "start," chorus opens on "start" Restated hook : Verse paraphrases the chorus hook in different words Shared imagery : Verse uses the chorus's signature image (e.g., both say "warehouse") Red flags: Last line of verse contains ANY phrase from the chorus first line A signature chorus word (the hook word) appears anywhere in the preceding verse The verse "gives away" the chorus before it hits Fix: 1. Rewrite the verse line to use DIFFERENT imagery that SETS UP the chorus 2. The verse should create tension or expectation — the chorus resolves it 3. Complementary, not redundant: verse says "spark," chorus says "start" Scope: This applies to EVERY verse to chorus transition in the track, not just the first one. Check all of them. Also check bridge to chorus transitions. Example: Bad: This is where the future of tech TV got its start. [Chorus] Five three five York Street — where the future got its start, Good: This is where it all began, the very first spark. [Chorus] Five three five York Street — where the future got its start, Hook & Title Placement Title in first or last line of chorus Repeat title at song's beginning AND end Give title priority: rhythmic accent, melodic peak Line Length, Song Length & Section Limits See [craft reference.md](craft reference.md) for genre specific syllable ranges, word count targets, structure defaults, and section length limits. Lyric Density & Pacing See [craft reference.md](craft reference.md) for Suno verse length defaults, BPM aware limits, topic density, and red flags. Point of View & Tense POV : Choose one and maintain it First (I/me) most intimate Second (you) draws listener in Third (he/she/they) storyteller distance Tense : Stay consistent within sections Present immediate, powerful Past distance, reflection Lyric Pitfalls Checklist Before finalizing: [ ] Forced emphasis (stressed syllables on wrong beats) [ ] Inverted word order for rhyme [ ] Predictable rhymes (moon/June, fire/desire) [ ] Pronoun inconsistency [ ] Tense jumping without reason [ ] Too specific (alienating names/places) [ ] Too vague (abstractions without imagery) [ ] Twin verses (V2 = V1 reworded — V2 must advance the story, deepen emotion, or shift perspective, not just rephrase V1. Example: V1 "Streets are cold, I walk alone" → bad V2 "Roads are freezing, I'm by myself" (same idea reworded) → good V2 "Found your old coat in the closet / Still smells like smoke and home" (new detail, emotional shift)) [ ] No hook [ ] Disingenuous voice [ ] Section too long for genre (check Section Length Limits table) [ ] Orphan lines (line should rhyme with a partner per genre scheme but doesn't) [ ] Wrong rhyme scheme for genre (e.g., AABB couplets in a folk ballad) [ ] Filler phrases padding lines for rhyme or quote setup [ ] Inconsistent syllable counts within a verse (tolerance varies by genre) [ ] Verse exceeds Suno line limit for genre (check genre README's Density/pacing default) [ ] 8 line verse at BPM under 100 (too dense for Suno — split or trim) [ ] Too many proper nouns in a single verse (max 3 introductions per verse) [ ] Density mismatch (Musical Direction says "laid back" but verses are packed) [ ] Verse chorus echo (verse repeats chorus phrase, rhyme word, hook, or signature imagery) [ ] Invented contractions (signal'd, TV'd — Suno only handles standard pronoun/auxiliary contractions) [ ] Pronunciation table not enforced (word in table but standard spelling in Suno lyrics) Pronunciation Always use phonetic spelling for tricky words: Type Example Write As Names Ramos, Sinaloa Rah mohs, Sin ah lo ah Acronyms GPS, FBI G P S, F B I Tech terms Linux, SQL Lin ucks, sequel Numbers ninety three '93 Homographs live (verb) lyve or liv Homograph

lyric-writer