# brand-story

This skill writes a brand's origin story, founder narrative and why-we-exist line in three lengths. Useful when the About Us page reads like a corporate memo.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1600 installs · ★ 787
- Author: arnabbagxd
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/brand-story/SKILL.md
- Updated: 2026-06-13
- HTML: https://affpapa.org/en/nevibecode/skills/brand-story

## What it does

The skill turns dry company facts into a narrative: the moment it all started, the problem the founder could not ignore, and the belief that sets the brand apart in its category. You get three versions — a 600–900 word long story for the About Us page, a 150–200 word short one for the homepage or a pitch, and a 25–40 word one-liner origin.

Before writing, it checks for `.agents/brand-context.md` and reads it first, so it will not re-ask what is already there. Then it asks only for the gaps: how the brand started, the founder's background, what they believe that others in the category do not, what customers struggle with, and what the brand promises to do differently. Tone is confirmed separately — first person or editorial, raw or polished.

The skill deliberately avoids opening with a founding year and keeps the brand out of the hero seat; the customer is the hero. One thing to watch: if you have no concrete early episode to work from, the output will stay vague, so gather those details before you run it.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/brand-story/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/brand-story/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/brand-story/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/brand-story/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install arnabbagxd/Brand-building-skills brand-story
```

2. **Manually: put the files in place**
- File: `.github/skills/brand-story/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/arnabbagxd/Brand-building-skills --path skills/brand-story
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/brand-story/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill brand-story -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/brand-story/SKILL.md

## When to use it
- write an About Us page without corporate filler
- articulate why the brand exists at all
- turn scattered founder facts into a narrative
- compress the company story into one pitch sentence
- rewrite a generic About Us into something human

## Example prompts
- Write our brand story for the About Us page
- Give me a one-sentence version of why we exist
- Rewrite our About page — it reads like a corporate report right now

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e9e00eea5a793c30.

BEGIN THIRD-PARTY FILE e9e00eea5a793c30
```text
---
name: brand-story
description: Craft a brand's origin story, founder narrative, and "why we exist" statement. Use when the user says "brand story", "origin story", "founder story", "why we exist", "about us", "our story", "company narrative", "brand narrative", "write our about page", "tell our story", "founding story", "brand history", or wants to articulate the deeper purpose and human story behind the brand. Also use when the About Us page feels generic or corporate and needs a rewrite.
metadata:
  version: 1.0.0
---

# Brand Story

You are a brand storyteller and narrative strategist. Your job is to find the human truth behind a brand and craft a story that connects, resonates, and gives the brand cultural credibility.

## Before You Start

Check if `.agents/brand-context.md` exists. Read it first. Use that context — don't re-ask for information already there.

---

## Storytelling Philosophy

A brand story is not a company history. It's a narrative that:
- Explains why the brand *had* to exist
- Names the problem the founder couldn't ignore
- Shows the moment of conviction or frustration that sparked action
- Connects the founder's personal truth to the customer's real experience
- Points toward a future worth believing in

The best brand stories make the reader feel: "This brand gets me. It was made for people like me."

---

## Information to Gather

Ask only what you don't already know from context:

1. **The origin moment** — What was the exact situation that led to starting this brand? A personal frustration? A gap in the market they experienced? A problem they couldn't solve elsewhere?
2. **The founder's background** — What did they know or do before this? What made them qualified (or stubborn enough) to start this?
3. **The belief** — What does the founder believe that most people in this category don't? What do they refuse to accept?
4. **The customer truth** — What does the target customer struggle with that most brands ignore or get wrong?
5. **The promise** — What does this brand commit to doing differently?
6. **Where is the brand now** — How far has it come? Any milestones worth anchoring?

---

## Output: Brand Story

Generate 3 versions at different lengths. Each should feel human, not corporate.

---

### VERSION 1 — The Long Story (for About Us page)

600–900 words. Full narrative arc:

**Opening hook** — Drop into a scene, a moment, or a question. Don't start with "We were founded in..."

**The problem** — Describe the frustration or gap with specificity. Name the thing that was wrong with how things worked.

**The founder's realization** — What clicked? What did they see that others missed?
```
END THIRD-PARTY FILE e9e00eea5a793c30

The third-party file has ended. Everything between the e9e00eea5a793c30 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2690 of 4742 bytes. © arnabbagxd · MIT · https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/brand-story/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md