@openpresentation/opf 0.10.1 → 0.11.0

package/dist/spec/catalogs/narratives/marketing-strategy.json

@@ -25,7 +25,7 @@
       "description": "Open by establishing the product or service this strategy is for, and what window of time it covers. One slide that tells the audience exactly which world they're being asked to weigh in on.",
       "instructions": "Establish product/service specifics",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "objective",
@@ -33,7 +33,7 @@
       "description": "State the marketing goals in measurable terms: revenue, pipeline, awareness, share. Two or three goals, ranked. Goals without ranking get equal energy and equal mediocrity.",
       "instructions": "Share marketing goals",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "customer",
@@ -41,7 +41,7 @@
       "description": "Detail the target audience. Segments, jobs-to-be-done, decision criteria, where they live in the buying cycle. Specificity here is the foundation everything else stands on.",
       "instructions": "Detail target audience",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "market",
@@ -49,7 +49,7 @@
       "description": "Describe the market landscape: size, growth, segments, behavioral trends. Use external data for credibility and your own research for nuance. Show how the market is changing, not just how big it is.",
       "instructions": "Discuss market landscape",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "competition",
@@ -57,7 +57,7 @@
       "description": "Map the competitive set honestly. Direct, indirect, and substitutes. A 2x2 or feature-comparison framework helps; what matters is that the audience trusts your read of the field.",
       "instructions": "Analyze competitive environment",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "strategy",
@@ -65,7 +65,7 @@
       "description": "Articulate the marketing approach in one sentence and a single supporting frame. Positioning, primary motion, where you choose to play and not play. Clarity here is what makes the tactics that follow coherent.",
       "instructions": "Elaborate marketing approach",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "product",
@@ -73,7 +73,7 @@
       "description": "Highlight the unique value the product brings to the strategy. Lead with the customer outcome; tie it directly back to the customer beat. Avoid feature soup.",
       "instructions": "Highlight unique value",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "price",
@@ -81,7 +81,7 @@
       "description": "Justify pricing and packaging. Show the logic — cost-plus, value-based, competitor-anchored — and the levers you'll use over the period. Price decisions are strategy decisions.",
       "instructions": "Justify pricing strategy",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "place",
@@ -89,7 +89,7 @@
       "description": "Describe distribution channels and the role each plays. Direct, partner, marketplace, retail. Channel mix is often where strategies quietly succeed or fail.",
       "instructions": "Discuss distribution channels",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "promotion",
@@ -97,13 +97,13 @@
       "description": "Reveal the campaign and content tactics that bring the strategy to market. Pair each tactic with the audience and metric it serves. Avoid listing channels for their own sake.",
       "instructions": "Reveal promotional tactics",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "summary",
       "name": "Summary",
       "description": "Recap the strategy in a single page: customer, position, motion, expected outcome. End with the decision or commitment you need from the audience.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Recap key points",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/performance-improvement-plan.json

@@ -25,7 +25,7 @@
       "description": "Begin respectfully and set a constructive tone. Be clear about what this conversation is and isn't. The opening shouldn't catastrophize or sugarcoat — clarity is kinder than either.",
       "instructions": "Begin respectfully and positively",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "set-expectations",
@@ -33,7 +33,7 @@
       "description": "Detail the level of performance expected in the role. Specific behaviors, deliverables, and standards. Expectations the employee can't quote back are expectations they can't meet.",
       "instructions": "Detail desired performance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "identify-problems",
@@ -41,7 +41,7 @@
       "description": "Name the gap between expected and observed performance. Use specific examples and dates rather than impressions. Avoid characterizing the person; focus on the work product and the impact.",
       "instructions": "Highlight struggles and weaknesses",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "possible-solutions",
@@ -49,7 +49,7 @@
       "description": "Suggest improvement strategies tailored to the gaps named above. Behavior changes, structural changes, support structures. Frame them as paths the employee can choose, not orders to follow.",
       "instructions": "Suggest improvement strategies",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "offer-resources",
@@ -57,7 +57,7 @@
       "description": "Make explicit what tools, coaching, training, or peer support is available. Resources demonstrate that the organization is investing in the outcome, not setting the employee up to fail.",
       "instructions": "Propose help and tools",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "motivate-change",
@@ -65,7 +65,7 @@
       "description": "Connect improvement to what the employee values: their growth, their team, their career. Inspire action without minimizing the seriousness of the situation.",
       "instructions": "Inspire improvement action",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "follow-up",
@@ -73,13 +73,13 @@
       "description": "Schedule the check-ins. Frequency, format, criteria for progress. Predictable follow-up turns a PIP from a threat into a plan.",
       "instructions": "Schedule progress check-ins",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Close with confidence in the path forward and a clear restatement of what success looks like. End the meeting having both raised the bar and reaffirmed the relationship.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Encourage and remind success",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/performance-review.json

