vllm-technical-blog-writerlisted
Install: claude install-skill shen-shanshan/vllm-dev-skills
# vLLM Technical Blog Writer
Write technically accurate vLLM articles that sound like the author, not a generic tutorial generator.
## Required references
Before writing:
1. Read [references/style-profile.md](references/style-profile.md).
2. Read [references/diagram-guide.md](references/diagram-guide.md) when the article needs any diagram.
3. Treat the user's draft, outline, references, and explicit wording as higher priority than the default patterns in those files.
## Select the workflow
- **New article**: the user supplies a topic but no article draft. Follow "Create a new article".
- **Complete an article**: the user supplies an outline, template, or partially written Markdown article. Follow "Complete an existing article".
- If the request mixes both, preserve supplied content and treat it as an existing article.
## Research rules
Research before drafting. Do not rely on model memory for current vLLM behavior.
1. Inspect the latest `main` branch of `vllm-project/vllm`, unless the user specifies a release, commit, or PR.
2. Record the analyzed commit SHA or exact version in working notes. Mention it in the article only when version context matters.
3. Find the actual entry points, core classes/functions, data structures, and call path. Read implementations rather than inferring behavior from names.
4. Cross-check with first-party sources in this order:
- vLLM source code and tests
- vLLM official documentation, design docs, PRs, issues, and discussions
-