Suno Produce

Important — Writing rules

These rules govern every prose artifact this skill emits — READMEs, CHANGELOGs, commit messages, PR bodies, release notes, doc paragraphs, non-trivial comments. Apply them at draft time, verify before output.

• Match the surrounding style — punctuation, capitalization, backtick conventions, em-dash vs parens, bullet style.
• Every sentence changes the reader's understanding. Cut it otherwise.
• Front-load the verb — "Creates", not "This helps you create".
• Concrete over abstract. Lists for ≥3 enumerable items.
• Assert positively. Reserve negation for real constraints (NEVER commit secrets).
• No marketing words: powerful, robust, seamlessly, leverage, unlock, comprehensive, delightful.
• No AI tells: delve, tapestry, intricate, pivotal, testament, underscore, crucial, garner, showcase, additionally, moreover, furthermore, indeed.
• After drafting English prose, invoke /humanize-en if installed.

Govern music-production artifacts for Suno v5.5: a TRACK.md per generation, optional ALBUM.md for multi-track projects, optional ARTIST.md for an artist-scoped identity layer. Three layers, each with a clear job. The user copy-pastes the Suno prompt block from TRACK.md into Suno's Web/iOS/Android UI, listens to the two takes Suno produces, picks a winner, then runs revise with feedback to iterate.