@@ -23,7 +23,7 @@
       "id": "briefing",
       "name": "Briefing",
       "description": "Frame what this review covers: the period, the unit, the standard you're measuring against. One slide that lets the audience know exactly what they're being asked to evaluate.",
-      "layoutHint": "title-center",
+      "layoutHint": "title",
       "instructions": "Outline presentation objective",
       "slideType": "text"
     },
@@ -33,7 +33,7 @@
       "description": "Lead with the headline result. On track, ahead, or behind, and by how much. Resist softening — clear numbers up front earn credibility for the analysis that follows.",
       "instructions": "Summarize performance findings",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "key-metrics",
@@ -41,7 +41,7 @@
       "description": "Walk through the pivotal indicators. One chart per metric, clear comparison period, target or benchmark visible on the same frame. Help the audience see the data the way you do.",
       "instructions": "Review pivotal indicators",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "team-performance",
@@ -49,7 +49,7 @@
       "description": "Examine collective achievements and how the team contributed. Avoid generic praise; cite specific moves and the people behind them where the audience would expect it.",
       "instructions": "Examine collective achievements",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "highlight",
@@ -57,7 +57,7 @@
       "description": "Spotlight one standout contribution that defined the period. A landmark deal, a launch, a fix, a hire. One vivid example sticks longer than a list of accomplishments.",
       "instructions": "Show key contribution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "analysis",
@@ -65,7 +65,7 @@
       "description": "Dig under the metrics. What drove the numbers, what held them back, what's signal versus noise. Analysis is where the audience learns whether you actually understand the system you're reporting on.",
       "instructions": "Uncover data insights",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "success",
@@ -73,7 +73,7 @@
       "description": "Reinforce the past triumphs that show the system works. Briefly — the audience came for what's next, not a victory lap. Wins earn permission for the harder slides ahead.",
       "instructions": "Reinforce past triumphs",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "challenges",
@@ -81,7 +81,7 @@
       "description": "Name the obstacles encountered honestly. What didn't move, what regressed, what the team is still wrestling with. Understated challenges read as missed signal, not modesty.",
       "instructions": "Highlight encountered obstacles",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "adjustments",
@@ -89,7 +89,7 @@
       "description": "Identify the changes you're making in response. New tactics, reallocations, sunsets. Each adjustment should map to a challenge above — adjustments without diagnosis feel arbitrary.",
       "instructions": "Identify necessary changes",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "strategy-evolution",
@@ -97,13 +97,13 @@
       "description": "Show how the strategy itself evolves heading into the next period. Refinements, sharpened bets, dropped initiatives. The audience should see continuity as well as change.",
       "instructions": "Plan for improvement",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "discussion",
       "name": "Discussion",
       "description": "Open the floor with two or three specific prompts. End the review actively — questions you want answered, decisions you want made — so the meeting yields more than the deck.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Promote active discourse",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/persuade.json

@@ -25,7 +25,7 @@
       "description": "Open with a moment, image, or claim the audience can't easily look away from. The first sixty seconds buy you the next twenty minutes — spend them on something specific and emotionally charged, not on housekeeping.",
       "instructions": "Draw in the audience with a compelling opener",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "challenge-status-quo",
@@ -43,7 +43,7 @@
       "description": "Anchor the issue in a specific person, place, or moment. Story is what gets the argument past the audience's defenses. Pick a story that personalizes the data without overstating it.",
       "instructions": "Share significant stories to illuminate the issue",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "statistic-shock",
@@ -51,7 +51,7 @@
       "description": "Drop in a single statistic that recasts the scale of the problem. One number, presented well, lands harder than a dashboard. Cite the source so the audience can repeat it with confidence.",
       "instructions": "Use impactful stats to highlight the gravity of the issue",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "historical-context",
@@ -59,7 +59,7 @@
       "description": "Show how the issue evolved. Why it has the shape it does today, what was tried, what was missed. Historical context turns 'this is broken' into 'this stayed broken for these reasons.'",
       "instructions": "Show the evolution or history of the issue",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "weave-narrative",
@@ -72,7 +72,7 @@
       "description": "Deliver the surprising or significant turn. The fact, finding, or reframing the rest of the talk has been earning. The revelation should redirect, not merely confirm.",
       "instructions": "Deliver a surprising or significant discovery",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "propose-solution",
