[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70KZ21R2N8NG4RKB5KMS6PN":3,"skill-same:01M70KZ21R2N8NG4RKB5KMS6PN":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},"01M70KZ21R2N8NG4RKB5KMS6PN","clarify",null,"Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.","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\u002Fclarify\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"true","user","copy","understand","instructions","ux","text","when","use","writing","improve","labels","ux writing","messages","bad","error messages","ux copy","microcopy","error","2026-11-10 10:12:30",false,"---\nname: clarify\ndescription: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nIdentify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.\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. Additionally gather: audience technical level and users' mental state in context.\n\n---\n\n## Assess Current Copy\n\nIdentify what makes the text unclear or ineffective:\n\n1. **Find clarity problems**:\n   - **Jargon**: Technical terms users won't understand\n   - **Ambiguity**: Multiple interpretations possible\n   - **Passive voice**: \"Your file has been uploaded\" vs \"We uploaded your file\"\n   - **Length**: Too wordy or too terse\n   - **Assumptions**: Assuming user knowledge they don't have\n   - **Missing context**: Users don't know what to do or why\n   - **Tone mismatch**: Too formal, too casual, or inappropriate for situation\n\n2. **Understand the context**:\n   - Who's the audience? (Technical? General? First-time users?)\n   - What's the user's mental state? (Stressed during error? Confident during success?)\n   - What's the action? (What do we want users to do?)\n   - What's the constraint? (Character limits? Space limitations?)\n\n**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.\n\n## Plan Copy Improvements\n\nCreate a strategy for clearer communication:\n\n- **Primary message**: What's the ONE thing users need to know?\n- **Action needed**: What should users do next (if anything)?\n- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?)\n- **Constraints**: Length limits, brand voice, localization considerations\n\n**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words.\n\n## Improve Copy Systematically\n\nRefine text across these common areas:\n\n### Error Messages\n**Bad**: \"Error 403: Forbidden\"\n**Good**: \"You don't have permission to view this page. Contact your admin for access.\"\n\n**Bad**: \"Invalid input\"\n**Good**: \"Email addresses need an @ symbol. Try: name@example.com\"\n\n**Principles**:\n- Explain what went wrong in plain language\n- Suggest how to fix it\n- Don't blame the user\n- Include examples when helpful\n- Link to help\u002Fsupport if applicable\n\n### Form Labels & Instructions\n**Bad**: \"DOB (MM\u002FDD\u002FYYYY)\"\n**Good**: \"Date of birth\" (with placeholder showing format)\n\n**Bad**: \"Enter value here\"\n**Good**: \"Your email address\" or \"Company name\"\n\n**Principles**:\n- Use clear, specific labels (not generic placeholders)\n- Show format expectations with examples\n- Explain why you're asking (when not obvious)\n- Put instructions before the field, not after\n- Keep required field indicators clear\n\n### Button & CTA Text\n**Bad**: \"Click here\" | \"Submit\" | \"OK\"\n**Good**: \"Create account\" | \"Save changes\" | \"Got it, thanks\"\n\n**Principles**:\n- Describe the action specifically\n- Use active voice (verb + noun)\n- Match user's mental model\n- Be specific (\"Save\" is better than \"OK\")\n\n### Help Text & Tooltips\n**Bad**: \"This is the username field\"\n**Good**: \"Choose a username. You can change this later in Settings.\"\n\n**Principles**:\n- Add value (don't just repeat the label)\n- Answer the implicit question (\"What is this?\" or \"Why do you need this?\")\n- Keep it brief but complete\n- Link to detailed docs if needed\n\n### Empty States\n**Bad**: \"No items\"\n**Good**: \"No projects yet. Create your first project to get started.\"\n\n**Principles**:\n- Explain why it's empty (if not obvious)\n- Show next action clearly\n- Make it welcoming, not dead-end\n\n### Success Messages\n**Bad**: \"Success\"\n**Good**: \"Settings saved! Your changes will take effect immediately.\"\n\n**Principles**:\n- Confirm what happened\n- Explain what happens next (if relevant)\n- Be brief but complete\n- Match the user's emotional moment (celebrate big wins)\n\n### Loading States\n**Bad**: \"Loading...\" (for 30+ seconds)\n**Good**: \"Analyzing your data... this usually takes 30-60 seconds\"\n\n**Principles**:\n- Set expectations (how long?)\n- Explain what's happening (when it's not obvious)\n- Show progress when possible\n- Offer escape hatch if appropriate (\"Cancel\")\n\n### Confirmation Dialogs\n**Bad**: \"Are you sure?\"\n**Good**: \"Delete 'Project Alpha'? This can't be undone.\"\n\n**Principles**:\n- State the specific action\n- Explain consequences (especially for destructive actions)\n- Use clear button labels (\"Delete project\" not \"Yes\")\n- Don't overuse confirmations (only for risky actions)\n\n### Navigation & Wayfinding\n**Bad**: Generic labels like \"Items\" | \"Things\" | \"Stuff\"\n**Good**: Specific labels like \"Your projects\" | \"Team members\" | \"Settings\"\n\n**Principles**:\n- Be specific and descriptive\n- Use language users understand (not internal jargon)\n- Make hierarchy clear\n- Consider information scent (breadcrumbs, current location)\n\n## Apply Clarity Principles\n\nEvery piece of copy should follow these rules:\n\n1. **Be specific**: \"Enter email\" not \"Enter value\"\n2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity)\n3. **Be active**: \"Save changes\" not \"Changes will be saved\"\n4. **Be human**: \"Oops, something went wrong\" not \"System error encountered\"\n5. **Be helpful**: Tell users what to do, not just what happened\n6. **Be consistent**: Use same terms throughout (don't vary for variety)\n\n**NEVER**:\n- Use jargon without explanation\n- Blame users (\"You made an error\" → \"This field is required\")\n- Be vague (\"Something went wrong\" without explanation)\n- Use passive voice unnecessarily\n- Write overly long explanations (be concise)\n- Use humor for errors (be empathetic instead)\n- Assume technical knowledge\n- Vary terminology (pick one term and stick with it)\n- Repeat information (headers restating intros, redundant explanations)\n- Use placeholders as the only labels (they disappear when users type)\n\n## Verify Improvements\n\nTest that copy improvements work:\n\n- **Comprehension**: Can users understand without context?\n- **Actionability**: Do users know what to do next?\n- **Brevity**: Is it as short as possible while remaining clear?\n- **Consistency**: Does it match terminology elsewhere?\n- **Tone**: Is it appropriate for the situation?\n\nRemember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human.","Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.\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. Additionally gather: audience technical level and users' mental state in context.\n\n---\n\n## Assess Current Copy\n\nIdentify what makes the text unclear or ineffective:\n\n1. **Find clarity problems**:\n   - **Jargon**: Technical terms users won't understand\n   - **Ambiguity**: Multiple interpretations possible\n   - **Passive voice**: \"Your file has been uploaded\" vs \"We uploaded your file\"\n   - **Length**: Too wordy or too terse\n   - **Assumptions**: Assuming user knowledge they don't have\n   - **Missing context**: Users don't know what to do or why\n   - **Tone mismatch**: Too formal, too casual, or inappropriate for situation\n\n2. **Understand the context**:\n   - Who's the audience? (Technical? General? First-time users?)\n   - What's the user's mental state? (Stressed during error? Confident during success?)\n   - What's the action? (What do we want users to do?)\n   - What's the constraint? (Character limits? Space limitations?)\n\n**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.\n\n## Plan Copy Improvements\n\nCreate a strategy for clearer communication:\n\n- **Primary message**: What's the ONE thing users need to know?\n- **Action needed**: What should users do next (if anything)?\n- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?)\n- **Constraints**: Length limits, brand voice, localization considerations\n\n**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words.\n\n## Improve Copy Systematically\n\nRefine text across these common areas:\n\n### Error Messages\n**Bad**: \"Error 403: Forbidden\"\n**Good**: \"You don't have permission to view this page. Contact your admin for access.\"\n\n**Bad**: \"Invalid input\"\n**Good**: \"Email addresses need an @ symbol. Try: name@example.com\"\n\n**Principles**:\n- Explain what went wrong in plain language\n- Suggest how to fix it\n- Don't blame the user\n- Include examples when helpful\n- Link to help\u002Fsupport if applicable\n\n### Form Labels & Instructions\n**Bad**: \"DOB (MM\u002FDD\u002FYYYY)\"\n**Good**: \"Date of birth\" (with placeholder showing format)\n\n**Bad**: \"Enter value here\"\n**Good**: \"Your email address\" or \"Company name\"\n\n**Principles**:\n- Use clear, specific labels (not generic placeholders)\n- Show format expectations with examples\n- Explain why you're asking (when not obvious)\n- Put instructions before the field, not after\n- Keep required field indicators clear\n\n### Button & CTA Text\n**Bad**: \"Click here\" | \"Submit\" | \"OK\"\n**Good**: \"Create account\" | \"Save changes\" | \"Got it, thanks\"\n\n**Principles**:\n- Describe the action specifically\n- Use active voice (verb + noun)\n- Match user's mental model\n- Be specific (\"Save\" is better than \"OK\")\n\n### Help Text & Tooltips\n**Bad**: \"This is the username field\"\n**Good**: \"Choose a username. You can change this later in Settings.\"\n\n**Principles**:\n- Add value (don't just repeat the label)\n- Answer the implicit question (\"What is this?\" or \"Why do you need this?\")\n- Keep it brief but complete\n- Link to detailed docs if needed\n\n### Empty States\n**Bad**: \"No items\"\n**Good**: \"No projects yet. Create your first project to get started.\"\n\n**Principles**:\n- Explain why it's empty (if not obvious)\n- Show next action clearly\n- Make it welcoming, not dead-end\n\n### Success Messages\n**Bad**: \"Success\"\n**Good**: \"Settings saved! Your changes will take effect immediately.\"\n\n**Principles**:\n- Confirm what happened\n- Explain what happens next (if relevant)\n- Be brief but complete\n- Match the user's emotional moment (celebrate big wins)\n\n### Loading States\n**Bad**: \"Loading...\" (for 30+ seconds)\n**Good**: \"Analyzing your data... this usually takes 30-60 seconds\"\n\n**Principles**:\n- Set expectations (how long?)\n- Explain what's happening (when it's not obvious)\n- Show progress when possible\n- Offer escape hatch if appropriate (\"Cancel\")\n\n### Confirmation Dialogs\n**Bad**: \"Are you sure?\"\n**Good**: \"Delete 'Project Alpha'? This can't be undone.\"\n\n**Principles**:\n- State the specific action\n- Explain consequences (especially for destructive actions)\n- Use clear button labels (\"Delete project\" not \"Yes\")\n- Don't overuse confirmations (only for risky actions)\n\n### Navigation & Wayfinding\n**Bad**: Generic labels like \"Items\" | \"Things\" | \"Stuff\"\n**Good**: Specific labels like \"Your projects\" | \"Team members\" | \"Settings\"\n\n**Principles**:\n- Be specific and descriptive\n- Use language users understand (not internal jargon)\n- Make hierarchy clear\n- Consider information scent (breadcrumbs, current location)\n\n## Apply Clarity Principles\n\nEvery piece of copy should follow these rules:\n\n1. **Be specific**: \"Enter email\" not \"Enter value\"\n2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity)\n3. **Be active**: \"Save changes\" not \"Changes will be saved\"\n4. **Be human**: \"Oops, something went wrong\" not \"System error encountered\"\n5. **Be helpful**: Tell users what to do, not just what happened\n6. **Be consistent**: Use same terms throughout (don't vary for variety)\n\n**NEVER**:\n- Use jargon without explanation\n- Blame users (\"You made an error\" → \"This field is required\")\n- Be vague (\"Something went wrong\" without explanation)\n- Use passive voice unnecessarily\n- Write overly long explanations (be concise)\n- Use humor for errors (be empathetic instead)\n- Assume technical knowledge\n- Vary terminology (pick one term and stick with it)\n- Repeat information (headers restating intros, redundant explanations)\n- Use placeholders as the only labels (they disappear when users type)\n\n## Verify Improvements\n\nTest that copy improvements work:\n\n- **Comprehension**: Can users understand without context?\n- **Actionability**: Do users know what to do next?\n- **Brevity**: Is it as short as possible while remaining clear?\n- **Consistency**: Does it match terminology elsewhere?\n- **Tone**: Is it appropriate for the situation?\n\nRemember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human.",{"name":5,"description":7,"argument-hint":43,"user-invocable":44},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fclarify",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 clarify",{"tool":61,"command":62},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill clarify",{"tool":64,"command":65},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill clarify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fclarify\u002FSKILL.md",[],[69,87,121,145,167,187],{"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,28,86],"methodology","xiaolai","xiaolai methodology","朋友","投资","收入",{"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":6,"sourceHtmlUrl":91,"categories":92,"keywords":101,"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",[93,96],{"categoryNo":94,"categoryName":95,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[89,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":131,"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",[127,128],{"categoryNo":94,"categoryName":95,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":129,"categoryName":130,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000036","内容创作者",[123,20,132,133,134,135,136,137,110,138,139,140,26,27,141,142,143,144],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"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",[151],{"categoryNo":94,"categoryName":95,"taxonomyType":78,"taxonomyTypeDesc":79},[153,154,123,155,156,143,157,158,159,160,161,162,163,164,108,165,26,27,102,166],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":177,"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",[173,174,175,176],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":94,"categoryName":95,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":129,"categoryName":130,"taxonomyType":99,"taxonomyTypeDesc":100},[178,28,179,180,181,182,118,26,27,183,184,185,186],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":195,"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",[193,194],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":129,"categoryName":130,"taxonomyType":99,"taxonomyTypeDesc":100},[196,28,197,106,198,184,26,179,182,27,185],"Rules","writing rules","project rules"]