From namecast
Use this skill when the user wants to divine or generate brand name ideas for a company, product, or project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/namecast:generate-namesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Divine creative brand name candidates based on company context, mission, and target market.
Divine creative brand name candidates based on company context, mission, and target market.
Before generating names, understand:
Generate names across multiple styles:
Names that describe what the company does.
Made-up words that sound good.
Names that evoke a concept related to the business.
Two words combined.
Names that work as acronyms or can become one.
Names derived from people or locations.
## Brand Name Candidates for {BUSINESS_TYPE}
Based on your description: "{brief summary}"
### Top Recommendations
1. **{Name}** - {brief rationale}
2. **{Name}** - {brief rationale}
3. **{Name}** - {brief rationale}
### Full Candidate List
#### Descriptive Names
- {Name}: {one-line explanation}
- {Name}: {one-line explanation}
#### Abstract/Invented Names
- {Name}: {one-line explanation}
- {Name}: {one-line explanation}
#### Metaphor Names
- {Name}: {one-line explanation}
- {Name}: {one-line explanation}
#### Compound Names
- {Name}: {one-line explanation}
- {Name}: {one-line explanation}
### Quick Availability Check
{Run quick domain check on top 3 recommendations}
### Next Steps
Would you like me to run a full evaluation on any of these names?
Do:
Avoid:
User: "I'm building a platform that helps small businesses automate their accounting. Target market is non-technical small business owners. We want to feel friendly and approachable, not intimidating."
Then generate names using the framework, emphasizing friendly/approachable options and avoiding technical jargon.
npx claudepluginhub maxghenis/namecast --plugin namecastGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.