Deck Builder — Taking the friction out of presentations
Working within a network meant collaborating with agencies using Google Slides, Figma, Keynote and PowerPoint. At Keep Left, even routine presentations often needed a designer to clean them up before they could go out.
Content and design availability rarely lined up neatly. One person would be waiting for the content, while another was waiting for someone to format it.
The team turns its own notes or rough slides into an on-brand deck without waiting on a designer. Under the hood it’s an AI skill I built in Claude on top of Keep Left’s design system.
Working from the team’s content
A Word document or rough set of PowerPoint slides can provide the input. The team prepares what it needs to say, then the skill uses the design system to build the deck.
For routine presentations, that reduces the dependency on a separate design booking and the back-and-forth required to finish the job.
Preserving the information
The skill is required to preserve the supplied data. Its job is to interpret the presentation requirements and arrange the content, while retaining the information the team provided.
The finished deck still needs review before it is used.
Rolling it out
I set a two-month onboarding period, with every output sent to me for review. Feedback from those decks was used to refine the skill and establish a review step in the workflow.
Time saved
I estimate it can save around three to four hours per presentation across preparation, formatting and cleanup.
My role
I built the Claude-based skill, established the input and review workflow and managed its rollout.
Deck Builder — Taking the friction out of presentations
I built Keep Left’s design system and the guidance for interpreting content, then reviewed the outputs as an art director and refined the skill.
Client
Keep Left
My role
Workflow design and AI skill development
When
2026
Left brain