Skip to content
Back to skills

Brand Story Builder

ASecurity

Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song.

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 12, 2026
ai-agentsgo

Security analysis

A100/100

Scanned June 12, 2026

npx -y skills add hamza-ali-shahjahan/hamzaish --skill brand-story-builder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brand Story Builder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Brand Story Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hamza-ali-shahjahan-brand-story-builder/badge)](https://www.skillsdirectory.com/skills/hamza-ali-shahjahan-brand-story-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: brand-story-builder
description: Build the brand foundation — positioning, story, voice, naming, visual primitives — so every other launch asset (landing, content, outreach) sings the same song.
---

# Brand Story Builder

## When you activate
- Before a product's first launch
- After a pivot
- When the user says: "what's our story?", "positioning for X", "voice and tone for Y"

## What you produce
Saved to `products/<name>/launch/brand.md`:

```
## Brand — <product>

### Positioning statement (the April Dunford structure)
For <target customer> who <statement of need>, <product name> is the <market category> that <key benefit>. Unlike <primary competitive alternative>, we <key differentiator>.

### Origin story (3 sentences)
<setup — the problem we kept seeing>
<turn — why no one was solving it well>
<commitment — what we're doing about it>

### Voice & tone
- We sound like: <3 adjectives> (e.g., direct, technical, irreverent)
- We don't sound like: <3 adjectives>
- Pet phrases we use: <list>
- Phrases we never use: <list of marketing-jargon we reject>

### Visual primitives
- Color palette: <primary + 2 accents + neutral>
- Typography: <heading font / body font, from `fontsource` or system stack>
- Logo direction: <wordmark | mark+wordmark | letter mark> + <one-line aesthetic>
- Imagery: <photo | illustration | abstract | none>

### Naming check
- Does the name pass: pronounceable, googleable, .com available, no trademark collision in adjacent space, doesn't mean something weird in 3+ languages
- Result: ✅ / ⚠️ / ❌

### Taglines (3 candidates ranked)
1. <tagline> — best for <where>
2. ...
3. ...

### Anti-positioning (what we are NOT)
3 things we explicitly say we don't do.
```

## Protocol
1. Read the product's `prd.md` + `scope.md` + most-recent interview synthesis.
2. Use April Dunford's positioning structure as the spine.
3. Pull the origin story from the founder's actual motivation (ask Hamza if unclear — don't fabricate).
4. Voice: anchor on Hamza's voice from `brain/persona.md`, then nudge based on audience (B2B enterprise = more formal; indie devs = more direct/irreverent).
5. Naming: run the check honestly. If the name fails, recommend 3 alternatives.
6. Anti-positioning is the most underused brand exercise — force it.

## Sources
- `knowledge-base/launch-stage/seo-content-strategy.md` (for naming/SEO interaction)
- `knowledge-base/founders-wisdom/100k-arr-tactics.md`

## What you don't do
- Don't write fluffy "mission statements." If a sentence could be on any startup's About page, delete it.
- Don't pick taglines that are clever but unclear.
- Don't skip the .com availability check.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.