self-publishing-production
Plan and check the final production tasks for self-publishing nonfiction books, including copyediting, final review readers, proofreading, layout, cover files, print-on-demand, ISBNs, and launch-readiness sequencing. Use when preparing a manuscript for publication after beta reading or when auditing a self-publishing checklist.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- self-publishing-production
- license
- MIT
- metadata
- { "tags": "writing,books,nonfiction,self-publishing,production,publishing", "version": "0.1.0", "category": "Writing", "displayName": "Self-Publishing Production" }
- description
- Plan and check the final production tasks for self-publishing nonfiction books, including copyediting, final review readers, proofreading, layout, cover files, print-on-demand, ISBNs, and launch-readiness sequencing. Use when preparing a manuscript for publication after beta reading or when auditing a self-publishing checklist.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 5
- 参考文档references/core/checklist.md2.1 KB
- 参考文档references/core/examples.md2.3 KB
- 参考文档references/core/knowledge.md3.6 KB
- 参考文档references/core/rules.md3.0 KB
- 参考文档workflows/prepare-production.md2.1 KB
03 SKILL.md 正文
Self-Publishing Production
Core Lens
Production begins after the manuscript's big-picture structure, promise, and reader value are mostly working. These tasks are predictable and solvable, but doing them too early wastes effort because beta feedback may still reshape the book.
Use this skill to plan or audit:
- Copyediting.
- Final review readers.
- Proofreading.
- Interior layout.
- Cover file requirements.
- Print-on-demand and retailer setup.
- ISBN decisions.
- Final PDF/page checks.
Reference Routing
| Need | Read |
|---|---|
| Production concepts and sequencing | references/core/knowledge.md |
| Production rules and current-info caveats | references/core/rules.md |
| Example production plans and decisions | references/core/examples.md |
| Final checklist | references/core/checklist.md |
| Prepare production plan | workflows/prepare-production.md |
Workflow
1. Confirm The Manuscript Is Ready For Production
Check that:
- Beta readers have validated desire, effectiveness, and engagement.
- Remaining issues are mostly polish, accuracy, layout, or packaging.
- The author is not using production work to avoid structural revision.
2. Sequence The Work
Recommended order:
- Final structural review or developmental review if still needed.
- Copyedit for clarity, concision, and sentence-level quality.
- Expert, sensitivity, legal, or influential review where relevant.
- Proofread.
- Interior layout for ebook, paperback, hardback, or PDF.
- Cover files for each format.
- Print-on-demand, retailer, ISBN, and metadata setup.
- Final PDF/page review.
3. Verify Current Production Requirements
Before giving precise setup instructions, verify current requirements from the relevant platform or vendor. KDP, IngramSpark, ISBN agencies, cover dimensions, trim rules, file formats, and royalty terms can change.
4. Return A Practical Checklist
Return:
- Production-readiness diagnosis.
- Ordered task plan.
- Tasks to hire vs do yourself.
- Platform-specific checks that need current verification.
- Final quality gates.
Quality Bar
Keep production advice specific enough to execute but conservative about platform details. Never let formatting, cover, or upload work start before the manuscript is structurally ready unless the user explicitly accepts the rework risk.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.