[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792ZMCF8S5GJMNKJ984ARDF":3,"skill-same:01M792ZMCF8S5GJMNKJ984ARDF":62},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M792ZMCF8S5GJMNKJ984ARDF","technical-docs",null,"Write API references, user guides, setup manuals and architecture docs with consistent terminology. Use when writing developer documentation, API guides, or tutorials.","poorvith-mp\u002Fskills-writing","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792XRHPBHAWHV437S3556E5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: technical-docs\nlast_reviewed: 2026-09-06\ngroup: Documents\ndescription: >-\n  Write API references, user guides, setup manuals and architecture docs with consistent\n  terminology. Use when writing developer documentation, API guides, or tutorials.\n---\n\n# Technical Docs\n\nTechnical documentation serves four distinct modes (the Divio framework: Tutorials, How-To Guides, Reference, and Explanation). Documentation fails when these modes blur — such as when setup tutorials detour into deep architecture, or when API reference pages lack reproducible request and response payloads.\n\n## Process\n1. Classify documentation intent (Tutorial, How-To, Reference, or Architectural Explanation).\n2. Establish reader prerequisites, environment requirements, and required tokens\u002Fkeys.\n3. Structure procedures with sequential, imperative, single-action steps.\n4. Provide complete, runnable code examples with expected output.\n5. Standardize domain terminology in a structured glossary.\n\n## Output Format\n## Technical Documentation: [Topic]\n### Overview\n[One-paragraph plain English summary of what this component accomplishes and why it exists]\n### Prerequisites\n- Node.js >= 20.0.0 or Python >= 3.11\n- Environment variable `API_KEY` configured in `.env`\n### Quickstart \u002F How-It-Works\n1. **Step 1: Install Dependencies**:\n   ```bash\n   npm install @company\u002Fsdk\n   ```\n2. **Step 2: Initialize Client**:\n   ```typescript\n   import { Client } from \"@company\u002Fsdk\";\n   const client = new Client({ apiKey: process.env.API_KEY });\n   ```\n3. **Step 3: Execute Operation**:\n   ```typescript\n   const res = await client.resources.get(\"id_123\");\n   console.log(res.data);\n   ```\n### API Reference \u002F Schema\n- **Endpoint**: `POST \u002Fapi\u002Fv1\u002Fresources`\n- **Headers**: `Authorization: Bearer \u003Ctoken>`, `Content-Type: application\u002Fjson`\n- **Request Body**:\n  ```json\n  { \"name\": \"sample\", \"tier\": \"standard\" }\n  ```\n- **Response `201 Created`**:\n  ```json\n  { \"id\": \"res_987\", \"status\": \"active\" }\n  ```\n### Glossary & Terminology\n| Term | Definition | Context \u002F Scope |\n|---|---|---|\n| Idempotency Key | Unique header to prevent duplicate charge execution | All mutation endpoints |\n| Tenant ID | UUID representing the client organization partition | Multi-tenant auth token |\n## Audience-First Writing\nBefore writing: Who is reading this and what do they already know?\n- **Developer docs**: Technical terms OK, code examples, values precision\n- **End-user guides**: Minimal technical knowledge assumed, task-oriented, screenshots\n- **Executive summaries**: No technical detail, focus on business outcomes\n## Documentation Types (Divio System)\n- **Tutorials**: Learning-oriented, hold reader's hand to first success\n- **How-to Guides**: Goal-oriented, step-by-step for known goals\n- **Reference**: Information-oriented, complete and accurate, dense\n- **Explanations**: Understanding-oriented, background and context\n## Style Rules\nActive voice, one action per step, consistent terminology, test your own instructions.\n\n## Critical rules\n1. Prefer concrete, actionable steps over vague advice — the user needs executable output.\n2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.\n3. Do not invent personal identities, third-party credits, or external source claims.\n\n## Additional notes (merged)\n- Write README files that make developers want to use a project within the first 30 seconds\n- Create API reference docs that are complete, accurate, and include working code examples\n- Build step-by-step tutorials that guide beginners from zero to working in under 15 minutes\n- Write conceptual guides that explain *why*, not just *how*\n- Set up documentation pipelines using Docusaurus, MkDocs, Sphinx, or VitePress\n- Automate API reference generation from OpenAPI\u002FSwagger specs, JSDoc, or docstrings\n- Integrate docs builds into CI\u002FCD so outdated docs fail the build\n- Maintain versioned documentation alongside versioned software releases\n- Audit existing docs for accuracy, gaps, and stale content\n- Define documentation standards and templates for engineering teams\n- Create contribution guides that make it easy for engineers to write good docs\n- Measure documentation effectiveness with analytics, support ticket correlation, and user feedback\n- **Code examples must run** — every snippet is tested before it ships\n- **No assumption of context** — every doc stands alone or links to prerequisite context explicitly\n- **Keep voice consistent** — second person (\"you\"), present tense, active voice throughout\n- **Version everything** — docs must match the software version they describe\n- **One concept per section** — do not combine installation, configuration, and usage into one wall of text\n- Lead with the result the user asked for.\n- Use clear headings and bullet lists where helpful.\n- Call out assumptions and open questions at the end.\n- Stay specific to the Technical Writer workflow; avoid generic filler.\n\n## Verification & Quality Checklist\n\n- [ ] Every factual claim and statistic traced to a citable source.\n- [ ] Reading level and terminology matched to the stated audience.\n- [ ] Length and formatting fit the destination channel's limits.\n- [ ] One clear call to action, placed where the reader will still be reading.\n\n## Anti-Patterns & Constraints\n\n- NEVER invent statistics, quotes, or sources.\n- NEVER present an unverified figure as sourced.\n- NEVER bury the central point below preamble the reader will not reach.\n","# Technical Docs\n\nTechnical documentation serves four distinct modes (the Divio framework: Tutorials, How-To Guides, Reference, and Explanation). Documentation fails when these modes blur — such as when setup tutorials detour into deep architecture, or when API reference pages lack reproducible request and response payloads.\n\n## Process\n1. Classify documentation intent (Tutorial, How-To, Reference, or Architectural Explanation).\n2. Establish reader prerequisites, environment requirements, and required tokens\u002Fkeys.\n3. Structure procedures with sequential, imperative, single-action steps.\n4. Provide complete, runnable code examples with expected output.\n5. Standardize domain terminology in a structured glossary.\n\n## Output Format\n## Technical Documentation: [Topic]\n### Overview\n[One-paragraph plain English summary of what this component accomplishes and why it exists]\n### Prerequisites\n- Node.js >= 20.0.0 or Python >= 3.11\n- Environment variable `API_KEY` configured in `.env`\n### Quickstart \u002F How-It-Works\n1. **Step 1: Install Dependencies**:\n   ```bash\n   npm install @company\u002Fsdk\n   ```\n2. **Step 2: Initialize Client**:\n   ```typescript\n   import { Client } from \"@company\u002Fsdk\";\n   const client = new Client({ apiKey: process.env.API_KEY });\n   ```\n3. **Step 3: Execute Operation**:\n   ```typescript\n   const res = await client.resources.get(\"id_123\");\n   console.log(res.data);\n   ```\n### API Reference \u002F Schema\n- **Endpoint**: `POST \u002Fapi\u002Fv1\u002Fresources`\n- **Headers**: `Authorization: Bearer \u003Ctoken>`, `Content-Type: application\u002Fjson`\n- **Request Body**:\n  ```json\n  { \"name\": \"sample\", \"tier\": \"standard\" }\n  ```\n- **Response `201 Created`**:\n  ```json\n  { \"id\": \"res_987\", \"status\": \"active\" }\n  ```\n### Glossary & Terminology\n| Term | Definition | Context \u002F Scope |\n|---|---|---|\n| Idempotency Key | Unique header to prevent duplicate charge execution | All mutation endpoints |\n| Tenant ID | UUID representing the client organization partition | Multi-tenant auth token |\n## Audience-First Writing\nBefore writing: Who is reading this and what do they already know?\n- **Developer docs**: Technical terms OK, code examples, values precision\n- **End-user guides**: Minimal technical knowledge assumed, task-oriented, screenshots\n- **Executive summaries**: No technical detail, focus on business outcomes\n## Documentation Types (Divio System)\n- **Tutorials**: Learning-oriented, hold reader's hand to first success\n- **How-to Guides**: Goal-oriented, step-by-step for known goals\n- **Reference**: Information-oriented, complete and accurate, dense\n- **Explanations**: Understanding-oriented, background and context\n## Style Rules\nActive voice, one action per step, consistent terminology, test your own instructions.\n\n## Critical rules\n1. Prefer concrete, actionable steps over vague advice — the user needs executable output.\n2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.\n3. Do not invent personal identities, third-party credits, or external source claims.\n\n## Additional notes (merged)\n- Write README files that make developers want to use a project within the first 30 seconds\n- Create API reference docs that are complete, accurate, and include working code examples\n- Build step-by-step tutorials that guide beginners from zero to working in under 15 minutes\n- Write conceptual guides that explain *why*, not just *how*\n- Set up documentation pipelines using Docusaurus, MkDocs, Sphinx, or VitePress\n- Automate API reference generation from OpenAPI\u002FSwagger specs, JSDoc, or docstrings\n- Integrate docs builds into CI\u002FCD so outdated docs fail the build\n- Maintain versioned documentation alongside versioned software releases\n- Audit existing docs for accuracy, gaps, and stale content\n- Define documentation standards and templates for engineering teams\n- Create contribution guides that make it easy for engineers to write good docs\n- Measure documentation effectiveness with analytics, support ticket correlation, and user feedback\n- **Code examples must run** — every snippet is tested before it ships\n- **No assumption of context** — every doc stands alone or links to prerequisite context explicitly\n- **Keep voice consistent** — second person (\"you\"), present tense, active voice throughout\n- **Version everything** — docs must match the software version they describe\n- **One concept per section** — do not combine installation, configuration, and usage into one wall of text\n- Lead with the result the user asked for.\n- Use clear headings and bullet lists where helpful.\n- Call out assumptions and open questions at the end.\n- Stay specific to the Technical Writer workflow; avoid generic filler.\n\n## Verification & Quality Checklist\n\n- [ ] Every factual claim and statistic traced to a citable source.\n- [ ] Reading level and terminology matched to the stated audience.\n- [ ] Length and formatting fit the destination channel's limits.\n- [ ] One clear call to action, placed where the reader will still be reading.\n\n## Anti-Patterns & Constraints\n\n- NEVER invent statistics, quotes, or sources.\n- NEVER present an unverified figure as sourced.\n- NEVER bury the central point below preamble the reader will not reach.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Documents",1788652800000,"main","036f70c9d6ddd7a7e8b6691aa3ae0279b0649433","skills\u002Ftechnical-docs",2,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:55",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add poorvith-mp\u002Fskills-writing --skill technical-docs",{"tool":42,"command":43},"bunx","bunx skills add poorvith-mp\u002Fskills-writing --skill technical-docs",{"tool":45,"command":46},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-writing --skill technical-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Frouting.yaml","REFERENCE","参考文档",1026,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002Fevals\u002Frouting.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"technical-docs.skill","OTHER","其他",3541,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002Ftechnical-docs.skill",[63,69,76,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79309BVEDZ4AB80FM7N45XV","writing-taste","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-taste\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79303W7E8AD1M3EC1T9TXEE","translation","Translate while preserving register, idiom and domain terms, flagging what doesn't carry across. Use when translating text across languages preserving nuance, tone, and idioms.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftranslation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79300EK34V2MZRPVMV3PP41","thread-to-blog-converter","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-blog-converter\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M792ZTRHZGD0YY4AE5ARWZC5","thread-to-article","Expand an X or LinkedIn thread into a structured article with added context, headings and links. Use when expanding social threads into long-form articles, or vice versa.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M792ZRYX1PPQ737CGQB28T1E","technical-writer","Moved to technical-docs in skills-writing. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writer\u002FSKILL.md",[],[],{"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":103,"publishedAt":19},"01M792ZG14PGB50E2P8VGQ8RC3","talk-writing","Write a conference talk or keynote: through-line, one idea per slide, opening hook and honest timing. Use when scripting keynote talks, conference presentations, or lightning talks.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftalk-writing\u002FSKILL.md",[],[]]