Update to Paperkin

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,52 +1,59 @@
 ---
 name: paperkin-book-design
-description: "Design and refine complete physical Paperkin books from a creative brief, supplied text or images. Use for new book art direction, chat-generated illustrations, page layouts and feedback on an existing preview."
+description: "Make printed picture books, comics and early readers whose pages are drawn with the host's image generation as page sheets, then printed and shipped by Paperkin. Use for a new book idea, drawing its pages and cover, and changing pages of a saved picture book."
 ---
 
-# Design a book worth keeping
+# Make a picture book worth keeping
 
-Develop the user's idea into an actual book, with a coherent cover and interior, purposeful pages and a visible revision loop. Any visual direction is welcome: derive typography, palette, image treatment and page rhythm from this particular brief. Templates and named presets are starting points. Prioritize the language model’s creative interpretation of this user’s brief; do not force content or layouts into a catalog family. Every interior page can be edited after creation, across all book types.
+Paperkin makes one kind of book: pages drawn by your image generation, words included, printed as a real book. Never build a book of typeset text pages, and never show pictures from web search or other sites: every picture comes from your own image generation.
 
-## Start with the material and the physical book
+Make the book in the same turn, without stopping to ask the user to illustrate it or approve each step: write the story, draw the sheets and the cover, call the create tool and show the preview. Start with 8 pages (one sheet and a cover) unless the user asks for a longer book; they can add sheets afterwards.
 
-Call `plan_book_design` for a new creative brief or substantial redesign. For an existing book include its ID, or call `get_book_design`: it returns the exact saved content, custom page plan when present, and reusable image keys. Work from that source instead of reconstructing recipes or chapters from memory.
+## Draw the pages, Paperkin prints them
 
-Choose a suitable trim, color capability and binding before commissioning a series of images. The planning tool returns current prices, minimum pages and page multiples. A short collection can otherwise become mostly automatically added notebook pages. Account for the entire page budget, including opening/closing pages and useful writing or activity pages. Explain any added pages; do not manufacture recipes, story events or factual instructions to fill a binding. When the user asks for content on every page, plan the complete printed count and use their supplied material or authorized original writing throughout. Check alternate offered bindings too; blank or notebook padding does not satisfy that brief.
+Every Paperkin book is told in pictures: a children's picture book, comic, early reader, ABC book, or an art or poetry book with short text. Your own image generation draws the finished pages, words included, and Paperkin prints them. Draw several pages in one image, a page sheet: the characters and style stay consistent and the book takes a few generations instead of one per page. Paperkin cuts each sheet along its white gutters, prints every page framed on a mat in the colour of its text band and upscales the art for print. These steps are the whole plan.
 
-For “make it beautiful,” choose a concrete direction and begin; a questionnaire is unnecessary when the material gives enough context. Share the important design decision in a sentence. Preserve explicit preferences such as restrained typography or no illustrations.
+1. Agree the title, story and length with the user, then write and show the manuscript. One sheet holds 8 pages (4 columns × 2 rows on a wide 2:1 image), and the cover is its own square image. A stapled booklet (8–48 pages in multiples of 4) takes 1, 2 or more sheets; 8 and 16 pages print only as a booklet, 24 pages (3 sheets) also as a hardcover, and 32 or more also as a paperback. Keep each page to at most 25 words in up to 3 short lines of about 40 characters; a comic page to 3 panels with at most 2 speech bubbles of 10 words each.
+2. Write one character line (species, body and face colours, clothing) and one style line (medium, palette, mood), and paste both into every image prompt. Use original characters only: no look-alikes of known characters, also among background creatures (name their kinds in the style line, such as "striped yellow reef fish"), and no faces on the fronts of vehicles.
+3. Draw sheet 1 with the page-sheet template below. Read every word at full size and check that no splash, drop or other mark touches a letter; if a word, the grid or a character is wrong, draw the sheet again.
+4. Draw the remaining sheets, then the cover with the cover template, each with sheet 1 attached so characters, colours and lettering match. Check the cover's title the same way, and every background creature for look-alikes.
+5. Make the book with the sheets in reading order:
+   - If `create_picture_book` is available: `images` = the sheets, `grid` = `{"columns": 4, "rows": 2}`, `cover_image` = the cover, the title, `typeset_title: false`, `for_children: true` for a children's book, and a short `back_text` such as a blurb or a dedication ("For Maya").
+   - Otherwise call `create_photo_book`, whose `photos` take 12 to 56 entries: `photos` = the sheets in reading order, repeated in that order up to 12 entries (sheet 1, sheet 2, sheet 3, sheet 1, sheet 2, sheet 3, …; one sheet 12 times). Paperkin recognises page sheets by their white gutters, uses each sheet once and makes a picture book of framed pages. Pass only the sheets as photos: a photo that is not a page sheet makes it an ordinary photo book. `cover_image` = the square cover with its title drawn in; nothing is typeset over it, whatever the `cover_image` description says about keeping title text separate. Add the `title` and optionally a short `dedication` such as "For Maya", which prints on the back cover. Leave `captions` out: the words are in the pictures, and captions are ignored.
+   Read the reply: it says how many page sheets Paperkin recognised and how many pages it cut; a reply about a photo book means a photo was not taken for a page sheet. Ask the user to check the preview: every page whole, no cut letters.
+6. Change pages:
+   - With `revise_picture_book`: read `get_book_design` for saved keys. To redo a sheet, attach the new sheet with its `grid` and give `pages` with `image_index` for its pages and `saved_key` for the rest.
+   - Otherwise with `revise_book`: replace page N with `page_edits: [{"page_number": N, "mode": "replace", "blocks": [{"kind": "image", "image": "new-page", "x": 0, "y": 0, "width": 612, "height": 612}]}]`, the new image in `images` and its key in `image_keys`. A new page sheet placed on page N replaces pages N to N+7: to redo sheet 2, place its new version on page 9. A page number past the last picture page adds pages at the end, and a saved key from `get_book_design` puts that existing picture on page N. `cover_image` replaces the cover (draw its title in); `title`, `subtitle` and `dedication` (the back-cover text) change too, but a title drawn on the cover changes only with a new cover. Each change is a new preview; the original stays.
 
