From great-publishers
Generate an Astro book-site scaffold from manuscript/ chapters. v0.1 documents the contract and stubs the wiring — the working Astro template ships in templates/astro-book-site/ in a future release. Use when a manuscript is ready to ship as a public-facing book site (typography-first reading experience, dark/light mode, scroll-based, optional chapter illustrations and embedded clips). Output lands in a sibling repo to the project so the book site has its own deploy lifecycle.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-publishers:publishers-build-book-siteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold an Astro book site from a project's `manuscript/` chapters.
Scaffold an Astro book site from a project's manuscript/ chapters.
This skill ships the contract for the book-site build in v0.1. The working Astro template — typography-first layout, IntersectionObserver fade-in <Illustration> and <ClipLoop> components, dark/light mode, scroll-based reading, GitHub Pages config, MDX integration — is being scaffolded in a separate repo and will land at templates/astro-book-site/ of this plugin in a follow-up release.
In v0.1, the skill does the resolution work, generates the chapter manifest, and reports what would be built. In v0.2 it will copy the template into the target directory and wire in the chapter content.
When the Astro template is in place (v0.2+), this skill will:
.great-authors/project.md) for title, premise, voice rules.manuscript/*.md in lexicographic order.film/render/kling/keyframes/*.png and embedded clips in film/render/<engine>/*.mp4.<plugin-install-path>/templates/astro-book-site/ into a sibling directory at <project-parent>/<project-slug>-book/..great-authors/project.mdmanuscript/cd <project-slug>-book && npm install && npm run dev to preview locally; git init && git push to ship.great-authors and is ready for a public-facing book site.Not for: marketing pages (great-marketers — see /marketers-write-launch-copy --channel web), landing sites for a SaaS or service (out of scope), one-page essays (use a static blog template instead).
When this skill is invoked with a <project> argument (or no argument, meaning the current directory):
Resolve the project root. If <project> is provided, treat it as a directory path or a slug under the user's projects directory. If no argument, use the current working directory.
Verify the project structure:
.great-authors/project.md must existmanuscript/ must exist with at least one .md chapterRead the bible:
.great-authors/project.md — title, genre, premise, voice rules.great-authors/voice.md — voice rules in detail (informs site copy)Enumerate the manuscript:
manuscript/*.md in lexicographic order (chapter-01.md, chapter-02.md, ...)Enumerate the visual assets (optional but auto-wired if present):
film/render/kling/keyframes/*.png — chapter illustrationsfilm/render/kling/*.mp4 and film/render/veo/*.mp4 — embedded clipschapter-01.png becomes the illustration for chapter-01.mdIn v0.1, report the scaffold plan. Print what would be built when the template lands:
📚 Book site plan (v0.1 — template not yet in place):
Project: <title>
Source: <project-root>
Target: <project-parent>/<project-slug>-book/
Chapters: <N> (chapter-01.md ... chapter-NN.md)
Total words: <N>
Illustrations: <N> matched, <N> chapters without
Clips: <N> matched, <N> chapters without
When templates/astro-book-site/ lands (v0.2):
- The template copies into <target>
- Each chapter becomes <slug>.mdx with the chapter body
- Matched illustrations and clips are wired into the chapter pages
- npm run dev previews; git push deploys via GitHub Pages workflow
For now, run /publishers-build-book-site again once v0.2 ships, or
manually copy the Astro template when you have it and re-run this skill.
In v0.2+ (post-template-landing), execute the scaffold:
<project-parent>/<project-slug>-book/templates/astro-book-site/* into itastro.config.mjs, src/site-config.ts, package.jsonsrc/content/chapters/<slug>.mdx with chapter bodypublic/illustrations/<slug>.png and reference from the chapter MDXpublic/clips/<slug>.mp4 and reference from the chapter MDXnpm install && npm run dev commandAstro is the v0.1/v0.2 default. Hugo and Eleventy are filed as v1.x stubs — when those land, this skill takes a --backend <name> argument. For v0.1, the skill is Astro-only.
/publishers-publish-github-pages (filed for v1.0). The skill scaffolds the repo; the user pushes.tina-brown-editor via /publishers-channel tina and saves to publishers/jacket-copy/. The book-site build reads those files if they exist.chip-kidd-designer, diana-vreeland-editor, or george-lois-designer via /publishers-channel. The book-site build reads the cover concept brief from publishers/covers/<slug>.md if it exists and renders the cover image at the appropriate spot in the site (when the cover image PNG itself is present — image-gen integration is filed for v1.0's /publishers-design-cover).great-authors. Don't pre-generate or paraphrase.<project>.example.com or username.github.io/<project> without entangling the manuscript repo.<ClipLoop> and <Illustration> components in the template are intentionally minimal: typography-first reading is the priority. Animation and motion are deferred to the chapter clip files themselves; the components just place them quietly in the page rhythm.Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub sethshoultes/great-minds-constellation --plugin great-publishers