naming
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.
Best use case
naming is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using naming should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/naming/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How naming Compares
| Feature / Agent | naming | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<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
1. Reads your project materials (README, package.json, vision doc)
2. Extracts naming seeds (core function, metaphors, audience, differentiators)
3. Generates 8-12 name candidates using tech naming strategies
4. **Checks domain availability** across all Vercel-supported TLDs
5. **Checks GitHub** for popular repos with the same name
6. **Searches for existing products** in the same space
7. 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 likeRelated Skills
vision
Create or review a high-level vision document capturing project goals and purpose. Use when asked to "define the vision", "what is this project", "set goals", or when starting a new project that needs clarity on purpose and direction.
using-arc
Use when starting any conversation - establishes Arc's skill routing, instruction priority, and bootstrap rules
tidy
Clean up completed plans in docs/arc/plans/. Archives or deletes finished plans. Use when asked to "clean up plans", "tidy the docs", "archive old plans", or after completing implementation to remove stale planning documents.
testing
Comprehensive testing strategy. Creates test plans covering unit, integration, and E2E. Uses specialist agents for each test type. Supports vitest and Playwright with auth testing guidance for Clerk and WorkOS.
suggest
Opinionated recommendations for what to work on next based on Linear issues, tasks, and codebase. Use when asked "what should I work on", "what's next", "suggest priorities", or when starting a session and unsure where to begin.
seo
Deep SEO audit for web projects. Analyzes codebase for crawlability, indexability, on-page SEO, structured data, social previews, and technical foundations. Optionally runs Lighthouse and PageSpeed against a live URL. Reports findings with severity, offers direct fixes or /arc:detail plans. Use when asked to "audit SEO", "check SEO", "review SEO", or "is my site SEO-ready".
responsive
Audit and fix responsive/mobile issues across every page of a project, using browser screenshots at two breakpoints (375px mobile, 1440px desktop). Design-aware: reads existing design docs to preserve aesthetic intent, not just "make it fit." Use when asked to "make it responsive", "fix mobile", "responsive audit", or after building a desktop-first UI that needs mobile adaptation.
refactor
Discover architectural friction and propose structural refactors with competing interface designs. Focuses on deepening shallow modules, consolidating coupled code, and improving testability. Use when asked to "improve the architecture", "find refactoring opportunities", "deepen modules", "consolidate coupling", "make this more testable", or "find architectural friction".
prune-agents
Kill orphaned Claude subagent processes that didn't exit cleanly. Use when asked to "prune agents", "clean up agents", "kill orphaned processes", or when subagents accumulate from Task tool usage.
progress
Internal skill for progress journal management. Other skills append to docs/arc/progress.md for cross-session context. Not invoked directly by users.
letsgo
Production readiness checklist covering domains, SEO, security, and deployment. Use when asked to "ship it", "deploy to production", "go live", "launch", or when preparing a project for production deployment.
implement
Scope-aware implementation workflow with TDD and continuous quality checks. Use when asked to "implement this", "build this feature", "execute the plan", or after /arc:ideate has created a design doc. For small work it creates a lightweight inline plan; for larger work it creates or loads a full implementation plan and executes task-by-task with build agents.