From supervibe
Use WHEN the user asks to create, revise, approve, or export a presentation deck to build a storyboard, HTML slide preview, feedback loop, approved PPTX, and Google Drive handoff. Trigger phrases: 'make a presentation', 'prepare pitch deck', 'create pptx', 'deck for investors', 'presentation mockup'.
npx claudepluginhub vtrka/supervibe --plugin supervibeThis skill is limited to using the following tools:
Build a presentation deck through the same visible review loop as design prototypes: brief, storyboard, HTML preview, browser feedback, approval, `.pptx` export, and Google Drive handoff.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Build a presentation deck through the same visible review loop as design prototypes: brief, storyboard, HTML preview, browser feedback, approval, .pptx export, and Google Drive handoff.
Before storyboard or visual direction, run project memory, code search, and internal supervibe:design-intelligence lookup for slide strategy, layout, copy, chart, typography, color, background, brand, and token evidence. Presentation-director owns narrative; presentation-deck-builder owns implementation.
Read docs/references/design-expert-knowledge.md before deck structure or visual direction. Start with Design Pass Triage from the Eight-Pass Expert Routine and classify deck-owned passes as required | reuse | delegated | skipped | N/A. For decks inside an approved design system, reuse preference and visual-system decisions unless the deck requires a new audience posture, brand reset, or missing token/asset extension. If the system is candidate or needs_revision, resume design-system approval before treating it as reusable. Run the relevant product/audience fit, local evidence lookup, reference scan, storyboard/flow, responsive slide preview, quality review, and feedback/approval passes. External references are supplemental; use the internet only for current references or official platform evidence after local data has been checked.
Use after /supervibe-presentation or whenever the user asks for a pitch deck, report deck, product demo deck, sales deck, training deck, or a .pptx deliverable. This skill is for presentation artifacts, not production UI.
Follow docs/references/skill-expert-operating-standard.md: start from source
of truth, preserve retrieval evidence, apply scope safety, use real producers
with runtime receipts for durable delegated outputs, verify before completion
claims, and keep confidence below gate when evidence is partial.
Before storyboard, preview, or export, read source materials, existing presentation artifacts, approved design-system state, project memory, design intelligence evidence, open browser feedback, and media capability output. If a deck already has approval or unresolved feedback, resume that state instead of starting a parallel deck.
Deck brief lacks audience, desired action, source material, language, or length
-> Ask one focused Step N/M question before storyboard.
Approved design system exists
-> Reuse tokens and visual language; request a design-system extension for missing deck needs.
Deck has unresolved feedback or an approval marker
-> Resume that state instead of starting a parallel deck.
User requests PPTX export before preview approval
-> Block export and route through preview approval.
Requested media exceeds local capabilities
-> Offer storyboard frames, animated HTML, poster sequences, SVG/Lottie specs, or static alternatives.
.pptx is produced only after the user approves the HTML slide preview or an existing deck spec.Step N/M:..supervibe/artifacts/prototypes/_design-system/manifest.json is approved, use its tokens and component language. If deck visuals require new tokens, request a design-system extension instead of inventing a parallel style..supervibe/artifacts/presentations/<slug>/references.md.node "<resolved-supervibe-plugin-root>/scripts/detect-media-capabilities.mjs" --json. If video tooling is unavailable, use storyboard frames, animated HTML preview, poster-frame sequences, SVG/Lottie specs, or static visual metaphors.npm run feedback:status, resolve each item with node scripts/feedback-status.mjs --resolve <id> --resolution <path>, and do not rework already resolved feedback unless the user reopens it..supervibe/artifacts/presentations/<slug>/
brief.md
references.md
storyboard.md
deck.json
preview/index.html
assets/
_reviews/
feedback-resolutions/
export/
google-drive-handoff.md
.supervibe/artifacts/prototypes/_design-system/ if present. If missing, ask whether to run /supervibe-design first or create a presentation-only direction.deck.json using templates/presentation/deck-spec.json.preview/index.html so the user can inspect slides in a browser with the feedback overlay.node scripts/preview-server.mjs --root .supervibe/artifacts/presentations/<slug>/preview --label "<slug> deck" --daemon.**Presentation preview ready:** http://localhost:NNNN
**State:** draft
What do we do next?
- โ
**Approve** - lock deck content and visuals, then export `.pptx`
- โ **Revise** - tell me what to change; I will update the preview and mark feedback items
- ๐ **Alternative** - create another visual/story direction with explicit tradeoffs
- ๐ **Deep review** - run copy, polish, and accessibility reviewers
- ๐ **Stop** - keep as draft
The browser feedback overlay is supplemental. Browser feedback comments are revision inputs, not approval signals. Wait for explicit choice. PPTX export stays blocked until .approval.json is written after the user approves.
feedback-resolutions/<id>.md and mark the item resolved..supervibe/artifacts/presentations/<slug>/.approval.json with status, approvedAt, approvedBy, slide count, feedback rounds, and preview URL.node scripts/build-presentation.mjs --input .supervibe/artifacts/presentations/<slug>/deck.json --output .supervibe/artifacts/presentations/<slug>/export/<slug>.pptx.google-drive-handoff.md from the template. If an authenticated Drive integration exists in the host project, use it; otherwise prepare a drive-ready manifest with file path, title, owner, folder target, and upload steps.=== Presentation Deck ===
Slug: <slug>
Location: .supervibe/artifacts/presentations/<slug>/
Slides: <count>
Preview URL: http://localhost:NNNN
Approval: draft | approved
Export: .supervibe/artifacts/presentations/<slug>/export/<slug>.pptx | pending
Drive handoff: .supervibe/artifacts/presentations/<slug>/google-drive-handoff.md | pending
Confidence: <N>.<dd>/10
Override: <true|false>
Rubric: prototype
asking-multiple-questions-at-once - bundling audience, goal, style, assets, and deadline into one message.advancing-without-feedback-prompt - exporting .pptx without giving the user the approve/revise/alternative/deep-review/stop choice.random-regen-instead-of-tradeoff-alternatives - creating a new deck direction without naming what changes and what it gives up.pptx-before-approval - producing the final deck before the preview is accepted.parallel-design-system - inventing a separate deck visual system when an approved project design system exists.promising-video-without-capability-check - committing to video export without checking available local tools.reference-copying - copying a deck's layout or brand wholesale instead of extracting patterns.supervibe:_design:presentation-director - story, audience, visual references, and design direction.supervibe:_design:presentation-deck-builder - deck spec, preview, feedback revisions, PPTX export, and Drive handoff.supervibe:_design:creative-director - brand and visual direction.supervibe:_design:copywriter - headline, narrative, and speaker-note copy.supervibe:_design:ui-polish-reviewer - visual QA for final slides.supervibe:_design:accessibility-reviewer - contrast, readable type, and reduced-motion checks.deck.json validates against the supported structure.supervibe-preview and accepts browser feedback..pptx export..pptx exists and begins with ZIP magic bytes PK..pptx and names the target owner/folder.