@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.
@@ -0,0 +1,147 @@
1
+ # Brand Archetypes — DomainForge Reference
2
+
3
+ Detailed naming conventions and real-world examples for each archetype.
4
+
5
+ ---
6
+
7
+ ## B2B SaaS
8
+
9
+ **Energy:** Clean, confident, metaphorical. The name implies movement, clarity, or structure without describing the feature.
10
+
11
+ **Naming rules:**
12
+ - 2 syllables preferred
13
+ - Avoid literal product descriptors
14
+ - Strong in .io, .com, .app
15
+ - Names should work on a pitch deck and a billboard equally
16
+
17
+ **Real examples:** Linear, Notion, Loom, Coda, Airtable, Asana, Monday, Intercom, Segment, Amplitude
18
+
19
+ **Generated in this style:** Florae, Tarka, Velta, Quell, Driftio, Relais, Lumora
20
+
21
+ ---
22
+
23
+ ## DevTool / CLI
24
+
25
+ **Energy:** Technical, fast, lowercase-first, terminal-native. The name should look good in a README code block.
26
+
27
+ **Naming rules:**
28
+ - Ultra short: 3-6 chars ideal
29
+ - Works in lowercase: `bun`, `zed`, `vite`, `elysia`, `hono`
30
+ - Hard consonants, one or two syllables
31
+ - .dev, .sh, .io, .build are natural TLDs
32
+
33
+ **Real examples:** Vite, Bun, Deno, Zed, Hono, Elysia, Nx, Turbo, Rspack, Biome
34
+
35
+ **Generated in this style:** Kolt, Trakt, Vex, Quik, Flox, Zarx, Pakt
36
+
37
+ ---
38
+
39
+ ## Consumer AI / Assistant
40
+
41
+ **Energy:** Warm, approachable, slightly magical. The name should make someone feel they're talking to a smart friend, not a machine.
42
+
43
+ **Naming rules:**
44
+ - Soft consonants: l, m, n, r, v
45
+ - Often ends in a vowel sound
46
+ - Works well with color-based brand identity
47
+ - .ai, .com, .app
48
+
49
+ **Real examples:** Claude, Gemini, Perplexity, Otter, Arc, Luma, Cleo, Elsa
50
+
51
+ **Generated in this style:** Lumio, Vela, Miren, Norai, Elva, Cavio, Flori
52
+
53
+ ---
54
+
55
+ ## Fintech / Finance
56
+
57
+ **Energy:** Trust, precision, motion. The name should feel like a Bloomberg terminal meets a design studio.
58
+
59
+ **Naming rules:**
60
+ - Sharp, confident, no ambiguity
61
+ - Avoid anything that sounds like a bank from 1990
62
+ - Money metaphors are fine if subtle (Ramp, Brex)
63
+ - .com preferred for trust. .io acceptable for startup phase.
64
+
65
+ **Real examples:** Stripe, Brex, Ramp, Fey, Mercury, Woven, Pilot, Rippling
66
+
67
+ **Generated in this style:** Relo, Vault, Quota, Ledge, Pario, Finem, Strata
68
+
69
+ ---
70
+
71
+ ## Crypto / Web3
72
+
73
+ **Energy:** Abstract, futuristic, mythological, or mathematical. Conveys decentralization and boldness.
74
+
75
+ **Naming rules:**
76
+ - Abstract or mythological references work well
77
+ - Single strong word or invented word
78
+ - .xyz, .eth, .io, .network
79
+ - Avoid: "Chain", "Block", "Coin", "Token" as standalone words (oversaturated)
80
+
81
+ **Real examples:** Uniswap, Phantom, Zora, Blur, Magic Eden, Argent, Aztec, Arbitrum
82
+
83
+ **Generated in this style:** Zorex, Vanta, Epoch, Axiom, Phaos, Kairos, Ethra
84
+
85
+ ---
86
+
87
+ ## Marketplace / Community
88
+
89
+ **Energy:** Active verbs, community ownership, mutual benefit. The name should feel like a place people go, not a tool they use.
90
+
91
+ **Naming rules:**
92
+ - Often a noun that implies gathering or exchange
93
+ - Avoid corporate suffixes
94
+ - .com strongly preferred (trust for transactions)
95
+ - Names can be slightly longer (8-10 chars) if memorable
96
+
97
+ **Real examples:** Faire, Convoy, Lemon, Airbnb, Etsy, Depop, Whatnot
98
+
99
+ **Generated in this style:** Parcel, Agora, Cordo, Vaunt, Quorum, Relai, Bourse
100
+
101
+ ---
102
+
103
+ ## Agency / Studio / Creative
104
+
105
+ **Energy:** Distinctive, memorable, slightly mysterious. The name is itself a creative act.
106
+
107
+ **Naming rules:**
108
+ - Can be more unusual than product companies
109
+ - Single strong word or a word pair
110
+ - The name IS the brand — it doesn't need to hint at services
111
+ - .com, .studio, .co, .design
112
+
113
+ **Real examples:** Pentagram, Huge, Instrument, IDEO, Ueno, Frog, Wolff Olins, Character
114
+
115
+ **Generated in this style:** Sonder, Veld, Karst, Plinth, Tenon, Gravel, Serif
116
+
117
+ ---
118
+
119
+ ## Viral / Consumer App
120
+
121
+ **Energy:** Ultra-sticky, short enough to say in a conversation, works as a verb. "I'll just [name] it."
122
+
123
+ **Naming rules:**
124
+ - 4-6 characters max for elite tier
125
+ - Can be a real word used out of context (Snap, Zoom, Slack)
126
+ - Invented words must be phonetically obvious
127
+ - .com ideally, .app acceptable
128
+
129
+ **Real examples:** Snap, Zoom, Slack, Loom, Figma, Duolingo, Vine, Kik, Byte
130
+
131
+ **Generated in this style:** Flick, Noti, Velo, Quip, Swiv, Drft, Glim
132
+
133
+ ---
134
+
135
+ ## Open Source / Indie Hacker
136
+
137
+ **Energy:** Clever, slightly nerdy, expressive. The community should feel like they discovered a secret.
138
+
139
+ **Naming rules:**
140
+ - Wordplay and references welcome
141
+ - Can be slightly longer if the reference is clever
142
+ - Works in `.dev`, `.sh`, `.tools`, `.fyi`
143
+ - GitHub org name matters as much as domain
144
+
145
+ **Real examples:** Excalidraw, Mermaid, Obsidian, Logseq, Foam, Tana, Anytype
146
+
147
+ **Generated in this style:** Dendron, Vellum, Glyph, Praxis, Quartz, Ligature, Motif
@@ -0,0 +1,141 @@
1
+ # Sample Outputs — DomainForge Reference
2
+
3
+ Reference examples of full analyses. Use these to calibrate output quality and format.
4
+
5
+ ---
6
+
7
+ ## Example 1: B2B Project Management SaaS
8
+
9
+ **User input:** "I'm building a project management tool for design teams"
10
+
11
+ ---
12
+
13
+ ## DomainForge Analysis — Design Team Project Management
14
+
15
+ **Archetype detected:** B2B SaaS / Design-adjacent
16
+ **Naming mode:** Unicorn (prioritizing brandability)
17
+
18
+ ---
19
+
20
+ ### Top Recommendations
21
+
22
+ #### 1. florae.io — 91/100
23
+ Florae carries the Latin root for flora (organic growth, living systems) while the -ae ending gives it an elegant, design-studio quality. It communicates structure and life without being literal. Feels at home in a Figma plugin panel, a Notion-style homepage, or a Linear-style app.
24
+
25
+ **Domain:** florae.io — likely available (~$38/yr Porkbun)
26
+ **Social:** @florae — check X, GitHub, Instagram
27
+ **Trademark:** Clean — no known conflicts
28
+ **Scoring:** Brandability 24/25 · Pronunciation 14/15 · Memorability 13/15 · Length 10/10 · SEO 7/10 · Social 8/10 · Trademark 10/10 · Viral 5/5
29
+
30
+ #### 2. tarka.app — 86/100
31
+ Tarka is an invented word built on strong phonetics — hard T opening, clean two syllables, -a ending that works across languages. It has the energy of a design tool that moves fast. Short enough for an icon, distinctive enough to own.
32
+
33
+ **Domain:** tarka.app — likely available (~$14/yr)
34
+ **Social:** @tarka — moderate availability, check first
35
+ **Trademark:** Clean
36
+ **Scoring:** Brandability 22/25 · Pronunciation 15/15 · Memorability 13/15 · Length 10/10 · SEO 6/10 · Social 7/10 · Trademark 10/10 · Viral 3/5
37
+
38
+ #### 3. veltra.io — 83/100
39
+ Veltra combines "velocity" with the "-tra" suffix common in elegant Latin-derived words. Reads as premium, motion-oriented, and international. Strong visual shape — ascenders (l, t) create a distinctive wordmark.
40
+
41
+ **Domain:** veltra.io — available (~$35/yr)
42
+ **Social:** @veltra — likely available
43
+ **Trademark:** Check against "Veltra" travel company (different industry, manageable)
44
+ **Scoring:** Brandability 21/25 · Pronunciation 14/15 · Memorability 12/15 · Length 9/10 · SEO 6/10 · Social 8/10 · Trademark 8/10 · Viral 5/5
45
+
46
+ ---
47
+
48
+ ### Also Strong (75-84)
49
+
50
+ - **lumora.co** — 81/100 — Warm, premium, evocative. Luma + -ora. Strong for a design-adjacent product that wants to feel approachable.
51
+ - **kestrel.app** — 79/100 — A real word (bird of prey, speed) used out-of-context. Memorable, distinctive, visual. Check trademark.
52
+ - **relais.io** — 76/100 — French for "relay" or "waystation". Subtle, international, collaborative energy.
53
+
54
+ ---
55
+
56
+ ### Naming Evolution Tree
57
+
58
+ ```
59
+ task + design
60
+ ├─ taskora (too literal)
61
+ ├─ florae (winner — abstracted from growth/structure)
62
+ ├─ veltra (motion/velocity angle)
63
+ ├─ tarka (phonetic construction)
64
+ └─ krona (time/completion, Norse root)
65
+ ```
66
+
67
+ ---
68
+
69
+ ### Registrar Recommendation
70
+
71
+ For **florae.io**: Porkbun ($38.08/yr renewal) or Cloudflare Registrar.
72
+ For **tarka.app**: Porkbun or Namecheap (~$14/yr). .app requires HTTPS (already best practice).
73
+
74
+ ---
75
+
76
+ ## Example 2: Developer CLI Tool
77
+
78
+ **User input:** "Building a CLI tool for managing environment variables across projects"
79
+
80
+ ---
81
+
82
+ ## DomainForge Analysis — Environment Variable CLI Tool
83
+
84
+ **Archetype detected:** DevTool / CLI
85
+ **Naming mode:** Indie Hacker + DevTool (short, technical, lowercase-first)
86
+
87
+ ---
88
+
89
+ ### Top Recommendations
90
+
91
+ #### 1. envx.dev — 94/100
92
+ `env` (universally understood in developer context) + `x` (the execution/extension convention). It reads naturally in a terminal: `npx envx init`, `envx push`, `envx pull`. The `.dev` TLD makes it unambiguous. Extremely memorable in the developer community.
93
+
94
+ **Domain:** envx.dev — check availability (~$12/yr)
95
+ **Social:** @envxdev on GitHub (primary), @envx on X
96
+ **Trademark:** Clean
97
+
98
+ #### 2. dotforge.dev — 88/100
99
+ .dotfile + forge. Developer community understands `.` prefix conventions immediately. Strong combination of familiar reference and creation energy.
100
+
101
+ **Domain:** dotforge.dev — available (~$12/yr)
102
+ **Social:** @dotforge — likely available
103
+ **Trademark:** Clean
104
+
105
+ #### 3. vaultx.sh — 84/100
106
+ Vault (secure storage) + x (CLI convention). `.sh` TLD is a cultural signal for shell tools. `vault` communicates security without overthinking it.
107
+
108
+ **Domain:** vaultx.sh — check availability (~$10/yr)
109
+ **Social:** @vaultx — moderate availability
110
+ **Trademark:** Flag — HashiCorp Vault is well-known. Consider alternative if going commercial.
111
+
112
+ ---
113
+
114
+ ### Also Strong
115
+
116
+ - **dotenv.run** — 80/100 — `dotenv` is the exact term of art, .run implies CLI execution. Very keyword-rich.
117
+ - **envault.dev** — 78/100 — `env` + `vault`. Descriptive but clever portmanteau.
118
+ - **quark.sh** — 76/100 — Physics reference (smallest unit). Clean, 5 chars, .sh TLD. Perfectly brandable.
119
+
120
+ ---
121
+
122
+ ## Example 3: SEO Skill Integration
123
+
124
+ **Context:** User is working on SEO strategy targeting "project management for remote teams"
125
+
126
+ ---
127
+
128
+ *DomainForge activating in SEO mode to complement current strategy.*
129
+
130
+ **SEO Domain Recommendations** (keyword-aligned):
131
+
132
+ | Domain | Search interest | Competition | Verdict |
133
+ |--------|----------------|-------------|---------|
134
+ | remotetasks.io | Medium | High | Skip — too generic |
135
+ | asyncwork.app | Low | Low | Interesting — emerging term |
136
+ | teamdrift.co | Low | Very low | Brand + SEO balance |
137
+ | remotehq.io | Medium | Medium | Overused pattern — skip |
138
+
139
+ **Recommendation in SEO context:** `asyncwork.app` targets an emerging keyword ("async work", "async team") with low competition, and the domain itself is brandable enough to double as a real product name. Score: 79/100.
140
+
141
+ *For a full brand naming analysis, run DomainForge standalone on this project.*
@@ -0,0 +1,168 @@
1
+ # Naming Patterns — DomainForge Reference
2
+
3
+ A systematic library of naming techniques with examples. Use these to generate diverse, high-quality name candidates.
4
+
5
+ ---
6
+
7
+ ## Pattern 1: Phonetic Construction
8
+
9
+ Build words from scratch using phonetic principles. Hard consonants (k, v, x, t, r) + short vowels = strong brand energy.
10
+
11
+ **Formula:** [hard consonant] + [short vowel] + [consonant cluster] + [vowel ending]
12
+
13
+ **Strong consonant openers:** K, V, T, R, B, Z, Dr, Str, Tr, Fl, Gr
14
+ **Strong endings:** -ra, -ta, -ix, -ex, -io, -a, -on, -ar
15
+
16
+ **Examples generated:**
17
+ - Kova (ko-va) — clean, two syllables
18
+ - Veltra — motion + structure
19
+ - Trixa — technical, memorable
20
+ - Zarka — exotic, strong
21
+ - Florix — botanical + tech
22
+ - Drova — fast, directional
23
+
24
+ ---
25
+
26
+ ## Pattern 2: Latin/Greek Root Mining
27
+
28
+ Classical roots are underused. They feel learned without being inaccessible.
29
+
30
+ **High-value Latin roots:**
31
+
32
+ | Root | Meaning | Branding angle |
33
+ |------|---------|----------------|
34
+ | lumen | light | clarity, illumination, insight |
35
+ | forma | shape, form | design, structure, output |
36
+ | nexus | connection | network, integration, link |
37
+ | arbor | tree | growth, structure, branching |
38
+ | finis | end, boundary | completion, precision |
39
+ | plex | network, woven | complexity, integration |
40
+ | vox | voice | communication, audio |
41
+ | apex | peak | excellence, achievement |
42
+ | iter | journey, path | workflow, progress |
43
+ | ratio | reason, calculation | analytics, logic |
44
+
45
+ **Derivative examples:**
46
+ - Lumora (lumen + -ora suffix) = light-like, elegant
47
+ - Formix (forma + -ix) = structured, technical
48
+ - Plexio (plex + -io) = networked platform feel
49
+ - Arbora (arbor + -a) = growth-oriented
50
+
51
+ **High-value Greek roots:**
52
+
53
+ | Root | Meaning | Branding angle |
54
+ |------|---------|----------------|
55
+ | aether | sky, upper air | cloud, elevation |
56
+ | kairos | the right moment | timing, optimization |
57
+ | phaos | light | clarity, AI, insight |
58
+ | telos | end, goal | achievement, outcomes |
59
+ | logos | word, reason | content, intelligence |
60
+ | holos | whole | complete, unified |
61
+
62
+ ---
63
+
64
+ ## Pattern 3: Semantic Blending
65
+
66
+ Take two meaningful words, truncate both, merge them. The result should flow naturally.
67
+
68
+ **Process:**
69
+ 1. Pick two words with relevant meaning
70
+ 2. Try 3-4 truncation points for each
71
+ 3. Combine and test phonetically
72
+ 4. Drop syllables until it flows
73
+
74
+ **Examples:**
75
+
76
+ | Word 1 | Word 2 | Result | Notes |
77
+ |--------|--------|--------|-------|
78
+ | flow | archive | Florc → **Florvex** | push further from obvious |
79
+ | relay | motion | Rel + Mo → **Relmo** | clean, 2 syllables |
80
+ | draft | engine | Draf + In → **Drafin** | clean |
81
+ | pulse | framework | Puls + Ra → **Pulsra** | invented, clean |
82
+ | shift | record | Shif + to → **Shifto** | better than Shifrec |
83
+
84
+ **Key insight:** The blend works when you can't tell where one word ends and the other begins.
85
+
86
+ ---
87
+
88
+ ## Pattern 4: Modified Real Words
89
+
90
+ Take a real, familiar word and make it slightly unreal. Just enough to be ownable.
91
+
92
+ **Techniques:**
93
+ - Drop the last letter: `Note → Noto`, `Frame → Frama`
94
+ - Change one vowel: `Draft → Dreft`, `Craft → Creft`
95
+ - Add one letter: `Arc → Arco`, `Flux → Fluxa`
96
+ - Swap a consonant: `Link → Linc`, `Track → Trakk`
97
+
98
+ **Strong source words for modification:**
99
+ Arc, Beam, Bolt, Cast, Core, Craft, Crest, Dash, Draft, Draw, Drift, Edge, Flow, Forge, Frame, Gleam, Grid, Helm, Hook, Jolt, Key, Lace, Lane, Layer, Lead, Lens, Link, Loop, Mark, Mesh, Mode, Node, Note, Path, Pilot, Port, Prism, Pulse, Relay, Ridge, Ring, Root, Route, Rune, Scale, Scout, Seed, Shift, Signal, Sketch, Slate, Slice, Slide, Sort, Space, Span, Sprint, Stage, Stem, Stream, Strike, Surge, Sweep, Sync, Thread, Track, Trace, Trail, Tune, Vault, View, Wave, Weave, Zone
100
+
101
+ ---
102
+
103
+ ## Pattern 5: Compound Truncation
104
+
105
+ Two complete words mashed together. Keep it under 10 chars total.
106
+
107
+ **Rule:** Both words must survive truncation and still carry meaning.
108
+
109
+ **Good compounds:**
110
+ - `byteforge` (byte + forge) — technical + creation
111
+ - `stacklane` (stack + lane) — developer + path
112
+ - `driftwork` (drift + work) — motion + structure (8 chars) ✓
113
+ - `dotforge` (dotfile + forge) — developer community signal + creation
114
+
115
+ **Strong short prefixes for compounds:**
116
+ arc, bit, bot, byte, cue, dev, dot, fly, hop, hub, ion, key, lab, low, net, node, one, ops, pop, raw, run, tap, via, web, wire, zero
117
+
118
+ ---
119
+
120
+ ## Pattern 6: The Naming Evolution Tree
121
+
122
+ Start from one root concept and branch in 5+ directions before committing.
123
+
124
+ **Template:**
125
+ ```
126
+ [root concept]
127
+ ├─ literal form (usually bad, but start here)
128
+ ├─ metaphorical form
129
+ ├─ phonetic variation
130
+ ├─ Latin/Greek derivative
131
+ └─ modified/blended form
132
+ ```
133
+
134
+ **Example — root concept: "momentum"**
135
+ ```
136
+ momentum
137
+ ├─ Momentum (bad: too long, not ownable)
138
+ ├─ Momen (truncated, passable)
139
+ ├─ Movo (motion + -o suffix)
140
+ ├─ Impetus (too formal, interesting)
141
+ ├─ Kyneto (Greek kinetos = moving)
142
+ ├─ Velo (velo = fast, Latin)
143
+ ├─ Torque (real word, physics)
144
+ └─ Torqa (modified, ownable) ← strong candidate
145
+ ```
146
+
147
+ Always run this tree before presenting names. Ensures diversity of approach.
148
+
149
+ ---
150
+
151
+ ## Anti-Pattern Library
152
+
153
+ Names that should never be recommended.
154
+
155
+ **Banned prefixes:**
156
+ Smart, Next, Fast, Quick, Easy, Best, Top, Pro, Super, Ultra, Hyper, Mega, Power, Auto, Digital, Digi, Tech, Techno, AI (as prefix without strong reason)
157
+
158
+ **Banned suffixes:**
159
+ -Pro, -Hub, -Platform, -Solution, -Suite, -System, -Engine, -Tool, -Service, -Online, -Now, -Plus, -Max, -360, -365, -24/7
160
+
161
+ **Banned patterns:**
162
+ - Two-word generic compounds: TaskManager, FileOrganizer, DataAnalyzer
163
+ - Misspelled common words for no reason: Kool, Xpert, Gr8
164
+ - Geek-coded nonsense: l33t, h4x, pwn
165
+ - Anything ending in -ify or -ize alone: Taskify, Notionize
166
+ - Acronyms that spell nothing: BPMS, SAAS, CRMS
167
+
168
+ **The test:** Say the name out loud: *"Have you tried [name]?"* — If it sounds like you're describing a feature rather than a product, it fails.
@@ -0,0 +1,168 @@
1
+ # Scoring Rubric — DomainForge Reference
2
+
3
+ Detailed evaluation criteria for each scoring factor. Total: 100 points.
4
+
5
+ ---
6
+
7
+ ## 1. Brandability (25 points)
8
+
9
+ The most important factor. A brandable name is ownable, distinctive, and evocative without being literal.
10
+
11
+ **25 pts:** Instantly evocative. Could be mistaken for a funded YC startup. Feels inevitable in retrospect. No one else would have this name.
12
+
13
+ **20 pts:** Strong brand potential. Distinctive, not generic. Minor issues (slight literal hint, or minor phonetic awkwardness).
14
+
15
+ **15 pts:** Decent. Works but forgettable. Might be used by other small companies in adjacent spaces.
16
+
17
+ **10 pts:** Generic. Describes the category. Could be anyone's product name.
18
+
19
+ **0-5 pts:** Terrible. Contains "Smart", "Pro", "Next", "Hub", "Platform", "Solution", "AI" as standalone suffix, or "Tech" as suffix.
20
+
21
+ **Questions to evaluate:**
22
+ - Would a journalist write this name in an article without needing to explain it?
23
+ - Could this appear on a billboard with only the name and a logo?
24
+ - Is it ownable in a crowded market?
25
+
26
+ ---
27
+
28
+ ## 2. Pronunciation (15 points)
29
+
30
+ The name must be sayable by anyone, anywhere. If someone can't say it on a podcast without spelling it out, it fails.
31
+
32
+ **15 pts:** Phonetically obvious. Pronounceable in English, Spanish, Mandarin, German with no ambiguity.
33
+
34
+ **12 pts:** Clear in English. Minor ambiguity in other languages (acceptable for US-focused products).
35
+
36
+ **8 pts:** Requires a moment of thought. Could be said two ways. Might cause embarrassment on a podcast.
37
+
38
+ **4 pts:** Regularly mispronounced. Confusing vowel combinations. Silent letters that aren't obvious.
39
+
40
+ **0 pts:** Unpronounceable or actively confusing.
41
+
42
+ **Red flags:**
43
+ - `gh` in unexpected positions
44
+ - `ph` that could be read as `f` or `p`
45
+ - Endings in `-cht`, `-gn`, `-mn`
46
+ - Double vowels with ambiguous pronunciation: `ei`, `ie`, `oe` mid-word
47
+
48
+ ---
49
+
50
+ ## 3. Memorability (15 points)
51
+
52
+ Will someone remember this name 48 hours after hearing it once?
53
+
54
+ **15 pts:** Sticks immediately. Phonetic hooks. Rhythm. Visual distinctiveness. Could be recalled after hearing in passing.
55
+
56
+ **12 pts:** Memorable with one repetition.
57
+
58
+ **8 pts:** Forgettable. Blends in with similar names in the space.
59
+
60
+ **4 pts:** Actively hard to remember. No hooks, no rhythm, no distinctiveness.
61
+
62
+ **0 pts:** Interchangeable with dozens of other names. No retrieval cue.
63
+
64
+ **What aids memorability:**
65
+ - Alliteration (partial or full)
66
+ - Unexpected consonant clusters
67
+ - Real words used out-of-context (Stripe is a stripe)
68
+ - Strong visual shape (short words with tall letters: k, l, h, t)
69
+ - Ends with a hard stop: Stripe, Slack, Brex, Spark
70
+
71
+ ---
72
+
73
+ ## 4. Length & Shape (10 points)
74
+
75
+ Shorter is almost always better. But more important than length is the visual and phonetic shape.
76
+
77
+ **10 pts:** 4-6 characters. Perfect. Works on favicon, app icon, business card, billboard.
78
+
79
+ **8 pts:** 7-8 characters. Good. Still works everywhere.
80
+
81
+ **6 pts:** 9-10 characters. Acceptable. Gets long in some contexts.
82
+
83
+ **3 pts:** 11-12 characters. Borderline. Will get truncated on mobile.
84
+
85
+ **0 pts:** 13+ characters, or contains hyphens, numbers, or special characters.
86
+
87
+ **Shape bonus (+2, applied outside rubric):** If the name has strong visual letter shape — ascenders and descenders creating visual rhythm — note it as a branding advantage. Example: `Figma` has visual balance. `Stripe` has strong uprights.
88
+
89
+ ---
90
+
91
+ ## 5. SEO Keyword Potential (10 points)
92
+
93
+ This factor's weight doubles (to 20) when the user is in SEO mode.
94
+
95
+ **10 pts:** Contains a high-volume keyword that is also not oversaturated. Domain doubles as a search entry point.
96
+
97
+ **7 pts:** Keyword adjacent. Topically relevant without being exact-match.
98
+
99
+ **4 pts:** No keyword value, but no SEO penalty either. Neutral.
100
+
101
+ **0 pts:** Exact-match domain for a spammy or oversaturated keyword, or name so generic it can't rank for its own brand term.
102
+
103
+ **Note:** For premium B2B SaaS and consumer brands, SEO weight is naturally lower. A name like "Linear" or "Notion" ranks for its brand, not keywords. Penalize this factor less for Unicorn and Premium modes.
104
+
105
+ ---
106
+
107
+ ## 6. Social Handle Availability (10 points)
108
+
109
+ Platforms checked: X/Twitter, GitHub, Instagram, LinkedIn.
110
+
111
+ **10 pts:** Handle available on all 4 major platforms.
112
+
113
+ **7 pts:** Available on 3/4. Missing one non-critical platform.
114
+
115
+ **4 pts:** Available on 2/4. X or GitHub taken is a significant issue for tech products.
116
+
117
+ **1 pt:** Only 1 available. Major friction for launch.
118
+
119
+ **0 pts:** Taken everywhere. Abandon this name unless it is exceptional in every other dimension.
120
+
121
+ **Platform priority by archetype:**
122
+ - DevTool: GitHub > X > Others
123
+ - Consumer app: Instagram > X > TikTok > Others
124
+ - B2B SaaS: LinkedIn > X > GitHub > Others
125
+ - Open source: GitHub > X > Others
126
+
127
+ ---
128
+
129
+ ## 7. Trademark Risk (10 points)
130
+
131
+ **10 pts:** No similar registered trademarks in any adjacent category. Clean search.
132
+
133
+ **7 pts:** Minor similarity to small/regional brands. Not an issue at launch, low risk.
134
+
135
+ **4 pts:** Similar to a known brand in a different industry. Use with caution. Legal opinion recommended before scaling.
136
+
137
+ **0 pts:** Clearly similar to a major brand, tech company, or recent acquisition target. Do not use.
138
+
139
+ **Auto-reject patterns:**
140
+ - Any name that sounds like: Google, Meta, Apple, Microsoft, Stripe, Vercel, Linear, OpenAI, Anthropic, Notion, Figma, GitHub, Nvidia, Adobe, Shopify, Twilio, Salesforce, HubSpot
141
+ - Names containing trademarked terms: GPT, Gemini, Copilot
142
+ - Names that could cause consumer confusion with a direct competitor
143
+
144
+ ---
145
+
146
+ ## 8. Viral Potential (5 points)
147
+
148
+ Can this name spread on its own? Would people use it as a verb or a reference?
149
+
150
+ **5 pts:** Has potential to become a verb or a cultural reference. ("Just Stripe it", "Loom me that")
151
+
152
+ **3 pts:** Natural to recommend. Easy to say in conversation. No friction in word-of-mouth.
153
+
154
+ **1 pt:** People would describe the product, not say the name. No natural referral hook.
155
+
156
+ **0 pts:** Actively awkward to say in conversation.
157
+
158
+ ---
159
+
160
+ ## Final Score Interpretation
161
+
162
+ | Score | Verdict |
163
+ |-------|---------|
164
+ | 90-100 | Exceptional. Present as #1 recommendation with enthusiasm. |
165
+ | 80-89 | Strong. Solid option, recommend confidently. |
166
+ | 70-79 | Good. Include in shortlist with notes on weaknesses. |
167
+ | 60-69 | Weak. Only show if nothing stronger is available. Add caveat. |
168
+ | Below 60 | Reject. Do not present to user. Iterate instead. |