Publish Google Play Books

Publish Google Play Books

Core Workflow

Use this skill for Google Play Books publishing preparation. Do not actually submit, upload, or change live bookstore data unless the user explicitly asks and an authenticated browser or connector is available.

1. Identify the release files:
   • EPUB: prefer the newest dist/v*/ai-sigil-epub-v*.epub; otherwise use output/*.epub.
   • Cover: prefer the newest dist/v*/cover-v*.png; otherwise use a user-provided cover.
   • Listing copy: prefer docs/google-play-books-listing.md if present.
2. Validate the EPUB:
   • Run the repo validation or release packaging script when available.
   • Run EPUBCheck if the project has a helper such as tools/check-epub.ps1.
   • Inspect generated EPUB internals for Google Play Books CSS warnings if the user reports them.
3. Prepare bookstore metadata:
   • Title, subtitle, author, language, description, categories, keywords, target readers, and author bio.
   • Use references/listing-copy.md for reusable wording patterns.
4. Prepare upload guidance:
   • Tell the user exactly which EPUB and cover file to upload.
   • Mention that platform fields must match EPUB metadata.
   • Mention that Google Play Books processing warnings should be fixed at source and then repackaged.
5. Do not push to GitHub or submit to Google Play Books unless the user explicitly confirms.

Validation Commands

For PowerShell ebook repos, prefer existing project scripts:

powershell -ExecutionPolicy Bypass -File .\tools\package-release.ps1 -Version <version>

If only EPUBCheck is needed:

powershell -ExecutionPolicy Bypass -File .\tools\check-epub.ps1

For Google Play Books CSS warnings, scan source and generated files for unsupported declarations:

rg -n "webkit-text-size-adjust|webkit-touch-callout|webkit-user-select|khtml-user-select|moz-user-select|ms-user-select|user-select" .

If the declarations come from Pandoc syntax highlighting, add this to the Pandoc command:

--syntax-highlighting=none

Then rebuild and inspect the EPUB internals if needed.

Output Checklist

When finishing a publishing-prep task, report:

• The EPUB path to upload.
• The cover path to upload.
• EPUBCheck result.
• Whether Google Play Books warning patterns remain.
• Listing copy changes or ready-to-paste text.
• Any uncommitted or ignored files that matter.

Keep responses concise and practical.