Claude Code write-blog for measured technical release recaps
Write a first-person technical account of the problem, attempts, turning point, and measured result.
中文Install in Claude Code
Use Claude Code with the draft, source references, and recorded test results. PPDS Docs places posts under blog/.
- Review `.claude/skills/write-blog/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/write-blog/` in your project and save the reviewed file as `.claude/skills/write-blog/SKILL.md`.
- Start Claude Code from that project's root, then select `/write-blog` in the slash menu.
Example task
The benchmark fixture is {rows: 400, beforeSeconds: 8, afterSeconds: 3}. The first attempt changed styles without affecting data load time.What to check
Explain the unsuccessful attempt and preserve the test context and evidence for {rows: 400, beforeSeconds: 8, afterSeconds: 3}. Include useful alternative text for informative images.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should a technical release recap include a failed attempt?
Include the attempt that helps explain the eventual choice. Ground measured results in the actual record without turning a single fixture into a universal claim.