Author the brand strategy substrate BEFORE any visual generation — a discovery questionnaire → positioning statement, value proposition, target audience, and archetype — then bulk-draft business/product names + taglines and hand a human-curated shortlist. Owns the strategy-before-visuals gate artifact. Naming availability + trademark collisions route to security-reviewer; not legal advice.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brand-identity-studio:brand-strategy-and-namingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The first and most expensive brand decision: what the brand *means* and what it's *called*. Everything
The first and most expensive brand decision: what the brand means and what it's called. Everything downstream — the logo, the palette, the type, the brand book — is directed against this. Author it deliberately, because a fuzzy position generates slop no matter how good the model is.
Strategy is authored, naming is curated. Neither is auto-generated as a final answer. AI explores; the human decides. Any naming-availability or trademark-collision judgment is routed to
ravenclaude-core:security-reviewer(and counsel) — this skill states facts, not legal conclusions. Prices[unverified].
../../templates/brand-strategy-brief.md:
positioning statement, value proposition, target audience, competitive frame, and archetype (with the
rejected alternatives named). This file is the strategy-before-visuals gate artifact — no visual
concept is generated until it exists.security-reviewer.identity-systems-designer to direct the visual system against.| # | Question | Why it matters |
|---|---|---|
| 1 | What does the business actually do, in one sentence a stranger understands? | Kills jargon; forces clarity |
| 2 | What is the real alternative the customer is choosing you over (incl. "do nothing")? | Positioning is against the alternative, not a category |
| 3 | Who is the target customer — specifically (not "everyone")? | Audience precision drives voice + visual register |
| 4 | What emotional job does the brand do (status, safety, belonging, rebellion)? | Picks the archetype |
| 5 | Three brands you admire and why — and three you never want to resemble | Constraint donors: "like Stripe but warmer, avoid blue" |
| 6 | What must NEVER be true of this brand? | Negative constraints escape the legible middle |
| 7 | Where does the brand live (site, packaging, app, retail)? | Fixes which identity assets are in scope |
For [target audience] who [need/context], [brand] is the [category/frame] that [key benefit / point of difference] — unlike [the real alternative] — because [reason to believe].
Write it, then pressure-test: could a competitor claim the same sentence? If yes, it's not a position.
The 12 brand archetypes (Hero, Sage, Explorer, Creator, Ruler, Magician, Innocent, Everyman, Jester, Lover,
Caregiver, Outlaw) are a starting lens, not a horoscope. Pick one primary + at most one secondary; name why
the tempting alternatives were rejected. The archetype constrains voice and visual register — it is a design
input, not a personality quiz. Traverse the tier-selection tree in
../../knowledge/brand-decision-trees.md if the engagement scope is
still open.
Screen each candidate on:
.com/handle plausibly obtainable; obvious TM collision flagged to
security-reviewer (a real clearance search is counsel's job, not this skill's).Present the shortlist with the rubric scores + the trade-offs, and let a human choose. Naming types: coined (Kodak), real-word (Apple), compound (Facebook), descriptive (weak TM), evocative (Nike). Note the type per candidate.
npx claudepluginhub mcorbett51090/ravenclaude --plugin brand-identity-studioGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Forks private projects, strips secrets/internal references, verifies cleanliness, and packages them with CLAUDE.md, README, and setup.sh for safe public release.