[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BPQFFRDP232QCZ6ST77RC":3,"skill-same:01M73BPQFFRDP232QCZ6ST77RC":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M73BPQFFRDP232QCZ6ST77RC","documentation-writing",null,"Creates clear, accessible documentation and communications for diverse audiences. Use when: writing guides, creating documentation, drafting communications, or synthesizing complex information for technical and non-technical audiences.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocumentation-writing\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: documentation-writing\ndescription: >\n  Creates clear, accessible documentation and communications for diverse audiences.\n  Use when: writing guides, creating documentation, drafting communications, or synthesizing\n  complex information for technical and non-technical audiences.\nversion: 1.0.3\nscope: common\nstatus: active\nowner: pm\nlast_reviewed: 2026-11-08\nprerequisites: none\nrelates_to:\n  - skill: team-builder\n    type: composes_with\ngemini-parity: skip\nmetadata:\n  type: implementation\n  triggers:\n    - write documentation\n    - create guide\n    - draft communication\n    - write manual\n    - create tutorial\n    - documentation\n    - technical writing\n---\n\n## Context\n\nThis skill provides comprehensive documentation writing capabilities, from technical guides to user-friendly manuals. It ensures documentation is clear, well-structured, accessible, and appropriately targeted to the intended audience.\n\n## When to Use\n\n**Technical Documentation**:\n- Trigger: \"Write technical documentation\" or \"Create API reference\"\n- Use Case: Documenting technical systems, APIs, or code\n\n**User Guides**:\n- Trigger: \"Create user guide\" or \"Write manual\"\n- Use Case: Helping end users understand and use products or features\n\n**Process Documentation**:\n- Trigger: \"Document process\" or \"Create workflow guide\"\n- Use Case: Explaining how to complete tasks or procedures\n\n**Communications**:\n- Trigger: \"Draft announcement\" or \"Write communication\"\n- Use Case: Sharing information with stakeholders or teams\n\n---\n\n## Execution Steps\n\n## Step 1: Audience Analysis\n\n**Purpose**: Understand who will read the documentation and their needs.\n\n**Audience Assessment**:\n1. **Technical Level**:\n   - Technical experts (developers, engineers)\n   - Technical users (power users, administrators)\n   - Non-technical users (end users, general audience)\n   - Mixed audiences\n\n2. **Knowledge Base**:\n   - What prior knowledge do they have?\n   - What terminology will they understand?\n   - What concepts need explanation?\n   - What examples will resonate?\n\n3. **Use Context**:\n   - When will they use this documentation?\n   - What problem are they trying to solve?\n   - What's their urgency or stress level?\n   - What format do they prefer?\n\n4. **Accessibility Needs**:\n   - Language requirements (English, Korean, multi-language)\n   - Reading level considerations\n   - Format preferences (visual, text, interactive)\n   - Disability accommodations\n\n**Korean Plain-Language Preference (`순우리말`-first)**: when the deliverable is Korean, prefer native Korean words over loanwords where a natural, widely-understood equivalent exists (e.g. `만들기` over `크리에이션`, `알림` over `노티피케이션`). Settled loanwords (`컴퓨터`, `데이터`, `소프트웨어`, `파일`) and established technical terms remain permitted — clarity and standard terminology take precedence. When editing existing Korean documents for other reasons, nativize the touched sections incrementally; no bulk rewrites.\n\n**Output**: Audience profile with characteristics and needs\n\n---\n\n## Step 2: Information Architecture\n\n**Purpose**: Structure documentation for clarity and navigation.\n\n**Structuring Principles**:\n1. **Hierarchical Organization**:\n   - Overview → Details → Reference\n   - High-level concepts → Specific tasks\n   - General information → Edge cases\n\n2. **Progressive Disclosure**:\n   - Start with essentials\n   - Reveal complexity gradually\n   - Link to detailed information\n   - Provide multiple depth levels\n\n3. **Logical Flow**:\n   - Chronological (step-by-step processes)\n   - Task-based (common user goals)\n   - Conceptual (building understanding)\n   - Reference (alphabetical, searchable)\n\n4. **Navigation Design**:\n   - Table of contents\n   - Section headers and subheaders\n   - Cross-references and links\n   - Index or search keywords\n\n**Common Documentation Structures**:\n- **Getting Started Guide**: Setup → First steps → Common tasks\n- **User Manual**: Overview → Features → Instructions → Reference\n- **Technical Guide**: Architecture → Implementation → API → Examples\n- **Troubleshooting**: Symptoms → Causes → Solutions → Prevention\n\n**Output**: Documentation outline with structure and flow\n\n---\n\n## Step 3: Content Creation\n\n**Purpose**: Write clear, actionable content.\n\n**Writing Principles**:\n1. **Clarity First**:\n   - Use simple, direct language\n   - One idea per sentence\n   - Active voice over passive\n   - Specific over general\n\n2. **Accessibility**:\n   - Define technical terms on first use\n   - Provide examples and analogies\n   - Use visual aids (diagrams, screenshots)\n   - Consider non-native speakers\n\n3. **Actionability**:\n   - Start with verbs for instructions\n   - Provide step-by-step procedures\n   - Include expected results\n   - Add troubleshooting guidance\n\n4. **Scannability**:\n   - Use bullet points and lists\n   - Highlight important information\n   - Break text into short paragraphs\n   - Use descriptive headers\n\n**Content Types**:\n1. **Procedural Content**:\n   - Step-by-step instructions\n   - Numbered lists for sequences\n   - Conditional steps (if\u002Fthen)\n   - Warnings and cautions\n\n2. **Conceptual Content**:\n   - Explanations and definitions\n   - Examples and use cases\n   - Diagrams and illustrations\n   - Analogies and comparisons\n\n3. **Reference Content**:\n   - Tables and matrices\n   - Code examples and snippets\n   - Configuration options\n   - Error messages and solutions\n\n**Output**: Complete documentation content with clear structure\n\n---\n\n## Step 4: Visual Communication\n\n**Purpose**: Enhance understanding with visual elements.\n\n**Visual Design Guidelines**:\n1. **Diagrams and Flowcharts**:\n   - Use for processes and workflows\n   - Keep simple and focused\n   - Label all elements clearly\n   - Include legends if needed\n\n2. **Screenshots and Images**:\n   - Show actual interface elements\n   - Highlight important areas\n   - Add annotations and callouts\n   - Maintain consistent style\n\n3. **Tables and Charts**:\n   - Organize complex information\n   - Use clear headers and labels\n   - Highlight key data points\n   - Provide context and interpretation\n\n4. **Code Examples**:\n   - Show working examples\n   - Add comments explaining code\n   - Use syntax highlighting\n   - Include expected output\n\n**Visual Accessibility**:\n- Provide text alternatives (alt text)\n- Ensure sufficient color contrast\n- Use readable fonts and sizes\n- Consider color blindness\n\n**Output**: Visual elements that enhance understanding\n\n---\n\n## Step 5: Review and Refine\n\n**Purpose**: Ensure documentation meets quality standards.\n\n**Quality Checklist**:\n- [ ] Content is accurate and complete\n- [ ] Structure is logical and navigable\n- [ ] Language is clear and accessible\n- [ ] Examples are relevant and helpful\n- [ ] Visual aids support understanding\n- [ ] Formatting is consistent\n- [ ] Cross-references work correctly\n- [ ] Technical terms are defined\n- [ ] Instructions are actionable\n- [ ] Troubleshooting covers common issues\n\n**Testing Methods**:\n1. **Usability Testing**:\n   - Have users follow documentation\n   - Observe where they get stuck\n   - Ask for feedback on clarity\n   - Test with diverse users\n\n2. **Technical Review**:\n   - Subject matter expert review\n   - Technical accuracy verification\n   - Completeness check\n   - Edge case coverage\n\n3. **Editorial Review**:\n   - Grammar and spelling check\n   - Style guide consistency\n   - Formatting verification\n   - Link testing\n\n**Output**: Refined documentation with quality assurance\n\n---\n\n## Step 6: Publishing and Maintenance\n\n**Purpose**: Make documentation available and keep it current.\n\n**Publishing Considerations**:\n1. **Format Selection**:\n   - Markdown (for version control and collaboration)\n   - HTML (for web publishing)\n   - PDF (for offline reading and printing)\n   - Interactive (for tutorials and guides)\n\n2. **Distribution**:\n   - Documentation sites (GitBook, ReadTheDocs)\n   - Wikis and knowledge bases\n   - Inline help and tooltips\n   - Print manuals\n\n3. **Version Control**:\n   - Track documentation versions\n   - Maintain change logs\n   - Archive outdated versions\n   - Tag documentation releases\n\n4. **Maintenance**:\n   - Review schedule (quarterly, per release)\n   - Update procedures\n   - Feedback collection\n   - Accuracy verification\n\n**Maintenance Tasks**:\n- Update for product changes\n- Revise based on user feedback\n- Add new FAQs and troubleshooting\n- Remove or archive outdated content\n- Update screenshots and examples\n\n**Output**: Published documentation with maintenance plan\n\n---\n\n## Output Format\n\n**For Technical Documentation**:\n- API references with parameters and responses\n- Architecture documentation with diagrams\n- Setup and installation guides\n- Configuration references\n- Troubleshooting guides\n\n**For User Documentation**:\n- Getting started guides\n- Feature explanations\n- How-to tutorials\n- FAQ sections\n- Best practices guides\n\n**For Process Documentation**:\n- Workflow descriptions\n- Procedure manuals\n- Training materials\n- Onboarding guides\n- Standard operating procedures\n\n---\n\n## Best Practices\n\n**Writing Quality**:\n✅ **Do**:\n- Write for your specific audience\n- Use simple, direct language\n- Provide examples and context\n- Include visual aids\n- Test with actual users\n- Update regularly\n\n❌ **Don't**:\n- Assume prior knowledge\n- Use jargon without explanation\n- Create walls of text\n- Skip visual formatting\n- Write for \"everyone\" (be specific)\n- Set and forget documentation\n\n**Structure Quality**:\n✅ **Do**:\n- Start with overview\n- Use progressive disclosure\n- Provide multiple navigation paths\n- Include cross-references\n- Add search keywords\n- Create scannable content\n\n❌ **Don't**:\n- Bury important information\n- Create deep hierarchies\n- Make users read everything\n- Use ambiguous headers\n- Ignore different learning styles\n- Write monolithic documents\n\n---\n\n## Common Mistakes to Avoid\n\n**Content Anti-Patterns**:\n1. **Information Dump**: Including everything without organization\n2. **Assumption Trap**: Assuming reader knows what you know\n3. **Tone Mismatch**: Too formal or too casual for audience\n4. **Update Neglect**: Letting documentation become outdated\n5. **Missing Context**: Focusing on what without explaining why\n\n**Structure Anti-Patterns**:\n1. **Poor Organization**: Illogical flow or grouping\n2. **Navigation Fail**: Difficult to find specific information\n3. **Inconsistency**: Different styles or formats in same doc\n4. **Gaps**: Missing steps or important information\n5. **Overcompleteness**: Including unnecessary detail\n\n---\n\n## Related Skills\n\n- **research-analysis**: For gathering information to document\n- **technical-writing**: For specialized technical documentation\n- **accessibility-review**: For ensuring documentation accessibility\n- **visual-design**: For creating effective diagrams and visual aids\n\n---\n\n## Documentation Tools\n\n**Authoring Tools**:\n- Markdown editors (Typora, VS Code, Obsidian)\n- Documentation generators (Jekyll, Hugo, Docusaurus)\n- Wiki platforms (Confluence, Notion, GitBook)\n- Content management systems\n\n**Collaboration Tools**:\n- Version control (Git)\n- Review tools (GitHub PRs, Google Docs comments)\n- Style guides (Google Developer Documentation Style Guide)\n- Editorial calendars\n\n**Publishing Platforms**:\n- Static site generators (MkDocs, Docusaurus)\n- Documentation hosting (GitBook, ReadTheDocs)\n- Knowledge bases (Confluence, Notion)\n- Versioned documentation (Git-backed)\n\n**Quality Tools**:\n- Grammar checkers (Grammarly, LanguageTool)\n- Link checkers (broken link detectors)\n- SEO tools (for public documentation)\n- Analytics (user engagement tracking)\n","## Context\n\nThis skill provides comprehensive documentation writing capabilities, from technical guides to user-friendly manuals. It ensures documentation is clear, well-structured, accessible, and appropriately targeted to the intended audience.\n\n## When to Use\n\n**Technical Documentation**:\n- Trigger: \"Write technical documentation\" or \"Create API reference\"\n- Use Case: Documenting technical systems, APIs, or code\n\n**User Guides**:\n- Trigger: \"Create user guide\" or \"Write manual\"\n- Use Case: Helping end users understand and use products or features\n\n**Process Documentation**:\n- Trigger: \"Document process\" or \"Create workflow guide\"\n- Use Case: Explaining how to complete tasks or procedures\n\n**Communications**:\n- Trigger: \"Draft announcement\" or \"Write communication\"\n- Use Case: Sharing information with stakeholders or teams\n\n---\n\n## Execution Steps\n\n## Step 1: Audience Analysis\n\n**Purpose**: Understand who will read the documentation and their needs.\n\n**Audience Assessment**:\n1. **Technical Level**:\n   - Technical experts (developers, engineers)\n   - Technical users (power users, administrators)\n   - Non-technical users (end users, general audience)\n   - Mixed audiences\n\n2. **Knowledge Base**:\n   - What prior knowledge do they have?\n   - What terminology will they understand?\n   - What concepts need explanation?\n   - What examples will resonate?\n\n3. **Use Context**:\n   - When will they use this documentation?\n   - What problem are they trying to solve?\n   - What's their urgency or stress level?\n   - What format do they prefer?\n\n4. **Accessibility Needs**:\n   - Language requirements (English, Korean, multi-language)\n   - Reading level considerations\n   - Format preferences (visual, text, interactive)\n   - Disability accommodations\n\n**Korean Plain-Language Preference (`순우리말`-first)**: when the deliverable is Korean, prefer native Korean words over loanwords where a natural, widely-understood equivalent exists (e.g. `만들기` over `크리에이션`, `알림` over `노티피케이션`). Settled loanwords (`컴퓨터`, `데이터`, `소프트웨어`, `파일`) and established technical terms remain permitted — clarity and standard terminology take precedence. When editing existing Korean documents for other reasons, nativize the touched sections incrementally; no bulk rewrites.\n\n**Output**: Audience profile with characteristics and needs\n\n---\n\n## Step 2: Information Architecture\n\n**Purpose**: Structure documentation for clarity and navigation.\n\n**Structuring Principles**:\n1. **Hierarchical Organization**:\n   - Overview → Details → Reference\n   - High-level concepts → Specific tasks\n   - General information → Edge cases\n\n2. **Progressive Disclosure**:\n   - Start with essentials\n   - Reveal complexity gradually\n   - Link to detailed information\n   - Provide multiple depth levels\n\n3. **Logical Flow**:\n   - Chronological (step-by-step processes)\n   - Task-based (common user goals)\n   - Conceptual (building understanding)\n   - Reference (alphabetical, searchable)\n\n4. **Navigation Design**:\n   - Table of contents\n   - Section headers and subheaders\n   - Cross-references and links\n   - Index or search keywords\n\n**Common Documentation Structures**:\n- **Getting Started Guide**: Setup → First steps → Common tasks\n- **User Manual**: Overview → Features → Instructions → Reference\n- **Technical Guide**: Architecture → Implementation → API → Examples\n- **Troubleshooting**: Symptoms → Causes → Solutions → Prevention\n\n**Output**: Documentation outline with structure and flow\n\n---\n\n## Step 3: Content Creation\n\n**Purpose**: Write clear, actionable content.\n\n**Writing Principles**:\n1. **Clarity First**:\n   - Use simple, direct language\n   - One idea per sentence\n   - Active voice over passive\n   - Specific over general\n\n2. **Accessibility**:\n   - Define technical terms on first use\n   - Provide examples and analogies\n   - Use visual aids (diagrams, screenshots)\n   - Consider non-native speakers\n\n3. **Actionability**:\n   - Start with verbs for instructions\n   - Provide step-by-step procedures\n   - Include expected results\n   - Add troubleshooting guidance\n\n4. **Scannability**:\n   - Use bullet points and lists\n   - Highlight important information\n   - Break text into short paragraphs\n   - Use descriptive headers\n\n**Content Types**:\n1. **Procedural Content**:\n   - Step-by-step instructions\n   - Numbered lists for sequences\n   - Conditional steps (if\u002Fthen)\n   - Warnings and cautions\n\n2. **Conceptual Content**:\n   - Explanations and definitions\n   - Examples and use cases\n   - Diagrams and illustrations\n   - Analogies and comparisons\n\n3. **Reference Content**:\n   - Tables and matrices\n   - Code examples and snippets\n   - Configuration options\n   - Error messages and solutions\n\n**Output**: Complete documentation content with clear structure\n\n---\n\n## Step 4: Visual Communication\n\n**Purpose**: Enhance understanding with visual elements.\n\n**Visual Design Guidelines**:\n1. **Diagrams and Flowcharts**:\n   - Use for processes and workflows\n   - Keep simple and focused\n   - Label all elements clearly\n   - Include legends if needed\n\n2. **Screenshots and Images**:\n   - Show actual interface elements\n   - Highlight important areas\n   - Add annotations and callouts\n   - Maintain consistent style\n\n3. **Tables and Charts**:\n   - Organize complex information\n   - Use clear headers and labels\n   - Highlight key data points\n   - Provide context and interpretation\n\n4. **Code Examples**:\n   - Show working examples\n   - Add comments explaining code\n   - Use syntax highlighting\n   - Include expected output\n\n**Visual Accessibility**:\n- Provide text alternatives (alt text)\n- Ensure sufficient color contrast\n- Use readable fonts and sizes\n- Consider color blindness\n\n**Output**: Visual elements that enhance understanding\n\n---\n\n## Step 5: Review and Refine\n\n**Purpose**: Ensure documentation meets quality standards.\n\n**Quality Checklist**:\n- [ ] Content is accurate and complete\n- [ ] Structure is logical and navigable\n- [ ] Language is clear and accessible\n- [ ] Examples are relevant and helpful\n- [ ] Visual aids support understanding\n- [ ] Formatting is consistent\n- [ ] Cross-references work correctly\n- [ ] Technical terms are defined\n- [ ] Instructions are actionable\n- [ ] Troubleshooting covers common issues\n\n**Testing Methods**:\n1. **Usability Testing**:\n   - Have users follow documentation\n   - Observe where they get stuck\n   - Ask for feedback on clarity\n   - Test with diverse users\n\n2. **Technical Review**:\n   - Subject matter expert review\n   - Technical accuracy verification\n   - Completeness check\n   - Edge case coverage\n\n3. **Editorial Review**:\n   - Grammar and spelling check\n   - Style guide consistency\n   - Formatting verification\n   - Link testing\n\n**Output**: Refined documentation with quality assurance\n\n---\n\n## Step 6: Publishing and Maintenance\n\n**Purpose**: Make documentation available and keep it current.\n\n**Publishing Considerations**:\n1. **Format Selection**:\n   - Markdown (for version control and collaboration)\n   - HTML (for web publishing)\n   - PDF (for offline reading and printing)\n   - Interactive (for tutorials and guides)\n\n2. **Distribution**:\n   - Documentation sites (GitBook, ReadTheDocs)\n   - Wikis and knowledge bases\n   - Inline help and tooltips\n   - Print manuals\n\n3. **Version Control**:\n   - Track documentation versions\n   - Maintain change logs\n   - Archive outdated versions\n   - Tag documentation releases\n\n4. **Maintenance**:\n   - Review schedule (quarterly, per release)\n   - Update procedures\n   - Feedback collection\n   - Accuracy verification\n\n**Maintenance Tasks**:\n- Update for product changes\n- Revise based on user feedback\n- Add new FAQs and troubleshooting\n- Remove or archive outdated content\n- Update screenshots and examples\n\n**Output**: Published documentation with maintenance plan\n\n---\n\n## Output Format\n\n**For Technical Documentation**:\n- API references with parameters and responses\n- Architecture documentation with diagrams\n- Setup and installation guides\n- Configuration references\n- Troubleshooting guides\n\n**For User Documentation**:\n- Getting started guides\n- Feature explanations\n- How-to tutorials\n- FAQ sections\n- Best practices guides\n\n**For Process Documentation**:\n- Workflow descriptions\n- Procedure manuals\n- Training materials\n- Onboarding guides\n- Standard operating procedures\n\n---\n\n## Best Practices\n\n**Writing Quality**:\n✅ **Do**:\n- Write for your specific audience\n- Use simple, direct language\n- Provide examples and context\n- Include visual aids\n- Test with actual users\n- Update regularly\n\n❌ **Don't**:\n- Assume prior knowledge\n- Use jargon without explanation\n- Create walls of text\n- Skip visual formatting\n- Write for \"everyone\" (be specific)\n- Set and forget documentation\n\n**Structure Quality**:\n✅ **Do**:\n- Start with overview\n- Use progressive disclosure\n- Provide multiple navigation paths\n- Include cross-references\n- Add search keywords\n- Create scannable content\n\n❌ **Don't**:\n- Bury important information\n- Create deep hierarchies\n- Make users read everything\n- Use ambiguous headers\n- Ignore different learning styles\n- Write monolithic documents\n\n---\n\n## Common Mistakes to Avoid\n\n**Content Anti-Patterns**:\n1. **Information Dump**: Including everything without organization\n2. **Assumption Trap**: Assuming reader knows what you know\n3. **Tone Mismatch**: Too formal or too casual for audience\n4. **Update Neglect**: Letting documentation become outdated\n5. **Missing Context**: Focusing on what without explaining why\n\n**Structure Anti-Patterns**:\n1. **Poor Organization**: Illogical flow or grouping\n2. **Navigation Fail**: Difficult to find specific information\n3. **Inconsistency**: Different styles or formats in same doc\n4. **Gaps**: Missing steps or important information\n5. **Overcompleteness**: Including unnecessary detail\n\n---\n\n## Related Skills\n\n- **research-analysis**: For gathering information to document\n- **technical-writing**: For specialized technical documentation\n- **accessibility-review**: For ensuring documentation accessibility\n- **visual-design**: For creating effective diagrams and visual aids\n\n---\n\n## Documentation Tools\n\n**Authoring Tools**:\n- Markdown editors (Typora, VS Code, Obsidian)\n- Documentation generators (Jekyll, Hugo, Docusaurus)\n- Wiki platforms (Confluence, Notion, GitBook)\n- Content management systems\n\n**Collaboration Tools**:\n- Version control (Git)\n- Review tools (GitHub PRs, Google Docs comments)\n- Style guides (Google Developer Documentation Style Guide)\n- Editorial calendars\n\n**Publishing Platforms**:\n- Static site generators (MkDocs, Docusaurus)\n- Documentation hosting (GitBook, ReadTheDocs)\n- Knowledge bases (Confluence, Notion)\n- Versioned documentation (Git-backed)\n\n**Quality Tools**:\n- Grammar checkers (Grammarly, LanguageTool)\n- Link checkers (broken link detectors)\n- SEO tools (for public documentation)\n- Analytics (user engagement tracking)\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":37,"description":41,"gemini-parity":42,"last_reviewed":43,"prerequisites":44},"pm","common","active","1.0.3",{"type":28,"triggers":29},"implementation",[30,31,32,33,34,35,36],"write documentation","create guide","draft communication","write manual","create tutorial","documentation","technical writing",[38],{"type":39,"skill":40},"composes_with","team-builder","Creates clear, accessible documentation and communications for diverse audiences. Use when: writing guides, creating documentation, drafting communications, or synthesizing complex information for technical and non-technical audiences.\n","skip",1794096000000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883",".claude\u002Fskills\u002Fdocumentation-writing",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill documentation-writing",{"tool":59,"command":60},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill documentation-writing",{"tool":62,"command":63},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill documentation-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocumentation-writing\u002FSKILL.md",true,[],[68,76,81,86,91,96],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":75},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":75},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":87,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":75},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":92,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":75},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":75},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]