Eidetic

Writing Guidelines

Voice, tone, and content principles for consistent, human-centered communication across Eidetic interfaces.

Clear

Use simple, direct language. Avoid jargon and technical terms when possible.

Human

Write like you're talking to a person, not a machine. Be warm and approachable.

Concise

Keep it short. Every word should earn its place. Respect users' time.

Helpful

Guide users toward success. Provide context and next steps when needed.

Voice vs. Tone

Voice is consistent—it's who we are. Tone adapts to the situation.

Voice
Always the same

  • Professional but not stiff
  • Confident but not arrogant
  • Friendly but not casual
  • Smart but not condescending

Tone
Adapts to context

Success messages
Celebratory
Error messages
Supportive
Onboarding
Encouraging
Warnings
Serious

Writing Principles

Core guidelines for all UI copy and content.

  • Lead with the action: Put the most important information or action first. "Save changes" not "Would you like to save your changes?"
  • Use active voice: "You created a new project" not "A new project was created by you"
  • Be specific: "3 items selected" not "Items selected". Give users concrete information.
  • Avoid double negatives: "Enable notifications" not "Don't disable notifications"
  • Use sentence case: Capitalize only the first word and proper nouns. "Create new project" not "Create New Project"
  • Skip the period on single sentences: Button labels and short descriptions don't need periods. Use them in paragraphs.

Button Labels

Buttons should clearly describe the action they perform.

Do: Be specific and action-oriented
  • Save changes
  • Delete project
  • Send invitation
  • Create account
  • Download report
Don't: Be vague or generic
  • OK
  • Submit
  • Click here
  • Yes / No
  • Continue

Button Label Patterns

ActionPrimarySecondary
CreatingCreate [noun]Cancel
EditingSave changesDiscard
DeletingDelete [noun]Keep [noun]
Confirming[Specific action]Cancel
SendingSend [noun]Save draft

Headings & Titles

Clear, scannable headings help users navigate quickly.

Do: Be clear and descriptive
  • Account settings
  • Recent activity
  • Team members
  • Billing history
  • Notification preferences
Don't: Be clever or vague
  • Your stuff
  • What's been happening
  • The squad
  • Money matters
  • Stay in the loop

Numbers & Dates

Consistent formatting makes data easier to scan and understand.

Numbers

  • 1-9: Spell out (one, two, three)
  • 10+: Use numerals (10, 100, 1,000)
  • Large numbers: Abbreviate (1.2K, 3.5M)
  • Percentages: Use symbol (85%)
  • Currency: Symbol before ($99.00)

Dates & Times

  • Relative: Just now, 5 min ago, Yesterday
  • This week: Monday, Tuesday
  • This year: Jan 15, Feb 28
  • Other years: Jan 15, 2024
  • Time: 2:30 PM (12-hour with AM/PM)

Inclusive Language

Write for everyone. Use language that welcomes all users.

Do: Be inclusive
  • They submitted their request
  • Enter your name
  • Team member
  • Assigned to
  • Parent/Guardian
Don't: Make assumptions
  • He submitted his request
  • Enter your Christian name
  • Manpower
  • Master/Slave
  • Mother/Father only

Accessibility in Writing

  • Don't rely on color alone to convey meaning ("Click the red button")
  • Avoid directional language ("See the panel on the right")
  • Write descriptive link text ("View documentation" not "Click here")
  • Use plain language (aim for 8th-grade reading level)

Writing for AI Interfaces

Special considerations when writing for AI-powered features.

  • Set expectations: Be clear about what AI can and cannot do. "AI suggestions may not always be accurate"
  • Explain confidence: Help users understand certainty levels. "High confidence" vs "Needs review"
  • Provide attribution: Make it clear when content is AI-generated. Use badges or labels.
  • Enable control: Give users options to adjust, reject, or override AI suggestions.
  • Be transparent: Explain why AI made a recommendation when possible.
Do: Be transparent about AI
  • AI suggested this response
  • Based on your past activity
  • Review AI recommendations
  • 87% confidence
  • Edit AI-generated content
Don't: Hide AI involvement
  • Magic suggestion!
  • We know what you want
  • Trust our recommendation
  • Definitely correct
  • Auto-generated (locked)

Quick Reference

Always

  • Use sentence case
  • Lead with verbs in buttons
  • Be specific over generic
  • Use active voice
  • Test with real users

Never

  • Use jargon without explanation
  • Blame the user for errors
  • Use ALL CAPS (except acronyms)
  • End with exclamation marks!!!
  • Use "please" excessively

Consider

  • Mobile screen space
  • Localization needs
  • Screen reader users
  • Cognitive load
  • Emotional context