book-builder

Convert Markdown design documents into bilingual MD, DOCX, and PDF books.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/saintgo7/claude-skills --skill book-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: book-builder
Source: https://github.com/saintgo7/claude-skills/tree/main/book-builder
Command: npx skills add https://github.com/saintgo7/claude-skills --skill book-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Book Builder helps you convert scattered project/design Markdown documents into a cohesive, print-ready bilingual book (MD/DOCX/PDF in ko/en) with consistent chapter structure, cover, TOC, and section numbering—without manually stitching formats and layouts.

Core Features & Use Cases

  • Bilingual book pipeline (MD → DOCX/PDF): Produces Korean/English outputs with consistent numbering and TOC for a smooth reading/operational handoff.
  • 17-chapter standard synthesis: Creates a structured “single-book narrative” from multiple design docs by synthesizing (re-writing and reorganizing) instead of copying.
  • Pandoc + XeLaTeX publishing workflow: Runs a reusable generate.sh pipeline driven by a Pandoc/LaTeX configuration and language-specific font setup.
  • Quality gates for publication readiness: Encourages cover placement, section numbering, and reference/appendix completeness suitable for technical publishing.

Quick Start

Ask the skill to create a bilingual book from your project design documents using the standard 17-chapter structure and generate MD/DOCX/PDF outputs for ko and en.

Frequently Asked Questions about book-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert multiple Markdown design documents into a single print-ready bilingual book?

To convert Markdown design documents into a print-ready bilingual book, this skill synthesizes 10–20 project files into a structured 17-chapter narrative. It generates cohesive MD, DOCX, and PDF outputs with consistent numbering for both Korean and English.

How does a Pandoc and XeLaTeX publishing pipeline handle CJK fonts for technical documentation?

A Pandoc and XeLaTeX publishing pipeline handles CJK fonts by applying language-specific font configuration during PDF generation. This ensures Korean and other CJK characters render correctly in the final print-ready technical book.

Can I generate DOCX and PDF outputs from Markdown with a consistent chapter and section numbering structure?

Yes, you can generate DOCX and PDF outputs with consistent chapter and section numbering. The pipeline reorganizes multiple design docs into a standard 17-chapter structure, ensuring numbering aligns across both language outputs.

What is the best way to compile scattered technical writing files into a cohesive book with a cover and TOC?

The best way to compile scattered technical writing into a cohesive book is synthesizing the content into a single narrative rather than copying. This pipeline generates a structured book complete with cover, TOC, and appendix sections.

Do I need to manually stitch formats and layouts when creating a bilingual technical book?

No, you do not need to manually stitch formats and layouts when creating a bilingual technical book. The reusable generate.sh pipeline automates the Pandoc and XeLaTeX configuration to produce print-ready artifacts directly.