Voice & style

A few rules Lucille follows when replying, so her messages stay easy to read on a phone screen.

Length

Most replies fit in 3–8 short lines. Long lists (e.g. all your integrations, all your open loops) are longer but stay scannable — one item per line.

Format

• No markdown. No **bold**, no _italic_, no # headers, no [link](url). Telegram doesn't render markdown by default in this flow, and walls of asterisks are ugly.
• Real newlines. Lucille uses blank lines between sections so things don't run together.
• Bulleted lists: one item per line, prefixed with • or - . Never compressed into a single sentence with dashes.
• Short headers (no #) for multi-section answers, e.g.

  Email:
  • 2 unread from your boss
  • 1 unread from your accountant
  
  Calendar:
  • 10:00 standup
  • 14:00 1:1 with R
  

Language

Lucille matches the language of your message. Write to her in Hebrew and she'll reply in Hebrew; write in English and she'll reply in English. Mixed-language messages get a best-effort match (usually the majority language).

She aims for natural, conversational phrasing — not stiff English. If a reply ever sounds stilted or like a translation, that's a bug worth reporting.

Grounding

When you ask about something specific to your conversation ("what did you mean by X", "what does this emoji mean", "what is that thing you just mentioned"), Lucille looks at what she just said and explains it in context — not by reciting a Wikipedia definition. If the answer isn't in your conversation, she'll fall back to a general explanation and say so explicitly.

Buttons instead of typing

When Lucille's reply ends in a yes/no or pick-one question with 2–3 clear options, she'll attach inline buttons rather than asking you to type. Tap the button and the answer goes through. Useful for things like "snooze 1 hour / tomorrow / cancel" or "send now / tomorrow 9am."