Use when working inside the ppt-workbench-studio repo, or when the user asks to use their Studio/plugin workflow to generate a deck in the browser editor. Default to reading source links first, then using the user's default browser to open Studio UI, trigger generation, and stop once the request is sent. Use API-first only for true headless generation. Do not use temporary browser profiles.
Use when a Studio deck should explain one system, architecture, chip, engine, platform, device, or core object through a dominant pseudo-3D HTML/CSS hero model page. Focus on left narrative, right single model, strong spatial depth, and restrained executive presentation without dashboard clutter.
neutral core analysis and visualization methodology for PPT Studio generation. Use when generating evidence-led HTML report pages from a brief, especially when deciding whether a chart is justified, how to keep one page to one point, and how to use published module manifests without hard-locking the page into a template.
Repair generated Studio deck pages after real render-fit review without inventing new evidence.
Academic research presentation plugin for Studio. Use when the brief is a paper, study, experiment, method/result presentation, or scholarly research deck.
Case-study narrative plugin for Studio. Use when the brief is really about one company, customer, transformation, rollout, or before/after story and should not default to a strategy memo.
Strategy-mode narrative plugin for Studio. Use only when the brief explicitly asks for decision support, recommendations, prioritization, board, investor, or leadership framing.