howells/naming
skills/naming/SKILL.md
Generate and validate project names. Reads codebase context, produces candidates using tech naming strategies, and checks domain + GitHub availability. Use when naming a new project, renaming, or validating an existing name.
$ install --global
skillsauthnpx skillsauth add howells/arc namingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:47 PM1.7s1 file scanned
SKILL.md
- name:
- naming
- description:
- |
- license:
- MIT
- author:
- howells
- order:
- 19
- desc:
- Project naming
- summary:
- Generate project name candidates and validate domain + GitHub availability.
- what:
- |
- why:
- |
- - "Domain availability is checked via whois (.com) and dig (all other TLDs). Priority TLDs:
- .com, .dev, .app, .sh, .io.
- position:
- utility
<tool_restrictions>
MANDATORY Tool Restrictions
REQUIRED TOOLS:
AskUserQuestion— Preserve the one-question-at-a-time interaction pattern for every follow-up question, including exploring names, checking TLDs, and choosing strategies. In Claude Code, use the tool. In Codex, ask one concise plain-text question at a time unless a structured question tool is actually available in the current mode. Keep context before the question to 2-3 sentences max, and do not narrate missing tools or fallbacks to the user. </tool_restrictions>
Naming Workflow
Generate and validate project/product name candidates using the naming agent.
What This Does
- Reads your project materials (README, package.json, vision doc)
- Extracts naming seeds (core function, metaphors, audience, differentiators)
- Generates 8-12 name candidates using tech naming strategies
- Checks domain availability across all Vercel-supported TLDs
- Checks GitHub for popular repos with the same name
- Searches for existing products in the same space
- Presents ranked recommendations with availability matrix
Process
Step 1: Read the Project
Use Task tool to spawn the naming agent:
Task agent: arc:research:naming
"Read the codebase at [path] and generate name candidates.
Check domain availability, GitHub popularity, and product conflicts.
Present ranked recommendations."
The agent handles the full naming process autonomously.
Step 2: Present Results
The agent returns a structured report. Present it to the user as-is.
Step 3: Explore Further
If the user likes a name, ask:
AskUserQuestion:
question: "What would you like to do with [name]?"
header: "Next Steps"
options:
- label: "Check more TLDs"
description: "Search additional TLDs for [name] availability"
- label: "Generate similar names"
description: "Create more names using the [strategy] style"
- label: "Register domain"
description: "Get the command to register [best available domain]"
- label: "Done"
description: "I've picked my name"
Usage
/arc:naming # Name the current project
/arc:naming ~/Sites/myproject # Name a specific project
Output
For each recommended name:
- Strategy used — Verb, Metaphor, Portmanteau, etc.
- Why it works — What makes this name fit the project
- Domain availability — Matrix across priority TLDs + all Vercel TLDs with no DNS
- GitHub conflicts — Popular repos (1k+ stars) sharing the name
- Product conflicts — Existing products in the same space
When to Use
- Starting a new project and need a name
- Current name feels weak or generic
- Validating an existing name choice
- Rebranding or renaming
- Checking domain availability for a name you like
Related Skills
howells/launch
development
VerifiedTrustedCommunity
Go-live and shareability checklist covering the basics needed to make a project visitable, shareable, and ready for a first real audience. Use when asked to "launch", "go live", "make this shareable", "get this ready to show people", or prepare a project for a public URL.
22SKILL.mdUpdated May 23, 2026
howells/refactor
development
VerifiedTrustedCommunity
Discover architectural friction and propose structural refactors with competing interface options. Focuses on deepening shallow modules, extracting grouped concerns into packages/modules, breaking up god files, reducing duplication, and improving testability. Use when asked to "improve the architecture", "find refactoring opportunities", "deepen modules", "consolidate coupling", "break up god components", "extract this into a package", "make this more testable", or "find architectural friction".
22SKILL.mdUpdated Apr 20, 2026
howells/vision
development
VerifiedTrustedCommunity
Create, review, or revise a concise project vision document that captures what a project is, who it is for, why it exists, success criteria, constraints, non-goals, and decision principles. Use when starting a new project, clarifying product direction, aligning a codebase for future agent work, defining a north star, or turning a vague idea into docs/vision.md.
22SKILL.mdUpdated Apr 5, 2026
howells/using-arc
tools
VerifiedTrustedCommunity
Use when starting any conversation - establishes Arc's skill routing, instruction priority, and bootstrap rules
22SKILL.mdUpdated Apr 5, 2026