[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVG1YENRRC07563F6RSS3X":3,"skill-same:01M7EVG1YENRRC07563F6RSS3X":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EVG1YENRRC07563F6RSS3X","presentation-designer",null,"Design compelling slide decks with narrative structure, visual clarity, and delivery-ready polish.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-presentation-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: presentation-designer\ndescription: Design compelling slide decks with narrative structure, visual clarity, and delivery-ready polish.\ncategory: creative-design\n---\n\n## Overview\n\nGreat presentations are stories with slides, not documents with animations. The\ndesigner's job is to\nmake the narrative land: one idea per slide, visuals that amplify (not\nduplicate) the speaker's\nwords, and a deck that works both presented and read. This skill covers\nnarrative structure, slide\ndesign craft, and the practical details of delivery.\n\n## When to use\n\n- Designing pitch decks, keynote presentations, or sales decks\n\n- Turning a dense report into a presentable slide narrative\n\n- Fixing a \"wall of text\" deck\n\n- Creating templates for team or company use\n\n- Preparing for an important talk or investor meeting\n\n## Core concepts\n\n- - - **Narrative first, slides second.** Outline the story before designing\n  anything: the tension\n  (problem), the turn (insight), the resolution (your solution\u002Fproposal), the\nask. Slides serve the\n  story arc.\n- - - **One idea per slide.** If a slide needs \"and also,\" it needs to be two\n  slides. Audiences can\n  hold one point at a time; decks that respect this feel effortless.\n- - - **Assertion-evidence structure.** Headline states the conclusion (\"Churn\n  dropped 40% after\n  onboarding revamp\"), body provides the evidence (chart, image, 3 bullets max).\nHeadlines that just\n  label (\"Q3 Results\") waste the most valuable line.\n- - - **Visuals amplify, text supports.** A slide the audience must read is a\n  slide competing with the\n  speaker. Aim for glanceable: big number, simple chart, evocative image — with\nyou providing the\n  narrative.\n- - - **The 10\u002F20\u002F30-ish rule.** Keep it tight: ~10 key ideas, ~20 minutes of\n  content for a 30-minute\n  slot (leave room for discussion), 30pt minimum-ish for body text. Fewer,\nbigger, clearer.\n- - - **Design the read-alone version.** Most decks get forwarded without the\n  speaker. Speaker notes\n  or an appendix should let the deck survive on its own — without cluttering the\npresented slides.\n\n## Practical workflow\n\n1. 1. 1. **Write the story.** Outline: opening (why should they care?), 3-5 key\n   points in logical\n   sequence, closing (what should they do\u002Ffeel?). Get the narrative approved\nbefore designing.\n2. 2. 2. **Storyboard the slides.** One line per slide: the assertion headline.\n   Check the headlines\n   alone tell the story — they should read as an executive summary.\n3. 3. 3. **Design the system.** Title layouts, section dividers, content layouts\n   (big number, chart,\n   image+text, quote), consistent footer\u002Fnumbering. Build the master slides\nfirst.\n4. 4. 4. **Build for glanceability.** Maximum ~30 words per slide (fewer is\n   better), charts simplified\n   to one message (highlight the data point, gray out the rest), images\nfull-bleed where they earn\n   it.\n5. 5. 5. **Refine the details.** Alignment, consistent chart styles, readable\n   font sizes from the back\n   of the room (test at 50% zoom), accessible color contrast, alt text for key\nvisuals.\n6. 6. 6. **Rehearse with the deck.** Time it, note where slides fight the\n   narration, cut ruthlessly.\n   Every slide that doesn't advance the story is a candidate for the appendix.\n7. 7. 7. **Prep delivery files.** PDF backup (fonts embedded), 16:9 and 4:3\n   versions if the venue is\n   unknown, videos embedded (not linked), clicker tested, notes printed or on a\nsecond device.\n\n## Common pitfalls\n\n- - - **The document-deck.** 200 words per slide, 60 slides, read aloud to the\n  audience. If it's a\n  document, send a document; if it's a presentation, present.\n- - - **Bullet-point anesthesia.** Slide after slide of undifferentiated\n  bullets. Vary layouts, use\n  visuals, and remember: bullets are for grocery lists.\n- - - **Chart junk.** 3D effects, excessive gridlines, legends requiring\n  cross-referencing. Simplify\n  every chart to one message; annotate directly on the data.\n- - - **Tiny text.** If the back row can't read it, it shouldn't be on the\n  slide. 24pt minimum for\n  body, bigger for headlines.\n- - - **Inconsistent styling.** Five chart styles, three bullet styles, random\n  image treatments. The\n  template exists to be used — enforce it.\n- - - **No clear ask.** Ending with \"Questions?\" or \"Thank you\" instead of the\n  decision, action, or\n  feeling you need. The last slide should point forward, not just stop.\n","## Overview\n\nGreat presentations are stories with slides, not documents with animations. The\ndesigner's job is to\nmake the narrative land: one idea per slide, visuals that amplify (not\nduplicate) the speaker's\nwords, and a deck that works both presented and read. This skill covers\nnarrative structure, slide\ndesign craft, and the practical details of delivery.\n\n## When to use\n\n- Designing pitch decks, keynote presentations, or sales decks\n\n- Turning a dense report into a presentable slide narrative\n\n- Fixing a \"wall of text\" deck\n\n- Creating templates for team or company use\n\n- Preparing for an important talk or investor meeting\n\n## Core concepts\n\n- - - **Narrative first, slides second.** Outline the story before designing\n  anything: the tension\n  (problem), the turn (insight), the resolution (your solution\u002Fproposal), the\nask. Slides serve the\n  story arc.\n- - - **One idea per slide.** If a slide needs \"and also,\" it needs to be two\n  slides. Audiences can\n  hold one point at a time; decks that respect this feel effortless.\n- - - **Assertion-evidence structure.** Headline states the conclusion (\"Churn\n  dropped 40% after\n  onboarding revamp\"), body provides the evidence (chart, image, 3 bullets max).\nHeadlines that just\n  label (\"Q3 Results\") waste the most valuable line.\n- - - **Visuals amplify, text supports.** A slide the audience must read is a\n  slide competing with the\n  speaker. Aim for glanceable: big number, simple chart, evocative image — with\nyou providing the\n  narrative.\n- - - **The 10\u002F20\u002F30-ish rule.** Keep it tight: ~10 key ideas, ~20 minutes of\n  content for a 30-minute\n  slot (leave room for discussion), 30pt minimum-ish for body text. Fewer,\nbigger, clearer.\n- - - **Design the read-alone version.** Most decks get forwarded without the\n  speaker. Speaker notes\n  or an appendix should let the deck survive on its own — without cluttering the\npresented slides.\n\n## Practical workflow\n\n1. 1. 1. **Write the story.** Outline: opening (why should they care?), 3-5 key\n   points in logical\n   sequence, closing (what should they do\u002Ffeel?). Get the narrative approved\nbefore designing.\n2. 2. 2. **Storyboard the slides.** One line per slide: the assertion headline.\n   Check the headlines\n   alone tell the story — they should read as an executive summary.\n3. 3. 3. **Design the system.** Title layouts, section dividers, content layouts\n   (big number, chart,\n   image+text, quote), consistent footer\u002Fnumbering. Build the master slides\nfirst.\n4. 4. 4. **Build for glanceability.** Maximum ~30 words per slide (fewer is\n   better), charts simplified\n   to one message (highlight the data point, gray out the rest), images\nfull-bleed where they earn\n   it.\n5. 5. 5. **Refine the details.** Alignment, consistent chart styles, readable\n   font sizes from the back\n   of the room (test at 50% zoom), accessible color contrast, alt text for key\nvisuals.\n6. 6. 6. **Rehearse with the deck.** Time it, note where slides fight the\n   narration, cut ruthlessly.\n   Every slide that doesn't advance the story is a candidate for the appendix.\n7. 7. 7. **Prep delivery files.** PDF backup (fonts embedded), 16:9 and 4:3\n   versions if the venue is\n   unknown, videos embedded (not linked), clicker tested, notes printed or on a\nsecond device.\n\n## Common pitfalls\n\n- - - **The document-deck.** 200 words per slide, 60 slides, read aloud to the\n  audience. If it's a\n  document, send a document; if it's a presentation, present.\n- - - **Bullet-point anesthesia.** Slide after slide of undifferentiated\n  bullets. Vary layouts, use\n  visuals, and remember: bullets are for grocery lists.\n- - - **Chart junk.** 3D effects, excessive gridlines, legends requiring\n  cross-referencing. Simplify\n  every chart to one message; annotate directly on the data.\n- - - **Tiny text.** If the back row can't read it, it shouldn't be on the\n  slide. 24pt minimum for\n  body, bigger for headlines.\n- - - **Inconsistent styling.** Five chart styles, three bullet styles, random\n  image treatments. The\n  template exists to be used — enforce it.\n- - - **No clear ask.** Ending with \"Questions?\" or \"Thank you\" instead of the\n  decision, action, or\n  feeling you need. The last slide should point forward, not just stop.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-presentation-designer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill presentation-designer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill presentation-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill presentation-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-presentation-designer\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]