Guides initial domain choice for a single site: Brand vs Partial Match vs Exact Match domains, TLD selection (.ai, .com, .io), length, readability, history check, and defensive registration. A good domain affects SEO, brand perception, and UX. See domain-architecture when planning for multiple products; rebranding-strategy when changing domain.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondomain-selectionExecute the skills CLI command in your project's root directory to begin installation:
Fetches domain-selection from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate domain-selection. Access via /domain-selection in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides initial domain choice for a single site: Brand vs Partial Match vs Exact Match domains, TLD selection (.ai, .com, .io), length, readability, history check, and defensive registration. A good domain affects SEO, brand perception, and UX. See domain-architecture when planning for multiple products; rebranding-strategy when changing domain.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Reference: Alignify: Domain SEO – How to Choose SEO-Friendly Domains — detailed guide, AI brand naming, TLD recommendations, rebrand cases.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 2 (Positioning), 3 (Target Audience), 8 (Brand & Voice).
Identify:
| Type | Description | SEO | Brand | Best For |
|---|---|---|---|---|
| Branded Domain | Domain = brand; no functional keywords (Notion, Canva, Perplexity) | Long-term; Google favors brands | High | Teams; long-term brand building |
| Partial Match (PMD) | Part of domain relates to function (FlowGPT, Dify, Reportify) | Balance; signals topic | Medium | AI tools; balance SEO + brand |
| Exact Match (EMD) | Domain = search query (png2jpg.com, aiartgenerator.cc) | Fast early traffic; ceiling lower | Low | Solo devs; tool sites; site networks |
Google stance: Keywords in domain no longer directly affect ranking; domain still matters for UX and brand. EMDs work when paired with quality content; branded domains with entity recognition matter more long-term.
Recommendation:
| TLD | Use Case | Notes |
|---|---|---|
| .com | Default choice; highest trust | Most preferred; often expensive |
| .ai | AI products | ccTLD (Anguilla); auto-hyperlinks in Excel/Sheets/Feishu → natural backlinks; signals AI |
| .io | Tech, SaaS | Popular; geopolitical risk (Chagos Islands) |
| .co, .app, .pro | Alternatives | If .com taken |
| .new | Instant-create tools | For bolt.new, claude.new style; see Alignify .new guide |
AI products: Prefer .ai, .com, or .io. Avoid niche TLDs (.im, .xyz, .inc, .art, .dev)—higher risk of resolution issues (e.g., Notion .so outage).
| Rule | Purpose |
|---|---|
| Short & memorable | Easier to type, share, recall |
| Avoid hyphens | Looks unprofessional; can signal low quality |
| Check history | Use Archive.org; avoid previously penalized domains |
| Defensive registration | Register .net, .org, variants; redirect to main; do not deploy on multiple domains |
| Impersonation variants | For AI products: register brand+ai, brand+app, brand+official; see brand-protection for impersonation response |
| Accurate WHOIS; renew on time | Avoid loss or hijacking |
When brand name includes .ai (e.g., Character.ai, Leonardo.Ai), the full string auto-hyperlinks in Excel, Google Sheets, Feishu, and some IM apps. Each mention = potential backlink. Useful for AI products where the generic name alone (e.g., "Character") is a common noun.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
davila7/claude-code-templates
We added domain-selection from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
domain-selection is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
domain-selection fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
domain-selection reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend domain-selection for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added domain-selection from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in domain-selection — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
domain-selection has been reliable in day-to-day use. Documentation quality is above average for community skills.
domain-selection fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: domain-selection is focused, and the summary matches what you get after install.
showing 1-10 of 67