# Oobo.ai Brand Voice Guide

This guide outlines the communication style, tone, and patterns for oobo.ai, ensuring consistency and clarity across all brand content.

### Communication Style

**Overall Tone and Personality:**
Oobo.ai's voice is **authoritative, direct, and developer-centric**. We are a trusted problem-solver, confident in our technical solutions, and empathetic to the challenges faced by modern development teams. Our tone is professional yet approachable, reflecting a deep understanding of the developer's world. We are innovative and visionary, but always grounded in practical utility.

**Key Stylistic Elements and Patterns:**
*   **Concise and impactful:** We favor short, punchy sentences and headlines that get straight to the point.
*   **Problem-solution oriented:** Content often begins by highlighting a clear pain point, then positions Oobo as the elegant solution.
*   **Comparison and contrast:** We frequently use comparisons (e.g., "What git sees" vs. "What's invisible") to clarify our value proposition.
*   **Technical precision with clarity:** Complex technical concepts are explained clearly, often supported by code snippets, command-line examples, or simple conceptual diagrams.
*   **Modular structure:** Content is broken into distinct, digestible sections with clear headings, allowing for easy scanning and understanding.
*   **Direct instruction:** We provide clear, actionable commands and steps, especially in quick-start guides and feature explanations.
*   **Emphasis on "truth" and "visibility":** These themes underscore our core value of bringing transparency to the development process.

**Vocabulary Preferences and Word Choices:**
*   **Developer-native language:** We use terms familiar to our audience (e.g., `commit`, `sessions`, `tokens`, `attribution`, `repo`, `CLI`, `PRs`, `pipelines`).
*   **Action-oriented verbs:** Strong, active verbs convey efficiency and impact (e.g., `tracks`, `captures`, `extends`, `detects`, `builds`, `syncs`).
*   **Benefit-driven, concise nouns:** Words that immediately communicate value (e.g., `memory`, `work ledger`, `durable`, `searchable`, `enriched history`, `transparency`, `alignment`).
*   **Avoids marketing fluff:** We prioritize substance and clarity over buzzwords or overly hyperbolic language.

### Content Patterns

**Common Themes and Topics:**
*   **AI agent integration:** How Oobo enhances the workflow of AI agents in software development.
*   **Git extension/enhancement:** Positioning Oobo as a powerful, non-invasive addition to Git.
*   **Traceability and context:** Capturing the "why" behind code changes, not just the "what."
*   **Developer productivity and insights:** Tools for understanding work, costs, and team alignment.
*   **Open source ethos:** Highlighting our open-source foundation and community focus.
*   **The future of software development:** Envisioning a world where humans and agents build together more effectively.

**Structural Approaches to Content:**
*   **Progressive disclosure:** Start with the high-level concept, then dive into specifics, installation, and advanced features.
*   **Problem-solution narrative:** Clearly state a problem, then introduce Oobo as the definitive solution.
*   **Feature-benefit explanations:** Describe a feature, then immediately articulate its practical benefit.
*   **Code-first examples:** For technical explanations, code snippets often precede or accompany textual descriptions.

**Call-to-Action Styles and Patterns:**
*   **Immediate, actionable commands:** Installation instructions (`curl` commands) are prominent and easy to copy-paste.
*   **Implicit calls to explore:** Encouraging users to "see what happened" or "explore what happened" with Oobo's commands.
*   **Embedded commands:** `oobo` commands themselves act as calls to action, guiding users through interaction.
*   **Direct links:** Clear links to documentation, community, or source code for deeper engagement.

### Audience Interaction

**How the Brand Addresses its Audience:**
We speak to our audience as fellow developers – intelligent, technically proficient, and focused on efficiency. We acknowledge their pain points and offer solutions without condescension. The relationship is one of enablement and partnership.

**Level of Formality and Relationship Style:**
Our formality is **informal yet professional**. We use contractions and a direct, conversational style where appropriate, but maintain precision and respect for the technical subject matter. The relationship is collaborative, positioning Oobo as a powerful tool that empowers developers, rather than dictating how they work.

**Engagement and Conversation Patterns:**
Engagement is driven by practical value and utility. We anticipate developer questions (e.g., "Which repo did I fix auth in last week?") and provide direct answers through Oobo's capabilities. While primarily informative, our content invites interaction through hands-on usage and exploration of the CLI.

### Guidelines & Examples

**Do's and Don'ts for Brand Communication:**

*   **DO:**
    *   Be direct, clear, and concise.
    *   Use developer-centric language and examples.
    *   Focus on problems Oobo solves and the tangible benefits.
    *   Incorporate code snippets and command-line examples generously.
    *   Emphasize transparency, visibility, and "execution truth."
    *   Maintain an authoritative yet approachable tone.
    *   Highlight the open-source nature.

*   **DON'T:**
    *   Use overly casual or informal language that might diminish credibility.
    *   Employ marketing jargon or hyperbole without clear technical backing.
    *   Talk down to the audience or over-explain basic development concepts.
    *   Be vague or ambiguous about Oobo's functionality.
    *   Rely solely on abstract concepts without concrete examples.

**Example Phrases and Expressions that are "On-Brand":**
*   "Git for agents (and humans)."
*   "Nobody tracks work."
*   "Oobo gives every commit memory."
*   "The anchor. Oobo's core primitive."
*   "Two memories. Together they turn disposable local history into a durable, searchable work record."
*   "Use it like git."
*   "See what happened."
*   "The more autonomous software creation becomes, the more valuable execution truth becomes."
*   "15 tools. Zero plugins."

**Content Types and Formats the Brand Uses:**
*   Website marketing copy (like the homepage)
*   Quick start guides and installation instructions
*   Conceptual explanations (e.g., "The anchor," "Two memories")
*   Feature overviews and benefit statements
*   CLI documentation and command examples
*   Visionary statements (e.g., "The bigger picture")