album-conceptualizer
Album concepts, tracklist architecture, and thematic planning
Best use case
album-conceptualizer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Album concepts, tracklist architecture, and thematic planning
Teams using album-conceptualizer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/album-conceptualizer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How album-conceptualizer Compares
| Feature / Agent | album-conceptualizer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Album concepts, tracklist architecture, and thematic planning
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## 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. Read `~/.bitwize-music/config.yaml` → `paths.overrides`
2. Check for `{overrides}/album-planning-guide.md`
3. If exists: read and incorporate preferences
4. If not exists: 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
```
### How to Use Override
1. Load at invocation start
2. Apply track count preferences when planning
3. Respect structural requirements (include/avoid)
4. Favor preferred themes, avoid specified themes
5. Override preferences guide but don't restrict creativity
**Example:**
- User prefers 10-12 tracks
- User wants intro/outro always
- Result: Plan 12-track album with intro and outro tracks
---
## Album Types Summary
See [album-types.md](album-types.md) for detailed planning approaches.
| Type | Definition | Key Questions |
|------|------------|---------------|
| **Documentary** | Real events, factual storytelling | Timeline, sources, angle |
| **Narrative** | Fictional story across tracks | Protagonist, conflict, arc |
| **Thematic** | United by theme, not plot | Sub-themes, emotional journey |
| **Character Study** | Deep dive into a person | Aspects, time periods, through-line |
| **Collection** | Standalone songs, loose connection | Unifying element, flow |
---
## Tracklist Architecture
### Opening Track
- Immediate impact (within 30 seconds)
- Represents album's core identity
- Best introduction, not necessarily "best" track
### Closing Track
- Emotional payoff
- Thematic conclusion
- Leaves listener satisfied but wanting more
### Middle Tracks
- Avoid two slow songs in a row
- Vary tempos and energy
- Place strongest tracks at 3, 7, and 10
### The "Heart" of the Album (Track 5-7)
- Most important thematic statement
- Emotional centerpiece
- What the album is "really about"
---
## Pacing & Dynamics
### Energy Mapping
Map album energy as a curve with peaks and valleys.
**Avoid**: Flatline energy (all medium)
**Aim for**: Builds and releases
### Tempo Variation
Don't cluster all fast or all slow songs.
### Emotional Variation
Balance heavy and light - serious → playful → serious creates palette cleanser effect.
---
## Building the Album: Step-by-Step
### Phase 1: Foundation (Questions)
1. **Type**: Documentary, narrative, thematic, character study, collection?
2. **Scale**: EP (4-6), standard (8-12), double album (15+)?
3. **Genre**: What sonic palette?
4. **Theme/Story**: Central idea/event/character?
5. **Audience**: Who is this for?
### Phase 2: Concept Deep Dive
- **Documentary**: Research phase, key events, angle
- **Narrative**: Character, plot, emotional arc
- **Thematic**: Central theme, sub-themes, motifs
### Phase 3: Track Breakdown
- How many tracks can tell this concept?
- What does each track cover?
- Working titles, core focus, connection to whole
### Phase 4: Sequencing
1. Lay out all tracks in rough order
2. Check energy flow - map highs and lows
3. Check thematic flow - does story/theme progress?
4. Identify opener and closer
5. Place centerpiece (tracks 5-7)
6. Adjust for pacing
### Phase 5: Refinement
- Does every track earn its place?
- Is anything redundant?
- Are there gaps in the story/theme?
- Does opener hook? Does closer satisfy?
---
## Thematic Coherence
### Motifs & Callbacks
- **Lyrical motifs**: Repeated phrases, images, metaphors
- **Sonic motifs**: Recurring sounds, instruments, melodies
- **Structural motifs**: Parallel song structures
### Title Tracks
**When to have**: Album name is core concept, title track explicates it
**When not**: Album name is abstract, no single track captures full concept
---
## Questions to Ask the Artist
**Concept**:
- What are you trying to say?
- Why does this need to be an album vs single tracks?
- What do you want listeners to feel?
**Sonic**:
- What should it sound like?
- Reference albums/artists?
- Consistent genre or varied?
**Scope**:
- How many tracks feels right?
- How deep into this topic?
---
## Working with Workflow
### Creating Album Files
Once concept is solid, create:
1. `artists/[artist]/albums/[genre]/[album]/README.md` - Album overview
2. **RESEARCH.md** (if source-based) - Consolidated research
3. **SOURCES.md** (if source-based) - Bibliography
4. `tracks/XX-track-name.md` - Individual track files
---
## Workflow
As the album conceptualizer, you:
1. **Understand the vision** - What's the album about? What type?
2. **Develop theme** - Define central concept, emotional arc, motifs
3. **Define sonic direction** - Choose genre, style, production approach
4. **Structure tracklist** - Plan sequencing, pacing, track flow
5. **Plan visual concept** - Coordinate with album-art-director for artwork
6. **Create documentation** - Album README with concept, tracks, metadata
7. **Deliver blueprint** - Complete album plan ready for track creation
---
## Remember
1. **Load override first** - Check for `{overrides}/album-planning-guide.md` at invocation
2. **Apply user preferences** - Track counts, structure requirements, theme preferences
3. **The album is a journey** - Map it before you build it
4. **Know where you're going** - Concept, theme, resolution
5. **Plan the route** - Tracklist, sequencing, flow
6. **Make every stop count** - Each track earns its place
7. **Start strong** - Opener hooks them
8. **End stronger** - Closer leaves them wanting more
**When in doubt, cut.** Better a tight 8-track album than a bloated 15-track slog (unless user override specifies different preferences).Related Skills
album-ideas
Track and manage album ideas - brainstorming, planning, status tracking
album-art-director
Visual concepts for album artwork and AI art generation prompts
bgo
Automated Blender build-go workflow. Automatically builds, removes old version, installs, enables, and launches Blender with your extension/add-on. Use when you want to quickly test changes, execute complete build-to-launch cycle, or run custom packaging scripts with automatic Blender launch.
maintenance
Cleans up and organizes project files. Use when user mentions '整理', 'cleanup', 'アーカイブ', 'archive', '肥大化', 'Plans.md', 'session-log', or asks to clean up old tasks, archive completed items, or organize files. Do NOT load for: 実装作業, レビュー, 新機能開発, デプロイ.
hello-skill
每次对话开始时,声明"[Skills✏️已加载]"
zylvie-automation
Automate Zylvie tasks via Rube MCP (Composio). Always search tools first for current schemas.
zoominfo-automation
Automate Zoominfo tasks via Rube MCP (Composio). Always search tools first for current schemas.
zoho-invoice-automation
Automate Zoho Invoice tasks via Rube MCP (Composio): invoices, estimates, expenses, clients, and payment tracking. Always search tools first for current schemas.
zoho-inventory-automation
Automate Zoho Inventory tasks via Rube MCP (Composio): items, orders, warehouses, shipments, and stock management. Always search tools first for current schemas.
zoho-bigin-automation
Automate Zoho Bigin tasks via Rube MCP (Composio): pipelines, contacts, companies, products, and small business CRM. Always search tools first for current schemas.
zoho_desk-automation
Zoho Desk automation via Rube MCP -- toolkit not currently available in Composio; no ZOHO_DESK_ tools found
zoho-automation
Automate Zoho tasks via Rube MCP (Composio). Always search tools first for current schemas.