configure

## 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 ...