# Create Product Names With Strategy

Product naming often becomes a rushed list of options without clear strategy. This skill guides Claude, Codex, and Claude Code through discovery, naming routes, validation, and final selection.

## Install

```bash
npx skillstore add yunshu0909/product-naming
```

## Metadata

- Status: approved
- Slug: yunshu0909-product-naming
- Skillstore revision: r1
- Version status: missing
- Tree hash: 02af45d06ca2135d8fc221410e5de7e6c7669ab2c2328b5a9af86dd3dfce6456
- Author: yunshu0909
- GitHub username: yunshu0909
- License: MIT
- Repository: https://github.com/yunshu0909/yunshu\_skillshub/tree/master/product-naming
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/yunshu0909-product-naming
- Manifest: https://skillstore.pages.dev/api/skills/yunshu0909-product-naming/manifest

## Capabilities

- Guides a six-step product naming workflow from discovery to final confirmation.
- Extracts target users, product positioning, brand tone, naming constraints, and strategic tensions.
- Creates two to four naming routes with sample names, advantages, and drawbacks.
- Narrows a chosen route into three to five candidate names with clear explanations.
- Supports competitor naming research before recommending language, slogan, and naming strategy.
- Summarizes the decision chain behind the final product name.

## Use Cases

- Name a New Startup Product: Move from a rough product idea to naming routes, candidates, and a final naming strategy.
- Rename an Internal Tool: Clarify users, boundaries, and tone before choosing a clearer project or module name.
- Validate Shortlisted Names: Compare finalist names against competitor patterns and decide whether a slogan or local name is needed.

## Prompt Templates

### Start a Naming Session

```
Help me name a new product. Start by asking about users, positioning, boundaries, tone, language, length, and words to avoid.
```

### Extract Naming Constraints

```
Review this product brief and extract naming constraints. Identify strategic tensions, priorities, and missing questions before suggesting any names.
```

### Create Naming Routes

```
Based on our confirmed constraints, propose two to four naming routes. Include sample names, advantages, drawbacks, and a recommendation.
```

### Validate Finalists

```
Validate these finalist names against competitor naming patterns. Recommend one final name, slogan needs, and the decision rationale.
```

## Limitations

- It does not guarantee trademark, domain, or app store availability.
- It needs user input about audience, positioning, tone, and naming constraints.
- Competitor validation depends on available search access and current public information.
- It focuses on naming strategy, not full visual identity or legal review.

## Best Practices

- Share the target users, main use case, brand tone, and words to avoid before asking for names.
- Choose a naming route before requesting detailed candidate names.
- Validate finalist names with competitor research and legal review before launch.

## Anti Patterns

- Do not ask for a long name list before clarifying product positioning.
- Do not choose a name only because it sounds pleasant.
- Do not skip competitor, trademark, domain, and localization checks.

## Security Audit

- Audited at: 2026-07-08T10:58:07.185\+00:00
- Summary: The external command findings are false positives caused by Markdown fenced examples, not executable shell or Ruby backtick usage. The entropy finding is also a false positive because SKILL.md is readable product-naming guidance with no obfuscation or prompt injection evidence.

## Stats

- Views: 121
- Downloads: 13
- Favorites: 0
- Popularity score: 0