返回技能列表

genre-creator

bitwize-music-studio
更新于 2 days ago
7 次查看
209
37
209
在 GitHub 上查看
word

关于

This Claude Skill creates new genre documentation files for the bitwize-music library when triggered by specific commands like "/genre-creator" or "add genre." It automatically generates a slug, checks for duplicates, and uses web search to research and populate key facts like origin year and pioneer artists. Developers should use it to consistently add new, verified genre entries with proper file structure.

快速安装

Claude Code

推荐
主要方式
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
插件命令备选方式
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git 克隆备选方式
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/genre-creator

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

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.

GitHub 仓库

bitwize-music-studio/claude-ai-music-skills
路径: skills/genre-creator
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

相关推荐技能

content-collections

Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。

查看技能

polymarket

这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。

查看技能

creating-opencode-plugins

该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。

查看技能

sglang

SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。

查看技能