/arn-spark-naming
This skill should be used when the user says "naming", "brand name", "name my product", "find a name", "product naming", "brand naming", "what should I call it", "name ideas", "pick a name", "naming session", "help me name this", "brainstorm names", "come up with a name", "arn
$ npx -y skills add AppsVortex/arness --skill arn-spark-naming --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/arn-spark-naming
Context preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when the user says "naming", "brand name", "name my product", "find a name", "product naming", "brand naming", "what should I call it", "name ideas", "pick a name", "naming session", "help me name this", "brainstorm names", "come up with a name", "arn
SKILL.md
arn-spark-naming.SKILL.mdname: arn-spark-naming
description: >-
This skill should be used when the user says "naming", "brand name",
"name my product", "find a name", "product naming", "brand naming",
"what should I call it", "name ideas", "pick a name", "naming session",
"help me name this", "brainstorm names", "come up with a name",
"arn spark naming", "arn-spark-naming", or wants to find a brand
name for their product through strategic analysis, creative generation,
qualitative scoring, and due diligence including domain availability
and trademark screening.
version: 1.0.0
Arness Spark Naming
Guide a product from nameless concept to validated brand name through a structured 4-step methodology, driven by the `arn-spark-brand-strategist` agent. Produces a **naming brief** (`naming-brief.md`) in the vision directory and a **naming report** (`naming-report.md`) in the reports directory.
Prerequisites
1. Read the project's CLAUDE.md for the `## Arness` section. 2. Extract **Vision directory** and **Reports directory** paths. If no `## Arness` section exists or Arness Spark fields are missing, inform the user: "Arness Spark is not configured for this project yet. Run `/arn-brainstorming` to get started — it will set everything up automatically." Do not proceed without it. 3. Create directories if they do not exist.
Step 0: Context Gathering
Product context
Check for `<vision-dir>/product-concept.md`:
**If found:** Read and extract: vision statement, value proposition, target audience, product pillars, competitive landscape. Summarize the extracted context to the user: "Found your product concept. I'll use this as the foundation for naming."
**If not found:**
Ask (using `AskUserQuestion`):
**"No product concept found. How should I learn about your product?"** 1. **Describe your product** — Provide a description in the next message 2. **Point me to a file** — Specify a file path containing product information 3. **Explore current project** — I'll read README, package.json, and code to infer what the product does
If option 3: invoke `arn-spark-brand-strategist` in `brand-dna` mode with instructions to explore the project and summarize the product context.
Target market
Ask (using `AskUserQuestion`):
**"What is the primary target market? This determines trademark databases and languages for linguistic screening."** 1. **United States** — USPTO trademark search, English + Spanish linguistic check 2. **European Union** — EUIPO trademark search, English + French + German + Spanish + Italian 3. **United Kingdom** — IPO trademark search, English linguistic check 4. **Global / Multiple regions** — WIPO + major national databases, all major languages
Existing naming brief
Check for `<vision-dir>/naming-brief.md`:
**If found:**
Ask (using `AskUserQuestion`):
**"A naming brief already exists. How would you like to proceed?"** 1. **Resume from where I left off** — Continue from the first incomplete section 2. **Start fresh** — Preserve existing as naming-brief-previous.md and begin new
If resume: read the brief, detect which sections contain "-- Pending --" or are missing, and resume from the first incomplete step.
---
Step 1: Strategic Foundation (Brand DNA)
Invoke the `arn-spark-brand-strategist` agent in `brand-dna` mode via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context:
- Product context (from product-concept.md or user input)
- Competitive landscape (from product concept, or agent will research via WebSearch)
- Target market
The agent returns: brand personality profile, audience vocabulary, competitor name landscape, 1-2 recommended naming categories with rationale.
Present the Brand DNA analysis to the user.
Ask (using `AskUserQuestion`):
**"Proceed with the recommended naming categories?"** 1. **Yes, proceed with [recommended categories]** (Recommended) — Use the strategist's recommendation (substitute actual category names from the Brand DNA analysis) 2. **Choose different categories** — Select naming categories manually
If option 2:
Ask (using `AskUserQuestion`, `multiSelect: true`):
**"Select naming categories to explore (select all that apply):"** 1. **Descriptive** — Names that describe what the product does (PayPal, Dropbox) 2. **Evocative** — Names that suggest a feeling or metaphor (Slack, Nike) 3. **Invented / Abstract** — Completely new words (Spotify, Google) 4. **Lexical** — Wordplay, puns, alliteration (Pinterest, Netflix)
Then prompt (free-text): "Any existing name ideas, words you love, or words you hate? These will seed the creative sprint. Type 'none' or 'skip' to continue without seeds."
Write initial `<vision-dir>/naming-brief.md` using the creative brief template: > Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/creative-brief-template.md`
Populate: Context and Brand DNA sections. Mark remaining sections as "-- Pending --".
---
Step 2: Creative Sprint (The Big List)
Four generation rounds via `arn-spark-brand-strategist` in `generation` mode.
**Round 1 — Seed harvest:** Invoke agent with user's existing ideas and preferences as seeds. If no seeds, skip to Round 2.
**Round 2 — Category sprints:** Invoke agent once per selected category, requesting 50-80 candidates each. Pass the brand DNA context and dead directions. Present candidates to user after each category sprint for early feedback.
**Round 3 — Mashup round:** Invoke agent with all Round 1-2 candidates. Cross-pollinate fragments across categories. Target: 30-50 mashup candidates.
**Round 4 — User collaboration checkpoint:** Present the complete candidate list organized by category. This is a free-text conversation loop: the user marks favorites (star), flags directions to kill, and may suggest additional directions. Iterate until the user signals satisfaction.
Targe
Read more
name: arn-spark-naming description: >- This skill should be used when the user says "naming", "brand name", "name my product", "find a name", "product naming", "brand naming", "what should I call it", "name ideas", "pick a name", "naming session", "help me name this", "brainstorm names", "come up with a name", "arn spark naming", "arn-spark-naming", or wants to find a brand name for their product through strategic analysis, creative generation, qualitative scoring, and due diligence including domain availability and trademark screening. version: 1.0.0
Arness Spark Naming
Guide a product from nameless concept to validated brand name through a structured 4-step methodology, driven by the `arn-spark-brand-strategist` agent. Produces a **naming brief** (`naming-brief.md`) in the vision directory and a **naming report** (`naming-report.md`) in the reports directory.
Prerequisites
1. Read the project's CLAUDE.md for the `## Arness` section. 2. Extract **Vision directory** and **Reports directory** paths. If no `## Arness` section exists or Arness Spark fields are missing, inform the user: "Arness Spark is not configured for this project yet. Run `/arn-brainstorming` to get started — it will set everything up automatically." Do not proceed without it. 3. Create directories if they do not exist.
Step 0: Context Gathering
Product context
Check for `<vision-dir>/product-concept.md`:
**If found:** Read and extract: vision statement, value proposition, target audience, product pillars, competitive landscape. Summarize the extracted context to the user: "Found your product concept. I'll use this as the foundation for naming."
**If not found:**
Ask (using `AskUserQuestion`):
**"No product concept found. How should I learn about your product?"** 1. **Describe your product** — Provide a description in the next message 2. **Point me to a file** — Specify a file path containing product information 3. **Explore current project** — I'll read README, package.json, and code to infer what the product does
If option 3: invoke `arn-spark-brand-strategist` in `brand-dna` mode with instructions to explore the project and summarize the product context.
Target market
Ask (using `AskUserQuestion`):
**"What is the primary target market? This determines trademark databases and languages for linguistic screening."** 1. **United States** — USPTO trademark search, English + Spanish linguistic check 2. **European Union** — EUIPO trademark search, English + French + German + Spanish + Italian 3. **United Kingdom** — IPO trademark search, English linguistic check 4. **Global / Multiple regions** — WIPO + major national databases, all major languages
Existing naming brief
Check for `<vision-dir>/naming-brief.md`:
**If found:**
Ask (using `AskUserQuestion`):
**"A naming brief already exists. How would you like to proceed?"** 1. **Resume from where I left off** — Continue from the first incomplete section 2. **Start fresh** — Preserve existing as naming-brief-previous.md and begin new
If resume: read the brief, detect which sections contain "-- Pending --" or are missing, and resume from the first incomplete step.
---
Step 1: Strategic Foundation (Brand DNA)
Invoke the `arn-spark-brand-strategist` agent in `brand-dna` mode via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context:
- Product context (from product-concept.md or user input)
- Competitive landscape (from product concept, or agent will research via WebSearch)
- Target market
The agent returns: brand personality profile, audience vocabulary, competitor name landscape, 1-2 recommended naming categories with rationale.
Present the Brand DNA analysis to the user.
Ask (using `AskUserQuestion`):
**"Proceed with the recommended naming categories?"** 1. **Yes, proceed with [recommended categories]** (Recommended) — Use the strategist's recommendation (substitute actual category names from the Brand DNA analysis) 2. **Choose different categories** — Select naming categories manually
If option 2:
Ask (using `AskUserQuestion`, `multiSelect: true`):
**"Select naming categories to explore (select all that apply):"** 1. **Descriptive** — Names that describe what the product does (PayPal, Dropbox) 2. **Evocative** — Names that suggest a feeling or metaphor (Slack, Nike) 3. **Invented / Abstract** — Completely new words (Spotify, Google) 4. **Lexical** — Wordplay, puns, alliteration (Pinterest, Netflix)
Then prompt (free-text): "Any existing name ideas, words you love, or words you hate? These will seed the creative sprint. Type 'none' or 'skip' to continue without seeds."
Write initial `<vision-dir>/naming-brief.md` using the creative brief template: > Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/creative-brief-template.md`
Populate: Context and Brand DNA sections. Mark remaining sections as "-- Pending --".
---
Step 2: Creative Sprint (The Big List)
Four generation rounds via `arn-spark-brand-strategist` in `generation` mode.
**Round 1 — Seed harvest:** Invoke agent with user's existing ideas and preferences as seeds. If no seeds, skip to Round 2.
**Round 2 — Category sprints:** Invoke agent once per selected category, requesting 50-80 candidates each. Pass the brand DNA context and dead directions. Present candidates to user after each category sprint for early feedback.
**Round 3 — Mashup round:** Invoke agent with all Round 1-2 candidates. Cross-pollinate fragments across categories. Target: 30-50 mashup candidates.
**Round 4 — User collaboration checkpoint:** Present the complete candidate list organized by category. This is a free-text conversation loop: the user marks favorites (star), flags directions to kill, and may suggest additional directions. Iterate until the user signals satisfaction.
Targe
Showing the first part of this file.
Arness — H not required. Structured AI workflows for Claude Code. From first idea to production deploy. Seven entry commands. That's all you need to remember.
Repo: AppsVortex/arness
Other skills on arness.
- /arn-assessing
This skill should be used when the user says "assessing", "arness assessing", "assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "pattern compliance check", "codebase health check",
Open skill - /arn-code-assess
This skill should be used when the user says "arness code assess", "arn-code-assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "tech debt audit", "pattern compliance check", "codebase health
Open skill - /arn-code-batch-cve-fix
This skill should be used when the user says "fix CVEs", "patch vulnerabilities", "apply security patches", "resolve security advisories", "batch CVE fix", "patch dependencies", "fix security findings", "remediate CVEs", "apply CVE fixes", "batch fix vulnerabilities", "resolve
Open skill - /arn-code-batch-cve-scan
This skill should be used when the user says "scan for CVEs", "CVE scan", "check for vulnerabilities", "find vulnerabilities", "check security advisories", "dependabot triage", "dependabot scan", "scan dependencies for security issues", "audit dependencies", "vulnerability
Open skill - /arn-code-batch-implement
This skill should be used when the user says "batch implement", "implement all", "batch execution", "implement all features", "parallel implement", "implement in parallel", "arness batch implement", "arn-code-batch-implement", "run batch implementation", "implement everything",
Open skill - /arn-code-batch-merge
This skill should be used when the user says "batch merge", "merge batch", "arness batch merge", "arn-code-batch-merge", "merge all PRs", "merge batch PRs", "merge the batch", "merge implemented features", "batch merge PRs", "merge open PRs", "merge all feature PRs", "combine
Open skill

