book-structure-designer
Design book concepts, reader promises, central questions, arguments, tables of contents, chapter architecture, and chapter cards. Use when the user needs to turn an idea or research into a coherent bo
SKILL.mdskills/book-structure-designer/SKILL.md
GitHubBook Structure Designer
Workflow
Turn a book idea or research base into a coherent structure. Start by defining the book's promise, reader, central question, scope, and organizing principle.
Read:
references/book-concept-brief.mdfor the concept briefreferences/structure-patterns.mdfor book type structuresreferences/chapter-card-system.mdfor chapter-level planning
Structure Rules
- A table of contents is not a list of topics; each chapter must do a job.
- Practical books should move from reader problem to transformation.
- Scholarly/technical books should move from definitions to argument/system to application.
- Narrative nonfiction should balance chronology, evidence, and narrative momentum.
- Fiction structure belongs in
fiction-book-writingunless the user only needs high-level table-of-contents style planning.
Output Contract
End with:
## Book Concept Brief
- Working title:
- Reader:
- Reader promise:
- Central question:
- Scope:
- Differentiation:
## Table of Contents
| chapter | title | job | reader payoff | required research |
|---|---|---|---|---|
## Chapter Card
- Chapter:
- Function:
- Key claims/scenes:
- Examples/evidence:
- Open risks:
## Structure Rationale