# voice.md

## Communication Style

### Overall Tone and Personality
Waycar's tone is **direct, confident, and highly functional**, much like a reliable tool designed for developers. It's **authoritative** when explaining technical advantages, yet **approachable and empathetic** to user pain points. The personality is **efficient and solution-oriented**, valuing clarity and seamless operation. There's a subtle blend of technical prowess and user-centric care.

### Key Stylistic Elements and Patterns
*   **Concise and Punchy:** Short sentences and paragraphs are preferred. Headlines are often impactful, almost like taglines.
*   **Benefit-Driven Language:** Focuses on what the user gains, often starting with the outcome (e.g., "Your agents stay attached.").
*   **Problem/Solution Framing:** Clearly identifies a common issue (e.g., "SSH drops when your phone moves.") and immediately presents Waycar as the superior solution.
*   **Direct Comparisons:** Often juxtaposes Waycar's capabilities against alternatives (e.g., "mosh vs SSH").
*   **Extensive Use of Lists:** Bullet points are frequently used to break down features, benefits, and instructions for easy scanning.
*   **Action-Oriented Verbs:** Employs strong, active verbs that convey capability and efficiency (e.g., "survives," "catches up," "roams," "skips").
*   **Technical but Accessible:** Uses industry-specific terms (mosh, SSH, tmux, herdr) confidently, but ensures their impact and benefits are clear to a technically proficient audience.
*   **Emphasis on Security & Privacy:** Highlights "no account" and "nothing in between" as core values.

### Vocabulary Preferences and Word Choices
*   **Technical Terms:** `mosh`, `SSH`, `tmux`, `herdr`, `agent`, `host`, `terminal`, `UDP`, `Keychain`, `SwiftUI`.
*   **Benefit-Oriented:** `attached`, `survives`, `catches up`, `roams`, `seamless`, `quick`, `native`, `private`.
*   **Direct & Clear:** `still attached`, `no reconnect`, `just talk`, `pick up where you left off`, `straight to your machine`.
*   **Minimalist Adjectives:** Avoids overly flowery or marketing-heavy language, opting for precise and functional descriptors.

## Content Patterns

### Common Themes and Topics
*   **Connectivity & Persistence:** Maintaining sessions across network changes, surviving dead zones.
*   **Efficiency & Productivity:** Streamlining workflows, quick returns to tasks, skipping unnecessary steps.
*   **Integration & Compatibility:** Working with existing tools like `tmux` and `herdr`, and AI agents.
*   **Security & Privacy:** Emphasizing direct connections and no cloud accounts.
*   **Native Experience:** Highlighting the benefits of a native app and UI.

### Structural Approaches to Content
*   **Headline-Feature-Benefit:** Each major section starts with a bold, benefit-driven headline, followed by a brief explanation and a list of specific advantages.
*   **Numbered Steps:** Used for clear, sequential instructions (e.g., "Quit by accident?").
*   **Q&A Format:** Occasionally uses questions as sub-headers to address potential user queries.
*   **Visual Cues:** Implied use of icons or simple graphics to enhance readability (e.g., `_◎_`, `_▍_`).
*   **Comparison Tables:** Effective for outlining differences and compatibility between features or integrations.

### Call-to-Action Styles and Patterns
CTAs are direct and integrated into the content flow.
*   **Prominent Buttons:** "Download" is a clear, primary CTA.
*   **Embedded Commands:** Installation instructions are provided as direct code snippets (`curl -fsSL ...`).
*   **Implied Actions:** Within feature descriptions, actions are suggested (e.g., "Tap Test Mosh to check," "Tap Closed").
*   **Help & Support:** Links to "Help" and "Articles" are readily available for further engagement.

## Audience Interaction

### How the Brand Addresses Its Audience
The brand addresses its audience directly using "you" and "your," fostering a personal yet professional relationship. It speaks to developers and technical users, assuming a foundational understanding of concepts like SSH and mosh.

### Level of Formality and Relationship Style
The relationship is **professional and helpful**, like a trusted technical assistant. It avoids overly casual slang but isn't stiffly formal. There's an underlying empathy for the user's workflow and common frustrations, making the brand feel supportive and understanding.

### Engagement and Conversation Patterns
Engagement is primarily through providing clear solutions and information. While not overtly conversational, the language anticipates user questions and addresses them directly. Questions like "Quit by accident?" demonstrate an understanding of user behavior. The brand "talks" to the user by showing, not just telling, how Waycar improves their experience.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**Do's:**
*   **Be Direct and Concise:** Get straight to the point.
*   **Focus on Benefits:** Always articulate "what's in it for the user."
*   **Use Active Voice:** Emphasize Waycar's capabilities.
*   **Employ Bullet Points and Lists:** Enhance readability and scannability.
*   **Address the User Directly:** Use "you" and "your."
*   **Highlight Privacy and Security:** Reinforce "no account" and "nothing in between."
*   **Provide Technical Context:** Use relevant terms, but ensure the impact is clear.

**Don'ts:**
*   **Be Vague or Ambiguous:** Avoid corporate jargon or fluffy language.
*   **Over-Explain Basic Concepts:** Assume a baseline technical understanding.
*   **Use Passive Voice:** It weakens the message.
*   **Be Overly Formal or Casual:** Maintain a balanced, professional, yet approachable tone.
*   **Distract with Unnecessary Details:** Keep content focused on core features and benefits.

### Example Phrases and Expressions That Are "On-Brand"
*   "Your agents stay attached."
*   "survives network changes"
*   "Skip the terminal. Just talk to your agent."
*   "Quit by accident? Pick up where you left off."
*   "Phone to machine. Nothing in between."
*   "A real, native terminal."
*   "No reconnect."
*   "Still attached."

### Content Types and Formats the Brand Uses
*   **Marketing Landing Pages:** Feature-rich, benefit-driven overviews.
*   **Product Descriptions:** Detailed explanations of functionalities.
*   **How-to Guides/Setup Instructions:** Clear, step-by-step processes.
*   **Comparison Charts:** Highlighting differences between Waycar and other tools or features.
*   **FAQ Sections:** Addressing common questions directly.
*   **Help Articles:** In-depth support and troubleshooting.