# Branding Strategy

> Create or revise strategic branding for software products, innovation projects, frontend experiences, and presentation layers. Use when Codex needs to define naming criteria, product name options, positioning, value proposition, tagline, narrative, tone of voice, brand personality, trust signals, differentiation, and an initial visual direction that can feed a style guide or user interface design.

- Skill: `b-holanda/branding-strategy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add b-holanda/branding-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/b-holanda/branding-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: b-holanda (https://skillmd.com/u/b-holanda)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/b-holanda/branding-strategy

---


# Branding Strategy

Create the strategic foundation for a software brand before designing a style guide, interface, landing page, product page, pitch material, or visual assets.

This skill helps Codex produce:

- naming criteria;
- product or company name options;
- positioning;
- value proposition;
- tagline;
- short manifesto;
- tone of voice;
- brand personality;
- brand narrative;
- differentiation;
- trust signals;
- initial visual direction;
- style guide brief.

## Core Principle

Branding is not decoration. Every brand decision should support clarity, differentiation, trust, usability, and the product promise.

For software products, the brand should help users quickly understand:

- what the product does;
- who it is for;
- why it matters;
- why it can be trusted;
- how it feels to use;
- how it differs from alternatives.

## Source Priority

Before creating brand strategy, inspect available context such as:

- product or innovation briefs;
- research summaries;
- evidence maps;
- user interview notes;
- product requirements;
- frontend copy;
- existing UI screens;
- repository documentation;
- competitor notes;
- previous naming or positioning drafts.

If these sources are missing, proceed with a preliminary strategy and mark assumptions clearly.

## Evidence Rules

Never invent:

- market validation;
- trademark availability;
- domain availability;
- social handle availability;
- competitor facts;
- user preferences;
- official identity decisions;
- partnerships;
- customers;
- metrics.

When information is missing, say:

> There is not enough evidence in the available material. Treat this as a brand hypothesis that requires validation.

## Classification Labels

Classify important decisions as:

- Product evidence;
- Research evidence;
- User-provided direction;
- Branding best practice;
- Strategic hypothesis;
- Requires validation.

## Workflow

### 1. Understand the Product Essence

Extract:

- core problem;
- target users;
- solution;
- product category;
- key use cases;
- differentiation;
- maturity level;
- desired emotion;
- trust requirements;
- interface or presentation context;
- constraints from the user.

### 2. Define Brand Territory

Choose one or more symbolic territories, such as:

- clarity;
- trust;
- speed;
- intelligence;
- simplicity;
- precision;
- safety;
- creativity;
- automation;
- collaboration;
- craft;
- operational control;
- human support;
- transformation.

Justify each territory with product or research evidence when possible.

### 3. Define Naming Criteria

Evaluate names by:

- clarity;
- memorability;
- pronunciation;
- spelling;
- category fit;
- emotional fit;
- commercial strength;
- software/product fit;
- internationalization risk;
- genericness risk;
- confusion risk;
- visual identity potential;
- domain/trademark validation needs.

### 4. Generate Name Options

Group names by category:

- descriptive;
- symbolic;
- technical;
- action-oriented;
- human-centered;
- short;
- enterprise-ready;
- startup-like.

Use this format:

| Name | Category | Rationale | Strengths | Risks | Classification |
| --- | --- | --- | --- | --- | --- |

### 5. Select Recommendations

Choose 3 to 5 strongest options. For each:

- explain why it works;
- name the main risks;
- list validations needed;
- suggest how it could appear in UI, navigation, app title, or marketing copy.

### 6. Create Positioning

Generate:

- positioning statement;
- value proposition;
- main promise;
- tagline;
- short manifesto;
- voice principles;
- brand personality;
- differentiation narrative.

### 7. Define Initial Visual Direction

Without creating a final style guide, suggest:

- desired visual feeling;
- formality level;
- technology level;
- warmth level;
- color direction;
- typography direction;
- layout direction;
- icon or illustration direction;
- interface implications;
- restrictions for future design work.

### 8. Prepare Style Guide Brief

Prepare inputs for `style-guide`:

- brand essence;
- positioning;
- voice;
- personality;
- visual principles;
- color direction;
- typography direction;
- component tone;
- accessibility expectations;
- risks and validations.

## Output Format

Use the sections that fit the task:

## Brand Diagnosis

## Brand Territory

## Naming Criteria

## Name Options

## Recommended Names

## Preferred Name

## Positioning

## Value Proposition

## Tagline

## Short Manifesto

## Tone of Voice

## Brand Personality

## Initial Visual Direction

## Style Guide Brief

## Validation Needed

## Quality Criteria

A good output from this skill should:

- make the software product easier to understand;
- avoid random naming;
- connect brand decisions to evidence;
- support future frontend and view-layer design;
- prepare a style guide;
- separate facts from hypotheses;
- avoid exaggerated claims;
- list validation work still needed.