pragmatic-writing
SolidThis skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- robertguss
- Repository
- robertguss/claude-code-toolkit
- Created
- 8 months ago
- Last Updated
- 1 months ago
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
technical-writer
This skill should be used when the user asks to "write a blog post", "draft a postmortem", "document this process", "write an incident writeup", "review this article", "write API docs", "write a how-to guide", "compare these two tools", "write up this feature", "make this scannable", "restructure this draft", or "nobody finishes reading this". Produces technical writing that is problem-first, concrete, and humble: real numbers instead of adjectives, real incidents instead of invented scenarios, and structure built for how people actually read on a screen. Applies to public blogs, internal team docs, code reviews, and personal knowledge vaults. Supports a public-facing mode (more scaffolding) and an internal mode (tighter), and produces both when asked.
technical-writing
Use when writing or revising user-facing prose -- READMEs, changelogs, guides, adapter docs, or release notes. Audience-first structure with a quickstart before theory, every claim verified against the repo, and no invented benchmarks or features.
core-technical-writing
Doctrine for authoring clear, precise technical documentation in {{PROJECT_NAME}}. Covers hard rules for structure, voice, and vocabulary; format conventions by doc type (README, ADR, plan, CHANGELOG, API reference, runbook); anti-patterns that degrade clarity; and WRONG/CORRECT examples across doc types. Use when authoring or reviewing any documentation artifact — from a one-sentence inline comment to a multi-section ADR or a public API reference.