slice icon Context Slice

Writing Style Usage Guide

The writing style file at uiWriting Style uses a service-section structure. Each service (Gmail, Notion, Slack) has its own section to preserve context-specific styles.

File Structure

The file is organized by service sections:

# Writing Style

## Gmail Style

---

[Prose description of Gmail writing style]

## Notion Style

---

[Prose description of Notion writing style]

## Slack Style

---

[Prose description of Slack writing style]

Reading Service Sections

For email drafting:

  • Read the ## Gmail Style section
  • Extract prose description from that section
  • Use Gmail-specific patterns (greetings, signatures, email structure)

For Notion content:

  • Read the ## Notion Style section
  • Extract prose description from that section
  • Use Notion-specific patterns (document structure, organization)

For Slack messages:

  • Read the ## Slack Style section
  • Extract prose description from that section
  • Use Slack-specific patterns (brief messages, casual tone)

Section Format

Each service section

Prose description:

  • Natural language summary of writing style for that service
  • Distinctive characteristics
  • Examples of style patterns

Parsing Logic

When reading a service section:

  1. Find the section header: ## [Service] Style
  2. Extract content between that header and the next ## header (or end of file)
  3. Extract prose description:

Error Handling

If service section doesn't exist:

  • Check if file exists at all
  • If file exists but section missing, guide user to run the setup task for that service (Gmail, Notion, or Slack) which includes style analysis

If file doesn't exist:

  • Refuse to proceed until style is captured
  • Guide user to run the appropriate service's setup task

Why Service Sections?

Writing style varies significantly by context:

  • Email (Gmail): More formal, structured, greetings/signatures, longer form
  • Notion: More detailed, organized, documentation-style, longer form
  • Slack: More casual, brief, quick responses, shorter form

Preserving service-specific styles ensures accurate voice replication for each context.