← ClaudeAtlas

brand-initlisted

One-time interview to capture a jewellery brand's foundation (designer identity, palette, motifs, naming conventions, IP rules). Run once per brand; subsequent design work reads the foundation automatically.
hamedarabuk/jewellery-design-studio · ★ 0 · AI & Automation · score 73
Install: claude install-skill hamedarabuk/jewellery-design-studio
# brand-init ## Purpose Capture a jewellery brand's durable identity once, so every subsequent design piece can read it without the user having to re-explain. This is the analogue of `yt-channel-init` in the youtube-channel-studio repo. A brand foundation is a markdown file at `brands/<brand-slug>/foundation.md`. It is gitignored so personal brand data never ships in the public repo. ## When to invoke Invoke this skill when one of these is true: - The user is starting a new collection or licence pitch and no foundation exists yet at `brands/<brand-slug>/foundation.md`. - The user explicitly asks to "init a brand" or "set up a new brand." - The `design-from-reference` skill reports a missing foundation and the user wants to create one. Do NOT invoke this skill if a foundation already exists at the brand path. To update an existing foundation, edit the file directly or run the skill with the `--refresh` flag (asks each question pre-filled with the current answer; user can keep or change). ## Inputs Required: - `brand_slug`: a short hyphenated identifier for the brand (e.g. `mappin-webb-collection-01`, `emma-atelier`, `my-licensing-pitch-2026`). The skill creates `brands/<brand_slug>/` if it does not exist. Optional: - `brand_name`: the human-readable brand name (e.g. "Mappin & Webb Collection 01"). Defaults to a title-case form of the slug. ## Protocol 1. **Verify the slug.** If `brands/<brand_slug>/foundation.md` already exists, refuse with a one-line message: "F