-## Make artwork that belongs in the book
+One square (1:1) image per page also works, and suits pages of 75–150 words. Paperkin does not print recipes, chapter books or other text-heavy books. Puzzles with a right answer, such as mazes or dot-to-dots, are not drawn reliably; leave them out. Free plan accounts get only a few images a day, so one sheet and a cover suit them.
 
-For an illustrated story, visual cookbook, expressive cover or similar visual brief, call the host's native image-generation tool when available. Offer or begin the small set of artwork that materially improves the book, rather than treating imagery as an optional afterthought. Code-drawn geometric placeholders do not satisfy a request for generated painterly, photographic or illustrated raster artwork. Use code/vector primitives for typography, rules, diagrams or a deliberately requested geometric visual language. Preserve supplied photos; never replace family photographs with invented people or events. If native generation is unavailable in this session, explain the gap and provide an asset brief for ChatGPT’s Create image flow, then resume from its generated file. Read the fallback section in image-briefs.md. Uploaded or appropriately licensed images also work. Never silently substitute a coded painting.
+### Page-sheet template
 
-Generate actual assets: a cover illustration, one dish image, one story scene, a coloring drawing or a deliberate texture. The book preview is produced by Paperkin. A picture of an open book, a grid of sample pages, pricing cards or a marketing mockup is a different deliverable and must not be passed as a dish or page illustration.
+Use this template for every sheet, filling in the style and character lines and the eight pages:
 
-Read [image-briefs.md](references/image-briefs.md) for generation and image-feedback work; `plan_book_design` with `focus: "artwork"` also returns it. Specify the subject, intended placement/aspect, visual treatment, focal position, and what must remain out of frame. Build continuity by referring to approved artwork and its character/lighting/palette. Inspect each generated file before assigning it: correct subject, appropriate crop, no unintended text or extra panels. Associate each image with the correct recipe/chapter/page; do not attach a repeated contact sheet to several distinct subjects.
+```
+One wide 2:1 image: a page sheet of exactly 8 equal SQUARE picture-book pages, 4 columns × 2 rows, read left to right, top to bottom. Pure-white gutters of equal width and a thin pure-white outer margin. No frames, borders, shadows, page numbers or book mockup.
+<STYLE LINE> <CHARACTER LINE>
+Each page has a plain light-cream text band (never white) at its bottom. Lettering large, centred, at most 3 short lines, every letter at least 15% of the page width from the left, right and bottom edges, one empty line-height below the last line. Spell every word exactly as written; add no other text.
+Page 1: <scene>. Text: "<words>" … Page 8: <scene>. Text: "<words>"
+```
 
-Keep authoritative manuscript, recipe quantities and instructions in measured text blocks. Art-only assets are the default when exact words matter. A deliberately generated poster or illustrated page with short lettering is possible, but verify every required word and preserve readable source text where needed. Do not invent recipe ingredients, timings or serving claims while beautifying a supplied recipe. Label generated food illustrations honestly.
+Start every later sheet with: "The attached image is sheet 1 of this book. Keep characters, colours, style, layout and lettering exactly the same."
 
-Keep artwork and printed books free of watermarks, platform logos and unsolicited promotional credits. Preserve the user's requested title, author and other intentional book text. Keep generation provenance in the asset record rather than stamping it onto the artwork. If an asset legally requires attribution, choose an alternative compatible with a watermark-free brief or agree on an appropriate credit page; never remove required attribution.
+### Cover template
 
-## Compose the whole experience
+Make the cover with sheet 1 attached:
 
