[{"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,88,122,147,169,189],{"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":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":38},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[81,82,83,84,85,86,87],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":102,"publishedAt":38},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[94,97],{"categoryNo":95,"categoryName":96,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[90,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":132,"publishedAt":38},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[128,129],{"categoryNo":95,"categoryName":96,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":130,"categoryName":131,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000036","内容创作者",[124,133,134,135,136,137,138,139,111,140,141,142,27,28,143,144,145,146],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":38},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[153],{"categoryNo":95,"categoryName":96,"taxonomyType":78,"taxonomyTypeDesc":79},[155,156,124,157,158,145,159,160,161,162,163,164,165,166,109,167,27,28,103,168],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"publishedAt":38},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[175,176,177,178],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":95,"categoryName":96,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":130,"categoryName":131,"taxonomyType":100,"taxonomyTypeDesc":101},[180,86,181,182,183,184,119,27,28,185,186,187,188],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":197,"publishedAt":38},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[195,196],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":130,"categoryName":131,"taxonomyType":100,"taxonomyTypeDesc":101},[198,86,199,107,200,186,27,181,184,28,187],"Rules","writing rules","project rules"]