AGENT SKILL

presentation-designer

Design compelling slide decks with narrative structure, visual clarity, and delivery-ready polish.

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
presentation-designer
category
creative-design
description
Design compelling slide decks with narrative structure, visual clarity, and delivery-ready polish.

03 SKILL.md 正文

Overview

Great presentations are stories with slides, not documents with animations. The designer's job is to make the narrative land: one idea per slide, visuals that amplify (not duplicate) the speaker's words, and a deck that works both presented and read. This skill covers narrative structure, slide design craft, and the practical details of delivery.

When to use

  • Designing pitch decks, keynote presentations, or sales decks

  • Turning a dense report into a presentable slide narrative

  • Fixing a "wall of text" deck

  • Creating templates for team or company use

  • Preparing for an important talk or investor meeting

Core concepts

      • Narrative first, slides second. Outline the story before designing anything: the tension (problem), the turn (insight), the resolution (your solution/proposal), the ask. Slides serve the story arc.
      • One idea per slide. If a slide needs "and also," it needs to be two slides. Audiences can hold one point at a time; decks that respect this feel effortless.
      • Assertion-evidence structure. Headline states the conclusion ("Churn dropped 40% after onboarding revamp"), body provides the evidence (chart, image, 3 bullets max). Headlines that just label ("Q3 Results") waste the most valuable line.
      • Visuals amplify, text supports. A slide the audience must read is a slide competing with the speaker. Aim for glanceable: big number, simple chart, evocative image — with you providing the narrative.
      • The 10/20/30-ish rule. Keep it tight: ~10 key ideas, ~20 minutes of content for a 30-minute slot (leave room for discussion), 30pt minimum-ish for body text. Fewer, bigger, clearer.
      • Design the read-alone version. Most decks get forwarded without the speaker. Speaker notes or an appendix should let the deck survive on its own — without cluttering the presented slides.

Practical workflow

      1. Write the story. Outline: opening (why should they care?), 3-5 key points in logical sequence, closing (what should they do/feel?). Get the narrative approved before designing.
      1. Storyboard the slides. One line per slide: the assertion headline. Check the headlines alone tell the story — they should read as an executive summary.
      1. Design the system. Title layouts, section dividers, content layouts (big number, chart, image+text, quote), consistent footer/numbering. Build the master slides first.
      1. Build for glanceability. Maximum ~30 words per slide (fewer is better), charts simplified to one message (highlight the data point, gray out the rest), images full-bleed where they earn it.
      1. Refine the details. Alignment, consistent chart styles, readable font sizes from the back of the room (test at 50% zoom), accessible color contrast, alt text for key visuals.
      1. Rehearse with the deck. Time it, note where slides fight the narration, cut ruthlessly. Every slide that doesn't advance the story is a candidate for the appendix.
      1. Prep delivery files. PDF backup (fonts embedded), 16:9 and 4:3 versions if the venue is unknown, videos embedded (not linked), clicker tested, notes printed or on a second device.

Common pitfalls

      • The document-deck. 200 words per slide, 60 slides, read aloud to the audience. If it's a document, send a document; if it's a presentation, present.
      • Bullet-point anesthesia. Slide after slide of undifferentiated bullets. Vary layouts, use visuals, and remember: bullets are for grocery lists.
      • Chart junk. 3D effects, excessive gridlines, legends requiring cross-referencing. Simplify every chart to one message; annotate directly on the data.
      • Tiny text. If the back row can't read it, it shouldn't be on the slide. 24pt minimum for body, bigger for headlines.
      • Inconsistent styling. Five chart styles, three bullet styles, random image treatments. The template exists to be used — enforce it.
      • No clear ask. Ending with "Questions?" or "Thank you" instead of the decision, action, or feeling you need. The last slide should point forward, not just stop.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0