A name for your little one
Two-minute setup. Then you and your partner swipe through names privately, on your own phones, and find the ones you both love.
Your pool list
Every couple's pool list is different โ no generic default. As little as 10 minutes if you power through, or 15โ25 minutes if you both dive deep into your criteria over coffee. Once your free Claude.ai account is set up.
Two partners, one pool. You and your partner both swipe through the same list of names. One of you generates the pool, then shares it (button below). Both phones load the same pool (in something called a JSON format โ don't worry about that).
โ ๏ธ Keep this tab open while you're swiping. If the browser crashes or you close the tab, your swipes (yes/no/maybe) are lost. The names list itself stays saved. To play it safe, send your saved swipes to WhatsApp every so often โ you can paste them back to carry on.
Step-by-step: how to generate your pool list with Claude.ai
-
Open Claude.ai in a new tab. Free tier is fine.
Open Claude.ai โ - Sign in or sign up.
-
Run prompt 1 โ Claude interviews each of you about your criteria.
Show prompt 1
You are helping two parents capture their criteria for picking a baby name. Interview each partner separately. For each, ask: 1. Cultural / heritage origins they want represented or excluded 2. Phonetics they like (vowels-heavy / consonants-heavy / soft endings / etc.) 3. Length and syllable preferences 4. Names that are off-limits (family members, exes, characters, etc.) 5. Religious / cultural associations they want or want to avoid 6. Top 3 names they currently like (to anchor the style) 7. Top 3 names they actively reject (to anchor the no-go zone) 8. Surname they'll be paired with 9. Any siblings' names already taken (to avoid initials/rhythm clashes) 10. Accent considerations โ which accents the name will live in Conduct the interview, summarise each partner's criteria as a structured note.
- Answer Claude's questions together. Both partners' answers in the same conversation. Takes about 5 minutes if you skim, longer if you really dig in.
-
Run prompt 2 โ Claude generates the names. Aims for 500โ1,000.
Show prompt 2
Using the criteria notes from above, generate a pool of baby names that fit BOTH partners' criteria. Target 500 names minimum, up to 1,000. Generate as many as fit comfortably in your token budget without truncation. Quality over quantity past the 500 floor. For each name, output: - name (string) - origin (string โ e.g. "Welsh", "Sanskrit", "Hebrew") - meaning (short string, sourced) - syllables (integer) - source_note (one short sentence โ where the meaning comes from, or a flag like "soft phonetics, accent-stable") Rules: - Cite Behind the Name, Oxford Dictionary of First Names, or named cultural source for every meaning. Don't invent. - Drop anything in either partner's "off-limits" list. - Drop anything in the UK ONS top 30 unless explicitly OK'd. - Mix origins to avoid monoculture. - Keep accent-stable across the partners' relevant accents. CRITICAL OUTPUT FORMAT: Output ONE single raw JSON array and nothing else. - The very first character of your reply must be [ - The very last character of your reply must be ] - No markdown code blocks (no triple backticks) - No preamble like "Here's your array:" - No trailing commentary or explanation - No reasoning text before or after the array
-
Run prompt 3 โ Claude double-checks its own work.
Show prompt 3
Review the JSON array you just produced. For each name, verify: - meaning has a real source - name actually exists in that origin - not in the exclusion list Output the cleaned final array. CRITICAL OUTPUT FORMAT: Output ONE single raw JSON array and nothing else. - The very first character of your reply must be [ - The very last character of your reply must be ] - No markdown code blocks (no triple backticks) - No preamble or trailing commentary - No reasoning text before or after the array
-
Copy Claude's final reply โ that's the JSON. "JSON" is just a way of writing a list so the site can read it. Looks like
[{"name":"Alma",โฆ},โฆ]. Don't worry about understanding it. Press copy in Claude.ai, paste into the box below. - Paste it in the pool list box below โ that's it. The site is forgiving โ it'll strip away any extra wrappers Claude might add.
- Share with your partner. Once the pool is loaded, a "Copy pool to share" button appears at the bottom. Tap it, paste the JSON into your partner's chat (WhatsApp, Messages, anything). They paste it on their phone's setup page. Same pool, both phones.
Just to try the interface. Generate your real pool list afterwards.
How will you share your saved swipes with your partner?
When you've finished swiping, the app saves what you said yes/no/maybe to. You send that to your partner so the app can find matches.
Already swiped before? What you swiped lives in this browser only. Open the site on a different phone, and you'll start fresh โ paste your saved swipes into the matches page to carry on.