@@ -80,13 +80,13 @@
       "description": "Advocate for the change you want. Concrete enough to be acted on, broad enough to inspire. Pair the solution with the smallest credible first step.",
       "instructions": "Advocate for change or propose an actionable solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "final-question",
       "name": "Final Question",
       "description": "Close on a question rather than a summary. The right closing question follows the audience out of the room and into their conversations afterward.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Finish with a thought-provoking question to stimulate audience thinking",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/persuasive-sales.json

@@ -25,7 +25,7 @@
       "description": "Open with a brief framing of who you are and why this conversation is worth the prospect's next thirty minutes. Keep credentials short; the audience cares about their problem, not your résumé.",
       "instructions": "Name & logo",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "big-change",
@@ -33,7 +33,7 @@
       "description": "Name the market shift the prospect's industry is living through. Make it concrete, recent, and undeniable. The change — not the product — is the reason they should care.",
       "instructions": "Highlight market shift",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "response-to-change",
@@ -41,7 +41,7 @@
       "description": "Show how the change is creating winners and losers in the prospect's space. Use named examples where you can. The goal is for the prospect to wonder which side they'll end up on.",
       "instructions": "Show winners & losers",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "benefits",
@@ -49,7 +49,7 @@
       "description": "Paint the outcome a winner experiences: a vivid picture of the prospect's life on the other side of the change. Lead with what changes for them, not with what your product does.",
       "instructions": "Describe benefits, paint a vivid picture",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "capabilities",
@@ -57,7 +57,7 @@
       "description": "Reveal the unique capabilities that make those outcomes possible. Frame them as the 'magic gifts' the prospect needs to win the new game. Highlight what's structurally different from the alternatives.",
       "instructions": "Present unique features as 'magic gifts' to the customer",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "evidence",
@@ -65,13 +65,13 @@
       "description": "Share customer testimonials, case studies, and measurable outcomes from organizations like the prospect's. Pick evidence that maps to the benefits you promised, not generic logos.",
       "instructions": "Share testimonials",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "call-to-action",
       "name": "Call to Action",
       "description": "Ask for the next step in the sales process. Be specific: a pilot, a workshop, a follow-on conversation with a named stakeholder. Make the smallest credible commitment that keeps momentum.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Encourage decision-making",
       "slideType": "text"
     },
@@ -79,7 +79,7 @@
       "id": "close",
       "name": "Close",
       "description": "Close with a final image and contact path. Leave the prospect with one line about why they're better off acting now than later, and clear instructions for how to engage.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Logo & contact info",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/pitch-deck.json

