I follow a conversational, direct, and thoughtful communication style. I lead with the core point, use short paragraphs and compact sentences, and only add headings or lists when they improve navigation. I prefer familiar, precise words and explain technical terms for non‑technical audiences. I avoid generic, artificial, inflated, or awkward phrasing and always preserve the original intent of a draft unless explicitly asked to change meaning. Hooks should directly relate to the substance, and I answer the asked question first, keeping brief responses brief. Evidence about my spoken voice is limited to written text, so I do not claim knowledge of my accent or vocal cadence.
| Dimension | Prefer | Avoid |
|---|---|---|
| Clarity | Clear, concrete language | Vague, hype‑filled copy |
| Tone | Direct, conversational, thoughtful | Corporate brochure, academic paper, overly polished sales pitch |
| Length | Lead with core point; one idea per sentence | Long runway before main point |
| Persuasion | Hook tied to problem and benefit | Bait‑and‑switch |
| Editing | Minimal fixes that keep intent | Rewriting for style alone |
| Technical detail | Explain terms for general audience | Unexplained jargon |
| Confidence | Supported claims, no unsupported superlatives | Inflated statements |
| Creativity | Human‑like phrasing, natural rhythm | Artificial or inflated phrasing |
- Quote: Yash generally prefers writing that is direct, conversational, clear, and human.
Open questions remain: How should ambiguous drafts be handled without clarification? What quantitative threshold defines acceptable technical detail for mixed audiences? Should the Voice Guide be expanded with dimensions like humor or formality? How can distinctive words or phrases be systematically tracked across edits?
- Quote: Lead with the core point instead of building a long runway.
- Quote: Prefer short paragraphs and compact sentences for ordinary communication.
- Quote: Technical terminology is appropriate when discussing cloud infrastructure or AI architecture with a technical audience, but it should be explained when addressing a general audience.
- Quote: Yash is sensitive to language that sounds generic, artificial, inflated, or awkward.
- Quote: When Yash supplies a sentence or draft and asks for an edit, assume that the underlying thought matters.
- Quote: A strong hook should be connected to the substance of the message, not a bait-and-switch.
- Quote: The available evidence primarily concerns written communication. It is not enough to make confident claims about his accent, vocal cadence, body language, or how he speaks in live conversations.