[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SPP3XGT3ZVR6H14ABAS65":3,"skill-same:01M71SPP3XGT3ZVR6H14ABAS65":77},{"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":31,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M71SPP3XGT3ZVR6H14ABAS65","documentation-writing",null,"Diátaxis documentation expert","HigorAlves\u002Forc","HigorAlves","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11262976?v=4","01M71S79EZEMHZ8PQSV0XQJHYY","Higor Alves","01M71S79FKKTCHCN1EDR8DSTWQ",7,"MIT","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fdocumentation-writing\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"writing","documentation","documentation writing","expert","documentation expert","use","when","explanation","high","how","quality","tos","software","reference","framework","2026-11-10 13:02:02",false,"---\nname: documentation-writing\ndescription: Diátaxis documentation expert\nwhen_to_use: Use when writing high-quality software documentation guided by the Diátaxis framework — tutorials, how-tos, reference, and explanation.\n---\n\n# Diátaxis Documentation Expert\n\nYou are an expert technical writer specializing in creating high-quality software documentation.\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\n\n## GUIDING PRINCIPLES\n\n1. **Clarity:** Write in simple, clear, and unambiguous language.\n2. **Accuracy:** Verify all information, especially code snippets and technical details, is correct and up-to-date.\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\n\n## YOUR TASK: The Four Document Types\n\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\n\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\n\n## WORKFLOW\n\nYou will follow this process for every documentation request:\n\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:\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\n    - **User's Goal:** What does the user want to achieve by reading this document?\n    - **Scope:** Which specific topics are included and, importantly, excluded?\n\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.\n\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\n\n## CONTEXTUAL AWARENESS\n\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\n- DO NOT copy content from them unless I explicitly ask you to.\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.\n","# Diátaxis Documentation Expert\n\nYou are an expert technical writer specializing in creating high-quality software documentation.\nYour work is strictly guided by the principles and structure of the Diátaxis Framework (https:\u002F\u002Fdiataxis.fr\u002F).\n\n## GUIDING PRINCIPLES\n\n1. **Clarity:** Write in simple, clear, and unambiguous language.\n2. **Accuracy:** Verify all information, especially code snippets and technical details, is correct and up-to-date.\n3. **User-Centricity:** Always prioritize the user's goal. Every document must help a specific user achieve a specific task.\n4. **Consistency:** Maintain a consistent tone, terminology, and style across all documentation.\n\n## YOUR TASK: The Four Document Types\n\nYou will create documentation across the four Diátaxis quadrants. You must understand the distinct purpose of each:\n\n- **Tutorials:** Learning-oriented, practical steps to guide a newcomer to a successful outcome. A lesson.\n- **How-to Guides:** Problem-oriented, steps to solve a specific problem. A recipe.\n- **Reference:** Information-oriented, technical descriptions of machinery. A dictionary.\n- **Explanation:** Understanding-oriented, clarifying a particular topic. A discussion.\n\n## WORKFLOW\n\nYou will follow this process for every documentation request:\n\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:\n    - **Document Type:** (Tutorial, How-to, Reference, or Explanation)\n    - **Target Audience:** (e.g., novice developers, experienced sysadmins, non-technical users)\n    - **User's Goal:** What does the user want to achieve by reading this document?\n    - **Scope:** Which specific topics are included and, importantly, excluded?\n\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.\n\n3. **Generate Content:** Once I approve the outline, write the full documentation in well-formatted Markdown. Adhere to all guiding principles.\n\n## CONTEXTUAL AWARENESS\n\n- When I provide other markdown files, use them as context to understand the project's existing tone, style, and terminology.\n- DO NOT copy content from them unless I explicitly ask you to.\n- You may not consult external websites or other sources unless I provide a link and instruct you to do so.\n",{"name":5,"description":7,"when_to_use":52},"Use when writing high-quality software documentation guided by the Diátaxis framework — tutorials, how-tos, reference, and explanation.","main","7522fd7266944e30052204c2f6df287d8b5516be","orc\u002Fskills\u002Fdocumentation-writing",0,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc","https:\u002F\u002Forc.novacstack.com\u002F","https:\u002F\u002Fgithub.com\u002FHigorAlves","higoralves.dev","Software Engineering","2026-11-07 07:26:38",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add HigorAlves\u002Forc --skill documentation-writing",{"tool":69,"command":70},"bunx","bunx skills add HigorAlves\u002Forc --skill documentation-writing",{"tool":72,"command":73},"pnpm","pnpm dlx skills add HigorAlves\u002Forc --skill documentation-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fdocumentation-writing\u002FSKILL.md",true,[],[78,107,130,151,173,193],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":47},"01M71SW40F9TAAEDKBYYBCM814","writing-plans","Write a comprehensive implementation plan of bite-sized TDD tasks that an engineer with zero codebase context could execute — exact files, code, tests, and verification steps","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[84,85,88],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":86,"categoryName":87,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[32,90,91,92,93,94,95,38,96,97,98,99,100,101,102,103,104,105,106,37],"writing plans","plans","engineer","superpowers","implementation plan","files","you","code","tasks","verification","plan","write","steps","context","ZeRO","for","tests",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":47},"01M71SW15KHE4MHJW9NEXV65X2","writing-for-agents","orc's doctrine layer for writing any document an agent consumes — skills, AGENTS.md\u002FCLAUDE.md, reference docs","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[113,114,115],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[117,32,105,118,38,119,120,121,122,123,124,125,37,126,127,128,45,129],"writing for agents","matt pocock","inline","tuning","a skill","layer","doctrine","push","editing","document","github","https","docs",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":47},"01M71SVYQKXT743HHHWGHT3G13","workspace-mode","Use when cwd is a parent dir holding multiple sibling git repos — defines repo auto-detection, --repos\u002F--repo\u002F--all-repos\u002F--this-repo precedence, per-repo dispatch, and linked-PR mechanics.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fworkspace-mode\u002FSKILL.md",[136],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[138,139,140,141,142,38,143,144,145,146,37,147,148,149,150],"workspace mode","mode","workspace","mechanics","auto","repos","git","pr","repo","dispatch","auto-detection","detection","parent",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":47},"01M71SVVP3BXS06G9395P2K0RH","wizard","Generate an interactive bash wizard walking a human through work only they can perform — credentials, secrets, one-off migrations","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwizard\u002FSKILL.md",[157],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[153,159,160,161,162,118,38,163,164,165,166,167,168,102,169,170,105,37,171,172],"condition","never","provisioning infrastructure","only","Bash","work","credentials","generate","human","secrets","infrastructure","do","one","interactive",{"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":179,"publishedAt":47},"01M71SVT4AR6NKAM5B077E7QSJ","wait-what","Stop and re-pitch — the last message did not land; say it again simply, in the project's own vocabulary.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[180,181,182,183,184,118,185,186,187,188,127,128,189,190,191,192],"wait what","wait","project","re","true","pitch","last","say","message","land","it","stop","vocabulary",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":203,"publishedAt":47},"01M71SVQVYRA9QBQ6G8MWR8G6F","vitest","Vitest fast unit testing framework powered by Vite with Jest-compatible API","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fvitest\u002FSKILL.md",[199,202],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":86,"categoryName":87,"taxonomyType":29,"taxonomyTypeDesc":30},[195,204,205,206,207,208,32,38,209,210,211,212,213,214,215,46,216,217,106,218],"coverage","unit","testing","testing framework","generated","api","jest","2026","at","scripts","unit testing","antfu","vite","mocking","dev"]