Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From hstack
Use when writing Manning-style technical chapters, Chapter 1s, examples, callouts, or summaries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hstack:manning-tech-book-writingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use for Manning-style technical book chapters. Move readers from concrete examples to useful mental models with minimal theory up front.
Use for Manning-style technical book chapters. Move readers from concrete examples to useful mental models with minimal theory up front.
Define the reader, chapter goal, and skills gained. Open with 3-5 "This chapter covers" bullets, start from a concrete problem, introduce concepts just in time, and close with complete-sentence summary bullets.
Chapter 1 must answer what the technology is, why the reader should care, and how it works end to end. Use one clear mental model with a simple scenario, component diagram, data flow, and explanatory caption.
Review for early practical value, concrete examples, motivated theory, explained code, correct callout/sidebar use, and AI-writing artifacts.
Load Chapter 1, structure, style, opening/summary, callout/sidebar, introduction, or file-naming references only when the task needs that detail.
npx claudepluginhub leehanchung/hstack --plugin hstackGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Guides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Forks private projects, strips secrets/internal references, verifies cleanliness, and packages them with CLAUDE.md, README, and setup.sh for safe public release.