搜索
搜索结果
49 results for "documentation writer"
documentation-writer
Diátaxis 文档专家。一位专业的技术写作者，专注于根据 Diátaxis 技术文档编写框架的原则和结构，创建高质量的软件文档。
github
update-docs
Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.
neolabhq
document-writer
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.
onmax
brand-guidelines
Create a comprehensive brand standards document — covering logo usage, color, typography, voice, messaging, and application rules. Use when the user says "brand guidelines", "brand standards", "brand book", "style guide", "brand guide", "brand manual", "brand rules", "brand documentation", "brand toolkit", "onboarding designers or copywriters", "need a document for the team", "brand consistency across teams", or wants to codify all brand decisions into a reusable reference document.
arnabbagxd
technical-writer
Write comprehensive technical documentation including user guides, how-to articles, system architecture docs, onboarding materials, and knowledge base articles. Creates clear, structured documentation for technical and non-technical audiences. Use when users need technical writing, documentation, tutorials, or knowledge base content.
onewave-ai
prd-writer
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
pmpromptwriting-web-documentation
Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.
onmax
code-documenter
生成、格式化和验证技术文档——包括文档字符串、OpenAPI/Swagger 规范、JSDoc 注释、文档门户和用户指南。在需要为函数或类添加文档字符串、创建 API 文档、构建文档站点或编写教程和用户指南时使用。适用于 OpenAPI/Swagger 规范、JSDoc、文档门户、入门指南。
jeffallan
docs-write
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
metabase
write-feature-docs
根据新 Warp 功能的 PRODUCT.md 和/或 TECH.md 规范，起草完整的文档页面。当工程师编写了规范并需要为 warpdotdev/docs 仓库生成初版 MDX 草稿时使用。也适用于没有规范的功能，通过先研究代码库来处理。每当工程师提到为功能编写文档、起草文档页面、创建功能文档、启动工程文档工作流或将规范转换为文档时，调用此技能。适用于 warp-internal 或 warp-server。
warpdotdev
documentation
Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
mcollina
dart-write-documentation
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
dart-lang
doc-coauthoring
引导用户通过结构化工作流程共同撰写文档。当用户想要编写文档、提案、技术规范、决策文档或类似结构化内容时使用。此工作流程帮助用户高效传递上下文、通过迭代完善内容，并验证文档对读者有效。当用户提到编写文档、创建提案、起草规范或类似文档任务时触发。
anthropics
writing-docs
Remotion 文档编写与修改指南。适用于新增文档页面、编辑 packages/docs 目录下的 MDX 文件或撰写文档内容时。
remotion-dev
technical-writing
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
vercel
make-documentation
Use when writing READMEs, architecture, changelogs, release notes, runbooks, notebook docs, install docs, or security articles; produces docs. Do not trigger for API docs, AGENTS.md, or diagrams.
callicrate
dart-write-documentation
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
flutter
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
getsentrywrite-pr-description
Writes the body of a pull request - the summary, the repository template sections, and reviewer guidance such as a recommended reading order and focus areas. Use whenever drafting or revising a PR description, filling in a repository's PR template, refreshing a description that no longer matches the branch, or preparing a branch for review. Use it even when the user only says "open a PR", "put this up for review", or "write this up" without naming the description.
warpdotdev
typescript-docs
Generates comprehensive TypeScript documentation using JSDoc, TypeDoc, and multi-layered documentation patterns for different audiences. Use when creating API documentation, architectural decision records (ADRs), code examples, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.
giuseppe-trisciuoglio
k6-docs
Write or review k6 documentation across the three k6 repositories - k6-DefinitelyTyped (TypeScript types), k6-docs (user documentation), and k6 (release notes / changelog). Applies k6 doc style conventions, generates TypeScript type definitions, drafts release notes, and validates examples by running them against k6@master. Use when working on k6 documentation, the k6 changelog, the k6 release notes, k6 API reference, k6 TypeScript types, load testing docs, or when the user asks to write, edit, or review anything in the k6, k6-docs, or k6-DefinitelyTyped repos - even if they don't explicitly say "documentation".
grafanaoo-component-documentation
Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
github
technical-writing
Expert technical writing guidelines for creating clear, in-depth developer tutorials and documentation with practical, implementable knowledge
mindrally
minimax-docx
使用 OpenXML SDK (.NET) 进行专业的 DOCX 文档创建、编辑和格式化。提供三条流水线：(A) 从头创建新文档，(B) 填充/编辑现有文档内容，(C) 应用模板格式并执行 XSD 验证关卡。当用户想要生成、修改或格式化 Word 文档时，必须使用此技能——包括当用户说“写一份报告”、“起草一份提案”、“制作一份合同”、“填写此表格”、“重新格式化以匹配此模板”或任何最终输出为 .docx 文件的任务。即使用户没有明确提到“docx”，如果任务暗示需要可打印/正式文档，也应使用此技能。
minimax-ai