j945935cy Review Ebook Continuity
Core Workflow
Use this skill to inspect a manuscript as a book, not just as separate files.
- Map the manuscript:
- List chapter files in order.
- Identify title page, main chapters, appendices, and docs.
- Note the intended reader and book promise.
- Check progression:
- Does each chapter depend only on concepts already introduced?
- Does the order move from beginner setup to practical execution to publishing/release?
- Are appendices used for reference material rather than missing core explanations?
- Check each chapter:
- Goal, concepts, steps, example, common mistakes, summary.
- Bridge from previous chapter and bridge to next chapter when useful.
- No unexplained jumps, placeholder text, or stale version numbers.
- Check visual/content alignment:
- Screenshot file exists.
- Screenshot matches the chapter topic.
- Caption explains why the screenshot matters.
- Placeholder screenshots are not presented as final unless intentional.
- Produce findings:
- Lead with concrete issues by chapter/file.
- Include recommended fixes.
- If the user asked to execute, patch the manuscript directly and validate.
Review Style
When reviewing only, provide:
- High-priority continuity breaks.
- Medium-priority clarity or repetition issues.
- Low-priority polish suggestions.
- A short summary of what is already working.
When editing, keep changes local and scoped. Do not rewrite the whole book unless the chapter is too thin or structurally broken.
Common Commands
rg --files manuscript
rg -n "# |## |!\\[|TODO|placeholder|v0\\.|dist/v0\\.|version" manuscript docs README.md PROJECT_STATUS.md
rg -n "!\\[.*\\]\\(assets/images/.*\\)" manuscript
Use references/issue-types.md for classification and recommended fixes.