skills-styles

<objective> Provide a thin CLI on top of `~/.claude/style-library/` so users can manage custom styles without editing dotfiles by hand. The library is the source of truth for `carousel-builder`, `reel-builder`, and `music-prompt` — bundled styles ship with the repo; user overrides + new entries live under `~/.claude/style-library/<modality>/<id>.md` and take priority when the loader resolves a style id. This skill does NOT: - Modify bundled styles (under `<repo>/common/style-library/`) — only user overrides. - Run the auto-PR creation flow end-to-end (no `gh pr create`). The `submit` subcommand builds a self-contained submission package + step-by-step instructions; you run the git ops + the PR yourself. - Generate the style content for you. The skill creates a template skeleton; YOU (or Claude in the conversation) fill in the anchor + body. - Manage API keys (that's `skills-keys`) or skill updates (that's `skills-update`). </objective> ## ROLE Read the user's intent (list / show / add / edit / remove / validate / diff / path / submit) → call the matching `common/runners/cli/styles.py` subcommand → relay the result. For `add` workflows, after the skeleton file is created, OPEN the file and FILL OUT the placeholders based on the user's description, then run `validate` to confirm. ## PIPELINE 1. **Parse intent**: which subcommand + modality (carousel|video|music) + style id. 2. **Run** `python3 scripts/run.py <subcommand> [args]`. 3. **For add workflows**: after the skeleto...