brand-generator
Generate unique, ownable brand names with available domain names. Conducts a structured discovery interview about the product, vision, and positioning, then generates candidate names using linguistic construction patterns, filters for trademark and phonetic safety, checks domain availability via whois, and delivers a shortlist of vetted name + domain pairs. Use when user wants to name a product, company, SaaS app, or side project, or when they say "help me name", "brand name", "find a domain", "name my startup", "product naming", or "what should I call this".
What this skill does
# Brand Namer Generate unique brand names with verified-available domains through structured discovery and linguistic construction. ## Workflow ### Phase 1: Discovery Interview Conduct a focused interview to understand the product before generating any names. Ask these questions across 1-2 messages (do not overwhelm with all at once): **Round 1 — Core understanding:** - What does the product/company do in one sentence? - Who is the target user? - What category is this — a tool, platform, AI agent, marketplace, or consulting brand? **Round 2 — Strategic constraints:** - Will this expand beyond its current scope? (Determines how abstract the name should be) - What trust level is needed? (Career/finance/legal = serious tone; consumer/social = more flexibility) - What tone do you want? (e.g., technical, warm, minimal, bold, playful) - Any words or themes to avoid? - Preferred domain TLD? (.com ideal, .ai and .co acceptable) Do NOT proceed to name generation until discovery is complete. ### Phase 2: Name Generation Read [references/naming-framework.md](references/naming-framework.md) for construction patterns, phonetic rules, risk filters, and the quality scoring matrix. Generate **20-25 candidate names** by: 1. **Brainstorm semantic roots on the fly** — Do NOT rely on a static word list. Derive novel roots from the product's specific domain using: metaphors, foreign language fragments (Latin, Greek, Japanese, etc.), cross-domain analogies, phoneme invention, and abbreviation blends. Aim for roots that are *not* common English dictionary words. 2. **Apply construction patterns** (root + suffix, truncation, blending, vowel shifts, letter removal, partial root blends) 3. **Apply phonetic rules** — 2-4 syllables, one obvious pronunciation, passes phone test 4. **Pre-filter for novelty** — Before any domain check, reject candidates that are recognizable English words, obvious brand roots, or that you estimate are highly likely to be taken (e.g., "fitly", "formio", "pathly") ### Phase 3: Domain Verification Check domains for **all surviving candidates in a single batch** using the bundled script: ```bash scripts/check_domain.sh name1.com name1.ai name1.co name2.com name2.ai name2.co ... ``` Pass all candidates × all TLDs (.com, .ai, .co) in one call. Reject candidates where all reasonable TLDs are taken. ### Phase 4: Score & Web Validate Survivors Only now score and validate — don't waste effort on names with no available domains. 1. **Score each surviving candidate** on the 6-dimension quality matrix (reject below 20/30) 2. **Web validate** the top scorers via WebSearch (batch 3-4 searches in parallel): - No dominant company on SERP page 1 for the name - Not a medical/pharma term - Not a foreign-language profanity - No obvious trademark conflicts in the same industry - Reject any name that surfaces conflicts ### Phase 5: Present Shortlist Present 3-5 finalists in this format: ``` ## [Name] — [domain.tld] - **What it evokes:** [brief description of the associations] - **Score:** [X/30] (Distinctiveness / Pronounceability / Memorability / Flexibility / Legal Safety / Brandability) - **Domain status:** Available ([tld]) - **Risk notes:** [any minor concerns or "Clean"] ``` After presenting, ask the user which direction resonates and offer to: - Refine around a favorite - Generate more in a specific style - Run deeper validation (USPTO TESS, Crunchbase, GitHub, LinkedIn, social handles) ### Phase 6: Deep Validation (on request) When the user narrows to 1-2 finalists, run deeper checks via WebSearch: - `"[name]" site:crunchbase.com` - `"[name]" site:github.com` - `"[name]" site:linkedin.com/company` - `"[name]" trademark software` - `"@[name]" twitter` / `"@[name]" instagram` Report findings and confirm the final selection is clear.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".