# Configure

Sets up or edits the plugin configuration file interactively.

- Repository: https://github.com/bitwize-music-studio/claude-ai-music-skills (615 stars)
- Category: Engineering
- License: CC0-1.0
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -g -a claude-code -y`
Codex: `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -g -a codex -y`
Cursor: `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -g -a cursor -y`
Gemini CLI: `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add bitwize-music-studio/claude-ai-music-skills`

## Description

Sets up or edits the plugin configuration file interactively. Use on first-time setup, when config is missing, or when the user wants to change settings.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Your Task

**Input**: $ARGUMENTS

Route based on argument:
- `setup` or no argument → Interactive first-time setup
- `edit` → Edit specific settings
- `show` → Display current configuration
- `validate` → Check config for issues
- `reset` → Delete config and start fresh

---

# Plugin Configuration Skill

You help users set up and manage their `~/.bitwize-music/config.yaml` configuration.

## Config Location

```
~/.bitwize-music/config.yaml
```

## Commands

### `/configure` or `/configure setup`

Interactive first-time setup. Guide user through creating their config.

**Steps:**

1. Check if `~/.bitwize-music/config.yaml` exists
2. If exists, ask if they want to overwrite or edit instead
3. If creating new:
   - Create `~/.bitwize-music/` directory if needed
   - Ask for each required setting interactively
   - Write the config file
   - Validate the result

**Required settings to ask:**
1. `artist.name` - "What's your artist/project name?"
2. `paths.content_root` - "Where should albums and projects be stored? (e.g., ~/music-projects)"
3. `paths.audio_root` - "Where should mastered audio files go? (e.g., ~/music-projects/audio)"
4. `paths.documents_root` - "Where should research documents/PDFs go? (e.g., ~/music-projects/documents)"

**Optional settings:**
5. `artist.genres` - "What are your primary genres? (comma-separated, or skip)"
6. `urls.soundcloud` - "SoundCloud profile URL? (or skip)"

**Step 5: Overrides Directory (Optional)**

Ask:
> You can optionally provide a path to a directory containing override files.
> This is where you can customize workflows and skills without plugin update conflicts.
>
> Override files you can create:
>   - CLAUDE.md (custom workflow instructions)
>   - pronunciation-guide.md (artist names, character names)
>   - explicit-words.md (custom explicit word list)
>
> Default: ~/music-projects/overrides
>
> Enter path (or press Enter to use default):

If user provides path:
- Add to config: `paths.overrides: "[user-path]"`

The rest: https://github.com/bitwize-music-studio/claude-ai-music-skills/blob/HEAD/skills/configure/SKILL.md