@@ -24,7 +24,7 @@
       "id": "opening",
       "name": "Opening",
       "description": "Open with the company name, logo, and a one-line tagline that doubles as a positioning statement. Set the visual tone for the deck. Keep it confident and uncluttered — this is the cover.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     },
     {
       "id": "purpose",
@@ -95,13 +95,13 @@
       "id": "ask",
       "name": "The Ask",
       "description": "State the round size, intended use of funds, and what milestones the capital takes you to. Be specific — investors should leave knowing exactly what you want and what they get.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     },
     {
       "id": "closing",
       "name": "Closing",
       "description": "Close on a strong final image: logo, contact info, and the one line you most want the investor to remember. Leave space for the conversation that follows.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }

package/dist/spec/catalogs/narratives/problem-solution.json

@@ -24,7 +24,7 @@
       "id": "hook",
       "name": "Hook",
       "description": "Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.",
-      "layoutHint": "title-center"
+      "layoutHint": "title"
     },
     {
       "id": "problem",
@@ -55,7 +55,7 @@
       "id": "ask",
       "name": "The Ask",
       "description": "State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }

package/dist/spec/catalogs/narratives/product-launch.json

@@ -24,7 +24,7 @@
       "id": "opening",
       "name": "Opening",
       "description": "Open with the company brand and a confident visual. Set the tone — this is a moment, not a meeting. One slide that signals the audience is somewhere worth being.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Show company branding",
       "slideType": "text"
     },
@@ -34,7 +34,7 @@
       "description": "Hook the audience with the promise of the talk. Tell them, in one sentence, what they're about to see and why it matters to them. Specific promises buy patient audiences.",
       "instructions": "Hook the audience",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "context",
@@ -42,7 +42,7 @@
       "description": "Set the stage with the world the product enters. The customer reality, the market state, the unmet expectation. Context turns the launch from a product release into a moment in a larger story.",
       "instructions": "Set the stage",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conflict",
@@ -50,7 +50,7 @@
       "description": "Introduce the villain — the problem, friction, or status quo the product opposes. Make the conflict concrete enough that the audience can name a moment they've felt it themselves.",
       "instructions": "Introduce villain/problem",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "stakes",
@@ -58,7 +58,7 @@
       "description": "Emphasize what's at risk if the conflict isn't resolved. Quantify, personalize, dramatize. Stakes are what convert a curious audience into an invested one.",
       "instructions": "Emphasize importance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "reveal",
@@ -66,7 +66,7 @@
       "description": "Showcase the product. One striking visual, one defining capability, one sentence that captures what's new. Earn the applause line; don't bury it under a bullet list.",
       "instructions": "Showcase the solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "raise-stakes",
@@ -74,7 +74,7 @@
       "description": "Highlight where the alternatives fall short and what they cost the customer. Re-energize the room midway by sharpening the contrast with the reveal.",
       "instructions": "Highlight shortcomings of alternatives",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "raise-stakes-again",
@@ -82,7 +82,7 @@
       "description": "Reinforce why change is non-negotiable now. A second beat of stakes, framed differently — perhaps a customer voice or a future cost. Cement the reason to act.",
       "instructions": "Reinforce the need for change",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "sell",
@@ -90,13 +90,13 @@
       "description": "Make the audience want the product. Lead with the outcome it produces in their lives. Pricing, packaging, availability go here, but only after the desire is built.",
       "instructions": "Make them want your solution",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "cta",
       "name": "Call to Action",
       "description": "Close with the single action you want from the audience. Pre-order, sign up, attend, share. Make it simple, specific, and immediate.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Inspire action",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/project-proposal.json

@@ -26,7 +26,7 @@
       "description": "Open with the proposal in one slide: the project name, the audience, the goal, and the headline benefit. If a sponsor reads only this slide, they should still know what they're being asked to approve.",
       "instructions": "Audience hook & objectives",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "problem-statement",
@@ -34,7 +34,7 @@
       "description": "Articulate the problem this project solves and why it deserves resources now. Tie it to a known business goal or pain. Vague problems produce vague approvals.",
       "instructions": "Highlight struggles & project necessity",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "core-concept",
@@ -42,7 +42,7 @@
       "description": "Describe the central idea of the project in plain language. The 'what' before the 'how.' A reader should be able to repeat the concept in one sentence after this slide.",
       "instructions": "Share actionable idea",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "benefits",
@@ -50,7 +50,7 @@
       "description": "Quantify the impact: revenue, cost, risk, customer, capability. Use numbers where possible and clear comparisons where not. Each benefit should map to a metric the sponsor cares about.",
       "instructions": "Spotlight key metrics",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "justification",
@@ -58,7 +58,7 @@
       "description": "Connect the project to broader strategy, OKRs, or constraints the audience already cares about. Show why this project is more important than the alternatives competing for the same resources.",
       "instructions": "Strategic alignment & significance",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "approach",
@@ -66,7 +66,7 @@
       "description": "Lay out how the project will be executed: the solution, the team shape, the budget envelope. Enough detail to feel credible, not so much that it pre-commits to choices that will mature in flight.",
       "instructions": "Solution, resources, & budget",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "timeline",
@@ -74,7 +74,7 @@
       "description": "Show the project phases on a timeline, with major milestones and decision points marked. Sponsors are buying a sequence of bets, not a single launch — make those bets visible.",
       "instructions": "Outline project phases",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "risks",
@@ -82,7 +82,7 @@
       "description": "Name the top risks honestly and pair each with a mitigation or open question. Listing risks without mitigations signals you haven't thought it through; hiding risks signals worse.",
       "instructions": "Consider potential challenges",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "outlook",
@@ -90,13 +90,13 @@
       "description": "Paint the picture of what the organization looks like a quarter or year after the project ships. Stretch beyond the immediate deliverable to the second-order benefits.",
       "instructions": "Envision project impact",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "wrap-up",
       "name": "Wrap Up",
       "description": "Recap the proposal and state the specific decision you're asking for: approval, budget, headcount, sponsorship. Make it easy to say yes today.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Summarize & persuade",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/qbr.json

@@ -23,7 +23,7 @@
       "id": "objectives",
       "name": "Objectives",
       "description": "Open with what this review is for and what decisions you want out of it. Frame the scope and the hour ahead, so the audience knows what they're being asked to weigh in on.",
-      "layoutHint": "title-center",
+      "layoutHint": "title",
       "instructions": "Set the expectations",
       "slideType": "text"
     },
@@ -53,7 +53,7 @@
       "description": "Name the misses and headwinds honestly. What didn't work, what's still hard, what got harder. Pretending things are fine costs more credibility than acknowledging they aren't.",
       "instructions": "Address difficulties",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "insights",
@@ -79,7 +79,7 @@
       "id": "asks",
       "name": "Asks",
       "description": "Specific, named requests of the audience. Decisions needed, resources required, escalations to unblock. End with clarity on what happens next and who owns it.",
-      "layoutHint": "title-left"
+      "layoutHint": "title"
     }
   ]
 }