# voice.md

## Communication Style

### Overall Tone and Personality
Graphite's communication tone is **confident, innovative, and empowering**. We speak as an authority in modern software development, offering solutions that are both cutting-edge and practical. Our personality is that of a knowledgeable, efficient partner, focused on enabling developers and teams to achieve higher quality and faster delivery. We are professional yet approachable, always prioritizing clarity and directness.

### Key Stylistic Elements and Patterns
*   **Direct and Action-Oriented Language:** We use strong verbs and an active voice to convey immediate value and encourage action.
    *   *Example:* "Create, review, and ship without leaving your PR."
*   **Benefit-Driven Messaging:** Every feature or announcement is framed by the direct benefit it provides to developers and engineering teams.
    *   *Example:* "Review faster, ship sooner."
*   **Problem/Solution Framing:** We often implicitly or explicitly address common developer pain points (e.g., slow reviews, merge conflicts, unblocked work) and position Graphite as the definitive solution.
*   **Concise and Clear:** Our language is efficient, avoiding unnecessary jargon or overly complex sentence structures. We value precision and brevity.
*   **Repetition of Core Concepts:** Key terms like "stacked PRs," "AI code review," "merge queue," "faster," and "ship" are frequently used to reinforce our core value propositions.

### Vocabulary Preferences and Word Choices
*   **Tech-Savvy & Developer-Centric:** We use terms familiar to our audience (e.g., PRs, CI, monorepo, Git, CLI, VS Code, stack-aware, merge queue).
*   **Efficiency & Speed:** Words like *faster, sooner, accelerate, unblocked, instant, momentum, rapid, effortlessly, remarkably fast* are central to our messaging.
*   **Quality & Precision:** We emphasize *higher quality, critical bugs, high signal, focused, precise, reliable*.
*   **Collaboration & Flow:** Vocabulary includes *collaborative, team, unified, seamless, in flow, unblocked*.
*   **Innovation & Modernity:** We position ourselves as *next generation, future-oriented, reimagining, evolutionary, modern*.

## Content Patterns

### Common Themes and Topics
*   **Speed & Efficiency:** How to ship code faster, accelerate reviews, reduce delays, and boost developer productivity.
*   **Quality & Reliability:** Strategies for higher quality code, catching bugs, and improving PRs.
*   **Collaboration & Teamwork:** The power of stacked PRs, streamlined team workflows, and unblocking development.
*   **AI Integration:** The role of AI in code review, AI agents, and leveraging AI for enhanced development.
*   **Modern Development Practices:** Deep dives into stacked PRs, merge queues, efficient CI, and modern PR page design.
*   **Thought Leadership:** Exploring the future of engineering, the evolving role of AI, and best practices in software development.

### Structural Approaches to Content
*   **Marketing Copy:** Features clear headlines, benefit-driven paragraphs, social proof (customer testimonials), concise feature breakdowns, and prominent calls-to-action.
*   **Blog Posts:** Often start with intriguing titles ("Introducing...", "Reimagining...", "How we..."), are clearly categorized, employ a problem/solution narrative, provide educational insights, or announce new features/company milestones.

### Call-to-Action Styles and Patterns
Our CTAs are **direct, action-oriented, and often benefit-reinforcing**. They are clearly visible and typically accompanied by a low barrier to entry.
*   *Examples:* "Get started for free," "Request a demo," "Learn more," "Start stacking," "Sign up."
*   *Reinforcement:* "Free for your first 30 days. No credit card required."

## Audience Interaction

### How the Brand Addresses its Audience
We address our audience directly using "you" and "your," speaking to them as fellow engineers and developers. We position Graphite as a partner and enabler, providing the tools and insights necessary to achieve their professional goals. Our communication implicitly acknowledges their technical expertise and challenges.

### Level of Formality and Relationship Style
The relationship is **professional yet empathetic**. We are experts sharing valuable solutions and insights, but we also understand the day-to-day struggles of development teams. We maintain a respectful, empowering, and trustworthy tone, avoiding overly casual language or academic jargon.

### Engagement and Conversation Patterns
Our content is designed to be **informative and problem-solving**. While direct conversational elements are limited in written marketing, the underlying goal is to engage users by addressing their needs and providing actionable solutions. The presence of features like "Graphite Chat" and links to "Community Slack" suggest an openness to direct interaction.

## Guidelines & Examples

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

**Do's:**
*   Use active voice and strong, precise verbs.
*   Focus on tangible benefits for developers and engineering teams.
*   Employ tech-savvy but clear and accessible language.
*   Emphasize speed, quality, collaboration, and innovation.
*   Position Graphite as an essential tool and thought leader.
*   Address the audience directly using "you" and "your."
*   Provide actionable insights, solutions, or educational value.

**Don'ts:**
*   Use overly abstract, academic, or vague language.
*   Sound generic or overly salesy without substantiating claims.
*   Use jargon that isn't universally understood within the developer community.
*   Adopt a passive voice or indirect phrasing.
*   Overcomplicate sentences or ideas.

### Example Phrases and Expressions that are "On-Brand"
*   "The next generation of code review."
*   "Ship higher quality code, faster."
*   "Review faster, ship sooner."
*   "Stay unblocked with stacked PRs."
*   "Merge without conflicts or delays."
*   "The collaborative AI reviewer built into your PR page."
*   "Everything you need to ship faster."
*   "Seamless workflow."
*   "Reimagining the PR Page: Designing for speed and focus."
*   "Built for the world’s fastest engineering teams."

### Content Types and Formats the Brand Uses
*   Product announcements and launch blogs
*   Changelogs and feature updates
*   Engineering deep dives and how-to guides
*   Thought leadership articles on the future of development and AI
*   Customer success stories and case studies
*   Educational resources and guides (e.g., "how to write better unit tests")
*   Marketing landing pages and feature descriptions