[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M5ENE9FH237CYB3C2GKPZ":3,"skill-same:01M70M5ENE9FH237CYB3C2GKPZ":68},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":67},"01M70M5ENE9FH237CYB3C2GKPZ","extract",null,"Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.","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\u002Fextract\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"reusable","library","design tokens","systematic","ui patterns","build","component","create","consolidate","components","when","use","component library","design","reuse","true","tokens","system","for","2026-11-10 10:12:30",false,"---\nname: extract\ndescription: Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nIdentify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.\n\n## Discover\n\nAnalyze the target area to identify extraction opportunities:\n\n1. **Find the design system**: Locate your design system, component library, or shared UI directory (grep for \"design system\", \"ui\", \"components\", etc.). Understand its structure:\n   - Component organization and naming conventions\n   - Design token structure (if any)\n   - Documentation patterns\n   - Import\u002Fexport conventions\n   \n   **CRITICAL**: If no design system exists, ask before creating one. Understand the preferred location and structure first.\n\n2. **Identify patterns**: Look for:\n   - **Repeated components**: Similar UI patterns used multiple times (buttons, cards, inputs, etc.)\n   - **Hard-coded values**: Colors, spacing, typography, shadows that should be tokens\n   - **Inconsistent variations**: Multiple implementations of the same concept (3 different button styles)\n   - **Reusable patterns**: Layout patterns, composition patterns, interaction patterns worth systematizing\n\n3. **Assess value**: Not everything should be extracted. Consider:\n   - Is this used 3+ times, or likely to be reused?\n   - Would systematizing this improve consistency?\n   - Is this a general pattern or context-specific?\n   - What's the maintenance cost vs benefit?\n\n## Plan Extraction\n\nCreate a systematic extraction plan:\n\n- **Components to extract**: Which UI elements become reusable components?\n- **Tokens to create**: Which hard-coded values become design tokens?\n- **Variants to support**: What variations does each component need?\n- **Naming conventions**: Component names, token names, prop names that match existing patterns\n- **Migration path**: How to refactor existing uses to consume the new shared versions\n\n**IMPORTANT**: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable.\n\n## Extract & Enrich\n\nBuild improved, reusable versions:\n\n- **Components**: Create well-designed components with:\n  - Clear props API with sensible defaults\n  - Proper variants for different use cases\n  - Accessibility built in (ARIA, keyboard navigation, focus management)\n  - Documentation and usage examples\n  \n- **Design tokens**: Create tokens with:\n  - Clear naming (primitive vs semantic)\n  - Proper hierarchy and organization\n  - Documentation of when to use each token\n  \n- **Patterns**: Document patterns with:\n  - When to use this pattern\n  - Code examples\n  - Variations and combinations\n\n**NEVER**:\n- Extract one-off, context-specific implementations without generalization\n- Create components so generic they're useless\n- Extract without considering existing design system conventions\n- Skip proper TypeScript types or prop documentation\n- Create tokens for every single value (tokens should have semantic meaning)\n\n## Migrate\n\nReplace existing uses with the new shared versions:\n\n- **Find all instances**: Search for the patterns you've extracted\n- **Replace systematically**: Update each use to consume the shared version\n- **Test thoroughly**: Ensure visual and functional parity\n- **Delete dead code**: Remove the old implementations\n\n## Document\n\nUpdate design system documentation:\n\n- Add new components to the component library\n- Document token usage and values\n- Add examples and guidelines\n- Update any Storybook or component catalog\n\nRemember: A good design system is a living system. Extract patterns as they emerge, enrich them thoughtfully, and maintain them consistently.","Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse.\n\n## Discover\n\nAnalyze the target area to identify extraction opportunities:\n\n1. **Find the design system**: Locate your design system, component library, or shared UI directory (grep for \"design system\", \"ui\", \"components\", etc.). Understand its structure:\n   - Component organization and naming conventions\n   - Design token structure (if any)\n   - Documentation patterns\n   - Import\u002Fexport conventions\n   \n   **CRITICAL**: If no design system exists, ask before creating one. Understand the preferred location and structure first.\n\n2. **Identify patterns**: Look for:\n   - **Repeated components**: Similar UI patterns used multiple times (buttons, cards, inputs, etc.)\n   - **Hard-coded values**: Colors, spacing, typography, shadows that should be tokens\n   - **Inconsistent variations**: Multiple implementations of the same concept (3 different button styles)\n   - **Reusable patterns**: Layout patterns, composition patterns, interaction patterns worth systematizing\n\n3. **Assess value**: Not everything should be extracted. Consider:\n   - Is this used 3+ times, or likely to be reused?\n   - Would systematizing this improve consistency?\n   - Is this a general pattern or context-specific?\n   - What's the maintenance cost vs benefit?\n\n## Plan Extraction\n\nCreate a systematic extraction plan:\n\n- **Components to extract**: Which UI elements become reusable components?\n- **Tokens to create**: Which hard-coded values become design tokens?\n- **Variants to support**: What variations does each component need?\n- **Naming conventions**: Component names, token names, prop names that match existing patterns\n- **Migration path**: How to refactor existing uses to consume the new shared versions\n\n**IMPORTANT**: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable.\n\n## Extract & Enrich\n\nBuild improved, reusable versions:\n\n- **Components**: Create well-designed components with:\n  - Clear props API with sensible defaults\n  - Proper variants for different use cases\n  - Accessibility built in (ARIA, keyboard navigation, focus management)\n  - Documentation and usage examples\n  \n- **Design tokens**: Create tokens with:\n  - Clear naming (primitive vs semantic)\n  - Proper hierarchy and organization\n  - Documentation of when to use each token\n  \n- **Patterns**: Document patterns with:\n  - When to use this pattern\n  - Code examples\n  - Variations and combinations\n\n**NEVER**:\n- Extract one-off, context-specific implementations without generalization\n- Create components so generic they're useless\n- Extract without considering existing design system conventions\n- Skip proper TypeScript types or prop documentation\n- Create tokens for every single value (tokens should have semantic meaning)\n\n## Migrate\n\nReplace existing uses with the new shared versions:\n\n- **Find all instances**: Search for the patterns you've extracted\n- **Replace systematically**: Update each use to consume the shared version\n- **Test thoroughly**: Ensure visual and functional parity\n- **Delete dead code**: Remove the old implementations\n\n## Document\n\nUpdate design system documentation:\n\n- Add new components to the component library\n- Document token usage and values\n- Add examples and guidelines\n- Update any Storybook or component catalog\n\nRemember: A good design system is a living system. Extract patterns as they emerge, enrich them thoughtfully, and maintain them consistently.",{"name":5,"description":7,"argument-hint":43,"user-invocable":44},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fextract",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":56,"prompt":66,"zipAvailable":44},[57,60,63],{"tool":58,"command":59},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill extract",{"tool":61,"command":62},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill extract",{"tool":64,"command":65},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill extract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fextract\u002FSKILL.md",[],[69,78,86,94,102,110],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":77},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]