⚡ Promptolis Original · Learning & Growth
🎩 Cultural Register Coach — Formal, Informal, Contextual
Sounding fluent isn't vocabulary; it's register. When to use Sie vs. du, tú vs. usted, vous vs. tu, keigo vs. casual.
Why this is epic
The single biggest 'non-native' tell isn't accent — it's register misuse. Using tú when usted was appropriate, du when Sie was expected, casual keigo with a superior. Natives don't mind grammar imperfections; register mistakes signal 'doesn't understand the social situation.'
This prompt handles register for major-target-languages (Spanish, French, German, Japanese, Korean, Mandarin, Italian, Portuguese) with country-specific and situation-specific calibration. 'Spanish with Mexican family' is different from 'Spanish business in Madrid.'
Also covers written register (email openings, LinkedIn messages, formal letters) where register conventions differ from spoken. Business-formal Japanese email is more formal than spoken business Japanese.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
<language>German</language> <country-region>Germany (Munich specifically — I'm moving there for work)</country-region> <situation>First day at new job. Will meet my boss (CTO, about 50 years old), my direct team (5 people, mix of ages 25-45), and HR. Also company dinner that first week.</situation> <your-status>New hire, 34 years old, American, B2 German</your-status> <their-status>Colleagues in tech company. Company culture unclear — I've only had video interviews.</their-status> <medium>Spoken in-person, also some emails first day</medium>
Register Decision
Default: Sie (formal) with CTO + HR. Potentially du (informal) with team — but wait for their lead. Written emails: Sie with 'Sehr geehrte/r' opening until told otherwise.
Specific Language
With CTO (boss, 50, your superior):
- Sie form. 'Guten Tag, Herr [Surname]. Ich freue mich auf die Zusammenarbeit.'
- Stay Sie until HE invites du. He may: 'Wir duzen uns hier' (we use du here) — then switch.
- Email opening: 'Sehr geehrter Herr [Surname],' / close: 'Mit freundlichen Grüßen,'
With HR:
- Sie form in first meetings. HR tends formal regardless of company culture.
- Emails: Sehr geehrte Frau / Herr [Name]. Stay formal.
With team (5 people, mix of ages):
- Watch what they do. Munich tech culture often du by default — but NOT uniformly.
- If they introduce selves with first name only ('Ich bin Stefan') and use du with each other: they're signaling du-culture.
- If they introduce with first+last and use Sie with you: stay Sie.
- When uncertain: 'Soll ich Sie oder du sagen?' (Should I say Sie or du?) — this direct question is acceptable. Most teams appreciate it.
At company dinner first week:
- Mixed groups often trigger mixed registers. Younger tech colleagues may offer du; CTO still Sie until invited.
- Beer + dinner sometimes lowers register. Don't assume; follow their lead.
Country-Specific Notes
Munich (Bavaria) is moderately formal compared to Berlin tech. Berlin tech is often du-by-default; Munich tech often Sie-by-default with faster transitions to du than Swiss/Austrian companies.
Company-specific culture matters: tech startups often du; established firms Sie. You're moving to an established firm if CTO is 50 + structured role. Lean formal.
Written vs. Spoken Adjustments
First-week emails: always 'Sehr geehrte/r [Name]' opening + 'Mit freundlichen Grüßen' closing. Even with team members.
After Sie→du transition happens: casual email openings acceptable ('Hallo Stefan,' / 'Liebe [Name],').
Internal Slack / Teams chat: often more casual from Day 1. Match team's tone on instant-message platforms; keep email formal longer.
Invitation-to-Casual Watch
Explicit invitations:
- 'Wir duzen uns' (We use du here) — direct invitation
- 'Sag du zu mir' (Say du to me) — personal invitation
- 'Ich bin [First Name]' with informal handshake → often signals du-availability
- Team leader initiates du with everyone → you can use du with team (but still Sie with CTO potentially)
Implicit invitations (less clear):
- Using du with you first — that's clear but sometimes only one-way (they du you; you still Sie them) in professional contexts
- Bavarian regional note: Sie often held longer than in Berlin; don't rush
Common Register Errors
Error 1: Using du with everyone in tech assuming 'tech = casual.'
Munich isn't Berlin. Sie default safer.
Error 2: Mixing Sie + du in same conversation.
Once you're du with someone, stay du. Don't flip back to Sie — confusing.
Error 3: First name + Sie.
'Stefan, könnten Sie...' is awkward. Either 'Herr [Surname] + Sie' or 'Stefan + du.' Not mixed.
Error 4: Being overly formal in return after they've used du with you.
If team leader establishes du with the team, stay Sie only with CTO; team is du.
Error 5: American over-casualness ('Hey, how's it going!').
Even with du colleagues, German professional culture is more restrained than American. 'Guten Morgen, wie geht's?' is friendly-professional; 'Hey!' can read as too casual.
If You Make a Register Error
If you use du with someone who's expecting Sie:
'Entschuldigung, ich hätte Sie sagen sollen. Ich lerne noch.'
(Sorry, I should have said Sie. I'm still learning.)
Usually appreciated. Not catastrophic.
If you use Sie when they've already signaled du preference:
'Ich bin unsicher gewesen — sollen wir duzen?'
(I was uncertain — should we switch to du?)
Clear, acknowledges the signal you missed.
First-week general rule: if uncertain, Sie. Worst case: someone says 'Du kannst mich duzen' and you switch. That's normal + easy. Going from du-that-was-inappropriate back to Sie is harder.
Common use cases
- First meeting with target-language speakers (especially in-laws, business contacts, elders)
- Professional context move to target-language country
- Heritage learners returning to older relatives
- Writing email / letter / message in target language with relationship uncertainty
- Understanding when a native speaker has corrected your register
- Learning a second country's variant (Mexican Spanish vs. Argentine; European Portuguese vs. Brazilian)
Best AI model for this
Opus 4 strongly — register is subtle + cultural. Smaller models produce grammatically correct but register-wrong output.
Pro tips
- When in doubt, start formal. Moving from formal to casual feels natural; moving from casual to formal feels correcting.
- Age matters more than you think in many cultures. Default formal with anyone visibly older in public contexts.
- Status markers (profession, uniform, office) often trigger formal. Doctor, lawyer, teacher, officer: usually formal unless they invite otherwise.
- Written register is often 1 step more formal than spoken. Business email in Japanese/Korean especially.
- Regional variants matter. Mexican 'usted' use is different from Argentine; European Portuguese 'você' is quite formal (different from Brazilian use).
- Watch for invitations to casual. 'Tutéame' (Spanish) or 'duzen wir uns' (German) is explicit invitation to casual. Until invited, stay formal.
- If you mis-use register, not catastrophic. Apologize briefly, adjust. Usually appreciated as learning effort.
Customization tips
- For Japanese specifically: keigo (honorific language) is 3-tier complexity (humble, polite, honorific). Formal business context requires near-fluent honorifics; errors are noticed but tolerated for foreigners. Native-speakers patient with sincere effort.
- For Korean specifically: honorifics are vocabulary-based + verb-ending-based. Age matters enormously (1-year age differences create register differences). Strangers always start formal.
- For Spanish specifically: country variation is significant. Usted use ranges from 'rare in Argentine' to 'common in Mexican family' to 'polite-default in Colombian.' Don't generalize.
- For French specifically: vous with service workers + strangers + workplace; tu earned in friendships. Quebec French slightly more flexible than European.
- For Portuguese specifically: Brazilian 'você' is generally friendly-neutral; European 'você' is formal. 'Tu' in Europe is casual; in Brazil regional (northeast + some south). Big variation.
- For Thai / Vietnamese / other Asian languages with extensive honorifics: research specific cultural context — norms are intricate + highly-respected-when-followed.
Variants
Default Register Decision
Specific situation — which register to use
Email / Written
Formal/casual email register calibration
Business Context
Professional register conventions by language/country
Family / In-Laws
Heritage + marrying-into situations
Regional Variant Navigator
Country-specific register differences
Frequently asked questions
How do I use the Cultural Register Coach — Formal, Informal, Contextual prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Cultural Register Coach — Formal, Informal, Contextual?
Opus 4 strongly — register is subtle + cultural. Smaller models produce grammatically correct but register-wrong output.
Can I customize the Cultural Register Coach — Formal, Informal, Contextual prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: When in doubt, start formal. Moving from formal to casual feels natural; moving from casual to formal feels correcting.; Age matters more than you think in many cultures. Default formal with anyone visibly older in public contexts.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals