[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-tech-writer-ai-pipeline-zh":3,"seo:pack:tech-writer-ai-pipeline:zh":95},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":94},"tech-writer-ai-pipeline","📝","#0EA5E9","new","本周新建","技术写作者 AI 流水线","9 件套，给写 API 文档 \u002F tutorial \u002F 代码示例的技术写作者和 DevRel：覆盖现状审计、AI 一稿、从 spec 生代码、风格强制、多语言 reference 渲染、把文档喂给 AI 编辑器全链路。",[16,28,38,45,55,63,70,77,84],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3266,"2ef66824-9a18-47bc-8244-534359920c53","skill-seekers-convert-docs-repos-pdfs-to-skills","Skill Seekers — Convert Docs\u002FRepos\u002FPDFs to Skills","Convert docs sites, GitHub repos, and PDFs into Claude skills, with conflict detection and presets so teams can standardize reusable skills fast.","Skill Factory",40,0,"en","script","Script",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":34,"view_count":35,"vote_count":24,"lang_type":25,"type":36,"type_label":37},4458,"8550fc7e-9375-4fbf-842b-f69ca48d598a","claude-code-agent-technical-writer-8550fc7e","Claude Code Agent: Technical Writer","Use this agent when you need to create, improve, or maintain technical documentation including API references, user guides, SDK documentation, and getting-started guides....","TokRepo精选",28,"skill","Skill",{"id":39,"uuid":40,"slug":41,"title":42,"description":43,"author_name":34,"view_count":44,"vote_count":24,"lang_type":25,"type":36,"type_label":37},4281,"41c216a4-8ca0-4a10-819b-0da7e0497e69","claude-code-agent-api-documenter-41c216a4","Claude Code Agent: Api Documenter","Use this agent when creating or improving API documentation, writing OpenAPI specifications, building interactive documentation portals, or generating code examples for APIs. Speci",19,{"id":46,"uuid":47,"slug":48,"title":49,"description":50,"author_name":51,"view_count":52,"vote_count":24,"lang_type":25,"type":53,"type_label":54},2668,"a951911e-4838-11f1-9bc6-00163e2b0d79","openapi-generator-generate-client-sdks-server-stubs-api-a951911e","OpenAPI Generator — Generate Client SDKs and Server Stubs from API Specs","A code generation tool that produces client libraries, server stubs, API documentation, and configuration from OpenAPI 2.0\u002F3.x specifications in over 50 languages.","AI Open Source",92,"config","Config",{"id":56,"uuid":57,"slug":58,"title":59,"description":60,"author_name":61,"view_count":62,"vote_count":24,"lang_type":25,"type":36,"type_label":37},4185,"acc51033-52b5-11f1-9bc6-00163e2b0d79","scalar-open-source-api-platform-beautiful-references-acc51033","Scalar — Open-Source API Platform with Beautiful References","Scalar is an open-source API platform that provides a modern REST API client, beautiful auto-generated API references, and first-class OpenAPI and Swagger support for developer teams.","Script Depot",61,{"id":64,"uuid":65,"slug":66,"title":67,"description":68,"author_name":51,"view_count":69,"vote_count":24,"lang_type":25,"type":36,"type_label":37},1865,"13b1fee7-3cf7-11f1-9bc6-00163e2b0d79","vale-syntax-aware-prose-linter-technical-writing-13b1fee7","Vale — Syntax-Aware Prose Linter for Technical Writing","Vale is a command-line tool that enforces writing style guides on your prose, supporting custom rules for documentation teams to ensure consistent terminology, tone, and formatting across Markdown, AsciiDoc, and more.",73,{"id":71,"uuid":72,"slug":73,"title":74,"description":75,"author_name":61,"view_count":76,"vote_count":24,"lang_type":25,"type":36,"type_label":37},751,"2f24f820-a8de-430f-87d7-945401c6a0e3","markdownlint-lint-markdown-ai-content-quality-2f24f820","Markdownlint — Lint Markdown for AI Content Quality","Node.js markdown linter with 50+ rules. Ensure consistent formatting in CLAUDE.md, .cursorrules, README files, and AI-generated documentation across your project.",180,{"id":78,"uuid":79,"slug":80,"title":81,"description":82,"author_name":51,"view_count":83,"vote_count":24,"lang_type":25,"type":36,"type_label":37},2563,"b51f8b6b-46eb-11f1-9bc6-00163e2b0d79","starlight-documentation-framework-astro-b51f8b6b","Starlight — Documentation Framework for Astro","Starlight is a full-featured documentation framework built on Astro that generates fast, accessible, and SEO-friendly docs sites from Markdown and MDX with built-in navigation, search, and internationalization.",174,{"id":85,"uuid":86,"slug":87,"title":88,"description":89,"author_name":90,"view_count":91,"vote_count":24,"lang_type":25,"type":92,"type_label":93},229,"80630bbc-db0f-4254-bed5-8e5b639e5a34","context7-up-date-docs-mcp-ai-editors-80630bbc","Context7 — Up-to-Date Docs MCP for AI Editors","MCP server that provides AI code editors with up-to-date library documentation. Eliminates hallucinations from outdated training data. Supports 1000+ libraries. 51K+ stars.","MCP Hub",206,"mcp","MCP","tokrepo install pack\u002Ftech-writer-ai-pipeline",{"pageType":96,"pageKey":8,"locale":97,"title":98,"metaDescription":99,"h1":100,"tldr":101,"bodyMarkdown":102,"faq":103,"schema":119,"internalLinks":124,"citations":137,"wordCount":150,"generatedAt":151},"pack","zh","技术写作者 AI 流水线 — 9 件套，API 文档 \u002F Tutorial \u002F 代码示例全链路","Skill Seekers \u002F Technical Writer agent \u002F Api Documenter \u002F OpenAPI Generator \u002F Scalar \u002F Vale \u002F Markdownlint \u002F Starlight \u002F Context7 — 技术写作者和 DevRel 一个下午能装完的 AI 流水线。审计、起稿、生代码、查风格、渲染、发布。","技术写作者 AI 流水线 — 从审计到发布的 9 件套","9 个工具按安装顺序：把现有文档转成 agent 能读的 skill，用 technical-writer agent 起一稿，用 OpenAPI spec 生 reference + SDK 代码示例，把样式\u002FMarkdown lint 接进 CI，搭一个像样的文档站，最后把整站喂给 AI 编辑器。是流水线，不是购物清单。","## 这个 pack 包含什么\n\n你是技术写作者或 DevRel。日常输出是 API reference、上手指南、tutorial、三种语言的代码示例、一份没人读的 style guide。AI 终于能帮你了 — 但市场上 700+ 工具大部分是给营销文案用的通用 chat 工具。\n\n这个 pack 是**专为技术写作工作流挑的 9 件套**：审计现有内容、起 AI 一稿、从 OpenAPI spec 生代码示例、强制 prose + Markdown 风格、渲染不像 2014 年的 API reference、最后让你的文档能被用户在 Cursor \u002F Claude Code 里直接当 context 拉走。\n\n全部开源或有真正能用的免费档。没有一个是「用 AI 写博客」那种通用工具。**安装顺序很关键** — 每一步喂给下一步。\n\n## 推荐安装顺序（审计 → 一稿 → 风格 → 站点 → 发布）\n\n1. **Skill Seekers — Convert Docs\u002FRepos\u002FPDFs to Skills**（审计）— 从这里开始。把你现有的文档、代码库、内部 PDF 喂进去，输出结构化 skill 给下游 agent 加载。这是一次性的「我们已经有什么」审计，agent 在写任何一段之前先有上下文。\n2. **Claude Code Agent: Technical Writer**（一稿）— Anthropic 风格的 subagent，专门为 API reference \u002F 用户指南 \u002F SDK 文档 \u002F 上手流程调过。扔进 `.claude\u002Fagents\u002F`，指一个主题，得到一份**你只需要编辑而不需要重写**的初稿。\n3. **Claude Code Agent: Api Documenter**（API 专用一稿）— #2 的姊妹 agent，专攻 OpenAPI \u002F endpoint 形态。喂一份 spec 或路由处理器，得到带正确动词、状态码、示例 payload 的 reference 文本。\n4. **OpenAPI Generator — 从 spec 生 Client SDK + Server Stub**（代码示例）— 从一份 OpenAPI YAML 在 50+ 种语言里生可用 SDK 代码。这是你停止在每个页面手写 `curl` \u002F `Python` \u002F `Node` \u002F `Go` 示例的方式。spec 改了？重跑一遍，示例自动新鲜。\n5. **Scalar — 开源 API 平台 + 漂亮的 Reference 渲染**（reference 渲染）— 把 OpenAPI 渲染成不像 2014 年 Swagger UI 的现代 reference 页面。可自托管、可嵌入、可换主题。用户从 Google 搜进来落地的页面就是它。\n6. **Vale — 面向技术写作的语法感知散文 lint**（风格强制）— 杀手锏：lint Markdown \u002F RST \u002F AsciiDoc 对照你的 style guide，**不会误伤代码块**。内置 Microsoft、Google、Write the Docs 三套 style 包。CI 友好。自动抓 `utilize` → `use`、`e.g.,` → `for example`。\n7. **Markdownlint — Lint Markdown for AI Content Quality**（格式强制）— 机械的 Markdown 检查（标题层级、行尾空格、列表一致性、链接语法）。配合 Vale：Vale 管 prose 风格，Markdownlint 管文件结构。两个一起在 pre-commit 跑。\n8. **Starlight — Astro 文档框架**（文档站）— 文档站本体。Astro 原生、快、深色模式默认、移动端 sidebar 能用。和前面 agent + linter 输出的 Markdown 无缝对接。别陷入静态站选型大战 — 新站 Starlight 是无聊但正确的答案。\n9. **Context7 — 给 AI 编辑器的最新文档 MCP**（发布）— 没人讲的发布步骤。文档上线后，你希望用户在 Cursor \u002F Claude Code \u002F Codex 里写代码时，AI 能拉到你的最新文档作为 context（而不是幻觉你的 API）。Context7 给你的文档建索引、通过 MCP 提供。闭环：AI 帮你写文档，AI 再帮你的用户用文档。\n\n## 它们怎么协同\n\n```\n现有文档 \u002F 代码库\n   │\nSkill Seekers (#1) ── 审计，输出 agent 能加载的 skill\n   │\n   ├─→ Technical Writer agent (#2) ── 散文初稿\n   │       │\n   │       └─→ Markdown 文件\n   │\n   └─→ Api Documenter agent (#3) ←── OpenAPI spec\n           │\n           ├─→ OpenAPI Generator (#4) ── 代码示例（Python\u002FGo\u002FNode\u002Fcurl）\n           └─→ Scalar (#5) ── 渲染的 API reference\n                   │\nVale (#6) + Markdownlint (#7)\n   │\n   └─ 每次 commit 都跑，风格\u002F格式不过关直接挡 merge\n         │\nStarlight (#8) ── 编译文档站\n   │\n   └─ 部署 → Context7 (#9) 建索引 → AI 编辑器作为 context 拉走\n```\n\n承重三件套是 **Skill Seekers + Technical Writer agent + Vale**：审计、起稿、强制。没有审计 agent 会幻觉；没有 linter 一稿每次发版都偏离风格。其他 6 个是绕这个脊柱的生活质量升级。\n\n## 你会遇到的取舍\n\n- **Technical Writer agent (#2) vs Api Documenter (#3)** — 确实重叠。Technical Writer 干**整篇文档**（intro、tutorial、概念章节）。Api Documenter 是 endpoint 级（reference 行）。`\u002Fgetting-started` 页用 #2；`\u002Freference\u002Fusers\u002Fcreate` 用 #3。如果你 80% 是 reference，就把 #3 顶上。\n- **Scalar (#5) vs Swagger UI \u002F Redoc** — 三个都渲染 OpenAPI。Swagger UI 是每个后端框架的默认但视觉老。Redoc 漂亮但配置重。Scalar 是新选手，开箱视觉最好、纯 OSS、不会有许可坑。如果你已经用 Swagger UI 在跑、用户没抱怨，**不要为了好看迁移** — Scalar 是新项目的正解。\n- **Vale (#6) vs 语法检查器** — Vale 对照**明确的** style guide（Microsoft \u002F Google \u002F 自定义）lint。Grammarly \u002F LanguageTool 是猜的。文档量大就要明确 > 隐式 — 你要 CI 因为 `utilize` 直接 fail，让 agent 学会，而不是发布三周后看到一条波浪线。\n- **Starlight (#8) vs 静态站文档生成器 pack** — 现有的 static-site-docs pack 覆盖 VitePress \u002F Astro \u002F Mintlify \u002F Docusaurus \u002F Slidev。Starlight 是 Astro-based 但**专为文档预设主题**。新项目直接上 Starlight；Docusaurus 已经跑了就别迁。\n- **Context7 (#9) — 是不是杀鸡用牛刀？** — 如果你的用户不用 AI 编辑器才是。他们用。\n\n## 常见踩坑（尤其是 AI 幻觉 API 参数）\n\n- **别让 agent 编 endpoint 参数** — #2 和 #3 会很开心地编一个不存在的 `?include=` query param。修法：把**真实**的 OpenAPI spec 作为 context 喂进去（通过 #4 或直接贴文件），并在 agent 的 CLAUDE.md 里加一条规则「如果 spec 里没有这个参数，标 `[verify]` 而不是当成事实陈述」。\n- **Vale 多套 style 互打架** — 不要同时开 Microsoft + Google + Write-the-Docs。它们对牛津逗号、缩写、`which` vs `that` 的看法不一致。选一套 base，叠一套自定义。配置冲突的 PR 一周内会让团队崩溃。\n- **OpenAPI Generator 模板漂移** — 开箱模板生的 SDK 正确但难看。要发布到文档里，**一次性 override** 模板（半天工作量），把 override 提交到文档仓库。否则每次 spec 改都回退你的样式。\n- **Markdownlint 默认规则会拦正常 Markdown** — `MD013 line-length` 和 `MD041 first-line-heading` 会对完全合规的文件咆哮。第一天就用项目级 `.markdownlint.json`，别用默认。\n- **Context7 索引延迟** — 部署后给最多 24 小时让新页面进索引。新发的 tutorial 没出现别立刻排查集成，明天再看。",[104,107,110,113,116],{"q":105,"a":106},"Technical Writer agent (#2) 和 Api Documenter agent (#3) 必须两个都装吗？","大多数团队两个都用，但用在不同文档。Technical Writer (#2) 用来写叙述性文档 — 上手指南、tutorial、概念解释 — AI 需要把上下文串起来的地方。Api Documenter (#3) 用来写公式化的 reference 页面，希望在 `POST \u002Fusers`、状态码、请求体周围有一致的 prose。如果你 80% 是叙述性 tutorial，靠 #2；如果是纯 API 产品 200 个 endpoint，#3 挑大梁。",{"q":108,"a":109},"怎么防止 AI 幻觉 API 参数？","三层。第一，永远把 OpenAPI spec 作为 ground-truth context 喂给 Api Documenter agent — 别让它凭记忆写 reference。第二，在项目 CLAUDE.md 里加明确规则：「如果参数或状态码不在 spec 里，标 `[verify]`，不要当成事实陈述」。第三，让生成的文档跑一遍 OpenAPI Generator 的 test stub — 如果文档里描述的调用过不了生成 client 的类型检查，那就是幻觉信号。Agent 还是会编，但流水线能抓住。",{"q":111,"a":112},"为什么选 Scalar (#5) 而不是 Swagger UI 或 Redoc？","三个都渲染 OpenAPI。Swagger UI 是每个后端框架（FastAPI \u002F NestJS \u002F Spring）的默认、能用，但 UI 没跟上时代 — 一看就是 2014。Redoc 好看一些但配置重。Scalar 是最新选手，开箱视觉最好、纯开源、可换主题、能干净嵌入 Starlight。如果你已经在 Swagger UI 上跑、用户没抱怨，**别为了好看迁移** — Scalar 是新项目的正解。",{"q":114,"a":115},"这和「静态站 & 文档生成器」pack 不重复吗？","只有渲染层重叠，而且是刻意不重叠的。静态站 & 文档生成器 pack 覆盖 VitePress \u002F Astro \u002F Mintlify \u002F Docusaurus \u002F Slidev — 纯站点生成器。这个 pack 是喂给那些站点的**内容流水线**：审计、起稿、生代码、lint，最后用 Starlight 渲染（选它是因为 Astro 原生 + 文档预设主题，和另外 5 个互补）。两个 pack 互补 — 从那个 pack 选一个站点生成器，从这个 pack 选编辑流水线。",{"q":117,"a":118},"整条流水线能跑在 CI 里吗？","Vale (#6)、Markdownlint (#7)、OpenAPI Generator (#4)、Starlight (#8) 全部 CLI 优先，在 GitHub Actions \u002F GitLab CI 里干净运行。Agent 步骤（#2、#3）通常 writer 在本地跑 — 你不会想每次 push 都按 token 计费。常见配置：agent 在 Claude Code \u002F Cursor 里按需跑，CI 在每个 PR 跑 Vale + Markdownlint + OpenAPI Generator + Starlight build。Context7 (#9) 在文档上线后自动更新。Skill Seekers (#1) 是一次性 setup，不是 CI 步骤。",{"@context":120,"@type":121,"name":13,"description":122,"numberOfItems":123,"inLanguage":97},"https:\u002F\u002Fschema.org","ItemList","9 个开源 \u002F freemium 工具组成的流水线，面向技术写作者和 DevRel：审计、AI 起稿、从 spec 生代码、风格强制、文档站、AI 编辑器发布。",9,[125,129,133],{"url":126,"anchor":127,"reason":128},"\u002Fzh\u002Ftopics\u002Fstatic-site-docs","静态站 & 文档生成器 pack","互补的站点生成器选型（VitePress \u002F Docusaurus \u002F Mintlify），渲染这条流水线产出的文档",{"url":130,"anchor":131,"reason":132},"\u002Fzh\u002Ftopics\u002Fbackend-engineer-ai-toolkit","后端工程师 AI 工具包","共享 OpenAPI Generator — 给技术写作者协作的后端团队参考",{"url":134,"anchor":135,"reason":136},"\u002Fzh\u002Fai-tools-for\u002Fdocumentation","更多文档类 AI 工具","在这个 9 件套之外浏览完整的文档工具目录",[138,142,146],{"claim":139,"source_name":140,"source_url":141},"Vale 是语法感知的散文 linter，内置 Microsoft、Google、Write the Docs 三套 style 包","Vale 官方文档","https:\u002F\u002Fvale.sh\u002F",{"claim":143,"source_name":144,"source_url":145},"OpenAPI Generator 从 OpenAPI 2.0\u002F3.x spec 生成 50+ 种语言的客户端库和服务端 stub","OpenAPI Generator 项目","https:\u002F\u002Fopenapi-generator.tech\u002F",{"claim":147,"source_name":148,"source_url":149},"Scalar 是开源平台，把 OpenAPI 渲染成交互式 API reference","Scalar GitHub 仓库","https:\u002F\u002Fgithub.com\u002Fscalar\u002Fscalar",880,"2026-05-22T00:00:00Z"]