skills/marketing/brand-storytelling/SKILL.md
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
npx skillsauth add pedronauck/skills brand-storytellingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user craft compelling narratives that make their brand memorable using techniques from 30 product leaders and storytelling experts.
When the user asks for help with brand storytelling:
Andy Raskin: "This structure is about defining a movement—that's very different from 'I'm going to solve your problem.'" Frame your brand as the leader of a shift toward a new way of winning.
Brian Chesky: "One of the first things we do is figure out what the story is. The story often dictates the product. A story is a helpful way to develop a cohesive product." Define the narrative before finalizing features.
Matthew Dicks: "Every story is about a singular moment—I call it five seconds. A moment of transformation or realization. 98% of the story provides context to make that moment clear." Identify the single moment of change.
Merci Grace: "Every pitch should start in the middle of the action, like Mission Impossible. Tom Cruise is always doing crazy shit before the actual mission. It gets attention." Skip the boring setup—hook them immediately.
Jason Feifer: "Success stories aren't interesting. Problem-solving stories are. Frame your story around a specific challenge you faced and the counterintuitive way you solved it."
Mike Maples Jr: "The customer is the hero (Luke Skywalker), the founder is the mentor (Obi-Wan) providing the tools. Position your product as the lightsaber—the tool the hero needs."
Lulu Cheng Meservey: "Make it memorable. Make people want to say it of their own volition. Use analogies, colorful mental images, jokes. Replace adjectives with anecdotes people can repeat at dinner."
Camille Ricketts: "Effective storytelling paints an emotional picture of the vision. Convey the emotional quality of the mission, not just technical details, to enlist hearts and minds."
Christina Wodtke: "A beginning, middle, and end. Intrigue with a hook—a mystery, secret, or surprise. The middle delivers the message. Always end with success and celebration."
Yuhki Yamashata: "The goal is 'memification'—synthesize insights so they're catchy enough for execs to cite in meetings. Use metaphors to explain complex concepts."
For all 50 insights from 30 guests, see references/guest-insights.md
development
Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
tools
Orchestrate Claude and Codex worker TUIs from a controller agent through herdr panes and the herdr socket CLI. Use when delegating bounded tasks to herdr worker panes, running user-activated plan-first delegations (Claude Code plan mode, Codex Plan mode), waiting on native agent status (idle, working, blocked, done), or verifying worker reports. Workers launch as interactive TUIs via herdr agent start — never through headless runners (compozy exec, claude -p, codex exec). Not for cmux workspaces (see cmux-orchestration) and not for end-user herdr control.
tools
TanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.