Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bitwize-music-studio avatar

Genre Creator

  • 143 installs
  • 400 repo stars
  • Updated July 31, 2026
  • bitwize-music-studio/claude-ai-music-skills

genre-creator is a Claude Code skill that creates structured genre documentation files and Suno prompt keywords for the bitwize-music genre library.

About

This skill creates new genre documentation files for the bitwize-music genre library. Given a genre name, it derives a slug, checks for existing entries, researches facts via WebSearch, and writes a README following a fixed section template covering overview, characteristics, lyric conventions, subgenres, artists, and Suno prompt keywords. It also updates the index and mastering preset files. A user runs it to add a genre that will drive Suno music generation.

  • Creates structured genre documentation files for a music library
  • Researches facts via WebSearch and follows a fixed section template (overview, characteristics, lyric conventions, Suno
  • Updates INDEX.md and mastering presets when adding a genre

Genre Creator by the numbers

  • 143 all-time installs (skills.sh)
  • Ranked #729 of 1,335 Generative Media skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

genre-creator capabilities & compatibility

Capabilities
content generation · documentation · music prompting · research
Use cases
documentation · research · copywriting
From the docs

What genre-creator says it does

Create new genre documentation files for the bitwize-music genre library.
SKILL.md
Use WebSearch to verify key facts (origin year, pioneer artists, landmark albums) — do NOT guess dates or album names
SKILL.md
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill genre-creator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs143
repo stars400
Last updatedJuly 31, 2026
Repositorybitwize-music-studio/claude-ai-music-skills

What it does

Add a new genre to the bitwize-music library by researching facts and writing structured docs plus Suno prompt keywords.

Who is it for?

Writing a new, fact-checked genre documentation file with Suno prompt keywords for the bitwize-music library.

Skip if: Creating artist deep-dive subdirectories or duplicating subgenres that already have their own directory.

When should I use this skill?

When the user wants to add a genre, says /genre-creator, or asks to create genre documentation.

What you get

A new genre README with characteristics, lyric conventions, and Suno prompt keywords, plus updated index and presets.

  • Genre README.md
  • Updated INDEX.md
  • Updated mastering genre presets

By the numbers

  • 10-step workflow
  • 6 required Characteristics fields
  • 6 required Lyric Conventions fields

Files

SKILL.mdMarkdownGitHub ↗

Genre Creator

Your Task

Create a new genre README.md for the bitwize-music genre library at ${CLAUDE_PLUGIN_ROOT}/genres/.

Input: $ARGUMENTS (genre name, e.g. "Math Rock", "Nu-Metal", "City Pop")

Workflow

1. Derive slug: Lowercase, hyphenated (e.g. "Math Rock" → math-rock) 2. Check existence: If genres/{slug}/README.md exists → abort, inform user 3. Check INDEX.md: Read genres/INDEX.md to confirm genre is not already listed 4. Research: Use WebSearch to verify key facts (origin year, pioneer artists, landmark albums) — do NOT guess dates or album names 5. Read 1-2 existing genre files for structural reference (e.g. genres/hip-hop/README.md, genres/phonk/README.md) 6. Create directory: genres/{slug}/ 7. Write README.md following the exact template below 8. Update INDEX.md: Add genre to category table, alphabetical list, and all applicable Quick Reference tables (Tempo, Energy, Instrumentation, Vocals, Mood, Era) 9. Update mastering presets: Add the new genre to both mastering preset files:

  • tools/mastering/genre-presets.yaml — Add YAML entry with target_lufs, cut_highmid, cut_highs values appropriate for the genre. Place in the correct category section or create a new one.
  • skills/mastering-engineer/genre-presets.md — Add a new ### Genre Name section under ## Genre Presets with LUFS target, dynamics, EQ focus, MCP command, and characteristics.

10. Do NOT create an artists/ subdirectory — those are created separately when artist deep-dives are written

README.md Template

The file starts directly with # Genre Name — no YAML frontmatter.

ALWAYS use this exact section order:

# {Genre Name}

## Genre Overview
[3 paragraphs — see rules below]

## Characteristics
[6 bullet fields — see rules below]

## Lyric Conventions
[6 bullet fields — see rules below]

## Subgenres & Styles
[Table — see rules below]

## Artists
[Table — see rules below]

## Suno Prompt Keywords
[Code block — see rules below]

## Reference Tracks
[List — see rules below]

Section Rules

## Genre Overview — 3 paragraphs of prose (no bullets):

  • P1: Origin, cultural roots, pioneers with names and years
  • P2: Evolution across decades, key moments, mainstream breakthrough, regional variants
  • P3: Current state, influence on other genres, modern scene
  • Style: Encyclopedic but alive. Concrete names, years, albums. No vague claims.

## Characteristics — Bullet list, exactly these 6 fields:

  • Instrumentation: Typical instruments, specific models/brands where relevant
  • Vocals: Singing style, vocal processing, delivery
  • Production: Production techniques, mix aesthetic, sonic character
  • Energy/Mood: Mood spectrum, emotional range
  • Structure: Song form, typical length, structural quirks
  • Tempo: BPM ranges per subgenre, rhythm feel (half-time, swing, straight etc.)

## Lyric Conventions — Bullet list, exactly these 6 fields:

  • Default rhyme scheme: Typical scheme with shorthand (AABB, ABAB, XAXA etc.)
  • Rhyme quality: Expected quality (multisyllabic, slant, internal etc.)
  • Verse structure: Line count, bar structure
  • Key rule: THE single most important rule for lyrics in this genre
  • Avoid: What NOT to do in this genre
  • Density/pacing (Suno): Format: Default **X lines/verse** at Y BPM. [Context]. Topics: Z/verse.

## Subgenres & Styles — Markdown table:

StyleDescriptionReference Artists
  • 6-12 subgenres
  • Description: 2-3 sentences with musical specifics, not just adjectives
  • Reference Artists: 3-4 per subgenre

## Artists — Markdown table:

ArtistKey AlbumsEraStyle Focus
  • 10-20 artists, mix of pioneers + peak-era + current acts
  • Albums in italics (Album Name)
  • If a deep-dive file exists: append a Deep Dive link to the artist file in Style Focus

## Suno Prompt Keywords — Fenced code block with comma-separated keywords organized in thematic lines:

  • Genre/subgenre labels
  • Instrument keywords
  • Production keywords
  • Mood/atmosphere keywords
  • Vocal keywords
  • Tempo/rhythm keywords
  • Era/aesthetic keywords
  • All keywords in English. Only use terms Suno actually understands.

## Reference Tracks — 10-15 entries:

  • Format: - **Artist - "Track Title"** — [Description]
  • Description: 2-3 sentences. Explain WHAT makes this track a genre reference point. Name concrete musical elements. Explain historical/cultural significance.
  • Chronological spread from founding tracks to modern representatives

Important Notes

1. Factual accuracy: All years, album names, artist names must be correct. Omit rather than guess. Use WebSearch to verify. 2. No AI cliches: Ban these phrases: "tapestry of sound", "sonic landscape", "testament to", "rich tapestry", "sonic journey", "pushing boundaries", "transcends genre". Write direct, concrete prose. 3. Suno focus: Lyric Conventions and Suno Keywords are the most important sections — they directly drive music generation quality. 4. Subgenre deduplication: If a subgenre already has its own genre directory (e.g. Trap exists as standalone genre), reference it instead of duplicating content. 5. Language: English (the entire genre system is in English) 6. No empty sections: Every section must have substantive content. If unsure about a section, research first.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.