[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70N29C4KQ85SRHS0DF97J9S":3,"skill-same:01M70N29C4KQ85SRHS0DF97J9S":59},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":58},"01M70N29C4KQ85SRHS0DF97J9S","quieter",null,"Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.","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\u002Fquieter\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"bold","down","true","intensity","more","aesthetic","use","when","quality","user","2026-11-10 10:12:30",false,"---\nname: quieter\ndescription: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nReduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.\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 State\n\nAnalyze what makes the design feel too intense:\n\n1. **Identify intensity sources**:\n   - **Color saturation**: Overly bright or saturated colors\n   - **Contrast extremes**: Too much high-contrast juxtaposition\n   - **Visual weight**: Too many bold, heavy elements competing\n   - **Animation excess**: Too much motion or overly dramatic effects\n   - **Complexity**: Too many visual elements, patterns, or decorations\n   - **Scale**: Everything is large and loud with no hierarchy\n\n2. **Understand the context**:\n   - What's the purpose? (Marketing vs tool vs reading experience)\n   - Who's the audience? (Some contexts need energy)\n   - What's working? (Don't throw away good ideas)\n   - What's the core message? (Preserve what matters)\n\nIf any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.\n\n**CRITICAL**: \"Quieter\" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.\n\n## Plan Refinement\n\nCreate a strategy to reduce intensity while maintaining impact:\n\n- **Color approach**: Desaturate or shift to more sophisticated tones?\n- **Hierarchy approach**: Which elements should stay bold (very few), which should recede?\n- **Simplification approach**: What can be removed entirely?\n- **Sophistication approach**: How can we signal quality through restraint?\n\n**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision.\n\n## Refine the Design\n\nSystematically reduce intensity across these dimensions:\n\n### Color Refinement\n- **Reduce saturation**: Shift from fully saturated to 70-85% saturation\n- **Soften palette**: Replace bright colors with muted, sophisticated tones\n- **Reduce color variety**: Use fewer colors more thoughtfully\n- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule)\n- **Gentler contrasts**: High contrast only where it matters most\n- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness\n- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead\n\n### Visual Weight Reduction\n- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate\n- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness\n- **White space**: Increase breathing room, reduce density\n- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely\n\n### Simplification\n- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose\n- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes\n- **Reduce layering**: Flatten visual hierarchy where possible\n- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows\n\n### Motion Reduction\n- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing\n- **Remove decorative animations**: Keep functional motion, remove flourishes\n- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback\n- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic\n- **Remove animations entirely** if they're not serving a clear purpose\n\n### Composition Refinement\n- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling\n- **Align to grid**: Bring rogue elements back into systematic alignment\n- **Even out spacing**: Replace extreme spacing variations with consistent rhythm\n\n**NEVER**:\n- Make everything the same size\u002Fweight (hierarchy still matters)\n- Remove all color (quiet ≠ grayscale)\n- Eliminate all personality (maintain character through refinement)\n- Sacrifice usability for aesthetics (functional elements still need clear affordances)\n- Make everything small and light (some anchors needed)\n\n## Verify Quality\n\nEnsure refinement maintains quality:\n\n- **Still functional**: Can users still accomplish tasks easily?\n- **Still distinctive**: Does it have character, or is it generic now?\n- **Better reading**: Is text easier to read for extended periods?\n- **Sophistication**: Does it feel more refined and premium?\n\nRemember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality.","Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.\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 State\n\nAnalyze what makes the design feel too intense:\n\n1. **Identify intensity sources**:\n   - **Color saturation**: Overly bright or saturated colors\n   - **Contrast extremes**: Too much high-contrast juxtaposition\n   - **Visual weight**: Too many bold, heavy elements competing\n   - **Animation excess**: Too much motion or overly dramatic effects\n   - **Complexity**: Too many visual elements, patterns, or decorations\n   - **Scale**: Everything is large and loud with no hierarchy\n\n2. **Understand the context**:\n   - What's the purpose? (Marketing vs tool vs reading experience)\n   - Who's the audience? (Some contexts need energy)\n   - What's working? (Don't throw away good ideas)\n   - What's the core message? (Preserve what matters)\n\nIf any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.\n\n**CRITICAL**: \"Quieter\" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.\n\n## Plan Refinement\n\nCreate a strategy to reduce intensity while maintaining impact:\n\n- **Color approach**: Desaturate or shift to more sophisticated tones?\n- **Hierarchy approach**: Which elements should stay bold (very few), which should recede?\n- **Simplification approach**: What can be removed entirely?\n- **Sophistication approach**: How can we signal quality through restraint?\n\n**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision.\n\n## Refine the Design\n\nSystematically reduce intensity across these dimensions:\n\n### Color Refinement\n- **Reduce saturation**: Shift from fully saturated to 70-85% saturation\n- **Soften palette**: Replace bright colors with muted, sophisticated tones\n- **Reduce color variety**: Use fewer colors more thoughtfully\n- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule)\n- **Gentler contrasts**: High contrast only where it matters most\n- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness\n- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead\n\n### Visual Weight Reduction\n- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate\n- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness\n- **White space**: Increase breathing room, reduce density\n- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely\n\n### Simplification\n- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose\n- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes\n- **Reduce layering**: Flatten visual hierarchy where possible\n- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows\n\n### Motion Reduction\n- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing\n- **Remove decorative animations**: Keep functional motion, remove flourishes\n- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback\n- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic\n- **Remove animations entirely** if they're not serving a clear purpose\n\n### Composition Refinement\n- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling\n- **Align to grid**: Bring rogue elements back into systematic alignment\n- **Even out spacing**: Replace extreme spacing variations with consistent rhythm\n\n**NEVER**:\n- Make everything the same size\u002Fweight (hierarchy still matters)\n- Remove all color (quiet ≠ grayscale)\n- Eliminate all personality (maintain character through refinement)\n- Sacrifice usability for aesthetics (functional elements still need clear affordances)\n- Make everything small and light (some anchors needed)\n\n## Verify Quality\n\nEnsure refinement maintains quality:\n\n- **Still functional**: Can users still accomplish tasks easily?\n- **Still distinctive**: Does it have character, or is it generic now?\n- **Better reading**: Is text easier to read for extended periods?\n- **Sophistication**: Does it feel more refined and premium?\n\nRemember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality.",{"name":5,"description":7,"argument-hint":34,"user-invocable":35},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fquieter",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":47,"prompt":57,"zipAvailable":35},[48,51,54],{"tool":49,"command":50},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill quieter",{"tool":52,"command":53},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill quieter",{"tool":55,"command":56},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill quieter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fquieter\u002FSKILL.md",[],[60,79,113,137,159,179],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":29},"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",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[72,73,74,75,76,77,78],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"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":6,"sourceHtmlUrl":83,"categories":84,"keywords":93,"publishedAt":29},"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",[85,88],{"categoryNo":86,"categoryName":87,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[81,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":29},"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",[119,120],{"categoryNo":86,"categoryName":87,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[115,28,124,125,126,127,128,129,102,130,131,132,26,25,133,134,135,136],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":29},"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",[143],{"categoryNo":86,"categoryName":87,"taxonomyType":69,"taxonomyTypeDesc":70},[145,146,115,147,148,135,149,150,151,152,153,154,155,156,100,157,26,25,94,158],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":169,"publishedAt":29},"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",[165,166,167,168],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":86,"categoryName":87,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},[170,77,171,172,173,174,110,26,25,175,176,177,178],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":187,"publishedAt":29},"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",[185,186],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},[188,77,189,98,190,176,26,171,174,25,177],"Rules","writing rules","project rules"]