{"version":"1.0","dimension":"tones","items":[{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"formal","name":"Formal","summary":"Polished, restrained voice for board, investor, and regulator audiences.","description":"Authoritative without being cold. Use third-person constructions, full sentences, and concrete numbers. Avoid hedges and humor that depend on shared in-jokes; rely on clarity and precision to land.","voiceCues":["Use third person and the corporate 'we' sparingly.","Lead with the recommendation, then evidence.","Quote concrete numbers; avoid round-tripping ranges.","Prefer full sentences to bullet fragments on key claims."],"avoid":["Slang, idioms, or in-jokes.","Hedging language ('maybe', 'sort of', 'I think').","Marketing superlatives ('world-class', 'best-in-class').","Excessive emoji or exclamation points."],"samplePhrases":["Q4 revenue grew 18% year over year, led by enterprise expansion.","We recommend approving the Series B raise at $30M.","Net retention was 124%; gross retention was 96%."],"recommendedNarratives":["board-meeting","qbr","scqa","strategic-narrative"],"tags":["business","executive","formal"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"casual","name":"Casual","summary":"Warm, plain-spoken voice for internal updates and customer storytelling.","description":"Friendly and direct. Use first- and second-person freely; favor short sentences and contractions. Numbers are still welcome — they just sit alongside human-scale framing rather than leading.","voiceCues":["Use first and second person.","Use contractions ('we're', 'it's', 'don't').","Favor short sentences and active voice.","Frame metrics with a human-scale anchor when possible."],"avoid":["Stiff corporate jargon.","Long compound sentences.","Overuse of superlatives.","Bureaucratic passive voice."],"samplePhrases":["We shipped the new dashboard last week, and customers are already moving over.","Here's where we ended up on hiring this quarter.","It's been a busy month — here's the recap."],"recommendedNarratives":["weekly-progress","status-update","company-intro","all-hands"],"tags":["internal","warm","conversational"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"inspirational","name":"Inspirational","summary":"Aspirational, narrative-driven voice for keynotes, founders, and rallying cries.","description":"Reach for shared belief and possibility, then ground it in something concrete. Use vivid imagery and rhythm; avoid collapsing into hype by always pairing aspiration with a real anchor.","voiceCues":["Open with belief; close with action.","Use rhythm — paired phrases, repetition, deliberate beats.","Pair every aspirational claim with a concrete proof point.","Speak in present tense to make the future feel inevitable."],"avoid":["Empty hype without evidence.","Stacked superlatives ('the very best, world-changing, revolutionary').","Cynical or hedging language.","Dense data tables — push numbers into supporting slides."],"samplePhrases":["We're building the runtime that makes agents feel instant.","When latency disappears, what becomes possible?","The next decade of software belongs to teams who treat speed as a feature."],"recommendedNarratives":["golden-circle","conference-talk","venture-pitch","company-intro"],"tags":["motivational","keynote","founder"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"technical","name":"Technical","summary":"Precise, evidence-led voice for engineering, research, and product-detail audiences.","description":"Lead with the question or claim, then walk through the mechanism and the numbers. Use exact terminology; assume the audience can handle and prefers it. Diagrams, tables, and benchmarks are first-class.","voiceCues":["State the claim, then the mechanism, then the evidence.","Use exact terminology — don't soften technical terms for general readability.","Quote benchmarks with conditions (cold/warm, p50/p95/p99, dataset, hardware).","Prefer diagrams and tables over prose paragraphs for structural information."],"avoid":["Vague claims ('much faster', 'better', 'easier').","Marketing framing without supporting data.","Glossing over caveats and tradeoffs.","Casual register that obscures precision."],"samplePhrases":["p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.","We replaced the streaming serializer with a batched protobuf path; throughput rose 4.2× under load.","The result holds for context windows up to 32k tokens; beyond that, see appendix B."],"recommendedNarratives":["challenge-resolution","innovation","conference-talk","engineering-update"],"tags":["technical","engineering","research"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"persuasive","name":"Persuasive","summary":"Argument-led voice for sales, fundraising, and recommendation-driven decks.","description":"Frame every section as an argument that builds toward an ask. Surface objections, answer them, and pair claims with the strongest available proof. Read more like a memo than a report.","voiceCues":["Lead each section with the claim it's making.","Surface the strongest counter-argument and address it.","Pair every claim with proof — customer, benchmark, or analyst.","End on a clear ask with named owner and date."],"avoid":["Buried leads.","Symmetrical 'on one hand / on the other' framing without a verdict.","Information for its own sake — every chart should advance the argument.","Passive endings without a clear ask."],"samplePhrases":["Adopting our runtime cuts inference latency 8× while preserving accuracy.","The most common objection — 'we'll be locked in' — is addressed by our open OPF spec.","We're asking for a $30M Series B to ship into the enterprise tier."],"recommendedNarratives":["pitch-deck","venture-pitch","early-startup-pitch","persuasive-sales","project-proposal"],"tags":["sales","pitch","argumentative"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"authoritative","name":"Authoritative","summary":"Expert, declarative voice for category-defining and analyst-style decks.","description":"Adopt the perspective of someone who's seen the full landscape and is willing to call it. Use plain declaratives — strong claims with the receipts to back them. Step back from internal-only context and frame in terms the wider industry would recognize.","voiceCues":["Use declarative sentences; trust the reader to follow.","Frame in industry-wide terms, not company-internal language.","Cite outside sources — analysts, benchmarks, public peers.","Take a position; avoid 'on the other hand' symmetry without a verdict."],"avoid":["Hedging ('we believe', 'in our view') unless deliberately contrasting.","Internal jargon and unexplained acronyms.","First-person plural overload — speak for the work, not the team.","Tentative phrasing that softens strong claims."],"samplePhrases":["Agent latency is the bottleneck of the next AI cycle.","Three categories will absorb 80% of enterprise budget; we're built for the second.","The benchmarks are public; the gap holds across every comparable workload."],"recommendedNarratives":["strategic-narrative","pitch-deck","conference-talk","marketing-strategy"],"tags":["industry","category","analyst"]},{"$schema":"https://openpresentation.org/schema/opf-tone/v1","id":"conversational","name":"Conversational","summary":"Direct, dialog-style voice for podcasts, fireside chats, and small-group reviews.","description":"Sound like one half of a real conversation. Ask questions on the slide and answer them; keep paragraphs short; lean into examples over abstractions. Useful when the deck is meant to support a discussion rather than to lecture.","voiceCues":["Ask a question on the slide, then answer it on the next.","Use second person — speak to the room, not at it.","Lean on stories and concrete examples over abstract framing.","Keep each idea to one short paragraph; let the dialog do the rest."],"avoid":["Lecture-style monologue across many bullets.","Hedge-laden academic phrasing.","Stuffing slides — leave room for the discussion.","Inside-baseball references the room may not share."],"samplePhrases":["Why now? Two things changed in the last six months.","Here's the part that surprised us — and what we did about it.","If you take one thing from this section, take this."],"recommendedNarratives":["all-hands","company-intro","weekly-progress","performance-review"],"tags":["dialog","podcast","discussion"]}],"name":"Tones","description":"Presentation voice profiles that shape OPF generation cues, anti-patterns, sample phrasing, and narrative fit.","category":"tones","routes":{"web":"https://www.pptx.gallery/tones","api":"https://www.pptx.gallery/api/tones.json"},"opfSchema":{"name":"tone","url":"https://openpresentation.org/schema/opf-tone/v1"},"lastResearched":"2026-05-06","note":"Tone records follow the OPF tone schema shape from @openpresentation/opf. The id field is the stable OPF reference used by the root tone field; gallery pages keep the canonical record fields intact.","source":"https://www.npmjs.com/package/@openpresentation/opf dist/spec/catalogs/tones"}