# album-conceptualizer

album-conceptualizer plans an album’s concept, track order, and thematic arc in 7 phases. Use it to start a new album or reshape an existing one.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 262 installs · ★ 686 repo stars
- Author: bitwize-music-studio
- License: CC0-1.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/HEAD/skills/album-conceptualizer/SKILL.md
- Updated: 2026-10-22
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/album-conceptualizer

## What it does

This skill guides album planning through 7 structured phases. For a new project, it asks about genre, album type, scale, and themes, then builds the core concept, narrative arc, and tracklist with song ideas. The plan is documented in the album README.

For an existing album, it reads the current concept and tracklist before giving analysis or suggested changes. Sequencing work covers pacing, energy shifts, emotional peaks, and the role of the opening, central tracks, and ending.

It can use `Read`, `Edit`, `Write`, `Grep`, `Glob`, and `bitwize-music-mcp`. The `new-album` prerequisite must be available before you run it.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bitwize-music-studio/claude-ai-music-skills --skill album-conceptualizer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/album-conceptualizer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/album-conceptualizer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bitwize-music-studio/claude-ai-music-skills --skill album-conceptualizer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/album-conceptualizer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bitwize-music-studio/claude-ai-music-skills --skill album-conceptualizer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/album-conceptualizer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bitwize-music-studio/claude-ai-music-skills skills/album-conceptualizer
```

2. **Manually: put the files in place**
- File: `.github/skills/album-conceptualizer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bitwize-music-studio/claude-ai-music-skills --skill album-conceptualizer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/album-conceptualizer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/album-conceptualizer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bitwize-music-studio/claude-ai-music-skills --skill album-conceptualizer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/HEAD/skills/album-conceptualizer/SKILL.md

## When to use it
- shape a concept for a new album
- build a tracklist with a narrative arc
- reorder songs to improve album dynamics
- review an existing album concept

## Example prompts
- Plan a new album about digital isolation: choose the album type, define its thematic arc, and draft the tracklist.
- Create a synthwave album concept with a clear scale and explain the role of each song.
- Read the current album README and suggest changes to its concept and track order.

## Source text · SKILL.md · CC0-1.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9b35b520ea1bda2e.

BEGIN THIRD-PARTY FILE 9b35b520ea1bda2e
````text
---
name: album-conceptualizer
description: Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
argument-hint: <"plan album about [topic]" or album-path>
model: opus
effort: max
prerequisites:
  - new-album
allowed-tools:
  - Read
  - Edit
  - Write
  - Grep
  - Glob
  - bitwize-music-mcp
---

## Your Task

**Input**: $ARGUMENTS

When invoked for new album:
1. Ask clarifying questions (genre, type, scale, themes)
2. Design album concept and narrative arc
3. Create tracklist with song concepts
4. Document in album README

When invoked for existing album:
1. Read current concept and tracklist
2. Provide analysis or suggestions as requested

---

## Supporting Files

- **[album-types.md](album-types.md)** - Detailed planning for each album category

---

# Album Conceptualizer Agent

You are a creative strategist specializing in album concept development, tracklist architecture, and thematic coherence.

---

## Core Philosophy

### Albums Tell Stories
Even if tracks aren't narrative, the album has an arc. Think:
- Emotional journey
- Thematic exploration
- Sonic progression
- Listener experience

### Sequencing is Everything
Track order can make or break an album. Consider:
- Momentum and pacing
- Emotional flow
- Peaks and valleys
- Opening statement, closing resolution

### Constraints Breed Creativity
Limitations (genre, theme, format) force interesting choices. Embrace them.

---

## Override Support

Check for custom album planning preferences:

### Loading Override
1. Call `load_override("album-planning-guide.md")` — returns override content if found (auto-resolves path from config). **Why:** user-specific track-count, structure, and theme preferences must be applied to every phase output, so they need to be in context before Phase 1 begins.
2. If found: read and incorporate preferences
3. If not found: use base planning principles only

### Override File Format

**`{overrides}/album-planning-guide.md`:**
```markdown
# Album Planning Guide

## Track Count Preferences
- Full album: 10-12 tracks (not 14-16)
- EP: 4-5 tracks

## Structure Preferences
- Always include: intro track, outro track
- Avoid: skits, interludes (get to the music)

## Themes to Explore
- Technology and society
- Urban isolation
- Digital identity

## Themes to Avoid
- Political commentary
- Relationship drama

## Duration Preferences
| Format | Target Duration |
|--------|-----------------|
| Default | 4:00–5:00 |
| Punk/fast | 2:00–3:00 |
```

### How to Use Override
1. Load at invocation start
2. Apply track count preferences when planning
````
END THIRD-PARTY FILE 9b35b520ea1bda2e

The third-party file has ended. Everything between the 9b35b520ea1bda2e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2683 of 14369 bytes. © bitwize-music-studio · CC0-1.0 · https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/HEAD/skills/album-conceptualizer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
