non-fiction book writing
1
总安装量
0
周安装量
#43724
全站排名
安装命令
npx skills add https://github.com/ddrscott/wiz-marketplace --skill Non-Fiction Book Writing
Skill 文档
Non-Fiction Book Writing
Book Structure Patterns
The Problem-Solution Arc
Best for: Business books, self-help, methodology books
Part I: The Problem
- Chapter 1: The pain point (reader recognition)
- Chapter 2: Why existing solutions fail
- Chapter 3: The hidden cause
Part II: The Solution
- Chapter 4: Introduce your framework
- Chapter 5-7: Deep dive on each element
- Chapter 8: Implementation guide
Part III: The Transformation
- Chapter 9: Case studies / success stories
- Chapter 10: Your action plan
- Conclusion: The new reality
The Progressive Mastery Arc
Best for: How-to, educational, skill-building books
Part I: Foundations
- Chapter 1: Why this matters
- Chapter 2-3: Core concepts
Part II: Building Skills
- Chapter 4-7: Progressive techniques
- Each chapter builds on previous
Part III: Mastery
- Chapter 8-9: Advanced applications
- Chapter 10: Putting it all together
The Thematic Arc
Best for: Essay collections, thought leadership, exploration
Introduction: The unifying theme
Chapters 1-10: Independent essays
- Each explores one facet of theme
- Can be read in any order
- Connected by recurring motifs
Conclusion: Synthesis and call to action
Chapter Structure
The AIDA Chapter Formula
Attention: Open with a hook
- Personal story
- Surprising statistic
- Provocative question
- Bold claim
Interest: Build context
- Why this matters
- What’s at stake
- Common misconceptions
Desire: Deliver value
- Core teaching
- Examples and evidence
- Frameworks and tools
Action: Close with clarity
- Key takeaways
- Exercises or reflection
- Bridge to next chapter
Recommended Chapter Length
| Book Type | Words/Chapter | Chapters | Total Words |
|---|---|---|---|
| Business/Thought Leadership | 3,000-5,000 | 10-12 | 40,000-60,000 |
| How-To/Educational | 2,500-4,000 | 12-15 | 35,000-50,000 |
| Memoir/Narrative | 4,000-6,000 | 15-20 | 60,000-80,000 |
| Quick Read/Gift Book | 1,500-2,500 | 8-10 | 15,000-25,000 |
Image Placeholder Conventions
Syntax
<!-- IMAGE: [Detailed description for image generation] -->
Best Practices
Be Specific:
<!-- IMAGE: A circular diagram showing the 4 phases of the Board Game Test:
1) Define Start State (green), 2) Map Rules (blue), 3) Set Win Condition (gold),
4) Handle Edge Cases (red), with arrows connecting each phase in clockwise order -->
Include Style Cues:
<!-- IMAGE: A minimalist illustration of a person at a crossroads,
business professional style, muted earth tones, metaphor for decision-making -->
Specify Chart Types:
<!-- IMAGE: A horizontal bar chart comparing implementation time (weeks)
for Traditional Approach (12 weeks) vs Board Game Test Approach (4 weeks),
clean business style with teal and gray colors -->
Image Types to Include
- Conceptual Diagrams: Visualize frameworks and mental models
- Process Flowcharts: Show step-by-step procedures
- Comparison Charts: Before/after, this vs that
- Timeline Graphics: Show progression or history
- Infographics: Summarize key statistics or lists
- Metaphor Illustrations: Visual representations of abstract concepts
Placement Guidelines
- After introducing a concept: Reinforce with visual
- Complex processes: Break down with flowchart
- Key frameworks: Make memorable with diagram
- Chapter summaries: Infographic of takeaways
- Aim for 2-4 images per chapter
Writing Voice Guidelines
First Person (“I/We”)
Use when:
- Sharing personal stories
- Establishing authority through experience
- Creating intimacy with reader
- The author is the brand
Example: “When I first discovered this, I was skeptical. But after testing it with 50 clients…”
Second Person (“You”)
Use when:
- Giving direct instructions
- Making content feel personal
- Engaging the reader actively
Example: “You’ve probably experienced this: you walk into a meeting thinking you understand the process, only to discover…”
Third Person (“They/One”)
Use when:
- Academic or formal tone
- Discussing case studies
- Maintaining objectivity
Example: “Organizations that implement this approach typically see…”
Common Pitfalls to Avoid
- Starting with backstory: Hook first, context after
- Too much theory, not enough examples: Show, don’t just tell
- Jargon overload: Define terms, use plain language
- Uneven chapter lengths: Aim for consistency (±20%)
- Missing transitions: Bridge sections and chapters
- No clear takeaways: End every chapter with action items
- Image afterthought: Plan visuals during outlining
Reference Materials
For additional guidance, see:
${CLAUDE_PLUGIN_ROOT}/templates/chapter-template.md${CLAUDE_PLUGIN_ROOT}/templates/outline-template.md