Create a Beautiful Slide Deck

This is a starter skill for turning source material into a narrative presentation. Adapt it to the user's audience, purpose, voice, and existing way of working rather than treating it as a fixed template.

Context, setup, and planning

Try to understand:

• who will see the deck, what decision or action it should support, and what a good result looks like;
• the source material, required sections, length, deadline, and intended presentation or export format;
• the visual direction and brand, including any existing template or reference the user wants to follow.

When available and relevant, past accepted or winning decks, proposals, reports, discovery notes, and brand materials can calibrate the structure, language, evidence, and visual standard. They are not prerequisites.

For research-heavy, board, investor, proposal, or client decks, agree on the core question, evidence standard, and definition of done. Preserve useful source links and dates, distinguish facts from interpretation, and surface uncertainty rather than polishing over missing evidence.

Establish the narrative before designing slides. Present a concise plan for the story, sections, and visual direction so the user can correct the approach before the full deck is built.

Execution

1. Inside Strawberry, read and use the internal strawberry/general/visual-artifact skill installed by the Strawberry harness for deck creation, critique, and export; it is not part of this public repository. Outside Strawberry, use the environment's presentation tooling and preserve the same narrative, visual critique, and export review.
2. Build around the user's specifics and source material. Remove information that does not serve the audience, and do not invent claims, results, familiarity, or evidence.
3. For decision, pitch, or report decks, lead with the conclusion or finding, then show the evidence and implications in plain language. Use relevant approved visuals such as screenshots, product images, logos, or charts when they strengthen the story.
4. For proposals or RFP responses, map explicit requirements to the deck so important sections are not missed, and use relevant past case studies or team material when available.
5. Review the complete deck for narrative flow, accuracy, legibility, visual consistency, source quality, unsupported claims, and whether it meets the agreed definition of done.
6. Keep the deck reviewable. If it is intended for a client, board, investor, or other external audience, get the user's approval before delivering or sending it.

Suggested outcome

Deliver a polished, coherent visual slide deck ready to present or export. The deck—not an outline or wall of text—is the primary output.

Suggested next steps

After the user has reviewed the deck, incorporate their edits and offer the appropriate export. When the structure, voice, evidence standard, or visual direction will be reused, save the accepted process and concrete preferences as a user-owned skill.