[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FSXG3W5EZJE04VRYYT17J":3,"skill-same:01M70FSXG3W5EZJE04VRYYT17J":102},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FSXG3W5EZJE04VRYYT17J","adhd-friendly-documentation",null,"Create documentation optimized for ADHD and neurodivergent readers with short scannable content, clear hierarchy, progressive disclosure, actionable steps, and reduced cognitive load. Use when creating or improving any technical documentation (README files, API docs, tutorials, guides, onboarding materials) or when users request accessible, easy-to-scan, or beginner-friendly documentation.","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\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"adhd","documentation","adhd friendly","adhd friendly documentation","use","technical","README","scan","for","request","beginner-friendly","hierarchy","create","guides","api","when","files","short","actionable","neurodivergent","2026-11-10 10:12:30",false,"---\nname: adhd-friendly-documentation\ndescription: Create documentation optimized for ADHD and neurodivergent readers with short scannable content, clear hierarchy, progressive disclosure, actionable steps, and reduced cognitive load. Use when creating or improving any technical documentation (README files, API docs, tutorials, guides, onboarding materials) or when users request accessible, easy-to-scan, or beginner-friendly documentation.\n---\n\n# ADHD-Friendly Documentation\n\n## Overview\n\nThis skill transforms technical documentation into accessible, scannable content optimized for ADHD and neurodivergent readers. Apply ADHD-friendly principles to create documentation that reduces cognitive load, improves information retention, and enables quick scanning while maintaining technical accuracy.\n\n**Core principles:**\n- Short, scannable content with clear visual hierarchy\n- Progressive disclosure of complexity\n- Actionable steps with concrete examples\n- Visual aids and consistent formatting\n- Quick reference sections for rapid lookup\n\n## When to Use This Skill\n\nUse this skill when:\n- Creating new documentation (READMEs, guides, tutorials, API docs)\n- Improving existing documentation for accessibility\n- Users request \"easy to understand,\" \"beginner-friendly,\" or \"scannable\" docs\n- Writing onboarding materials or getting-started guides\n- Documenting complex systems that need clear explanation\n- Creating internal documentation or knowledge bases\n\n**Always apply** these principles to documentation unless the user explicitly requests a different style.\n\n## Creating ADHD-Friendly Documentation\n\n### Step 1: Choose the Right Template\n\nSelect the appropriate template from `assets\u002F` based on documentation type:\n\n**Quick Start \u002F README** → `assets\u002Ftemplate-quick-start.md`\n- Project introductions\n- Getting started guides\n- Repository README files\n- Installation instructions\n\n**API Documentation** → `assets\u002Ftemplate-api-docs.md`\n- Method\u002Ffunction reference\n- Library documentation\n- REST\u002FGraphQL API docs\n- SDK documentation\n\n**Tutorials** → `assets\u002Ftemplate-tutorial.md`\n- Step-by-step guides\n- Learning paths\n- Hands-on workshops\n- Feature walkthroughs\n\n### Step 2: Apply Core Patterns\n\nReference `references\u002Fadhd-patterns.md` for detailed guidance on:\n\n**Visual Hierarchy:**\n- Use clear H1\u002FH2\u002FH3 structure (max 3-4 levels deep)\n- Add generous whitespace between sections\n- Keep header nesting shallow for easy scanning\n\n**Scannable Content:**\n- Lead with key information (what\u002Fwhy in first 2-3 lines)\n- Use bullet points over paragraphs\n- Limit paragraphs to 2-3 sentences maximum\n- **Bold** important terms and actions\n- Use `code formatting` for technical terms\n\n**Progressive Disclosure:**\n- Start with TL;DR or Quick Start section\n- Provide quick wins before deep explanations\n- Link to details rather than including inline\n- Separate basic from advanced content\n\n**Action-Oriented:**\n- Start instructions with verbs (Install, Run, Create, Configure)\n- Number sequential steps clearly\n- Include expected outcomes after each step\n- Provide complete, runnable code examples\n\n**Cognitive Load Reduction:**\n- One concept per section\n- Use consistent terminology throughout\n- Define jargon on first use\n- Include time estimates for tutorials\n- Explain \"why\" for non-obvious steps\n\n### Step 3: Add Visual Elements\n\nEnhance scannability with:\n\n**Tables** for comparisons and structured data:\n```markdown\n| Feature | Option A | Option B |\n|---------|----------|----------|\n| Speed   | Fast     | Slow     |\n```\n\n**Callouts** for important information:\n```markdown\n> ⚠️ **Warning:** Critical information\n> 💡 **Tip:** Helpful suggestion\n> ℹ️ **Note:** Additional context\n> ✅ **Success:** Expected outcome\n```\n\n**Code blocks** with syntax highlighting:\n````markdown\n```language\n\u002F\u002F Complete, runnable example\n\u002F\u002F Comments for non-obvious parts\n```\n````\n\n**Checklists** for learning objectives:\n```markdown\n- [ ] Objective 1\n- [ ] Objective 2\n```\n\n### Step 4: Structure for Scanning\n\nOrganize information for quick navigation:\n\n**Information hierarchy:**\n1. Title + one-line summary\n2. Quick start (\u003C 2 minutes)\n3. Core concepts (5-10 min)\n4. Tutorials\u002Fguides (hands-on)\n5. API reference (lookup)\n6. Advanced topics (deep dives)\n\n**Section format:**\n- Lead with the most important info\n- Keep sections focused (one topic each)\n- Use consistent formatting patterns\n- Provide clear navigation (table of contents, next steps)\n\n### Step 5: Validate with Checklist\n\nUse `references\u002Fchecklist.md` to validate documentation quality:\n\n**Quick validation checks:**\n- ✅ Clear headers and structure\n- ✅ Paragraphs under 3 sentences\n- ✅ Sequential steps numbered\n- ✅ Code examples complete and runnable\n- ✅ Key terms bolded\n- ✅ One concept per section\n\n**Priority fixes** if time is limited:\n1. Add clear headers\n2. Break up long paragraphs\n3. Add quick start section\n4. Number sequential steps\n5. Bold key terms\n\nSee the complete checklist in `references\u002Fchecklist.md` for comprehensive validation.\n\n## Anti-Patterns to Avoid\n\nReference `references\u002Fadhd-patterns.md` for detailed anti-patterns. Key ones:\n\n**❌ Walls of text** - No paragraphs over 5 sentences\n- Instead: Break into bullet points or shorter paragraphs\n\n**❌ Hidden action steps** - Don't bury commands in prose\n- Instead: Use numbered lists with explicit actions\n\n**❌ Ambiguous language** - Avoid \"might,\" \"could,\" \"sometimes\"\n- Instead: Provide clear guidance on when to use what\n\n**❌ Missing expected outcomes** - Always show what should happen\n- Instead: Add \"You should see:\" after steps\n\n**❌ Undefined jargon** - Define technical terms on first use\n- Instead: Explain or link to definitions\n\n## Working with Existing Documentation\n\nWhen improving existing docs:\n\n1. **Assess current state** - Identify walls of text, missing structure, buried actions\n2. **Add quick wins first** - Quick start section, clear headers, numbered steps\n3. **Break up content** - Convert paragraphs to bullets, add whitespace\n4. **Add visual hierarchy** - Ensure proper header levels and structure\n5. **Validate** - Use checklist from `references\u002Fchecklist.md`\n\n**Preserve technical accuracy** while improving accessibility.\n\n## Resources\n\n### references\u002Fadhd-patterns.md\nComprehensive guide to ADHD-friendly documentation patterns including:\n- Core principles and detailed explanations\n- Specific patterns for different doc types (Quick Start, API, Tutorial, Troubleshooting)\n- Visual aids guidelines (tables, callouts, diagrams)\n- Anti-patterns with before\u002Fafter examples\n- Formatting conventions\n- Content organization strategies\n- Writing style guidelines\n- Accessibility considerations\n\n**Use this as the primary reference** for detailed pattern guidance.\n\n### references\u002Fchecklist.md\nQuick validation checklist with:\n- Structure & hierarchy checks\n- Scannability criteria\n- Progressive disclosure validation\n- Action steps quality\n- Cognitive load assessment\n- Visual elements checklist\n- Common anti-patterns to avoid\n- Quick validation tests (Skim Test, 30-Second Test)\n- Scoring system\n\n**Use this to validate** documentation before publishing.\n\n### assets\u002Ftemplate-quick-start.md\nTemplate for README files and getting-started guides with:\n- Quick start section (60 seconds)\n- What this does explanation\n- Common use cases\n- Next steps navigation\n- Quick reference\n- Troubleshooting section\n\n**Use when creating** project READMEs or quick-start guides.\n\n### assets\u002Ftemplate-api-docs.md\nTemplate for API and library documentation with:\n- Method documentation format\n- Parameter tables\n- Common examples\n- Error handling\n- Rate limiting and pagination\n- Complete working examples\n\n**Use when documenting** APIs, libraries, or SDKs.\n\n### assets\u002Ftemplate-tutorial.md\nTemplate for step-by-step tutorials with:\n- Learning objectives\n- Step-by-step instructions with checkpoints\n- Common issues sections\n- \"You're done\" celebration\n- Next steps and extensions\n- Complete code sections\n\n**Use when creating** hands-on tutorials or walkthroughs.\n\n## Best Practices\n\n**Start simple:**\n- Begin with template that matches doc type\n- Focus on quick wins (headers, bullets, quick start)\n- Add complexity progressively\n\n**Be consistent:**\n- Use same formatting patterns throughout\n- Maintain consistent terminology\n- Follow established conventions in templates\n\n**Test scannability:**\n- Can readers find what they need in 30 seconds?\n- Are headers descriptive and hierarchical?\n- Can someone skim bullets and understand the content?\n\n**Prioritize action:**\n- Make it easy to get started quickly\n- Provide working examples early\n- Show expected results\n\n**Reduce friction:**\n- Remove barriers to understanding\n- Explain non-obvious steps\n- Provide multiple entry points (quick start, deep dive, reference)\n\n## Writing Style\n\nUse imperative\u002Finfinitive form throughout:\n- ✅ \"Install the package using npm\"\n- ✅ \"To configure authentication, create a config file\"\n- ❌ \"You should install the package\"\n- ❌ \"If you want to configure authentication, you can create...\"\n\n**Voice:**\n- Present tense, active voice\n- Direct and conversational but precise\n- Command form for instructions\n\n**Sentence structure:**\n- Lead with action or key point\n- Keep under 20 words\n- One idea per sentence\n\n## Examples\n\n### Example 1: README Documentation\n\nUser asks: \"Create a README for my authentication library\"\n\n**Approach:**\n1. Start with `assets\u002Ftemplate-quick-start.md`\n2. Add one-line description of auth library\n3. Create 60-second quick start (install, configure, use)\n4. Show 2-3 common use cases with code\n5. Add API reference links\n6. Include troubleshooting for common auth issues\n7. Validate with `references\u002Fchecklist.md`\n\n### Example 2: API Documentation\n\nUser asks: \"Document my REST API endpoints\"\n\n**Approach:**\n1. Use `assets\u002Ftemplate-api-docs.md` structure\n2. For each endpoint: What it does, when to use, quick example\n3. Add parameter tables with types and descriptions\n4. Include authentication section\n5. Show error responses and handling\n6. Add rate limiting information\n7. Provide complete working examples\n\n### Example 3: Tutorial\n\nUser asks: \"Write a getting started guide for building a todo app\"\n\n**Approach:**\n1. Start with `assets\u002Ftemplate-tutorial.md`\n2. Define learning objectives and time estimate\n3. Break into clear steps (Setup → Add todos → Display → Complete)\n4. Each step: Goal, instructions, checkpoint, expected result\n5. Add \"What you learned\" summaries\n6. Include troubleshooting section\n7. Suggest next steps and extensions\n\n### Example 4: Improving Existing Docs\n\nUser asks: \"Make this documentation easier to understand\"\n\n**Approach:**\n1. Read existing documentation\n2. Identify issues (walls of text, missing structure, unclear actions)\n3. Add quick start section if missing\n4. Break paragraphs into bullets\n5. Add clear headers and hierarchy\n6. Make action steps explicit and numbered\n7. Add expected outcomes\n8. Validate with `references\u002Fchecklist.md`\n\n## Summary\n\nCreate documentation that is:\n- **Scannable** - Headers, bullets, whitespace\n- **Actionable** - Clear steps, working examples\n- **Progressive** - Quick start → concepts → advanced\n- **Accessible** - Low cognitive load, clear language\n- **Consistent** - Same patterns throughout\n\n**Always reference** `references\u002Fadhd-patterns.md` for detailed guidance and `references\u002Fchecklist.md` for validation. **Use templates** from `assets\u002F` as starting points for common documentation types.\n","# ADHD-Friendly Documentation\n\n## Overview\n\nThis skill transforms technical documentation into accessible, scannable content optimized for ADHD and neurodivergent readers. Apply ADHD-friendly principles to create documentation that reduces cognitive load, improves information retention, and enables quick scanning while maintaining technical accuracy.\n\n**Core principles:**\n- Short, scannable content with clear visual hierarchy\n- Progressive disclosure of complexity\n- Actionable steps with concrete examples\n- Visual aids and consistent formatting\n- Quick reference sections for rapid lookup\n\n## When to Use This Skill\n\nUse this skill when:\n- Creating new documentation (READMEs, guides, tutorials, API docs)\n- Improving existing documentation for accessibility\n- Users request \"easy to understand,\" \"beginner-friendly,\" or \"scannable\" docs\n- Writing onboarding materials or getting-started guides\n- Documenting complex systems that need clear explanation\n- Creating internal documentation or knowledge bases\n\n**Always apply** these principles to documentation unless the user explicitly requests a different style.\n\n## Creating ADHD-Friendly Documentation\n\n### Step 1: Choose the Right Template\n\nSelect the appropriate template from `assets\u002F` based on documentation type:\n\n**Quick Start \u002F README** → `assets\u002Ftemplate-quick-start.md`\n- Project introductions\n- Getting started guides\n- Repository README files\n- Installation instructions\n\n**API Documentation** → `assets\u002Ftemplate-api-docs.md`\n- Method\u002Ffunction reference\n- Library documentation\n- REST\u002FGraphQL API docs\n- SDK documentation\n\n**Tutorials** → `assets\u002Ftemplate-tutorial.md`\n- Step-by-step guides\n- Learning paths\n- Hands-on workshops\n- Feature walkthroughs\n\n### Step 2: Apply Core Patterns\n\nReference `references\u002Fadhd-patterns.md` for detailed guidance on:\n\n**Visual Hierarchy:**\n- Use clear H1\u002FH2\u002FH3 structure (max 3-4 levels deep)\n- Add generous whitespace between sections\n- Keep header nesting shallow for easy scanning\n\n**Scannable Content:**\n- Lead with key information (what\u002Fwhy in first 2-3 lines)\n- Use bullet points over paragraphs\n- Limit paragraphs to 2-3 sentences maximum\n- **Bold** important terms and actions\n- Use `code formatting` for technical terms\n\n**Progressive Disclosure:**\n- Start with TL;DR or Quick Start section\n- Provide quick wins before deep explanations\n- Link to details rather than including inline\n- Separate basic from advanced content\n\n**Action-Oriented:**\n- Start instructions with verbs (Install, Run, Create, Configure)\n- Number sequential steps clearly\n- Include expected outcomes after each step\n- Provide complete, runnable code examples\n\n**Cognitive Load Reduction:**\n- One concept per section\n- Use consistent terminology throughout\n- Define jargon on first use\n- Include time estimates for tutorials\n- Explain \"why\" for non-obvious steps\n\n### Step 3: Add Visual Elements\n\nEnhance scannability with:\n\n**Tables** for comparisons and structured data:\n```markdown\n| Feature | Option A | Option B |\n|---------|----------|----------|\n| Speed   | Fast     | Slow     |\n```\n\n**Callouts** for important information:\n```markdown\n> ⚠️ **Warning:** Critical information\n> 💡 **Tip:** Helpful suggestion\n> ℹ️ **Note:** Additional context\n> ✅ **Success:** Expected outcome\n```\n\n**Code blocks** with syntax highlighting:\n````markdown\n```language\n\u002F\u002F Complete, runnable example\n\u002F\u002F Comments for non-obvious parts\n```\n````\n\n**Checklists** for learning objectives:\n```markdown\n- [ ] Objective 1\n- [ ] Objective 2\n```\n\n### Step 4: Structure for Scanning\n\nOrganize information for quick navigation:\n\n**Information hierarchy:**\n1. Title + one-line summary\n2. Quick start (\u003C 2 minutes)\n3. Core concepts (5-10 min)\n4. Tutorials\u002Fguides (hands-on)\n5. API reference (lookup)\n6. Advanced topics (deep dives)\n\n**Section format:**\n- Lead with the most important info\n- Keep sections focused (one topic each)\n- Use consistent formatting patterns\n- Provide clear navigation (table of contents, next steps)\n\n### Step 5: Validate with Checklist\n\nUse `references\u002Fchecklist.md` to validate documentation quality:\n\n**Quick validation checks:**\n- ✅ Clear headers and structure\n- ✅ Paragraphs under 3 sentences\n- ✅ Sequential steps numbered\n- ✅ Code examples complete and runnable\n- ✅ Key terms bolded\n- ✅ One concept per section\n\n**Priority fixes** if time is limited:\n1. Add clear headers\n2. Break up long paragraphs\n3. Add quick start section\n4. Number sequential steps\n5. Bold key terms\n\nSee the complete checklist in `references\u002Fchecklist.md` for comprehensive validation.\n\n## Anti-Patterns to Avoid\n\nReference `references\u002Fadhd-patterns.md` for detailed anti-patterns. Key ones:\n\n**❌ Walls of text** - No paragraphs over 5 sentences\n- Instead: Break into bullet points or shorter paragraphs\n\n**❌ Hidden action steps** - Don't bury commands in prose\n- Instead: Use numbered lists with explicit actions\n\n**❌ Ambiguous language** - Avoid \"might,\" \"could,\" \"sometimes\"\n- Instead: Provide clear guidance on when to use what\n\n**❌ Missing expected outcomes** - Always show what should happen\n- Instead: Add \"You should see:\" after steps\n\n**❌ Undefined jargon** - Define technical terms on first use\n- Instead: Explain or link to definitions\n\n## Working with Existing Documentation\n\nWhen improving existing docs:\n\n1. **Assess current state** - Identify walls of text, missing structure, buried actions\n2. **Add quick wins first** - Quick start section, clear headers, numbered steps\n3. **Break up content** - Convert paragraphs to bullets, add whitespace\n4. **Add visual hierarchy** - Ensure proper header levels and structure\n5. **Validate** - Use checklist from `references\u002Fchecklist.md`\n\n**Preserve technical accuracy** while improving accessibility.\n\n## Resources\n\n### references\u002Fadhd-patterns.md\nComprehensive guide to ADHD-friendly documentation patterns including:\n- Core principles and detailed explanations\n- Specific patterns for different doc types (Quick Start, API, Tutorial, Troubleshooting)\n- Visual aids guidelines (tables, callouts, diagrams)\n- Anti-patterns with before\u002Fafter examples\n- Formatting conventions\n- Content organization strategies\n- Writing style guidelines\n- Accessibility considerations\n\n**Use this as the primary reference** for detailed pattern guidance.\n\n### references\u002Fchecklist.md\nQuick validation checklist with:\n- Structure & hierarchy checks\n- Scannability criteria\n- Progressive disclosure validation\n- Action steps quality\n- Cognitive load assessment\n- Visual elements checklist\n- Common anti-patterns to avoid\n- Quick validation tests (Skim Test, 30-Second Test)\n- Scoring system\n\n**Use this to validate** documentation before publishing.\n\n### assets\u002Ftemplate-quick-start.md\nTemplate for README files and getting-started guides with:\n- Quick start section (60 seconds)\n- What this does explanation\n- Common use cases\n- Next steps navigation\n- Quick reference\n- Troubleshooting section\n\n**Use when creating** project READMEs or quick-start guides.\n\n### assets\u002Ftemplate-api-docs.md\nTemplate for API and library documentation with:\n- Method documentation format\n- Parameter tables\n- Common examples\n- Error handling\n- Rate limiting and pagination\n- Complete working examples\n\n**Use when documenting** APIs, libraries, or SDKs.\n\n### assets\u002Ftemplate-tutorial.md\nTemplate for step-by-step tutorials with:\n- Learning objectives\n- Step-by-step instructions with checkpoints\n- Common issues sections\n- \"You're done\" celebration\n- Next steps and extensions\n- Complete code sections\n\n**Use when creating** hands-on tutorials or walkthroughs.\n\n## Best Practices\n\n**Start simple:**\n- Begin with template that matches doc type\n- Focus on quick wins (headers, bullets, quick start)\n- Add complexity progressively\n\n**Be consistent:**\n- Use same formatting patterns throughout\n- Maintain consistent terminology\n- Follow established conventions in templates\n\n**Test scannability:**\n- Can readers find what they need in 30 seconds?\n- Are headers descriptive and hierarchical?\n- Can someone skim bullets and understand the content?\n\n**Prioritize action:**\n- Make it easy to get started quickly\n- Provide working examples early\n- Show expected results\n\n**Reduce friction:**\n- Remove barriers to understanding\n- Explain non-obvious steps\n- Provide multiple entry points (quick start, deep dive, reference)\n\n## Writing Style\n\nUse imperative\u002Finfinitive form throughout:\n- ✅ \"Install the package using npm\"\n- ✅ \"To configure authentication, create a config file\"\n- ❌ \"You should install the package\"\n- ❌ \"If you want to configure authentication, you can create...\"\n\n**Voice:**\n- Present tense, active voice\n- Direct and conversational but precise\n- Command form for instructions\n\n**Sentence structure:**\n- Lead with action or key point\n- Keep under 20 words\n- One idea per sentence\n\n## Examples\n\n### Example 1: README Documentation\n\nUser asks: \"Create a README for my authentication library\"\n\n**Approach:**\n1. Start with `assets\u002Ftemplate-quick-start.md`\n2. Add one-line description of auth library\n3. Create 60-second quick start (install, configure, use)\n4. Show 2-3 common use cases with code\n5. Add API reference links\n6. Include troubleshooting for common auth issues\n7. Validate with `references\u002Fchecklist.md`\n\n### Example 2: API Documentation\n\nUser asks: \"Document my REST API endpoints\"\n\n**Approach:**\n1. Use `assets\u002Ftemplate-api-docs.md` structure\n2. For each endpoint: What it does, when to use, quick example\n3. Add parameter tables with types and descriptions\n4. Include authentication section\n5. Show error responses and handling\n6. Add rate limiting information\n7. Provide complete working examples\n\n### Example 3: Tutorial\n\nUser asks: \"Write a getting started guide for building a todo app\"\n\n**Approach:**\n1. Start with `assets\u002Ftemplate-tutorial.md`\n2. Define learning objectives and time estimate\n3. Break into clear steps (Setup → Add todos → Display → Complete)\n4. Each step: Goal, instructions, checkpoint, expected result\n5. Add \"What you learned\" summaries\n6. Include troubleshooting section\n7. Suggest next steps and extensions\n\n### Example 4: Improving Existing Docs\n\nUser asks: \"Make this documentation easier to understand\"\n\n**Approach:**\n1. Read existing documentation\n2. Identify issues (walls of text, missing structure, unclear actions)\n3. Add quick start section if missing\n4. Break paragraphs into bullets\n5. Add clear headers and hierarchy\n6. Make action steps explicit and numbered\n7. Add expected outcomes\n8. Validate with `references\u002Fchecklist.md`\n\n## Summary\n\nCreate documentation that is:\n- **Scannable** - Headers, bullets, whitespace\n- **Actionable** - Clear steps, working examples\n- **Progressive** - Quick start → concepts → advanced\n- **Accessible** - Low cognitive load, clear language\n- **Consistent** - Same patterns throughout\n\n**Always reference** `references\u002Fadhd-patterns.md` for detailed guidance and `references\u002Fchecklist.md` for validation. **Use templates** from `assets\u002F` as starting points for common documentation types.\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill adhd-friendly-documentation",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill adhd-friendly-documentation",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill adhd-friendly-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002FSKILL.md",true,[78,84,88,92,98],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Ftemplate-api-docs.md","ASSET","资产文件",5648,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002Fassets\u002Ftemplate-api-docs.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Ftemplate-quick-start.md",2600,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002Fassets\u002Ftemplate-quick-start.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Ftemplate-tutorial.md",4768,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002Fassets\u002Ftemplate-tutorial.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fadhd-patterns.md","REFERENCE","参考文档",7397,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002Freferences\u002Fadhd-patterns.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fchecklist.md",4134,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_config\u002Fopencode\u002Fskills\u002Fadhd-friendly-documentation\u002Freferences\u002Fchecklist.md",[103,120,149,173,195,214],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":112,"publishedAt":49},"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",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[113,114,115,116,117,118,119],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":49},"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",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[122,131,132,133,134,135,136,137,138,139,140,141,142,30,143,144,145,146,147,148],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","project wiki","disk","architecture","code","unknown","generated",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":159,"publishedAt":49},"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",[155,156],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":157,"categoryName":158,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[151,160,161,162,163,164,165,166,139,167,41,168,44,33,169,170,171,172],"user","content","视频","creator","generate video","videos","launch","video content","upload","auto","types","Video","创作",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":49},"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",[179],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},[181,182,151,183,184,171,185,186,187,188,189,190,191,192,137,193,44,33,131,194],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":205,"publishedAt":49},"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",[201,202,203,204],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":157,"categoryName":158,"taxonomyType":26,"taxonomyTypeDesc":27},[206,118,207,208,209,210,146,44,33,211,45,212,213],"writing skills","how","teach","write skill","write","claude code skills","how to","trigger",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":49},"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",[220,221],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":157,"categoryName":158,"taxonomyType":26,"taxonomyTypeDesc":27},[223,118,224,135,225,45,44,207,210,33,212],"Rules","writing rules","project rules"]