@veyralabs/skills 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +182 -0
- package/bin/cli.js +135 -0
- package/install.sh +226 -0
- package/package.json +47 -0
- package/skills/brandaudit/SKILL.md +278 -0
- package/skills/brandaudit/references/audit-framework.md +156 -0
- package/skills/brandaudit/references/examples/sample-audits.md +239 -0
- package/skills/brandaudit/references/rebrand-decisions.md +215 -0
- package/skills/brandaudit/references/weakness-patterns.md +187 -0
- package/skills/competitornames/SKILL.md +250 -0
- package/skills/competitornames/references/examples/sample-analyses.md +185 -0
- package/skills/competitornames/references/pattern-analysis.md +94 -0
- package/skills/competitornames/references/whitespace-mapping.md +146 -0
- package/skills/domainforge/SKILL.md +266 -0
- package/skills/domainforge/references/brand-archetypes.md +147 -0
- package/skills/domainforge/references/examples/sample-outputs.md +141 -0
- package/skills/domainforge/references/naming-patterns.md +168 -0
- package/skills/domainforge/references/scoring-rubric.md +168 -0
- package/skills/domainforge/references/tld-strategy.md +112 -0
- package/skills/namingguide/SKILL.md +264 -0
- package/skills/namingguide/references/examples/sample-guides.md +212 -0
- package/skills/namingguide/references/guide-structure.md +155 -0
- package/validate.js +142 -0
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
# Sample Analyses — CompetitorNames Reference
|
|
2
|
+
|
|
3
|
+
Two complete competitive naming analyses showing full output quality.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Example 1: Developer CLI / Config Management
|
|
8
|
+
|
|
9
|
+
**User input:** "I'm building a secrets and config management tool for developers. Who else is in this space and how are they named?"
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## CompetitorNames — Developer Config & Secrets Management
|
|
14
|
+
|
|
15
|
+
**Market:** Developer infrastructure / secrets management
|
|
16
|
+
**Competitors analyzed:** 10
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
### Naming Landscape Map
|
|
21
|
+
|
|
22
|
+
| Name | Style | Phonetic | Length | Archetype signal |
|
|
23
|
+
|------|-------|----------|--------|-----------------|
|
|
24
|
+
| Doppler | Metaphor/concept | Hard opener, soft landing | 7 | DevTool, premium |
|
|
25
|
+
| Vault | Real word out-of-context | Hard, punchy | 5 | Enterprise, security |
|
|
26
|
+
| Infisical | Invented (infosec + classical) | Soft, complex | 9 | Security-first devtool |
|
|
27
|
+
| Envkey | Descriptive compound | Soft-hard mix | 6 | Functional, utilitarian |
|
|
28
|
+
| dotenv | Descriptive + convention | Lowercase, soft | 6 | Indie, open source |
|
|
29
|
+
| 1Password | Descriptive + numeral | Mixed | 9 | Consumer-first |
|
|
30
|
+
| Bitwarden | Compound (bit + warden) | Hard | 8 | Security, open source |
|
|
31
|
+
| Chamber | Real word out-of-context | Soft | 7 | Enterprise |
|
|
32
|
+
| Teller | Real word out-of-context | Soft | 6 | Fintech-adjacent |
|
|
33
|
+
| Keybase | Descriptive compound | Mixed | 7 | Crypto-adjacent |
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
### Pattern Distribution
|
|
38
|
+
|
|
39
|
+
**Saturated (avoid):**
|
|
40
|
+
- Descriptive compounds: Envkey, dotenv, Keybase — 3 of 10 + pattern is tired in devtools
|
|
41
|
+
- "Security-coded" names: Vault, Bitwarden, Chamber, Infisical — 4 of 10 convey security explicitly → crowded signal
|
|
42
|
+
|
|
43
|
+
**Moderate (viable with strong execution):**
|
|
44
|
+
- Real word out-of-context: Vault, Chamber, Teller — 3 of 10, but Vault is dominant and owned by HashiCorp
|
|
45
|
+
|
|
46
|
+
**Open territory (1 competitor):**
|
|
47
|
+
- Physics/science metaphor: Doppler is alone — nobody else uses this pattern
|
|
48
|
+
- Fintech-style phonetics: Teller borrowed from fintech — only 1 name here
|
|
49
|
+
|
|
50
|
+
**Whitespace (0 competitors):**
|
|
51
|
+
- Latin/Greek root names: zero competitors use classical roots
|
|
52
|
+
- Ultra-short (≤4 chars): zero competitors — Zed/Bun/Nx energy completely absent
|
|
53
|
+
- Hard-consonant invented word: everyone is soft or descriptive — hard, punchy invented name is open
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
### Competitive Positioning Analysis
|
|
58
|
+
|
|
59
|
+
The config/secrets space names itself in two dominant clusters: security-coded (Vault, Bitwarden, Infisical) and utilitarian-descriptive (dotenv, Envkey, Keybase). Both clusters are saturated and neither is exciting.
|
|
60
|
+
|
|
61
|
+
Doppler is the notable outlier — a physics metaphor that has nothing to do with configuration management, executed with enough product quality to make it stick. It's the most "brandable" name in the space and it shows: Doppler has positioned as the premium tier while everyone else competes on features.
|
|
62
|
+
|
|
63
|
+
The whitespace is clear: a hard-consonant invented word or Latin-rooted name that signals speed and precision rather than security-paranoia or function-description would stand out immediately. The space needs its "Stripe" — short, hard, confident, says nothing about what it does.
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
### Naming Brief for This Market
|
|
68
|
+
|
|
69
|
+
**Avoid:**
|
|
70
|
+
- Descriptive compounds: Envkey/dotenv pattern — un-trademarkable and communicates commodity
|
|
71
|
+
- Security-coded language: "vault", "key", "secret", "cipher" — saturated, signals paranoia not productivity
|
|
72
|
+
- Soft, warm phonetics — this is a developer infrastructure tool, not a wellness app
|
|
73
|
+
|
|
74
|
+
**Explore:**
|
|
75
|
+
- Hard-consonant invented word: pure whitespace, highest differentiation
|
|
76
|
+
- Latin/Greek root: zero competitors, signals intelligence and precision
|
|
77
|
+
- Ultra-short (3-4 chars): completely open in this space, strong DevTool convention
|
|
78
|
+
|
|
79
|
+
**Phonetic target:** Hard opener (K, V, T, R), 4-7 chars, ends in hard stop or short vowel
|
|
80
|
+
|
|
81
|
+
**Differentiation requirement:** Must not contain or evoke: key, vault, secret, env, config, dot. Must feel fast and developer-native, not security-paranoid.
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
### DomainForge Brief
|
|
86
|
+
|
|
87
|
+
Archetype: DevTool / Developer Infrastructure
|
|
88
|
+
Mode: Indie Hacker + DevTool (short, technical, lowercase-first)
|
|
89
|
+
Avoid: -key, -env, -vault, -base, security-coded language, descriptive compounds
|
|
90
|
+
Explore: hard-consonant invented words, Latin roots (rapid/precise/contained), ultra-short
|
|
91
|
+
Phonetic target: 4-7 chars, hard opener, terminal-friendly in lowercase
|
|
92
|
+
Must stand out against: Doppler, Vault, dotenv, Infisical
|
|
93
|
+
|
|
94
|
+
*Activating DomainForge with this brief...*
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## Example 2: Consumer Journaling / Reflection Apps
|
|
99
|
+
|
|
100
|
+
**User input:** "I'm building a daily journaling app. What's the naming landscape look like?"
|
|
101
|
+
|
|
102
|
+
---
|
|
103
|
+
|
|
104
|
+
## CompetitorNames — Consumer Journaling & Reflection Apps
|
|
105
|
+
|
|
106
|
+
**Market:** Consumer / Mental wellness / Daily journaling
|
|
107
|
+
**Competitors analyzed:** 11
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
### Naming Landscape Map
|
|
112
|
+
|
|
113
|
+
| Name | Style | Phonetic | Length | Archetype signal |
|
|
114
|
+
|------|-------|----------|--------|-----------------|
|
|
115
|
+
| Day One | Real words (date + number) | Soft | 6 | Personal, warm |
|
|
116
|
+
| Daylio | Modified real word | Soft | 6 | Approachable, consumer |
|
|
117
|
+
| Reflectly | Descriptive + -ly suffix | Soft | 9 | Generic, dated |
|
|
118
|
+
| Journey | Real word (metaphor) | Soft | 7 | Warm, metaphorical |
|
|
119
|
+
| Bearable | Real word out-of-context | Soft | 8 | Clever, mental health |
|
|
120
|
+
| Moodnotes | Descriptive compound | Soft | 9 | Functional, clinical |
|
|
121
|
+
| Finch | Real word out-of-context | Soft | 5 | Warm, approachable |
|
|
122
|
+
| Stoic | Real word out-of-context | Hard opener | 5 | Intellectual, philosophy |
|
|
123
|
+
| Penzu | Invented word | Mixed | 5 | Neutral, forgettable |
|
|
124
|
+
| Rosebud | Real word compound | Soft | 7 | Warm, nostalgic |
|
|
125
|
+
| Clarity | Real word | Soft | 7 | Generic aspiration |
|
|
126
|
+
|
|
127
|
+
---
|
|
128
|
+
|
|
129
|
+
### Pattern Distribution
|
|
130
|
+
|
|
131
|
+
**Saturated (avoid):**
|
|
132
|
+
- Soft phonetics: 10 of 11 names — the entire space is soft, warm, gentle
|
|
133
|
+
- Real words used as brand: Day One, Journey, Bearable, Finch, Stoic, Rosebud, Clarity — 7 of 11
|
|
134
|
+
- Descriptive or functional naming: Reflectly, Moodnotes — both dated, both generic
|
|
135
|
+
|
|
136
|
+
**Open territory (1-2 competitors):**
|
|
137
|
+
- Hard consonant opener: only Stoic — philosophical angle creates a distinct cluster alone
|
|
138
|
+
- Invented word: only Penzu — but poorly executed (forgettable)
|
|
139
|
+
|
|
140
|
+
**Whitespace:**
|
|
141
|
+
- Short invented word with soft-warm phonetics that isn't a real word: nobody does this well
|
|
142
|
+
- Abstract concept from non-wellness domains: the fintech/devtool "confidence" — nobody in journaling is crisp and bold
|
|
143
|
+
- 4-char names: nobody — the shortest is Finch at 5
|
|
144
|
+
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
### Competitive Positioning Analysis
|
|
148
|
+
|
|
149
|
+
The journaling space is homogeneous in a way that creates opportunity. Every app except Stoic signals the same thing: warm, safe, gentle. Real words, soft consonants, metaphors of growth and nature. The space looks like a cozy living room with everyone dressed identically.
|
|
150
|
+
|
|
151
|
+
Stoic has found a gap — intellectual, philosophical, slightly austere. It attracts a specific user (Stoicism-adjacent, Marcus Aurelius readers, productivity-focused). But it's one player in a specific niche.
|
|
152
|
+
|
|
153
|
+
The real whitespace is a name that combines warm phonetics (mandatory for mental health) with crispness and confidence — not generic warmth. Something that sounds thoughtful without sounding like a blanket. The market has "comfort food" names. Nobody has the equivalent of a well-designed Muji product — clean, warm, precisely minimal.
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
157
|
+
### Naming Brief for This Market
|
|
158
|
+
|
|
159
|
+
**Avoid:**
|
|
160
|
+
- Generic aspiration words: Clarity, Journey, Reflect — saturated and un-ownable
|
|
161
|
+
- -ly suffix: Reflectly pattern is dead
|
|
162
|
+
- Descriptive compounds: Moodnotes pattern signals clinical utility, not emotional resonance
|
|
163
|
+
- Overtly nature/growth metaphors: Rosebud, Finch territory is full
|
|
164
|
+
|
|
165
|
+
**Explore:**
|
|
166
|
+
- Soft invented word that doesn't exist yet: clean, pronounceable, warm — Daylio did this but it's taken
|
|
167
|
+
- Short concept word from outside the wellness space: bring crispness into a soft landscape
|
|
168
|
+
- Latin/Greek root with warmth: zero competitors here — `Lumio`, `Velara`, `Morna`
|
|
169
|
+
|
|
170
|
+
**Phonetic target:** Soft consonants (l, m, n, r, v), ends in vowel sound, 4-6 chars
|
|
171
|
+
|
|
172
|
+
**Differentiation requirement:** Must feel warm but not generic. Must be distinctive enough that it doesn't disappear into the "cozy app" cluster. Must work as a verb: "I'll [name] about this."
|
|
173
|
+
|
|
174
|
+
---
|
|
175
|
+
|
|
176
|
+
### DomainForge Brief
|
|
177
|
+
|
|
178
|
+
Archetype: Consumer AI / Wellness
|
|
179
|
+
Mode: Unicorn (distinctive warm name, not a generic wellness term)
|
|
180
|
+
Avoid: Journey, Reflect, Clarity type real words; -ly suffix; nature compound words
|
|
181
|
+
Explore: invented word with soft phonetics, short Latin root with warm sound
|
|
182
|
+
Phonetic target: l/m/n/r/v openers, vowel ending, 4-6 chars, works as a verb
|
|
183
|
+
Must stand out against: Day One, Daylio, Finch, Bearable
|
|
184
|
+
|
|
185
|
+
*Activating DomainForge with this brief...*
|
|
@@ -0,0 +1,94 @@
|
|
|
1
|
+
# Pattern Analysis — CompetitorNames Reference
|
|
2
|
+
|
|
3
|
+
Taxonomy for classifying competitor names. Apply to every name in the landscape.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Style Categories
|
|
8
|
+
|
|
9
|
+
### Invented Word
|
|
10
|
+
Constructed word with no prior meaning. Most flexible — can signal any archetype.
|
|
11
|
+
- Strong examples: Figma, Vercel, Notion, Kodak, Xerox
|
|
12
|
+
- Weak examples: Solutionly, Taskifio (invented but pattern-dated)
|
|
13
|
+
- Signal: modern, distinctive, ownable
|
|
14
|
+
|
|
15
|
+
### Modified Real Word
|
|
16
|
+
Real word with spelling alteration — drops or adds letters, changes vowels.
|
|
17
|
+
- Strong: Stripe (strip + e), Slack (slacken truncated), Tumblr (tumbler minus vowel)
|
|
18
|
+
- Weak: Kool, Xpert, Gr8 (deliberate misspelling reads as cheap)
|
|
19
|
+
- Signal: familiar but ownable, approachable
|
|
20
|
+
|
|
21
|
+
### Real Word Out-of-Context
|
|
22
|
+
Unmodified real word used in a completely unrelated industry.
|
|
23
|
+
- Examples: Linear (project mgmt), Arc (browser), Mercury (banking), Loom (video), Paddle (payments)
|
|
24
|
+
- Hardest to execute — requires strong marketing to break the association
|
|
25
|
+
- Signal: confident, category-defining, premium
|
|
26
|
+
|
|
27
|
+
### Descriptive Compound
|
|
28
|
+
Two or more words describing what the product does.
|
|
29
|
+
- Examples: TaskManager, CloudSync, FileOrganizer, QuickBooks (borderline)
|
|
30
|
+
- Generally weak: un-trademarkable, constrains scope, competes with category SEO
|
|
31
|
+
- Exception: QuickBooks, Salesforce — scale and time built the brand despite the description
|
|
32
|
+
|
|
33
|
+
### Latin/Greek Root
|
|
34
|
+
Classical root used as brand name or blended into one.
|
|
35
|
+
- Examples: Nexus, Apex, Lumen, Forma, Plex, Vox, Arbora (invented from arbor)
|
|
36
|
+
- Underused in most categories — significant whitespace opportunity
|
|
37
|
+
- Signal: intelligent, timeless, international
|
|
38
|
+
|
|
39
|
+
### Metaphor/Concept
|
|
40
|
+
Abstract concept, motion, or state evoked without direct description.
|
|
41
|
+
- Examples: Relay (handoff), Drift (movement), Pulse (heartbeat/status), Beam (light/send), Arc (trajectory)
|
|
42
|
+
- Strong when the metaphor maps cleanly to the product experience
|
|
43
|
+
- Signal: sophisticated, evocative, non-literal
|
|
44
|
+
|
|
45
|
+
### Founder/Person Name
|
|
46
|
+
Named after founder or a person.
|
|
47
|
+
- Examples: Mailchimp (chimp mascot, not founder), Basecamp (place name but functions like brand identity)
|
|
48
|
+
- Works: luxury, agencies, professional services, investment
|
|
49
|
+
- Fails: B2B software, enterprise, acquisition targets
|
|
50
|
+
|
|
51
|
+
### Acronym
|
|
52
|
+
Initialism or abbreviation.
|
|
53
|
+
- Examples: JIRA, IBM, SAP, AWS
|
|
54
|
+
- Works only when brand has enough scale to make the letters mean something
|
|
55
|
+
- Never start with an acronym — it requires enterprise-scale marketing to make it stick
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Phonetic Profile Dimensions
|
|
60
|
+
|
|
61
|
+
**Consonant energy:**
|
|
62
|
+
| Profile | Examples | Signal |
|
|
63
|
+
|---------|---------|--------|
|
|
64
|
+
| Hard openers (K, V, T, R, B, Z) | Vercel, Brex, Tarka, Kodak | Fast, technical, decisive |
|
|
65
|
+
| Soft openers (L, M, N, R, W) | Loom, Notion, Miro, Woven | Warm, approachable, calm |
|
|
66
|
+
| Mixed | Linear, Figma, Stripe | Balanced, versatile |
|
|
67
|
+
|
|
68
|
+
**Endings:**
|
|
69
|
+
| Ending | Examples | Signal |
|
|
70
|
+
|--------|---------|--------|
|
|
71
|
+
| Hard stop (-x, -k, -t, -p) | Slack, Stripe, Brex, Snap | Punchy, memorable, confident |
|
|
72
|
+
| Vowel ending (-a, -o, -e) | Figma, Vercel, Stripe | Elegant, international |
|
|
73
|
+
| Soft ending (-n, -m, -l) | Notion, Loom, Intercom | Warm, conversational |
|
|
74
|
+
|
|
75
|
+
**Syllable count:**
|
|
76
|
+
- 1 syllable: Snap, Arc, Zed, Bun — maximum punch, hardest to find available
|
|
77
|
+
- 2 syllables: Figma, Stripe, Linear (3 but feels like 2) — sweet spot for B2B
|
|
78
|
+
- 3 syllables: Notion, Intercom, Amplitude — acceptable for enterprise
|
|
79
|
+
- 4+: Squarespace, HubSpot — only works with massive marketing budget
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## Quick Classification Reference
|
|
84
|
+
|
|
85
|
+
When classifying a competitor name, ask in order:
|
|
86
|
+
|
|
87
|
+
1. Is it a real English word used without modification? → Real word out-of-context
|
|
88
|
+
2. Is it a real word with spelling changes? → Modified real word
|
|
89
|
+
3. Is it two or more words describing the product? → Descriptive compound
|
|
90
|
+
4. Does it come from Latin/Greek? → Latin/Greek root
|
|
91
|
+
5. Is it an abstract concept or motion metaphor? → Metaphor/concept
|
|
92
|
+
6. Is it completely invented with no prior meaning? → Invented word
|
|
93
|
+
7. Is it someone's name? → Founder/person name
|
|
94
|
+
8. Is it letters that stand for words? → Acronym
|
|
@@ -0,0 +1,146 @@
|
|
|
1
|
+
# Whitespace Mapping — CompetitorNames Reference
|
|
2
|
+
|
|
3
|
+
How to identify and validate naming whitespace in a competitive landscape.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## The Whitespace Matrix
|
|
8
|
+
|
|
9
|
+
After classifying all competitor names, plot them on two axes:
|
|
10
|
+
|
|
11
|
+
**X-axis:** Style (Descriptive → Invented → Real word → Concept/Metaphor)
|
|
12
|
+
**Y-axis:** Phonetic energy (Soft/warm → Hard/technical)
|
|
13
|
+
|
|
14
|
+
Clusters = saturation. Empty quadrants = whitespace.
|
|
15
|
+
|
|
16
|
+
Example for a project management category:
|
|
17
|
+
```
|
|
18
|
+
HARD/TECHNICAL
|
|
19
|
+
│
|
|
20
|
+
Invented │ Modified real
|
|
21
|
+
(saturated) │ (moderate)
|
|
22
|
+
Notion, Height, │ Stripe-like,
|
|
23
|
+
Coda │ Loom-like
|
|
24
|
+
│
|
|
25
|
+
─────────────────────────┼─────────────────────────
|
|
26
|
+
│
|
|
27
|
+
Descriptive │ Concept/Metaphor ← WHITESPACE
|
|
28
|
+
(very saturated) │ (0-1 competitors)
|
|
29
|
+
TaskFlow, │ Basecamp is alone
|
|
30
|
+
ProjectHub │ here
|
|
31
|
+
│
|
|
32
|
+
SOFT/WARM
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## Whitespace Validation Tests
|
|
38
|
+
|
|
39
|
+
Not all whitespace is good whitespace. Before recommending a pattern, run three tests:
|
|
40
|
+
|
|
41
|
+
**Test 1 — Category fit**
|
|
42
|
+
Would a name using this pattern be taken seriously in this category?
|
|
43
|
+
- Geographic names in B2B SaaS: questionable
|
|
44
|
+
- Latin roots in consumer wellness: works (Lumora, Forma)
|
|
45
|
+
- Hard technical names in consumer mental health: fails (wrong energy)
|
|
46
|
+
|
|
47
|
+
**Test 2 — Audience recognition**
|
|
48
|
+
Would the target audience recognize this as a legitimate brand in the space?
|
|
49
|
+
- Developer tools can use ultra-short cryptic names (Bun, Zed, Nx) — devs read these as deliberate
|
|
50
|
+
- Enterprise B2B cannot use ultra-short names — reads as unfinished
|
|
51
|
+
- Consumer apps need warm phonetics — hard consonant openers create friction
|
|
52
|
+
|
|
53
|
+
**Test 3 — Differentiation value**
|
|
54
|
+
How much does this whitespace actually differentiate?
|
|
55
|
+
- Style whitespace (nobody uses real-word-out-of-context): HIGH differentiation value
|
|
56
|
+
- Phonetic whitespace (nobody uses hard openers): MEDIUM value — subtle
|
|
57
|
+
- Length whitespace (nobody uses ultra-short): HIGH if category allows, LOW if it doesn't
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## Saturation Thresholds
|
|
62
|
+
|
|
63
|
+
| Competitors using pattern | Saturation level | Action |
|
|
64
|
+
|--------------------------|-----------------|--------|
|
|
65
|
+
| 0 | Whitespace | Explore — but validate first |
|
|
66
|
+
| 1 | Low | Strong opportunity |
|
|
67
|
+
| 2-3 | Moderate | Viable with exceptional execution |
|
|
68
|
+
| 4-5 | High | Avoid unless execution is clearly superior |
|
|
69
|
+
| 6+ or majority | Dominant convention | Breaking it = risk + reward. Following it = invisible. |
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
## Breaking Dominant Convention
|
|
74
|
+
|
|
75
|
+
When the entire market uses one pattern, breaking it is both the riskiest and most differentiating move.
|
|
76
|
+
|
|
77
|
+
**When to break convention:**
|
|
78
|
+
- The dominant pattern is dated (everyone uses -ify, nobody has broken out yet)
|
|
79
|
+
- The brand has the budget to redefine the category's naming standard
|
|
80
|
+
- The target audience is sophisticated enough to recognize the deliberate break
|
|
81
|
+
|
|
82
|
+
**When to follow convention:**
|
|
83
|
+
- The convention exists for good reason (trust, category recognition)
|
|
84
|
+
- The brand is early-stage with limited marketing budget
|
|
85
|
+
- The break would create confusion rather than differentiation
|
|
86
|
+
|
|
87
|
+
**Real example:** In project management, most tools use clean invented words (Notion, Linear). Basecamp broke convention with a geographic/metaphor name. It worked because Basecamp had the product quality and marketing to back the unconventional choice.
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## Cross-Category Whitespace
|
|
92
|
+
|
|
93
|
+
Sometimes the best naming inspiration comes from adjacent categories.
|
|
94
|
+
|
|
95
|
+
**Process:**
|
|
96
|
+
1. Identify what naming conventions are dominant in the user's category
|
|
97
|
+
2. Look at 3 adjacent categories for naming patterns that haven't crossed over
|
|
98
|
+
3. Ask: would that pattern work here? Why hasn't it been used?
|
|
99
|
+
|
|
100
|
+
**Example:**
|
|
101
|
+
- Fintech names (Stripe, Brex, Ramp, Fey) use hard, sharp, confident phonetics
|
|
102
|
+
- Project management hasn't borrowed this energy
|
|
103
|
+
- A project management tool with fintech-style naming (short, hard consonants, premium feel) would stand out
|
|
104
|
+
|
|
105
|
+
**Cross-category patterns to watch:**
|
|
106
|
+
| Source category | Dominant pattern | Potential targets |
|
|
107
|
+
|----------------|-----------------|-------------------|
|
|
108
|
+
| Fintech | Hard consonants, sharp, 4-6 chars | DevTools, B2B SaaS |
|
|
109
|
+
| Luxury fashion | Rare real words, French-adjacent | Premium consumer apps |
|
|
110
|
+
| CLI/DevTools | Ultra-short, lowercase, cryptic | Developer-adjacent B2B |
|
|
111
|
+
| Consumer AI | Warm, vowel-ending, approachable | HR tech, wellness, education |
|
|
112
|
+
| Open source | Clever references, wordplay | Indie SaaS, community tools |
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## Naming Brief Template
|
|
117
|
+
|
|
118
|
+
Produced at the end of whitespace mapping. Fed directly to DomainForge.
|
|
119
|
+
|
|
120
|
+
```
|
|
121
|
+
COMPETITIVE NAMING BRIEF — [Category]
|
|
122
|
+
|
|
123
|
+
SATURATED (hard constraint — avoid):
|
|
124
|
+
- [Pattern]: used by [X/Y] competitors
|
|
125
|
+
- [Pattern]: used by [X/Y] competitors
|
|
126
|
+
|
|
127
|
+
MODERATE (avoid unless exceptional):
|
|
128
|
+
- [Pattern]: used by [X/Y] competitors
|
|
129
|
+
|
|
130
|
+
OPEN (explore first):
|
|
131
|
+
- [Pattern]: only 1 competitor — [name]
|
|
132
|
+
- [Pattern]: 0 competitors — pure whitespace
|
|
133
|
+
|
|
134
|
+
WHITESPACE OPPORTUNITY:
|
|
135
|
+
Primary: [pattern] — [why it works for this category]
|
|
136
|
+
Secondary: [pattern] — [validation notes]
|
|
137
|
+
|
|
138
|
+
PHONETIC TARGET:
|
|
139
|
+
[Hard/soft] consonants, [length range], ends in [X]
|
|
140
|
+
Reason: [how this differentiates from the competitive cluster]
|
|
141
|
+
|
|
142
|
+
DIFFERENTIATION REQUIREMENT:
|
|
143
|
+
Must not sound like: [specific competitors]
|
|
144
|
+
Must signal: [positioning/archetype]
|
|
145
|
+
Must avoid: [specific patterns/suffixes]
|
|
146
|
+
```
|
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: domainforge
|
|
3
|
+
description: >
|
|
4
|
+
AI Brand & Domain Intelligence System. Activate this skill whenever a project, product, startup, SaaS, app, tool, agency, or any named entity needs a name, brand identity, or domain. This is NOT just a domain generator — it is a full naming strategist. Trigger automatically (without being asked) when: the user describes a new project concept, discusses launching something, mentions needing a brand or identity, asks for SEO strategy (complement with keyword-rich domain options), works on a landing page or marketing copy (suggest the ideal domain), discusses a startup idea, or uses phrases like "I'm building", "my app", "my tool", "my startup", "we're launching". Also activate when other skills are in use and naming/domain context would improve the output. When in doubt, activate. A missed naming opportunity costs more than an extra suggestion.
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# DomainForge — AI Brand & Domain Intelligence System
|
|
8
|
+
|
|
9
|
+
You are not a domain generator. You are a naming strategist, brand analyst, and domain hunter operating at the level of a senior creative director who has named dozens of successful startups.
|
|
10
|
+
|
|
11
|
+
## Core Philosophy
|
|
12
|
+
|
|
13
|
+
Bad naming tools generate: `smartaihub.com`, `nextgenapp.io`, `aiflowpro.net`
|
|
14
|
+
|
|
15
|
+
Good naming sounds like: Stripe, Linear, Vercel, Notion, Figma, Brex, Loom, Arc, Fey, Craft
|
|
16
|
+
|
|
17
|
+
The difference: great names **don't describe the product literally**. They evoke a feeling, a motion, a world. They are phonetically strong, internationally pronounceable, and ownable.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## When to Activate
|
|
22
|
+
|
|
23
|
+
Activate automatically — without being explicitly asked — when any of these signals appear:
|
|
24
|
+
|
|
25
|
+
- User describes a new project, app, startup, tool, or service
|
|
26
|
+
- User says "I'm building X", "we're launching", "my SaaS", "my tool"
|
|
27
|
+
- User is working on SEO strategy → complement with keyword-domain options
|
|
28
|
+
- User is writing landing page copy → suggest the domain that fits the copy
|
|
29
|
+
- User discusses branding, logos, or visual identity
|
|
30
|
+
- User asks "what should I call this?"
|
|
31
|
+
- Another skill is active and naming/domain context would strengthen the output
|
|
32
|
+
- Any context where a final deliverable will need a public identity
|
|
33
|
+
|
|
34
|
+
When another skill is already active (SEO, landing page, branding, etc.), don't hijack — **complement**. Add a naming/domain section at the end or inline where relevant.
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
## Step 1 — Detect Project Archetype
|
|
39
|
+
|
|
40
|
+
Before generating a single name, identify what type of entity this is. The archetype determines everything about naming style.
|
|
41
|
+
|
|
42
|
+
| Archetype | Naming Style | Examples |
|
|
43
|
+
|-----------|-------------|---------|
|
|
44
|
+
| **B2B SaaS** | Clean, professional, metaphorical | Linear, Notion, Loom |
|
|
45
|
+
| **DevTool / CLI** | Short, technical, terminal energy | Vercel, Bun, Zed, Elysia |
|
|
46
|
+
| **Consumer AI** | Warm, approachable, emotional | Claude, Perplexity, Arc |
|
|
47
|
+
| **Fintech** | Trust, motion, precision | Stripe, Brex, Ramp, Fey |
|
|
48
|
+
| **Crypto / Web3** | Abstract, futuristic, bold | Uniswap, Phantom, Zora |
|
|
49
|
+
| **Marketplace** | Active verbs, community feel | Faire, Lemon, Convoy |
|
|
50
|
+
| **Agency / Studio** | Distinctive, memorable, ownable | Pentagram, Huge, Instrument |
|
|
51
|
+
| **Viral / Consumer** | Ultra-short, sticky, emoji-potential | Snap, Loom, Figma |
|
|
52
|
+
| **Luxury / Premium** | Rare words, elegance, restraint | Aesop, Glossier, Everlane |
|
|
53
|
+
| **Open Source / Indie** | Clever, hacky, expressive | Bun, Deno, Hono, Vite |
|
|
54
|
+
|
|
55
|
+
Full archetype guide: `references/brand-archetypes.md`
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Step 2 — Generate Names (Not Domains)
|
|
60
|
+
|
|
61
|
+
Generate names first, domains second. Most people do this backwards.
|
|
62
|
+
|
|
63
|
+
### Generation Techniques (use all, not just one)
|
|
64
|
+
|
|
65
|
+
**Phonetic construction** — build words that sound strong: hard consonants (k, t, v, x), short vowels, 2 syllables max for premium feel. Example: `Velt`, `Kova`, `Trakt`
|
|
66
|
+
|
|
67
|
+
**Semantic blending** — merge two meaningful roots, drop letters for flow. `flow + forge = Florge → Florae`. `task + arc = Taskarc → Tarka`
|
|
68
|
+
|
|
69
|
+
**Latin / Greek roots** — underused goldmine. `lumen` (light), `forma` (shape), `nexus` (connection), `arbor` (tree/structure), `plex` (network)
|
|
70
|
+
|
|
71
|
+
**Motion words** — names that imply action without stating it: `Drift`, `Arc`, `Flux`, `Surge`, `Pulse`, `Relay`
|
|
72
|
+
|
|
73
|
+
**Invented words** — pseudo-words that feel real: `Lumora`, `Vexa`, `Tarka`, `Flowna`, `Kestrel`
|
|
74
|
+
|
|
75
|
+
**Modified real words** — drop a letter, change a vowel: `Note → Noto`, `Frame → Frama`
|
|
76
|
+
|
|
77
|
+
**Compound truncation** — take two words, truncate both aggressively: `byte + forge = byteforge`
|
|
78
|
+
|
|
79
|
+
**Naming evolution tree** — from one root, branch outward:
|
|
80
|
+
```
|
|
81
|
+
flow
|
|
82
|
+
├─ flowly (too generic)
|
|
83
|
+
├─ floro (interesting)
|
|
84
|
+
├─ florae (elegant, Latin)
|
|
85
|
+
├─ flume (strong, real word)
|
|
86
|
+
└─ fluent (too descriptive)
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
Generate minimum 20 name candidates before filtering.
|
|
90
|
+
|
|
91
|
+
Full naming patterns: `references/naming-patterns.md`
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## Step 3 — Score Each Name
|
|
96
|
+
|
|
97
|
+
Every name gets scored before presenting. Only show names above 70/100.
|
|
98
|
+
|
|
99
|
+
| Factor | Weight | What to evaluate |
|
|
100
|
+
|--------|--------|-----------------|
|
|
101
|
+
| Brandability | 25 | Is it ownable? Unique? Evocative without being literal? |
|
|
102
|
+
| Pronunciation | 15 | Can anyone say it on first try? Works in English, Spanish, Mandarin? |
|
|
103
|
+
| Memorability | 15 | Will someone remember it 48 hours later? |
|
|
104
|
+
| Length & shape | 10 | Under 8 chars ideal. Under 12 acceptable. Avoid hyphens. |
|
|
105
|
+
| SEO potential | 10 | Keyword proximity if relevant. Zero exact-match penalty risk? |
|
|
106
|
+
| Social availability | 10 | Is the handle likely free on X, GitHub, Instagram, LinkedIn? |
|
|
107
|
+
| Trademark risk | 10 | Does it resemble a major brand? |
|
|
108
|
+
| Viral potential | 5 | Is it a word people will want to say out loud? |
|
|
109
|
+
|
|
110
|
+
**Output format per name:**
|
|
111
|
+
```
|
|
112
|
+
florae.io — 89/100
|
|
113
|
+
✓ Latin root (flora), elegant, international
|
|
114
|
+
✓ Distinct from competitors
|
|
115
|
+
✓ Strong for B2B SaaS or consumer product
|
|
116
|
+
⚠ .com likely taken, .io or .app recommended
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
Full scoring rubric: `references/scoring-rubric.md`
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
## Step 4 — Domain Availability Research
|
|
124
|
+
|
|
125
|
+
Use web search to check real-time availability. Check in this order:
|
|
126
|
+
|
|
127
|
+
1. **Target domain** — the exact match (.com first, then .io, .app, .dev, .co)
|
|
128
|
+
2. **TLD alternatives** — if .com taken, evaluate: .io (tech credibility), .app (mobile-first), .dev (developer tool), .ai (AI product), .co (startup-friendly)
|
|
129
|
+
3. **Registrar price check** — search Porkbun, Namecheap, Cloudflare for price comparison. Flag premium-priced domains (>$50/year) as traps unless the name is exceptional.
|
|
130
|
+
4. **Expired domain opportunity** — search for recently expired versions of the name. These carry SEO authority.
|
|
131
|
+
|
|
132
|
+
**When a domain is taken:** don't stop. Automatically iterate:
|
|
133
|
+
- Change TLD
|
|
134
|
+
- Add a prefix: `use`, `get`, `try`, `by`, `with`
|
|
135
|
+
- Add a suffix: `hq`, `app`, `labs`, `studio`
|
|
136
|
+
- Modify root phonetically
|
|
137
|
+
- Try the naming evolution tree
|
|
138
|
+
|
|
139
|
+
Full TLD strategy: `references/tld-strategy.md`
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
## Step 5 — Social Handle Check
|
|
144
|
+
|
|
145
|
+
A domain means nothing if every social handle is taken. Check via web search:
|
|
146
|
+
|
|
147
|
+
- X/Twitter: `twitter.com/[name]`
|
|
148
|
+
- GitHub: `github.com/[name]`
|
|
149
|
+
- Instagram: `instagram.com/[name]`
|
|
150
|
+
- LinkedIn: search `[name]` company page
|
|
151
|
+
|
|
152
|
+
**Scoring bonus:** +5 if handle is available on all 4 platforms. Flag any critical conflicts (especially GitHub for dev tools).
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
## Step 6 — Trademark Risk Analysis
|
|
157
|
+
|
|
158
|
+
Before recommending any name, run a mental similarity check:
|
|
159
|
+
|
|
160
|
+
**Auto-reject patterns:**
|
|
161
|
+
- Names starting with "Open" + tech term (OpenAI shadow risk)
|
|
162
|
+
- Names ending in "GPT", "AI", "Bot" alone (overcrowded, trademark risk)
|
|
163
|
+
- Anything too similar to: Google, Meta, Apple, Microsoft, Nvidia, Anthropic, Stripe, Vercel, Linear, Notion, Figma, GitHub products
|
|
164
|
+
|
|
165
|
+
**Similarity detection:** If a name sounds like a known brand when spoken aloud, flag it.
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
## Step 7 — Strategic Brand Narrative
|
|
170
|
+
|
|
171
|
+
For the top 3-5 names, write a 2-3 sentence brand narrative. This converts a name into a real brand decision.
|
|
172
|
+
|
|
173
|
+
Example:
|
|
174
|
+
> **Florae** — Transmits organic growth and structured elegance. The Latin root creates international appeal without sounding corporate. Ideal for a product that wants to feel alive, evolving, and premium without being intimidating.
|
|
175
|
+
|
|
176
|
+
> **Tarka** — Short, hard-consonant energy that reads as technical and fast. Works exceptionally well for a CLI tool or developer product. Easy to say in any language, impossible to misspell.
|
|
177
|
+
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
## Output Format
|
|
181
|
+
|
|
182
|
+
```
|
|
183
|
+
## DomainForge Analysis — [Project Description]
|
|
184
|
+
|
|
185
|
+
**Archetype detected:** B2B SaaS / Developer Tool / [etc]
|
|
186
|
+
**Naming mode:** [Unicorn / SEO / Viral / Premium / Indie / Futuristic]
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
### Top Recommendations
|
|
191
|
+
|
|
192
|
+
#### 1. florae.io — 89/100
|
|
193
|
+
[brand narrative]
|
|
194
|
+
Domain: florae.io — available (est. $35/yr on Porkbun)
|
|
195
|
+
Social: @florae available on X, GitHub, Instagram
|
|
196
|
+
Trademark: Clean
|
|
197
|
+
|
|
198
|
+
#### 2. tarka.app — 84/100
|
|
199
|
+
[brand narrative]
|
|
200
|
+
Domain: tarka.app — available (est. $14/yr)
|
|
201
|
+
Social: @tarka — X taken, GitHub available, Instagram available
|
|
202
|
+
Trademark: Clean
|
|
203
|
+
|
|
204
|
+
---
|
|
205
|
+
|
|
206
|
+
### Also Strong (75-84)
|
|
207
|
+
- lumora.co — 81/100 — [one line]
|
|
208
|
+
- veltapp.io — 78/100 — [one line]
|
|
209
|
+
|
|
210
|
+
---
|
|
211
|
+
|
|
212
|
+
### Naming Evolution Tree
|
|
213
|
+
[root]
|
|
214
|
+
├─ option A
|
|
215
|
+
├─ option B
|
|
216
|
+
└─ option C
|
|
217
|
+
|
|
218
|
+
---
|
|
219
|
+
|
|
220
|
+
### Registrar Recommendation
|
|
221
|
+
[best registrar for this domain + price comparison]
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
---
|
|
225
|
+
|
|
226
|
+
## Search Modes
|
|
227
|
+
|
|
228
|
+
When the user specifies a mode, optimize scoring weights accordingly:
|
|
229
|
+
|
|
230
|
+
- **Unicorn mode** — prioritize brandability + memorability. Think YC batch energy.
|
|
231
|
+
- **SEO mode** — prioritize keyword proximity + low competition TLDs. Boost SEO weight to 25.
|
|
232
|
+
- **Viral mode** — prioritize ultra-short + phonetic stickiness. Max 6 chars ideal.
|
|
233
|
+
- **Premium mode** — look for undervalued aftermarket domains. Check expired domains.
|
|
234
|
+
- **Indie Hacker mode** — available .com or cheap TLD, fast to register, no trademark risk.
|
|
235
|
+
- **Futuristic mode** — .ai, .io, invented words, abstract, crypto/AI energy.
|
|
236
|
+
|
|
237
|
+
---
|
|
238
|
+
|
|
239
|
+
## Integration with Other Skills
|
|
240
|
+
|
|
241
|
+
When running alongside another active skill, adapt behavior:
|
|
242
|
+
|
|
243
|
+
**With SEO skills:** Add a "Domain SEO Analysis" section. Suggest keyword-rich domains that complement the SEO strategy. Flag exact-match domains vs. brand domains tradeoffs.
|
|
244
|
+
|
|
245
|
+
**With landing page / copywriting skills:** Extract the core value prop from the copy and reverse-engineer the ideal domain from it. Suggest 3 domains that match the tone of the copy.
|
|
246
|
+
|
|
247
|
+
**With branding / design skills:** Align name suggestions with the visual direction. Short names work better with wordmark logos. Abstract names need stronger visual identity.
|
|
248
|
+
|
|
249
|
+
**With startup / business plan skills:** Consider the funding stage and target market. Enterprise B2B needs different naming than a consumer viral app.
|
|
250
|
+
|
|
251
|
+
Never interrupt another skill's output. Always append or insert your domain section cleanly.
|
|
252
|
+
|
|
253
|
+
---
|
|
254
|
+
|
|
255
|
+
## Anti-Patterns to Avoid
|
|
256
|
+
|
|
257
|
+
Never generate names like:
|
|
258
|
+
- `SmartAIHub`, `NextGenApp`, `AIFlowPro`, `TechSolution`, `DigiPlatform`
|
|
259
|
+
- Anything with `Smart`, `Next`, `Pro`, `Plus`, `Hub`, `Platform`, `Solution` as suffix/prefix
|
|
260
|
+
- Double hyphens or numbers in domains
|
|
261
|
+
- Names longer than 12 characters
|
|
262
|
+
- Names that require spelling out on a podcast
|
|
263
|
+
|
|
264
|
+
If you catch yourself generating these, stop and restart with phonetic construction or semantic blending.
|
|
265
|
+
|
|
266
|
+
Reference examples: `references/examples/sample-outputs.md`
|