naming

Generates product names through metaphor mapping and availability checks.

70|10|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/glacierphonk/naming --skill naming-glacierphonk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/glacierphonk/naming/tree/main
Command: npx skills add https://github.com/glacierphonk/naming --skill naming-glacierphonk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Naming is hard: teams struggle to produce names that are memorable, meaningful, and legally safe; many names fail due to weak metaphors, generic descriptions, and domain unavailability.

Core Features & Use Cases

  • Metaphor-driven process that maps concrete imagery to abstract function, reducing AI slop.
  • Stepwise workflow (brief, metaphor mapping, candidate generation, filtering, evaluation, availability, decision) with on-demand loading of reference files.
  • Availability checks across domains, repositories, package registries, and social handles to ensure real-world viability.

Use cases: naming a new SaaS, a product feature, an open source project, or a brand.

Quick Start

Describe your naming brief and run /naming to begin the seven-step process.

Frequently Asked Questions about naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate memorable brand names using metaphor mapping?

Metaphor mapping generates memorable brand names by linking concrete imagery to abstract product functions. This process reduces generic descriptions by systematically mapping functional attributes to evocative metaphors, producing distinctive and meaningful naming candidates.

What is the step by step process for naming a SaaS product?

The naming process for a SaaS product follows seven steps: defining the brief, metaphor mapping, generating candidates, filtering, evaluation, checking availability, and making a final decision. This workflow ensures names are meaningful and legally viable.

Can I check domain and social handle availability during the naming process?

Availability checks for domains, repositories, package registries, and social handles are integrated directly into the naming workflow. This ensures generated names are evaluated for real-world viability and legal safety before a final decision is made.

Does metaphor-driven naming work for open source projects and product features?

Metaphor-driven naming works for open source projects, product features, and SaaS brands. It enforces provenance-driven origins and cross-language considerations, ensuring names respect brand constraints while remaining distinctive across different contexts.

Why do generated product names fail and how does evaluation prevent it?

Product names fail due to weak metaphors, generic descriptions, and domain unavailability. Rigorous evaluation and real-world availability checks across registries and social handles prevent failure by filtering out legally unsafe or unviable candidates early.