OPF Tone
Technical
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.
Tone
Technical
4
cues
4
avoid
“p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.”
Generation cue
State the claim, then the mechanism, then the evidence.
Summary
Precise, evidence-led voice for engineering, research, and product-detail audiences.
OPF Field
tone
Schema
https://openpresentation.org/schema/opf-tone/v1
Voice Cues
- 1
State the claim, then the mechanism, then the evidence.
- 2
Use exact terminology — don't soften technical terms for general readability.
- 3
Quote benchmarks with conditions (cold/warm, p50/p95/p99, dataset, hardware).
- 4
Prefer diagrams and tables over prose paragraphs for structural information.
Avoid
- 1
Vague claims ('much faster', 'better', 'easier').
- 2
Marketing framing without supporting data.
- 3
Glossing over caveats and tradeoffs.
- 4
Casual register that obscures precision.
Sample Phrases
“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.”
Recommended Narrative IDs
challenge-resolutioninnovationconference-talkstatus-updateTags
OPF Config
tones:technical{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "PPTX.gallery — tones/technical",
"tone": "technical",
"tags": [
"gallery:tones/technical"
],
"slides": [
{
"id": "gallery-preview-1",
"layout": "text",
"title": "Tone preview",
"subtitle": "Voice tuned to the \"technical\" tone."
}
],
"catalogs": {
"default": {
"source": "https://www.pptx.gallery",
"tones": {
"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",
"status-update"
],
"tags": [
"technical",
"engineering",
"research"
]
}
},
"layouts": {
"text": {
"name": "Text",
"summary": "Prose. Several blocks sit side by side when short and stack when long.",
"tags": [
"Text"
],
"direction": "column",
"regions": [
{
"name": "title"
},
{
"name": "body",
"accepts": [
"text",
"list",
"quote",
"code",
"group"
],
"role": "primary",
"flow": "auto"
}
],
"description": "Explain one idea in continuous prose. Use paragraphs or flowing blocks for detail that needs to be read in sequence.",
"preview": {
"vectorSrc": "https://www.pptx.gallery/layout-previews/text.svg"
}
}
}
}
}
}Load this config in the gallery's visual editor, or in the Inspector at pptx.dev.