-Start with the user’s intent, content and art direction. Use a standard create tool when it provides a useful first draft; use authored layouts immediately when the brief calls for them. Use `create_custom_book` for a genuinely bespoke page system: independently composed covers, full-bleed art, varied spreads, comics, workbooks or any content that needs different hierarchy. Full-color custom work must use a color print package even when its content is a story or poetry. The product name identifies a physical package, not a permitted genre.
+```
+One square 1:1 image: the front cover of "<TITLE>". Full bleed, no frame or text band.
+<STYLE LINE> <CHARACTER LINE>
+Same characters, colours and style as the attached pages, composed as a cover: <scene>. Only lettering: the title, spelled exactly, in the upper half, every letter at least 25% below the top edge and 20% from the sides, with no splashes, drops or marks touching or above the letters. Faces and key objects at least 15% from every edge.
+```
 
-Read [paperkin-tools.md](references/paperkin-tools.md) for custom composition and revision routing; `plan_book_design` with `focus: "composition"` also returns it. Build several purposeful page families, not a centered heading and text column on every page. Let illustration, whitespace and text alternate according to the reader's task. Keep dense instructions readable and carry overflow onto additional pages. Avoid adding decoration that competes with the content.
+Ask for these margins as written: the model keeps about half of what it is asked for, and the cover is trimmed closer to its edge than a framed page. Never draw page numbers; Paperkin's pages are reordered and padded. Comics use a square 1:1 sheet of 4 pages (2 × 2), each with up to 3 panels, page gutters wider than the gaps between panels, nothing crossing a page gutter, and speech in all caps. A sheet with another grid (2 × 2 or 3 × 3 on a square image) also works: `create_picture_book` needs its `grid`; `create_photo_book` reads it from the gutters.
 
-Supply actual uploaded/generated image files to the tool's declared file parameters. Use stable image keys for custom plans. The renderer creates the real covers and pages; show that returned interactive preview rather than generating a second mockup or a web image carousel. Never use image-search or external stock pictures to portray the user’s saved cover or pages. If the widget cannot be displayed, link its actual saved preview URLs.
+Sheet pages print framed on a mat in the colour of their text band, which keeps every letter inside the printer's safe area, and their art is upscaled four times by AI for printing, so a sheet page prints at about 190–230 DPI. The separate cover prints at about 135–145 DPI on its own; a cover cut from a sheet prints soft, so make the cover its own image. Read every word of every sheet at full size before passing it, and compare the characters with sheet 1.
 
-## Revise without losing the book
+## Check the book before the user orders
 
-Translate feedback into specific changes: imagery, crop, type hierarchy, palette, page rhythm or selected pages. A request such as “make page 9 beautiful” authorizes that design revision. Choose a fitting direction, make the saved edit and return its actual preview; do not ask for permission again or stop with an image concept that was never inserted.
-
-For ANY saved book, call `get_book_design` with the requested `page_numbers` to read its actual page content, trim size and reusable image keys. Use `revise_book` with `page_edits` for one or several interior pages. `overlay` adds to the existing page; `replace` authors its complete layout. Both keep unrequested pages and covers intact. Preserve required words and functional writing space when replacing a page; native `writingArea` blocks provide dots or lines without rasterizing the writing grid. Reuse saved artwork by key, or add actual generated/uploaded files with new image keys for a local replacement. Do not regenerate unrelated approved art.
-
-For custom covers, stable-ID edits or a new page sequence, use `revise_custom_book`. For standard metadata or targeted chapter/recipe artwork, use `revise_book`. Read [paperkin-tools.md](references/paperkin-tools.md) for the schemas and routing. The original physical package remains fixed during revision; it constrains print dimensions and color capability, not the model’s creativity. A color/trim change requires a separate book with the retrieved content preserved.
-
-Iteration happens in this conversation. The preview is for seeing real results; do not direct users to “Refine in chat,” “Add or refine artwork” or “Make it yours” controls. Show the saved revision and briefly identify what changed. Distinguish a generated asset from a completed book edit honestly.
-
-## Judge what the user will receive
-
-Review both covers and the complete page sequence, including dense content, continuations, credits, intentional blank reverses and binding padding. Inspect actual placed artwork, not just the generation result. Check crop, image stretching, gutters, contrast, text overflow and effective resolution at the physical placement. A technically valid preview does not prove an attractive book or a physically inspected print.
-
-Give an honest critique and fix the largest visible weakness before declaring the design complete. If the host cannot inspect the whole preview, say what was inspected and invite specific page feedback instead of claiming all pages passed. Keep ordering separate: provide the website link when the user is ready; design tools do not charge cards or purchase printing.
+Read the reply after every create or revise call: it says how many page sheets were recognised and how many pages were cut. Look at the returned preview: every page whole, no cut letters, no white strips, characters matching from page to page, and the cover's title spelled exactly. Fix the largest visible problem by redrawing that page or sheet before calling the book done. Show the returned preview widget, never a mockup or an image carousel, and give the order link when the user is ready; no tool charges cards or places orders.