[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70H8MJMDHA437DP5HAETES8":3,"skill-same:01M70H8MJMDHA437DP5HAETES8":96},{"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},"01M70H8MJMDHA437DP5HAETES8","code-documenter",null,"Automatically detect and add comprehensive documentation to code files across multiple languages (Python, JavaScript\u002FTypeScript, C\u002FC++, Dart\u002FFlutter). Generate language-appropriate docstrings, comments, and examples following industry standards. Use when code files lack documentation, after implementing new features, or when requested to document code. Support single files and batch 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\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","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],"code documenter","documenter","code","use","dart","single","python","c++","standards","add","typescript","features","support","generate","documentation","across","batch","when","files","implementing","2026-11-10 10:12:30",false,"---\nname: code-documenter\ndescription: Automatically detect and add comprehensive documentation to code files across multiple languages (Python, JavaScript\u002FTypeScript, C\u002FC++, Dart\u002FFlutter). Generate language-appropriate docstrings, comments, and examples following industry standards. Use when code files lack documentation, after implementing new features, or when requested to document code. Support single files and batch documentation.\n---\n\n# Code Documenter\n\n## Overview\n\nAdd or update professional documentation to code files following language-specific best practices and industry conventions. Reduce cognitive load by providing clear, well-structured documentation that explains \"why\" rather than just \"what.\"\n\n## Related Tools\n\nThis skill focuses on **code-level documentation** (docstrings, inline comments).\n\nFor **project-level documentation**, use:\n- `\u002Fdoc-generate` - Generate API docs, architecture diagrams, README files\n- `code-documentation` plugin - Automated project documentation workflows\n\n**Decision**: Use this skill for code, plugin for projects.\n\n## Supported Languages\n\n- **Python**: PEP 257 docstrings with type hints (Google\u002FNumPy style)\n- **JavaScript\u002FTypeScript**: JSDoc\u002FTSDoc comments with examples\n- **C\u002FC++**: Doxygen-style documentation with memory safety notes\n- **Dart\u002FFlutter**: Triple-slash comments with widget documentation\n\n## When to Use This Skill\n\nThis skill should be used when:\n\n1. **Explicit request**: User asks to \"document this code\" or \"add documentation\"\n2. **Auto-detection scenarios**:\n   - New code has been written without documentation\n   - Existing code lacks adequate docstrings\u002Fcomments\n   - Public APIs are undocumented\n   - Complex logic needs explanation\n3. **After code changes**: When implementing features or fixing bugs\n4. **Before commits**: When preparing code for review\n\n## Documentation Workflow\n\n### Step 1: Identify Files to Document\n\nDetermine which files need documentation:\n\n- If user provides file path(s), use those specific files\n- If user says \"document my changes,\" check git status for modified files\n- If user says \"document this,\" use the file currently in context\n- For \"document everything,\" ask user to confirm scope\n\n### Step 2: Detect Language and Load Standards\n\nFor each file, detect the programming language by extension:\n\n- `.py` → Python: Read `references\u002Fpython_docs.md`\n- `.js, .ts, .jsx, .tsx` → JavaScript\u002FTypeScript: Read `references\u002Fjavascript_typescript_docs.md`\n- `.cpp, .cc, .h, .hpp, .c` → C\u002FC++: Read `references\u002Fcpp_docs.md`\n- `.dart` → Dart\u002FFlutter: Read `references\u002Fdart_flutter_docs.md`\n\nIf language is unsupported, inform user and skip the file.\n\nLoad only the relevant reference file into context to avoid token waste. Do not load all language references at once.\n\n### Step 3: Analyze Code Structure\n\nRead the target file and identify:\n\n1. **Top-level documentation**: Module\u002Ffile docstring\n2. **Classes\u002FInterfaces**: Class documentation, attributes, purpose\n3. **Functions\u002FMethods**: Parameter descriptions, return values, exceptions\n4. **Complex logic**: Areas needing inline comments\n5. **Constants\u002FEnums**: Purpose and usage documentation\n\n### Step 4: Apply Documentation Standards\n\nFollowing the loaded language standards, add documentation at the **standard detail level**:\n\n- Document all public APIs (classes, functions, methods)\n- Add module\u002Ffile-level documentation\n- Include parameter and return value descriptions\n- Add inline comments for non-obvious logic\n- Skip private methods unless they're complex\n- Include usage examples for complex APIs\n\n**Key Principles**:\n- First line should be a concise one-line summary\n- Explain \"why\" in comments, not \"what\"\n- Use proper formatting for the language (PEP 257, JSDoc, Doxygen, etc.)\n- Include type information where applicable\n- Add examples for complex usage patterns\n- Note side effects, thread safety, memory ownership\n\n### Step 5: Preserve Code Logic\n\n**CRITICAL**: Do not modify the actual code logic, only add documentation.\n\n- Add docstrings\u002Fcomments without changing functionality\n- Preserve existing formatting and style\n- Keep all existing code intact\n- Only add documentation blocks and inline comments\n\n### Step 6: Apply Changes\n\nUse the Edit tool to add documentation:\n\n1. **For module\u002Ffile documentation**: Add at the very top of the file\n2. **For class documentation**: Add immediately before class definition\n3. **For function documentation**: Add immediately before function definition\n4. **For inline comments**: Add on line above or at end of complex statements\n\nMake multiple small, focused edits rather than one large replacement.\n\n### Step 7: Verify and Report\n\nAfter documenting:\n\n1. Confirm all public APIs are documented\n2. Check that complex logic has explanatory comments\n3. Verify formatting matches language conventions\n4. Report summary to user:\n   - Files documented\n   - Documentation elements added (modules, classes, functions)\n   - Any issues or skipped items\n\n## Language-Specific Quick Reference\n\n### Python\n\n```python\n\"\"\"Module-level docstring explaining purpose.\"\"\"\n\nclass Example:\n    \"\"\"Class docstring with purpose.\n\n    Attributes:\n        attr_name: Description with type info\n    \"\"\"\n\n    def method(self, param: str) -> bool:\n        \"\"\"One-line description.\n\n        Args:\n            param: Parameter description\n\n        Returns:\n            Return value description\n\n        Raises:\n            ExceptionType: When this occurs\n        \"\"\"\n```\n\n### JavaScript\u002FTypeScript\n\n```typescript\n\u002F**\n * Function description.\n *\n * @param param - Parameter description\n * @returns Return value description\n * @throws {ErrorType} When error occurs\n *\n * @example\n * ```typescript\n * const result = example('value');\n * ```\n *\u002F\nfunction example(param: string): boolean {\n```\n\n### C\u002FC++\n\n```cpp\n\u002F**\n * @file filename.h\n * @brief Brief file description\n *\u002F\n\n\u002F**\n * @brief Function description\n *\n * @param param Parameter description\n * @return Return value description\n *\n * @warning Important warnings\n * @threadsafe Thread safety information\n *\u002F\nbool example(const std::string& param);\n```\n\n### Dart\u002FFlutter\n\n```dart\n\u002F\u002F\u002F Function description.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Detailed explanation if needed.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Returns description.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Throws [ExceptionType] when error occurs.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Example:\n\u002F\u002F\u002F ```dart\n\u002F\u002F\u002F final result = example('value');\n\u002F\u002F\u002F ```\nbool example(String param) {\n```\n\n## Examples\n\n### Example 1: Document Single Python File\n\n**User request**: \"Document this file\"\n\n**Process**:\n1. Detect file is Python (.py extension)\n2. Read `references\u002Fpython_docs.md`\n3. Analyze file structure (modules, classes, functions)\n4. Add PEP 257 docstrings following Google style\n5. Add inline comments for complex logic\n6. Report: \"Added module docstring, 3 class docstrings, 12 function docstrings, and 8 inline comments\"\n\n### Example 2: Document Changed TypeScript Files\n\n**User request**: \"Document my changes\"\n\n**Process**:\n1. Check git status for modified .ts\u002F.tsx files\n2. For each file: detect TypeScript\n3. Read `references\u002Fjavascript_typescript_docs.md`\n4. Add JSDoc comments to new\u002Fmodified functions\n5. Update existing docstrings if signatures changed\n6. Report: \"Documented 5 TypeScript files with 23 functions\"\n\n### Example 3: Document C++ Header\n\n**User request**: \"Add documentation to timer.h\"\n\n**Process**:\n1. Detect C++ from .h extension\n2. Read `references\u002Fcpp_docs.md`\n3. Add file-level @file and @brief\n4. Document all public classes and methods\n5. Add @note for thread safety, memory ownership\n6. Report: \"Added file header, 2 class docs, 15 method docs with threading notes\"\n\n## Advanced Features\n\n### Batch Documentation\n\nWhen documenting multiple files:\n\n1. Group files by language to minimize reference file loading\n2. Process all Python files, then JavaScript, then C++, etc.\n3. Load each language reference only once\n4. Report progress: \"Documenting file 3 of 8...\"\n5. Provide summary at end with breakdown by language\n\n### Smart Detection of Documentation Needs\n\nAutomatically identify what needs documentation:\n\n- **Missing module docstrings**: Top of file has no documentation\n- **Undocumented public APIs**: Classes\u002Ffunctions lack docstrings\n- **Complex logic**: Code blocks with high cyclomatic complexity\n- **Recent changes**: Functions modified in recent commits\n- **TODO\u002FFIXME comments**: Areas marked for attention\n\n### Handling Edge Cases\n\n**Mixed languages in project**: Document each file in its native style\n\n**Partially documented code**: Fill in gaps without duplicating existing docs\n\n**Generated code**: Skip auto-generated files (ask user if uncertain)\n\n**Test files**: Use simpler documentation (purpose and what is tested)\n\n**Legacy code**: Add minimal documentation first, suggest comprehensive pass\n\n## Best Practices\n\n1. **Read the file first**: Always read the target file before documenting\n2. **Load references as needed**: Don't load all language references at once\n3. **Multiple small edits**: Make focused edits rather than large replacements\n4. **Preserve formatting**: Match existing code style and indentation\n5. **Explain \"why\" not \"what\"**: Focus comments on reasoning, not mechanics\n6. **Include examples**: Add usage examples for complex APIs\n7. **Note constraints**: Document preconditions, thread safety, ownership\n8. **Update existing docs**: If code changed, update related documentation\n\n## Resources\n\n### references\u002F\n\nLanguage-specific documentation standards:\n\n- `python_docs.md` - PEP 257 conventions, type hints, Google\u002FNumPy style\n- `javascript_typescript_docs.md` - JSDoc\u002FTSDoc standards with examples\n- `cpp_docs.md` - Doxygen conventions, thread safety, memory management\n- `dart_flutter_docs.md` - Dart doc comments, Flutter widget documentation\n\nLoad only the relevant reference when documenting files in that language.\n","# Code Documenter\n\n## Overview\n\nAdd or update professional documentation to code files following language-specific best practices and industry conventions. Reduce cognitive load by providing clear, well-structured documentation that explains \"why\" rather than just \"what.\"\n\n## Related Tools\n\nThis skill focuses on **code-level documentation** (docstrings, inline comments).\n\nFor **project-level documentation**, use:\n- `\u002Fdoc-generate` - Generate API docs, architecture diagrams, README files\n- `code-documentation` plugin - Automated project documentation workflows\n\n**Decision**: Use this skill for code, plugin for projects.\n\n## Supported Languages\n\n- **Python**: PEP 257 docstrings with type hints (Google\u002FNumPy style)\n- **JavaScript\u002FTypeScript**: JSDoc\u002FTSDoc comments with examples\n- **C\u002FC++**: Doxygen-style documentation with memory safety notes\n- **Dart\u002FFlutter**: Triple-slash comments with widget documentation\n\n## When to Use This Skill\n\nThis skill should be used when:\n\n1. **Explicit request**: User asks to \"document this code\" or \"add documentation\"\n2. **Auto-detection scenarios**:\n   - New code has been written without documentation\n   - Existing code lacks adequate docstrings\u002Fcomments\n   - Public APIs are undocumented\n   - Complex logic needs explanation\n3. **After code changes**: When implementing features or fixing bugs\n4. **Before commits**: When preparing code for review\n\n## Documentation Workflow\n\n### Step 1: Identify Files to Document\n\nDetermine which files need documentation:\n\n- If user provides file path(s), use those specific files\n- If user says \"document my changes,\" check git status for modified files\n- If user says \"document this,\" use the file currently in context\n- For \"document everything,\" ask user to confirm scope\n\n### Step 2: Detect Language and Load Standards\n\nFor each file, detect the programming language by extension:\n\n- `.py` → Python: Read `references\u002Fpython_docs.md`\n- `.js, .ts, .jsx, .tsx` → JavaScript\u002FTypeScript: Read `references\u002Fjavascript_typescript_docs.md`\n- `.cpp, .cc, .h, .hpp, .c` → C\u002FC++: Read `references\u002Fcpp_docs.md`\n- `.dart` → Dart\u002FFlutter: Read `references\u002Fdart_flutter_docs.md`\n\nIf language is unsupported, inform user and skip the file.\n\nLoad only the relevant reference file into context to avoid token waste. Do not load all language references at once.\n\n### Step 3: Analyze Code Structure\n\nRead the target file and identify:\n\n1. **Top-level documentation**: Module\u002Ffile docstring\n2. **Classes\u002FInterfaces**: Class documentation, attributes, purpose\n3. **Functions\u002FMethods**: Parameter descriptions, return values, exceptions\n4. **Complex logic**: Areas needing inline comments\n5. **Constants\u002FEnums**: Purpose and usage documentation\n\n### Step 4: Apply Documentation Standards\n\nFollowing the loaded language standards, add documentation at the **standard detail level**:\n\n- Document all public APIs (classes, functions, methods)\n- Add module\u002Ffile-level documentation\n- Include parameter and return value descriptions\n- Add inline comments for non-obvious logic\n- Skip private methods unless they're complex\n- Include usage examples for complex APIs\n\n**Key Principles**:\n- First line should be a concise one-line summary\n- Explain \"why\" in comments, not \"what\"\n- Use proper formatting for the language (PEP 257, JSDoc, Doxygen, etc.)\n- Include type information where applicable\n- Add examples for complex usage patterns\n- Note side effects, thread safety, memory ownership\n\n### Step 5: Preserve Code Logic\n\n**CRITICAL**: Do not modify the actual code logic, only add documentation.\n\n- Add docstrings\u002Fcomments without changing functionality\n- Preserve existing formatting and style\n- Keep all existing code intact\n- Only add documentation blocks and inline comments\n\n### Step 6: Apply Changes\n\nUse the Edit tool to add documentation:\n\n1. **For module\u002Ffile documentation**: Add at the very top of the file\n2. **For class documentation**: Add immediately before class definition\n3. **For function documentation**: Add immediately before function definition\n4. **For inline comments**: Add on line above or at end of complex statements\n\nMake multiple small, focused edits rather than one large replacement.\n\n### Step 7: Verify and Report\n\nAfter documenting:\n\n1. Confirm all public APIs are documented\n2. Check that complex logic has explanatory comments\n3. Verify formatting matches language conventions\n4. Report summary to user:\n   - Files documented\n   - Documentation elements added (modules, classes, functions)\n   - Any issues or skipped items\n\n## Language-Specific Quick Reference\n\n### Python\n\n```python\n\"\"\"Module-level docstring explaining purpose.\"\"\"\n\nclass Example:\n    \"\"\"Class docstring with purpose.\n\n    Attributes:\n        attr_name: Description with type info\n    \"\"\"\n\n    def method(self, param: str) -> bool:\n        \"\"\"One-line description.\n\n        Args:\n            param: Parameter description\n\n        Returns:\n            Return value description\n\n        Raises:\n            ExceptionType: When this occurs\n        \"\"\"\n```\n\n### JavaScript\u002FTypeScript\n\n```typescript\n\u002F**\n * Function description.\n *\n * @param param - Parameter description\n * @returns Return value description\n * @throws {ErrorType} When error occurs\n *\n * @example\n * ```typescript\n * const result = example('value');\n * ```\n *\u002F\nfunction example(param: string): boolean {\n```\n\n### C\u002FC++\n\n```cpp\n\u002F**\n * @file filename.h\n * @brief Brief file description\n *\u002F\n\n\u002F**\n * @brief Function description\n *\n * @param param Parameter description\n * @return Return value description\n *\n * @warning Important warnings\n * @threadsafe Thread safety information\n *\u002F\nbool example(const std::string& param);\n```\n\n### Dart\u002FFlutter\n\n```dart\n\u002F\u002F\u002F Function description.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Detailed explanation if needed.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Returns description.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Throws [ExceptionType] when error occurs.\n\u002F\u002F\u002F\n\u002F\u002F\u002F Example:\n\u002F\u002F\u002F ```dart\n\u002F\u002F\u002F final result = example('value');\n\u002F\u002F\u002F ```\nbool example(String param) {\n```\n\n## Examples\n\n### Example 1: Document Single Python File\n\n**User request**: \"Document this file\"\n\n**Process**:\n1. Detect file is Python (.py extension)\n2. Read `references\u002Fpython_docs.md`\n3. Analyze file structure (modules, classes, functions)\n4. Add PEP 257 docstrings following Google style\n5. Add inline comments for complex logic\n6. Report: \"Added module docstring, 3 class docstrings, 12 function docstrings, and 8 inline comments\"\n\n### Example 2: Document Changed TypeScript Files\n\n**User request**: \"Document my changes\"\n\n**Process**:\n1. Check git status for modified .ts\u002F.tsx files\n2. For each file: detect TypeScript\n3. Read `references\u002Fjavascript_typescript_docs.md`\n4. Add JSDoc comments to new\u002Fmodified functions\n5. Update existing docstrings if signatures changed\n6. Report: \"Documented 5 TypeScript files with 23 functions\"\n\n### Example 3: Document C++ Header\n\n**User request**: \"Add documentation to timer.h\"\n\n**Process**:\n1. Detect C++ from .h extension\n2. Read `references\u002Fcpp_docs.md`\n3. Add file-level @file and @brief\n4. Document all public classes and methods\n5. Add @note for thread safety, memory ownership\n6. Report: \"Added file header, 2 class docs, 15 method docs with threading notes\"\n\n## Advanced Features\n\n### Batch Documentation\n\nWhen documenting multiple files:\n\n1. Group files by language to minimize reference file loading\n2. Process all Python files, then JavaScript, then C++, etc.\n3. Load each language reference only once\n4. Report progress: \"Documenting file 3 of 8...\"\n5. Provide summary at end with breakdown by language\n\n### Smart Detection of Documentation Needs\n\nAutomatically identify what needs documentation:\n\n- **Missing module docstrings**: Top of file has no documentation\n- **Undocumented public APIs**: Classes\u002Ffunctions lack docstrings\n- **Complex logic**: Code blocks with high cyclomatic complexity\n- **Recent changes**: Functions modified in recent commits\n- **TODO\u002FFIXME comments**: Areas marked for attention\n\n### Handling Edge Cases\n\n**Mixed languages in project**: Document each file in its native style\n\n**Partially documented code**: Fill in gaps without duplicating existing docs\n\n**Generated code**: Skip auto-generated files (ask user if uncertain)\n\n**Test files**: Use simpler documentation (purpose and what is tested)\n\n**Legacy code**: Add minimal documentation first, suggest comprehensive pass\n\n## Best Practices\n\n1. **Read the file first**: Always read the target file before documenting\n2. **Load references as needed**: Don't load all language references at once\n3. **Multiple small edits**: Make focused edits rather than large replacements\n4. **Preserve formatting**: Match existing code style and indentation\n5. **Explain \"why\" not \"what\"**: Focus comments on reasoning, not mechanics\n6. **Include examples**: Add usage examples for complex APIs\n7. **Note constraints**: Document preconditions, thread safety, ownership\n8. **Update existing docs**: If code changed, update related documentation\n\n## Resources\n\n### references\u002F\n\nLanguage-specific documentation standards:\n\n- `python_docs.md` - PEP 257 conventions, type hints, Google\u002FNumPy style\n- `javascript_typescript_docs.md` - JSDoc\u002FTSDoc standards with examples\n- `cpp_docs.md` - Doxygen conventions, thread safety, memory management\n- `dart_flutter_docs.md` - Dart doc comments, Flutter widget documentation\n\nLoad only the relevant reference when documenting files in that language.\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter",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 code-documenter",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill code-documenter",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill code-documenter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002FSKILL.md",true,[78,84,88,92],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcpp_docs.md","REFERENCE","参考文档",7507,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002Freferences\u002Fcpp_docs.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fdart_flutter_docs.md",11350,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002Freferences\u002Fdart_flutter_docs.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fjavascript_typescript_docs.md",5353,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002Freferences\u002Fjavascript_typescript_docs.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpython_docs.md",3347,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frghamilton3-dotfiles\u002Fdot_config\u002Fopencode\u002Fskills\u002Fcode-documenter\u002Freferences\u002Fpython_docs.md",[97,114,139,164,186,205],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"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",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[107,108,109,110,111,112,113],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":122,"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",[120,121],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[116,123,124,125,126,127,128,129,130,42,131,132,133,43,134,135,136,31,137,138],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","intent","cli","map","project wiki","disk","architecture","unknown","generated",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":149,"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",[145,146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[141,150,151,152,153,154,155,156,42,157,158,159,46,32,160,161,162,163],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"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",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,141,174,175,162,176,177,178,179,180,181,182,183,129,184,46,32,123,185],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":196,"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",[192,193,194,195],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},[197,112,198,199,200,201,31,46,32,202,47,203,204],"writing skills","how","teach","write skill","write","claude code skills","how to","trigger",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":213,"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",[211,212],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":26,"taxonomyTypeDesc":27},[214,112,215,127,216,47,46,198,201,32,203],"Rules","writing rules","project rules"]