Skip to content

rampstackco/claude-skills / skills/brand-ideation

brand-ideation

Verified

Generate, evaluate, and narrow brand concepts during early ideation including positioning territories, naming candidates, mood directions, and narrative angles. Use this skill whenever the user is in the early phase of brand creation, exploring brand directions, brainstorming names, building moodboards, generating positioning options, or trying to choose between multiple brand directions. Triggers on brand ideation, brand concept, naming, brand name, name candidates, positioning, brand positioning, mood board, brand directions, exploring brands, early brand work, brand exploration, brand brainstorm, brand options. Also triggers when the user has multiple half-formed brand ideas and needs help converging on one, even if they do not say 'ideation' explicitly.

FileKindSize
README.mdmarkdown355 B
SKILL.mdskill md9.4 KB
references/ideation-output-template.mdmarkdown4.6 KB
references/naming-evaluation-rubric.mdmarkdown6.3 KB

references/ideation-output-template.md

View on GitHub
# Brand Ideation Output Template

A fillable template for the ideation deliverable. Captures the candidate names, positioning territories, mood directions, and narrative angles produced during ideation.

The deliverable is not a single answer. It is a structured set of options the team can evaluate, narrow, and combine.

---

## Project metadata

**Brand / project:** [Name]
**Ideation lead:** [Name]
**Date:** [YYYY-MM-DD]
**Inputs used:** [Discovery report, brief, prior decks - link them]

---

## Recap: what we are ideating against

Two to four sentences. Pull from the discovery report. Anyone reading this deliverable cold should know:

- Who the audience is
- What position the brand is trying to take
- What the constraints are (legal, geographic, category)

> [Recap]

---

## Naming candidates

Generate widely first. Filter later. Aim for 30-50 candidates per round before applying the rubric.

### Round 1: divergent

| # | Name | Type | Source / inspiration |
|---|---|---|---|
| 1 | | Coined / descriptive / metaphorical / founder / acronym / compound / portmanteau | |
| 2 | | | |
| 3 | | | |
| ... | | | |

### Round 2: filtered shortlist

After applying the 6-criteria rubric (`naming-evaluation-rubric.md`), the names that survive.

| # | Name | Why it survived | Open concerns |
|---|---|---|---|
| 1 | | | |
| 2 | | | |
| 3 | | | |
| 4 | | | |
| 5 | | | |
| 6 | | | |

### Round 3: top 3 with full case

For each finalist, write a one-page case.

#### Finalist 1: [Name]

- **Pronunciation:** [How it is said]
- **Type:** [Coined, metaphor, etc.]
- **Meaning:** [What it evokes, intentionally or by association]
- **Why it works:** [Per the 6 criteria]
- **Risks:** [Domain availability, trademark, cultural concerns, audience misreading]
- **Domain status:** [.com / alternative TLDs / acquisition cost estimate]
- **Trademark status:** [Cleared by counsel / preliminary search clean / requires deeper search]
- **Visual potential:** [How it could render as a wordmark, monogram, icon]

#### Finalist 2: [Name]

[Same structure]

#### Finalist 3: [Name]

[Same structure]

---

## Positioning territories

The territories from discovery, sharpened into ideation directions. Each territory should produce a distinct creative direction.

### Territory 1: [Name]

- **One-sentence position:** [The territory in a sentence]
- **Voice direction:** [How it sounds]
- **Visual direction:** [How it looks]
- **Headline examples:** [3-5 sample headlines that could only come from this territory]
- **What it rules out:** [Names, treatments, or messages this territory disqualifies]

### Territory 2: [Name]

[Same structure]

### Territory 3: [Name]

[Same structure]

### Territory 4: [Name]

[Same structure]

---

## Mood directions

Three to five mood directions, each with reference imagery, color cues, and a one-line description. These are not final design - they are starting points for art direction.

### Mood 1: [Name, e.g., "Quiet confidence"]

- **Description:** [One line]
- **References:** [3-5 visual references with credit and one-line note on what to take from each]
- **Color cues:** [General feel, not exact palette]
- **Typography cues:** [General feel]
- **Photography or illustration direction:** [General feel]
- **Adjacent brands as reference:** [Not to copy, to triangulate]

### Mood 2: [Name]

[Same structure]

### Mood 3: [Name]

[Same structure]

---

## Narrative angles

Three to five candidate brand stories or origin narratives. Each is a different way of telling who this brand is and why it exists.

### Angle 1: [Name, e.g., "Founder's journey"]

- **Premise:** [The narrative angle in two sentences]
- **First page hero:** [What the homepage hero would say under this angle]
- **About page opening:** [The first paragraph of the about page]
- **Why it works:** [What it earns the brand]
- **Why it might fail:** [Risk]

### Angle 2: [Name]

[Same structure]

### Angle 3: [Name]

[Same structure]

---

## Synthesis: provisional recommendation

Even though ideation produces options, the team should leave with a provisional combination to test next.

> **Provisional combination:** Name [X], territory [Y], mood [Z], narrative [W].
>
> **Why this combination:** [Two sentences.]
>
> **What we test next:** [Concept board, name validation with audience, treatment exploration, etc.]

---

## Open questions

- [ ] [Trademark search needed for finalist names]
- [ ] [Domain acquisition feasibility]
- [ ] [Audience reaction test for top 2 names]
- [ ] [Stakeholder alignment session for territory selection]
- [ ] [Other]

---

## Sign-off

Ideation accepted by:

- [Name, role, date]
- [Name, role, date]

Recommended next phase: [Brand identity / further name validation / board-level review / etc.]
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall