One-click install
npx skills add https://github.com/howells/skills --skill nomen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nomen
Source: https://github.com/howells/skills/tree/main/nomen
Command: npx skills add https://github.com/howells/skills --skill nomen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nomen helps you avoid weak or conflicting project and product names by generating strong options and validating them against real-world availability signals.

Core Features & Use Cases

  • Structured name generation: Produces a ranked shortlist using multiple naming strategies (verbs, metaphors, compounds, portmanteaus, sound/rhythm, and domain references) rather than minor variants.
  • Evidence-based validation: Checks current web signals, developer ecosystem conflicts (e.g., GitHub org/repo and package registries), domain/DNS signals, and other availability indicators with careful uncertainty language.
  • Context-aware renaming support: Guides safe rename discovery across public surfaces (package identifiers, CLI commands, docs, env prefixes, app titles) while avoiding implementation changes unless requested.
  • Use Cases: Naming new products, renaming existing repos/packages/CLIs, validating a candidate name, and generating alternatives when constraints change.

Quick Start

Tell the agent: generate and validate 10 product name candidates for a developer tool called “Howells Sync”, using a professional and slightly editorial tone, and prefer names that are easy to spell and pronounce, then recommend a best choice with risks and next validation steps.

Frequently Asked Questions about nomen

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

FAQPage Schema
How do I generate and validate product names for a new developer tool?

Product name generation and validation produces a ranked shortlist using multiple naming strategies like metaphors and compounds, then checks GitHub namespaces, package registries, and domain availability signals to identify conflicts and evidence-based risks.

What's the best way to check if a package name conflicts before publishing?

Package conflict checks scan developer ecosystem registries and GitHub org/repo namespaces for existing identifiers, returning evidence-based availability signals with careful uncertainty language rather than definitive legal clearance.

Can I rename an existing CLI command and app title without breaking my codebase?

CLI renaming support guides safe rename discovery across public surfaces like package identifiers, docs, and env prefixes, identifying affected areas while avoiding implementation changes unless explicitly requested.

Does domain availability checking prove I can use a brand name legally?

Domain availability checking provides evidence-based DNS and web signals with careful uncertainty language, clearly caveating results as evidence rather than legal advice for brand strategy decisions.

How does name generation avoid producing minor variants of the same word?

Name generation applies multiple distinct strategies including verbs, metaphors, compounds, portmanteaus, sound/rhythm patterns, and domain references to produce structurally diverse candidates rather than minor variants.

What context do I need to provide for accurate brand name validation?

Brand name validation requires gathering codebase and product context, asking only for materially missing constraints, then running targeted web, GitHub, package, and domain checks to produce ranked recommendations with risks.