[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NMHNX64H803J8XKMCPDAW":3,"skill-same:01M70NMHNX64H803J8XKMCPDAW":61},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M70NMHNX64H803J8XKMCPDAW","typeset",null,"Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30],"true","more","use","when","fonts","type","text","hierarchy","typography","font","user","readability","2026-11-10 10:12:30",false,"---\nname: typeset\ndescription: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nAssess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\n## Assess Current Typography\n\nAnalyze what's weak or generic about the current type:\n\n1. **Font choices**:\n   - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)\n   - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)\n   - Are there too many font families? (More than 2-3 is almost always a mess)\n\n2. **Hierarchy**:\n   - Can you tell headings from body from captions at a glance?\n   - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)\n   - Are weight contrasts strong enough? (Medium vs Regular is barely visible)\n\n3. **Sizing & scale**:\n   - Is there a consistent type scale, or are sizes arbitrary?\n   - Does body text meet minimum readability? (16px+)\n   - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing\u002Fcontent page headings)\n\n4. **Readability**:\n   - Are line lengths comfortable? (45-75 characters ideal)\n   - Is line-height appropriate for the font and context?\n   - Is there enough contrast between text and background?\n\n5. **Consistency**:\n   - Are the same elements styled the same way throughout?\n   - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)\n   - Is letter-spacing intentional or default everywhere?\n\n**CRITICAL**: The goal isn't to make text \"fancier\" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.\n\n## Plan Typography Improvements\n\nConsult the [typography reference](reference\u002Ftypography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.\n\nCreate a systematic plan:\n\n- **Font selection**: Do fonts need replacing? What fits the brand\u002Fcontext?\n- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy\n- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)\n- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements\n\n## Improve Typography Systematically\n\n### Font Selection\n\nIf fonts need replacing:\n- Choose fonts that reflect the brand personality\n- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights\n- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)\n\n### Establish Hierarchy\n\nBuild a clear type scale:\n- **5 sizes cover most needs**: caption, secondary, body, subheading, heading\n- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)\n- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone\n- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need\n- **Marketing \u002F content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed\n\n### Fix Readability\n\n- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)\n- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)\n- Increase line-height slightly for light-on-dark text\n- Ensure body text is at least 16px \u002F 1rem\n\n### Refine Details\n\n- Use `tabular-nums` for data tables and numbers that should align\n- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text\n- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)\n- Set `font-kerning: normal` and consider OpenType features where appropriate\n\n### Weight Consistency\n\n- Define clear roles for each weight and stick to them\n- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)\n- Load only the weights you actually use (each weight adds to page load)\n\n**NEVER**:\n- Use more than 2-3 font families\n- Pick sizes arbitrarily — commit to a scale\n- Set body text below 16px\n- Use decorative\u002Fdisplay fonts for body text\n- Disable browser zoom (`user-scalable=no`)\n- Use `px` for font sizes — use `rem` to respect user settings\n- Default to Inter\u002FRoboto\u002FOpen Sans when personality matters\n- Pair fonts that are similar but not identical (two geometric sans-serifs)\n\n## Verify Typography Improvements\n\n- **Hierarchy**: Can you identify heading vs body vs caption instantly?\n- **Readability**: Is body text comfortable to read in long passages?\n- **Consistency**: Are same-role elements styled identically throughout?\n- **Personality**: Does the typography reflect the brand?\n- **Performance**: Are web fonts loading efficiently without layout shift?\n- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?\n\nRemember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.","Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\n## Assess Current Typography\n\nAnalyze what's weak or generic about the current type:\n\n1. **Font choices**:\n   - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)\n   - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)\n   - Are there too many font families? (More than 2-3 is almost always a mess)\n\n2. **Hierarchy**:\n   - Can you tell headings from body from captions at a glance?\n   - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)\n   - Are weight contrasts strong enough? (Medium vs Regular is barely visible)\n\n3. **Sizing & scale**:\n   - Is there a consistent type scale, or are sizes arbitrary?\n   - Does body text meet minimum readability? (16px+)\n   - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing\u002Fcontent page headings)\n\n4. **Readability**:\n   - Are line lengths comfortable? (45-75 characters ideal)\n   - Is line-height appropriate for the font and context?\n   - Is there enough contrast between text and background?\n\n5. **Consistency**:\n   - Are the same elements styled the same way throughout?\n   - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)\n   - Is letter-spacing intentional or default everywhere?\n\n**CRITICAL**: The goal isn't to make text \"fancier\" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.\n\n## Plan Typography Improvements\n\nConsult the [typography reference](reference\u002Ftypography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.\n\nCreate a systematic plan:\n\n- **Font selection**: Do fonts need replacing? What fits the brand\u002Fcontext?\n- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy\n- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)\n- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements\n\n## Improve Typography Systematically\n\n### Font Selection\n\nIf fonts need replacing:\n- Choose fonts that reflect the brand personality\n- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights\n- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)\n\n### Establish Hierarchy\n\nBuild a clear type scale:\n- **5 sizes cover most needs**: caption, secondary, body, subheading, heading\n- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)\n- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone\n- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need\n- **Marketing \u002F content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed\n\n### Fix Readability\n\n- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)\n- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)\n- Increase line-height slightly for light-on-dark text\n- Ensure body text is at least 16px \u002F 1rem\n\n### Refine Details\n\n- Use `tabular-nums` for data tables and numbers that should align\n- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text\n- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)\n- Set `font-kerning: normal` and consider OpenType features where appropriate\n\n### Weight Consistency\n\n- Define clear roles for each weight and stick to them\n- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)\n- Load only the weights you actually use (each weight adds to page load)\n\n**NEVER**:\n- Use more than 2-3 font families\n- Pick sizes arbitrarily — commit to a scale\n- Set body text below 16px\n- Use decorative\u002Fdisplay fonts for body text\n- Disable browser zoom (`user-scalable=no`)\n- Use `px` for font sizes — use `rem` to respect user settings\n- Default to Inter\u002FRoboto\u002FOpen Sans when personality matters\n- Pair fonts that are similar but not identical (two geometric sans-serifs)\n\n## Verify Typography Improvements\n\n- **Hierarchy**: Can you identify heading vs body vs caption instantly?\n- **Readability**: Is body text comfortable to read in long passages?\n- **Consistency**: Are same-role elements styled identically throughout?\n- **Personality**: Does the typography reflect the brand?\n- **Performance**: Are web fonts loading efficiently without layout shift?\n- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?\n\nRemember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.",{"name":5,"description":7,"argument-hint":36,"user-invocable":37},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Ftypeset",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":37},[50,53,56],{"tool":51,"command":52},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typeset",{"tool":54,"command":55},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typeset",{"tool":57,"command":58},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill typeset","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[62,71,79,87,95,103],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":70},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]