[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-tech-writer-ai-pipeline-fr":3,"seo:pack:tech-writer-ai-pipeline:fr":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","Nouveau · cette semaine","Pipeline IA du Rédacteur Technique","Neuf outils pour rédacteurs techniques et dev rel produisant docs d'API, tutoriels et exemples de code — couvre audit, premier jet, code depuis spec, contrôle de style, rendu de référence multilingue et docs accessibles aux IA.",[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":25,"title":97,"metaDescription":98,"h1":99,"tldr":100,"bodyMarkdown":101,"faq":102,"schema":118,"internalLinks":124,"citations":137,"wordCount":150,"generatedAt":151},"pack","Technical Writer's AI Pipeline — 9 Picks for API Docs, Tutorials & Code Samples","Skill Seekers, Technical Writer agent, Api Documenter, OpenAPI Generator, Scalar, Vale, Markdownlint, Starlight, Context7 — a deliberate pipeline a technical writer or dev rel can install in an afternoon. Audit, draft, generate, lint, render, publish.","Technical Writer's AI Pipeline — A Nine-Tool Stack from Audit to Publish","Nine picks in install order: turn your existing docs into agent skills, draft prose with a technical-writer agent, generate API reference from your OpenAPI spec, render it beautifully, enforce prose + Markdown style on every commit, ship a docs site, and finally make the whole thing discoverable to AI editors. Pipeline, not a shopping list.","## What's in this pack\n\nYou're a technical writer or dev rel. Your job is API references, getting-started guides, tutorials, code samples in three languages, and a style guide that nobody else reads. AI can finally help — but the marketplace has 700 picks and most of them are general-purpose chat tools dressed up for marketing copy.\n\nThis pack is the **opinionated nine-tool pipeline** built for the technical-writing workflow specifically: audit what you have, draft what you need, generate code samples from API specs, lint for style consistency, render API references that don't look like 2014, and keep the whole thing discoverable to the AI editors your users are pasting your docs into.\n\nEverything here is open-source or has a free tier that's actually usable. Nothing here is a generic \"write blog posts with AI\" tool. The order matters — each step feeds the next.\n\n## Install in this order (audit → first-draft → style → site → publish)\n\n1. **Skill Seekers — Convert Docs\u002FRepos\u002FPDFs to Skills** *(audit)* — Start here. Feed it your existing docs, your repo, and any internal PDFs. It produces structured skills that downstream agents can actually load. This is your one-time audit of \"what do we already know\" before any agent writes a single paragraph.\n2. **Claude Code Agent: Technical Writer** *(first draft)* — Anthropic-style subagent specifically tuned for API references, user guides, SDK docs, and getting-started flows. Drop it in `.claude\u002Fagents\u002F`, point it at a topic, get a first draft you actually have to edit (not rewrite).\n3. **Claude Code Agent: Api Documenter** *(API-specific draft)* — Sister agent to #2 but specialised for the OpenAPI\u002Fendpoint shape. Feed it a spec or a route handler, get reference prose with the right verbs, status codes, and example payloads.\n4. **OpenAPI Generator — Client SDKs + Server Stubs from Spec** *(code samples)* — Generate working SDK code in 50+ languages from a single OpenAPI YAML. This is how you stop hand-writing the `curl`\u002F`Python`\u002F`Node`\u002F`Go` examples on every page. Spec changes? Re-run the generator and your samples are fresh.\n5. **Scalar — Open-Source API Platform with Beautiful References** *(reference rendering)* — Renders OpenAPI as a modern reference page that doesn't look like 2014 Swagger UI. Self-hostable, embeddable, themeable. This is the page your users actually land on from Google.\n6. **Vale — Syntax-Aware Prose Linter for Technical Writing** *(style enforcement)* — The killer feature: lints Markdown\u002FRST\u002FAsciiDoc against your style guide *without* flagging code blocks. Ships with Microsoft, Google, and Write the Docs style packages. CI-friendly. Catches `utilize` → `use` and `e.g.,` → `for example` automatically.\n7. **Markdownlint — Lint Markdown for AI Content Quality** *(format enforcement)* — Mechanical Markdown checks (heading order, trailing spaces, list consistency, link syntax). Pair with Vale: Vale handles prose style, Markdownlint handles file structure. Both run in pre-commit.\n8. **Starlight — Documentation Framework for Astro** *(docs site)* — The docs site itself. Astro-native, fast, dark-mode default, sidebar navigation that works on mobile. Plays nicely with the Markdown your agents and linters just produced. Skip the static-site-builder beauty contest — Starlight is the boring correct answer for new sites.\n9. **Context7 — Up-to-Date Docs MCP for AI Editors** *(publish)* — The publish step nobody talks about. Once your docs are live, you want Cursor\u002FClaude Code\u002FCodex users to pull them as context when their LLM hallucinates your API. Context7 indexes your docs and serves them via MCP. The closing loop: AI helped you write, now AI helps your users *use*.\n\n## How they fit together\n\n```\nExisting docs\u002Frepo\n   │\nSkill Seekers (#1) ─── audit, produce agent-loadable skills\n   │\n   ├─→ Technical Writer agent (#2) ─── prose first draft\n   │       │\n   │       └─→ Markdown files\n   │\n   └─→ Api Documenter agent (#3) ←── OpenAPI spec\n           │\n           ├─→ OpenAPI Generator (#4) ─── code samples (Python\u002FGo\u002FNode\u002Fcurl)\n           └─→ Scalar (#5) ─── rendered API reference\n                   │\nVale (#6) + Markdownlint (#7)\n   │\n   └─ runs on every commit, blocks merge on style\u002Fformat failures\n         │\nStarlight (#8) ─── builds the docs site\n   │\n   └─ deploy → Context7 (#9) indexes it → AI editors fetch as context\n```\n\nThe load-bearing trio is **Skill Seekers + Technical Writer agent + Vale**: audit, draft, enforce. Without the audit step the agent hallucinates; without the linter the draft drifts off-style every release. The other six are quality-of-life upgrades around that spine.\n\n## Tradeoffs you'll hit\n\n- **Technical Writer agent (#2) vs Api Documenter (#3)** — Overlap is real. Technical Writer does the *whole document* (intro, tutorial, conceptual sections). Api Documenter is endpoint-focused (the reference rows). Use #2 for the `\u002Fgetting-started` page; use #3 for `\u002Freference\u002Fusers\u002Fcreate`. If your docs are 80% reference, lean on #3.\n- **Scalar (#5) vs Swagger UI \u002F Redoc** — Swagger UI is the default in every backend framework but visually dated. Redoc is prettier but config-heavy. Scalar is the new entrant with the best out-of-box look and an OSS license that won't bite. If you're already on Swagger UI and shipping, don't migrate for taste alone — wait for a redesign.\n- **Vale (#6) vs grammar checkers** — Vale lints against an explicit style guide (Microsoft, Google, custom). Grammarly\u002FLanguageTool guess. For docs at scale, explicit > implicit — you want CI to fail on \"utilize\" so the agent learns, not a wavy underline three weeks after publish.\n- **Starlight (#8) vs the static-site-docs pack** — The existing static-site-docs pack covers VitePress, Astro, Mintlify, Docusaurus, Slidev. Starlight is Astro-based but pre-themed *for docs specifically*. If you're greenfield, start with Starlight; if you have Docusaurus running, don't migrate.\n- **Context7 (#9) — is this overkill?** — Only if your users don't use AI editors. They do.\n\n## Common pitfalls (especially AI hallucinating API params)\n\n- **Don't let agents invent endpoint parameters** — #2 and #3 will happily make up a `?include=` query param that doesn't exist. The fix: pass the *actual* OpenAPI spec as context (via #4 or a direct file paste), and add a rule in the agent's CLAUDE.md saying \"if the parameter isn't in the spec, mark it `[verify]` instead of stating it.\"\n- **Vale styles fight each other** — Don't enable Microsoft + Google + Write-the-Docs all at once. They disagree on Oxford commas, contractions, and `which` vs `that`. Pick one base style, layer one custom pack on top. The PRs from a conflicting setup will demoralise the team in a week.\n- **OpenAPI Generator template drift** — Out-of-box templates produce correct-but-ugly SDKs. For published docs, override the templates *once* (it's a half-day) and check the overrides into your docs repo. Otherwise every spec change reverts your style.\n- **Markdownlint default rules block valid Markdown** — `MD013 line-length` and `MD041 first-line-heading` will scream at perfectly fine files. Run with a project `.markdownlint.json` from day 1, not the defaults.\n- **Context7 indexing latency** — Allow up to 24h after deploy for new pages to show up. Don't troubleshoot the integration if a brand-new tutorial isn't there yet; check tomorrow.",[103,106,109,112,115],{"q":104,"a":105},"Do I really need both a Technical Writer agent (#2) and an Api Documenter agent (#3)?","Most teams end up using both, but for different documents. Technical Writer (#2) is your tool for narrative docs — getting-started guides, tutorials, conceptual explainers — where the AI has to weave context together. Api Documenter (#3) is for the formulaic reference pages where you want consistent prose around `POST \u002Fusers`, status codes, request bodies. If your docs are 80% narrative tutorials, lean on #2; if you're a pure-API product with 200 endpoints, #3 carries the load.",{"q":107,"a":108},"How do I stop the AI from hallucinating API parameters?","Three layers. First, always pass the OpenAPI spec as ground-truth context to the Api Documenter agent — don't ask it to write reference docs from memory. Second, add an explicit rule in your project CLAUDE.md: \"if a parameter or status code is not in the spec, mark it `[verify]` and don't state it as fact.\" Third, run the generated docs through OpenAPI Generator's test stubs — if a documented call fails the generated client's type check, that's your hallucination signal. The agent will still fabricate sometimes; the pipeline is what catches it.",{"q":110,"a":111},"Why Scalar (#5) instead of Swagger UI or Redoc?","All three render OpenAPI. Swagger UI is the default in every backend framework (FastAPI, NestJS, Spring) and works fine, but the UI hasn't aged well — it screams 2014. Redoc looks better but configuration is heavy. Scalar is the newest entrant, looks modern out of the box, is fully open-source, themeable, and embeds cleanly into Starlight. If you're already shipping on Swagger UI and users aren't complaining, don't migrate just for taste — Scalar is the right pick for greenfield.",{"q":113,"a":114},"Doesn't this overlap with the Static Site & Docs Builders pack?","Only on the rendering layer, and intentionally not. The Static Site & Docs Builders pack covers VitePress, Astro, Mintlify, Docusaurus, Slidev — pure site generators. This pack is the *content pipeline* that feeds those sites: audit, draft, generate, lint, then render with Starlight (chosen because it's Astro-native and docs-pre-themed, distinct from the other five). The two packs are complementary — install the docs builder of your choice from one pack, then this pack for the editorial pipeline around it.",{"q":116,"a":117},"Can I run this whole pipeline in CI?","Vale (#6), Markdownlint (#7), OpenAPI Generator (#4), and Starlight (#8) are all CLI-first and run cleanly in GitHub Actions \u002F GitLab CI. The agent steps (#2, #3) are usually run locally by a writer — you don't want a model-priced bill on every push. A common setup: agents run on-demand in Claude Code or Cursor, then CI runs Vale + Markdownlint + OpenAPI Generator + Starlight build on every PR. Context7 (#9) updates automatically once your docs are live. Skill Seekers (#1) is a one-time setup step, not a CI step.",{"@context":119,"@type":120,"name":121,"description":122,"numberOfItems":123,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","Technical Writer's AI Pipeline","Nine open-source and freemium picks forming a deliberate pipeline for technical writers and dev rel: audit, AI first-draft, code-from-spec, style enforcement, docs site, and AI-editor publishing.",9,[125,129,133],{"url":126,"anchor":127,"reason":128},"\u002Fen\u002Ftopics\u002Fstatic-site-docs","Static Site & Docs Builders pack","Complementary site-generator picks (VitePress, Docusaurus, Mintlify) to render the docs this pipeline produces",{"url":130,"anchor":131,"reason":132},"\u002Fen\u002Ftopics\u002Fbackend-engineer-ai-toolkit","Backend Engineer's AI Toolkit","Shares OpenAPI Generator — useful for the backend team your tech writer collaborates with",{"url":134,"anchor":135,"reason":136},"\u002Fen\u002Fai-tools-for\u002Fdocumentation","More AI tools for documentation","Browse the full documentation-tool catalog beyond this curated nine-pick pipeline",[138,142,146],{"claim":139,"source_name":140,"source_url":141},"Vale is a syntax-aware prose linter that ships with Microsoft, Google, and Write the Docs style packages","Vale official documentation","https:\u002F\u002Fvale.sh\u002F",{"claim":143,"source_name":144,"source_url":145},"OpenAPI Generator produces client libraries and server stubs in 50+ languages from OpenAPI 2.0\u002F3.x specs","OpenAPI Generator project","https:\u002F\u002Fopenapi-generator.tech\u002F",{"claim":147,"source_name":148,"source_url":149},"Scalar is an open-source platform for rendering OpenAPI as interactive API references","Scalar GitHub repository","https:\u002F\u002Fgithub.com\u002Fscalar\u002Fscalar",920,"2026-05-22T00:00:00Z"]