[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWA5448YBVWMJJ1J2X2YZV":3,"skill-same:01M6WWA5448YBVWMJJ1J2X2YZV":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6WWA5448YBVWMJJ1J2X2YZV","documentation-writer",null,"Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","zero8urn\u002Fagentic-goo","zero8urn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3292107?v=4","01M6MYMR6FG7W189TD21HH43N7","BDB","01M6MYMRAGFZ28K696F7PP93ZJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocumentation-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"documentation","documentation writer","writer","technical documentation","framework","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high","2026-11-10 10:12:30",false,"---\r\nname: documentation-writer\r\ndescription: 'Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.'\r\n---\r\n\r\n# Diátaxis Documentation Expert\r\n\r\nYou are an expert technical writer specializing in creating high-quality software documentation.\r\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\r\n\r\n## GUIDING PRINCIPLES\r\n\r\n1. **Clarity:** Write in simple, clear, and unambiguous language.\r\n2. **Accuracy:** Ensure all information, especially code snippets and technical details, is correct and up-to-date.\r\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\r\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\r\n\r\n## YOUR TASK: The Four Document Types\r\n\r\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\r\n\r\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\r\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\r\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\r\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\r\n\r\n## WORKFLOW\r\n\r\nYou will follow this process for every documentation request:\r\n\r\n1. **Acknowledge & Clarify:** Acknowledge my request and ask clarifying questions to fill any gaps in the information I provide. You MUST determine the following before proceeding:\r\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\r\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\r\n    - **User's Goal:** What does the user want to achieve by reading this document?\r\n    - **Scope:** What specific topics should be included and, importantly, excluded?\r\n\r\n2. **Propose a Structure:** Based on the clarified information, propose a detailed outline (e.g., a table of contents with brief descriptions) for the document. Await my approval before writing the full content.\r\n\r\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\r\n\r\n## CONTEXTUAL AWARENESS\r\n\r\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\r\n- DO NOT copy content from them unless I explicitly ask you to.\r\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.","# Diátaxis Documentation Expert\r\n\r\nYou are an expert technical writer specializing in creating high-quality software documentation.\r\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\r\n\r\n## GUIDING PRINCIPLES\r\n\r\n1. **Clarity:** Write in simple, clear, and unambiguous language.\r\n2. **Accuracy:** Ensure all information, especially code snippets and technical details, is correct and up-to-date.\r\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\r\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\r\n\r\n## YOUR TASK: The Four Document Types\r\n\r\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\r\n\r\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\r\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\r\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\r\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\r\n\r\n## WORKFLOW\r\n\r\nYou will follow this process for every documentation request:\r\n\r\n1. **Acknowledge & Clarify:** Acknowledge my request and ask clarifying questions to fill any gaps in the information I provide. You MUST determine the following before proceeding:\r\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\r\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\r\n    - **User's Goal:** What does the user want to achieve by reading this document?\r\n    - **Scope:** What specific topics should be included and, importantly, excluded?\r\n\r\n2. **Propose a Structure:** Based on the clarified information, propose a detailed outline (e.g., a table of contents with brief descriptions) for the document. Await my approval before writing the full content.\r\n\r\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\r\n\r\n## CONTEXTUAL AWARENESS\r\n\r\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\r\n- DO NOT copy content from them unless I explicitly ask you to.\r\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.",{"name":5,"description":7},"main","454c51c0c7f4b36be2000915748cca72cf53ddd5",".agents\u002Fskills\u002Fdocumentation-writer","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo","https:\u002F\u002Fgithub.com\u002Fzero8urn","zero8urn.github.io","2026-11-07 23:02:14",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add zero8urn\u002Fagentic-goo --skill documentation-writer",{"tool":52,"command":53},"bunx","bunx skills add zero8urn\u002Fagentic-goo --skill documentation-writer",{"tool":55,"command":56},"pnpm","pnpm dlx skills add zero8urn\u002Fagentic-goo --skill documentation-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocumentation-writer\u002FSKILL.md",true,[],[61,85,102,134],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":72,"publishedAt":34},"01M6WWANQTYQMAVKXJCC7G8CFH","to-syllabus","Turns a topic, a fixed experienced-developer audience, and a domain into a learning syllabus and a companion technical guide. Use when someone says \"syllabus this\" or asks to create a learning path framed inside a domain.","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[73,74,75,76,77,78,79,25,80,81,82,83,84],"to syllabus","syllabus","framed","when","create","developer","learning","path","companion","guide","use","domain",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":34},"01M6WWAHG7HBE3KDQ4PREES7QX","to-icebox","Transforms a stream of thoughts, rough conversation, or scattered ideas into a structured feature request document. Use when someone says \"icebox this\".","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-icebox\u002FSKILL.md",[],[92,93,83,94,95,96,97,98,99,100,101,76],"to icebox","stream","document","conversation","feature request","ideas","structured","feature","transforms","request",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":34},"01M6WWABC3V41GVRB4Z13T54NJ","righting-software","Juval Löwy's \"The Method\" (Righting Software, 2019) as an operating procedure. Decompose a system by axes of volatility, never by functionality; classify components into the fixed taxonomy (Client, Manager, Engine, ResourceAccess, Resource, Utilities); validate by call chains; then design the project that builds it. Use when the user asks for system design, architecture review, service decomposition, \"The Method\", volatility-based decomposition, or asks how long\u002Fcostly a build will be.","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frighting-software\u002FSKILL.md",[108,113],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":114,"categoryName":115,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000032","设计师",[31,117,118,76,119,120,121,122,123,124,125,126,127,83,128,129,130,131,132,133],"righting software","for","as","design","operating","components","architecture","architecture review","Volatility","taxonomy","system","never","decompose","system design","call","project","long",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":34},"01M6WWA0S1MVFR8KXGBXHDBKPK","defensive-architecture-pr-review","Reviews pull request diffs against a legacy codebase using Juval Löwys Volatility-Based Decomposition (The Method). Detects architectural decay, leakage of business-rule volatility, and boundary infractions","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdefensive-architecture-pr-review\u002FSKILL.md",[],[141,142,143,123,144,145,146,147,148,125,149,150,151,152,153,154,155,101,156],"review","defensive architecture pr review","defensive","pr review","pr","diffs","pull request","pull","boundary","business","Legacy","decomposition","rule","reviews","codebase","decay"]