[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70MXXF9C1FQSWNR90FNGQWB":3,"skill-same:01M70MXXF9C1FQSWNR90FNGQWB":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},"01M70MXXF9C1FQSWNR90FNGQWB","normalize",null,"Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.","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\u002Fnormalize\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"design","mismatched","line","component","styles","route","with","drift","when","use","true","tokens","system","page","bring","feature","consistency","standards","back","2026-11-10 10:12:30",false,"---\nname: normalize\ndescription: Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.\nuser-invocable: true\nargument-hint: \"[feature (page, route, component...)]\"\n---\n\nAnalyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns.\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## Plan\n\nBefore making changes, deeply understand the context:\n\n1. **Discover the design system**: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for \"design system\", \"ui guide\", \"style guide\", etc.). Study it thoroughly until you understand:\n   - Core design principles and aesthetic direction\n   - Target audience and personas\n   - Component patterns and conventions\n   - Design tokens (colors, typography, spacing)\n   \n   **CRITICAL**: If something isn't clear, ask. Don't guess at design system principles.\n\n2. **Analyze the current feature**: Assess what works and what doesn't:\n   - Where does it deviate from design system patterns?\n   - Which inconsistencies are cosmetic vs. functional?\n   - What's the root cause—missing tokens, one-off implementations, or conceptual misalignment?\n\n3. **Create a normalization plan**: Define specific changes that will align the feature with the design system:\n   - Which components can be replaced with design system equivalents?\n   - Which styles need to use design tokens instead of hard-coded values?\n   - How can UX patterns match established user flows?\n   \n   **IMPORTANT**: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first.\n\n## Execute\n\nSystematically address all inconsistencies across these dimensions:\n\n- **Typography**: Use design system fonts, sizes, weights, and line heights. Replace hard-coded values with typographic tokens or classes.\n- **Color & Theme**: Apply design system color tokens. Remove one-off color choices that break the palette.\n- **Spacing & Layout**: Use spacing tokens (margins, padding, gaps). Align with grid systems and layout patterns used elsewhere.\n- **Components**: Replace custom implementations with design system components. Ensure props and variants match established patterns.\n- **Motion & Interaction**: Match animation timing, easing, and interaction patterns to other features.\n- **Responsive Behavior**: Ensure breakpoints and responsive patterns align with design system standards.\n- **Accessibility**: Verify contrast ratios, focus states, ARIA labels match design system requirements.\n- **Progressive Disclosure**: Match information hierarchy and complexity management to established patterns.\n\n**NEVER**:\n- Create new one-off components when design system equivalents exist\n- Hard-code values that should use design tokens\n- Introduce new patterns that diverge from the design system\n- Compromise accessibility for visual consistency\n\nThis is not an exhaustive list—apply judgment to identify all areas needing normalization.\n\n## Clean Up\n\nAfter normalization, ensure code quality:\n\n- **Consolidate reusable components**: If you created new components that should be shared, move them to the design system or shared UI component path.\n- **Remove orphaned code**: Delete unused implementations, styles, or files made obsolete by normalization.\n- **Verify quality**: Lint, type-check, and test according to repository guidelines. Ensure normalization didn't introduce regressions.\n- **Ensure DRYness**: Look for duplication introduced during refactoring and consolidate.\n\nRemember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness.","Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns.\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## Plan\n\nBefore making changes, deeply understand the context:\n\n1. **Discover the design system**: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for \"design system\", \"ui guide\", \"style guide\", etc.). Study it thoroughly until you understand:\n   - Core design principles and aesthetic direction\n   - Target audience and personas\n   - Component patterns and conventions\n   - Design tokens (colors, typography, spacing)\n   \n   **CRITICAL**: If something isn't clear, ask. Don't guess at design system principles.\n\n2. **Analyze the current feature**: Assess what works and what doesn't:\n   - Where does it deviate from design system patterns?\n   - Which inconsistencies are cosmetic vs. functional?\n   - What's the root cause—missing tokens, one-off implementations, or conceptual misalignment?\n\n3. **Create a normalization plan**: Define specific changes that will align the feature with the design system:\n   - Which components can be replaced with design system equivalents?\n   - Which styles need to use design tokens instead of hard-coded values?\n   - How can UX patterns match established user flows?\n   \n   **IMPORTANT**: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first.\n\n## Execute\n\nSystematically address all inconsistencies across these dimensions:\n\n- **Typography**: Use design system fonts, sizes, weights, and line heights. Replace hard-coded values with typographic tokens or classes.\n- **Color & Theme**: Apply design system color tokens. Remove one-off color choices that break the palette.\n- **Spacing & Layout**: Use spacing tokens (margins, padding, gaps). Align with grid systems and layout patterns used elsewhere.\n- **Components**: Replace custom implementations with design system components. Ensure props and variants match established patterns.\n- **Motion & Interaction**: Match animation timing, easing, and interaction patterns to other features.\n- **Responsive Behavior**: Ensure breakpoints and responsive patterns align with design system standards.\n- **Accessibility**: Verify contrast ratios, focus states, ARIA labels match design system requirements.\n- **Progressive Disclosure**: Match information hierarchy and complexity management to established patterns.\n\n**NEVER**:\n- Create new one-off components when design system equivalents exist\n- Hard-code values that should use design tokens\n- Introduce new patterns that diverge from the design system\n- Compromise accessibility for visual consistency\n\nThis is not an exhaustive list—apply judgment to identify all areas needing normalization.\n\n## Clean Up\n\nAfter normalization, ensure code quality:\n\n- **Consolidate reusable components**: If you created new components that should be shared, move them to the design system or shared UI component path.\n- **Remove orphaned code**: Delete unused implementations, styles, or files made obsolete by normalization.\n- **Verify quality**: Lint, type-check, and test according to repository guidelines. Ensure normalization didn't introduce regressions.\n- **Ensure DRYness**: Look for duplication introduced during refactoring and consolidate.\n\nRemember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness.",{"name":5,"description":7,"argument-hint":43,"user-invocable":44},"[feature (page, route, component...)]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fnormalize",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 normalize",{"tool":61,"command":62},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill normalize",{"tool":64,"command":65},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill normalize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnormalize\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",[],[]]