skills/diagnostic-deep-dive-writer/references/voice-profile.md

# Voice Profile

## Overall voice

A practitioner thinking out loud with a smart peer. Curious, technical, skeptical of easy answers, comfortable admitting uncertainty, and willing to make fun of the complexity without turning the post into comedy.

The writing should feel discovered in motion rather than delivered from a podium.

## Language

- Default to the language and dialect already demonstrated by the user or source material.
- For Egyptian Arabic, preserve natural spoken syntax and useful Arabic-English code-switching.
- Keep genuine industry terms in English when that is how practitioners say them: `ROAS`, `MMM`, `R-hat`, `Event ID`, `Decision Gate`, `Prior Sensitivity`.
- Do not add English as decoration. The reasoning should still be expressed in natural Arabic when Arabic is the base language.
- Do not sanitize useful roughness such as `طب`, `أهو`, `استنى`, `يعني`, `حاسك`, or quick self-corrections when the source voice uses them.

## Stance

Competent but curious. Never guru-like. Never fake-humble.

Show expertise through the questions asked, the distinctions made, the examples chosen, and the decisions that follow. Avoid declarations such as “as an expert” or “the secret is”.

## Rhythm

Use mixed paragraph lengths. A common cadence is:

1. normal sentence or short paragraph
2. short interruption
3. question
4. concrete example
5. deeper explanation
6. small human aside when the cognitive load gets high

Do not turn every sentence into a one-line paragraph. Do not smooth the prose into essay rhythm.

## Openings

Prefer one of these moves:

- a real friction point
- a question that kept returning during the work
- a surprising failure after something appeared to work
- a continuation of an unresolved question from the previous post
- a familiar practitioner belief that needs qualification

Avoid generic “today we will discuss” openings and manufactured clickbait.

## Explanation behavior

Introduce the need before the technical name.

Preferred order:

`experience/problem -> intuitive explanation -> technical name -> decision consequence`

Do not start with dictionary definitions unless the user explicitly asks for a glossary.

## Humor

Humor is a cognitive reset, not the content. Use it after dense material or to puncture overconfidence. Keep it sparse enough that the serious claim remains serious.

## Endings

For deep-dive series, prefer an unresolved next problem, experiment, or test over a generic summary or engagement CTA.

Use a lead-magnet CTA only when a real artifact exists and the CTA is part of the user's goal.