[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ES5G79TXVKEWK9JSZWC5KT":3,"skill-same:01M7ES5G79TXVKEWK9JSZWC5KT":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ES5G79TXVKEWK9JSZWC5KT","slide-design",null,"Rules for building presentation slides that people can actually read — applies Alexei Kapterev's \"Death by PowerPoint\" principles plus a working checklist. Use whenever making or revising slides, decks, presentations, pitch decks, or HTML slide decks, in any format (.pptx, HTML, PDF). Triggers on \"슬라이드\", \"발표자료\", \"덱\", \"deck\", \"slides\", \"presentation\", \"pitch deck\", or when a slide comes back as \"too complex \u002F 복잡해\".","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slide-design\ndescription: Rules for building presentation slides that people can actually read — applies Alexei Kapterev's \"Death by PowerPoint\" principles plus a working checklist. Use whenever making or revising slides, decks, presentations, pitch decks, or HTML slide decks, in any format (.pptx, HTML, PDF). Triggers on \"슬라이드\", \"발표자료\", \"덱\", \"deck\", \"slides\", \"presentation\", \"pitch deck\", or when a slide comes back as \"too complex \u002F 복잡해\".\n---\n\n# Slide design\n\n## The one rule\n\n**One point per slide.** If a slide is making two points, it is two slides.\nAn extra slide costs $0.00 — splitting is always cheaper than cramming.\n\nBefore building any slide, write its single point as one sentence.\nIf you can't, you don't know what the slide is for yet. Everything that\ndoes not serve that sentence gets deleted.\n\n## Death by PowerPoint — the principles\n\nFrom Alexei Kapterev's deck (~5M views), the four failure modes are\n**significance, structure, simplicity, rehearsal**. Three of them are ours:\n\n**Significance** — why does this slide exist? \"Significance creates passion;\npassion attracts attention; attention leads to action.\" A slide that only\ntransfers information is a handout, not a slide.\n\n**Structure** — give 3–4 reasons, never more. *\"They will not remember more\nanyway.\"* Common shapes: Problem → Pathway → Solution, or Problem → Solution\n→ Reasoning. The deck should survive being told in 5 minutes or 45.\n\n**Simplicity** — \"Everything should be made as simple as possible, but not\nsimpler.\"\n- Less text. More imagery.\n- Few matching colours. Very few fonts.\n- Photos, not clipart.\n- **\"People read faster than you speak. This means you are useless.\"**\n  Dense text on a slide makes the presenter redundant.\n- Reject mechanical rules like \"7 lines × 7 words\" — they produce cramped,\n  boring slides. The real test is whether one idea lands in 3 seconds.\n\n**Do not use slides as** a prompter, a handout, or a data dump. If detail is\nrequired, ship two artifacts: visual slides + a separate document with the\ndetail. Never one file trying to be both.\n\n## What this means in practice\n\n| Instead of | Do |\n|---|---|\n| A 6×5 table of who passed which round | A funnel of shrinking dots with the survivor highlighted |\n| A bullet list of five benefits | Five rows, one bold noun each, one line of support |\n| Two charts + notes + a table | Three slides |\n| A paragraph as the subtitle | One sentence, ≤ 20 words |\n| Explaining the mechanism in text | Draw the mechanism |\n\n**Read the slide from 3 metres away.** If the point isn't obvious before you\nread any body copy, the layout is wrong — not the copy.\n\n**Redundancy is clutter.** If the headline says it, the label doesn't need to.\nIf the next slide covers it, this slide doesn't.\n\n**Detail goes to the footnote.** Sources, caveats, secondary names, exact\ndates: one small grey line at the bottom. Present but not competing.\n\n## Checklist before shipping a slide\n\n1. Can I state the slide's point in one sentence? Is that sentence on the slide?\n2. Is anything here making a *second* point? → split the slide.\n3. Is any element repeating what another element already says? → delete it.\n4. Would a picture of the mechanism beat this text? → draw it.\n5. Does anything only matter to 5% of the audience? → footnote it.\n6. From 3 metres: what do I see first? Is that the point?\n\n## When the feedback is \"too complex\"\n\nDo not shrink the font or tighten the spacing. Remove content. Pick the single\nsentence, delete everything that isn't it, and give the survivor more room.\nMove what you deleted to a footnote, to a second slide, or to the appendix.\n\n## Building HTML decks\n\n- Fixed 1280×720 stage, `transform: scale()` to fit the viewport.\n- One design system across all slides: kicker → headline → one-line sub → body.\n  Same paddings, same type scale, same accent colour everywhere.\n- Commit to one background tone for the whole deck. Do not mix dark and light\n  slides unless the switch is doing deliberate work (title \u002F section only).\n- Animation is sequencing, not decoration: entrance order should follow the\n  order you speak in. Quiet slide transitions — a fast fade, nothing 3D.\n- Rebuild charts natively (SVG) rather than pasting screenshots, so they can\n  animate and stay legible. Screenshots are fine when the screenshot *is*\n  the evidence (a leaderboard, a news card).\n- No HTML-in-Canvas.\n- Self-contained single file: inline CSS\u002FJS, images as base64 data URIs.\n- Hide presenter chrome in fullscreen.\n- Verify with Playwright: screenshot every slide, check for 0 JS errors,\n  0 blank slides, and no element whose `scrollHeight\u002FscrollWidth` exceeds its\n  container (measure only the active slide — entrance transforms create false\n  positives on inactive ones).\n\n## Source\n\nAlexei Kapterev, *Death by PowerPoint* — https:\u002F\u002Fwww.slideshare.net\u002Fslideshow\u002Fdeath-by-powerpoint\u002F85551\n","# Slide design\n\n## The one rule\n\n**One point per slide.** If a slide is making two points, it is two slides.\nAn extra slide costs $0.00 — splitting is always cheaper than cramming.\n\nBefore building any slide, write its single point as one sentence.\nIf you can't, you don't know what the slide is for yet. Everything that\ndoes not serve that sentence gets deleted.\n\n## Death by PowerPoint — the principles\n\nFrom Alexei Kapterev's deck (~5M views), the four failure modes are\n**significance, structure, simplicity, rehearsal**. Three of them are ours:\n\n**Significance** — why does this slide exist? \"Significance creates passion;\npassion attracts attention; attention leads to action.\" A slide that only\ntransfers information is a handout, not a slide.\n\n**Structure** — give 3–4 reasons, never more. *\"They will not remember more\nanyway.\"* Common shapes: Problem → Pathway → Solution, or Problem → Solution\n→ Reasoning. The deck should survive being told in 5 minutes or 45.\n\n**Simplicity** — \"Everything should be made as simple as possible, but not\nsimpler.\"\n- Less text. More imagery.\n- Few matching colours. Very few fonts.\n- Photos, not clipart.\n- **\"People read faster than you speak. This means you are useless.\"**\n  Dense text on a slide makes the presenter redundant.\n- Reject mechanical rules like \"7 lines × 7 words\" — they produce cramped,\n  boring slides. The real test is whether one idea lands in 3 seconds.\n\n**Do not use slides as** a prompter, a handout, or a data dump. If detail is\nrequired, ship two artifacts: visual slides + a separate document with the\ndetail. Never one file trying to be both.\n\n## What this means in practice\n\n| Instead of | Do |\n|---|---|\n| A 6×5 table of who passed which round | A funnel of shrinking dots with the survivor highlighted |\n| A bullet list of five benefits | Five rows, one bold noun each, one line of support |\n| Two charts + notes + a table | Three slides |\n| A paragraph as the subtitle | One sentence, ≤ 20 words |\n| Explaining the mechanism in text | Draw the mechanism |\n\n**Read the slide from 3 metres away.** If the point isn't obvious before you\nread any body copy, the layout is wrong — not the copy.\n\n**Redundancy is clutter.** If the headline says it, the label doesn't need to.\nIf the next slide covers it, this slide doesn't.\n\n**Detail goes to the footnote.** Sources, caveats, secondary names, exact\ndates: one small grey line at the bottom. Present but not competing.\n\n## Checklist before shipping a slide\n\n1. Can I state the slide's point in one sentence? Is that sentence on the slide?\n2. Is anything here making a *second* point? → split the slide.\n3. Is any element repeating what another element already says? → delete it.\n4. Would a picture of the mechanism beat this text? → draw it.\n5. Does anything only matter to 5% of the audience? → footnote it.\n6. From 3 metres: what do I see first? Is that the point?\n\n## When the feedback is \"too complex\"\n\nDo not shrink the font or tighten the spacing. Remove content. Pick the single\nsentence, delete everything that isn't it, and give the survivor more room.\nMove what you deleted to a footnote, to a second slide, or to the appendix.\n\n## Building HTML decks\n\n- Fixed 1280×720 stage, `transform: scale()` to fit the viewport.\n- One design system across all slides: kicker → headline → one-line sub → body.\n  Same paddings, same type scale, same accent colour everywhere.\n- Commit to one background tone for the whole deck. Do not mix dark and light\n  slides unless the switch is doing deliberate work (title \u002F section only).\n- Animation is sequencing, not decoration: entrance order should follow the\n  order you speak in. Quiet slide transitions — a fast fade, nothing 3D.\n- Rebuild charts natively (SVG) rather than pasting screenshots, so they can\n  animate and stay legible. Screenshots are fine when the screenshot *is*\n  the evidence (a leaderboard, a news card).\n- No HTML-in-Canvas.\n- Self-contained single file: inline CSS\u002FJS, images as base64 data URIs.\n- Hide presenter chrome in fullscreen.\n- Verify with Playwright: screenshot every slide, check for 0 JS errors,\n  0 blank slides, and no element whose `scrollHeight\u002FscrollWidth` exceeds its\n  container (measure only the active slide — entrance transforms create false\n  positives on inactive ones).\n\n## Source\n\nAlexei Kapterev, *Death by PowerPoint* — https:\u002F\u002Fwww.slideshare.net\u002Fslideshow\u002Fdeath-by-powerpoint\u002F85551\n",{"name":5,"description":7},"main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill slide-design",{"tool":36,"command":37},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill slide-design",{"tool":39,"command":40},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill slide-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"INSTALL.md","REFERENCE","参考文档",2979,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FINSTALL.md",{"path":51,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":15},"LICENSE","许可证",1065,{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"README.ko.md",7281,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FREADME.ko.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"README.md",6416,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fhunkim\u002Fslide-skill\u002Fslide-skill\u002FREADME.md",[63,71,79,87,94,101],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]