Update to Inkroost: Comic & Manga Maker

{
  "description": "Plan, generate, review, finish, and optionally submit a chapter for any existing Inkroost comic, webtoon, or manga series. Use for requests such as a new chapter, next episode, another instalment, or revisions to a draft chapter.",
  "included_files": [],
  "name": "inkroost-create-chapter",
  "skill_md_contents": "---\nname: inkroost-create-chapter\ndescription: Plan, generate, review, finish, and optionally submit a chapter for any existing Inkroost comic, webtoon, or manga series. Use for requests such as a new chapter, next episode, another instalment, or revisions to a draft chapter.\n---\n\n# Create an Inkroost chapter\n\nAuthor a complete chapter through Inkroost's MCP tools while preserving the series' established story, format, cast, visual continuity, accessibility text, and publication boundaries.\n\nDiscover and call the MCP tools named below.\n\n## Ask only when the answer changes the work\n\nUse the client's structured question tool when available; otherwise ask concise questions in chat. Ask no more than three related questions at once.\n\nResolve missing decisions only when they materially affect story or spend and cannot be inferred safely after loading the series context, such as an ambiguous target series or a required character the request leaves unclear. A broad request such as \"make the next chapter\" delegates unspecified premise, length, cast, and dialogue choices: derive them from the established series, propose them in the beat sheet, and avoid conducting an interview. Ask about moderation only when the user's publication intent is unclear.\n\nUnderstand the request before spending on it. Check it against what matters most: who is in it, what happens, the tone (funny, scary, tender), the one thing that must be right (the key moment, joke or reveal), and any dialogue. When the user has not said what the chapter's most important moment is, ask that one question, offering two or three moments that fit the series so far, then build the beat sheet around it: set it up early, give it the biggest panel or its own page, and land it. For comedy, ask for the punchline when it is unsaid. One short message, at most three questions, never about what the user already said, never a second round; what they leave open is yours to decide. Skip the questions when they say \"just draw\" or \"you decide\", pasted a script, or on page 1 of a series with no drawn page. Before each generation call, say in one line what you are about to draw (\"Drawing: ...\" with who, what happens, the tone and the key moment) so the user can catch a misunderstanding before credits are spent.\n\nCredit-charged generation needs informed approval; for page 1 of a series with no drawn page yet, see *First page first*. Otherwise, before the first generation call, show the beat sheet, planned page count and variant count, call `estimate-generation-cost-tool`, and ask the user to approve the plan and estimated spend unless their request already explicitly approved that exact plan and spend. The estimate tool's `page_count` must be the total number of images requested (`story pages × variant_count`), not only the number of story pages. A client message such as \"approval not received\" is not a transient error: stop and ask the user rather than retrying around it.\n\n## Resolve the series and its rules\n\n1. Use `search-series-tool` or `list-series-tool` to resolve the user's series name. Never guess an ID; if several series match, show the matches and ask which one.\n2. Call `get-story-state-tool`, `get-consistency-context-tool`, `get-chapters-tool`, `get-locations-tool`, and `get-props-tool` for the resolved series.\n3. Determine the next unused chapter number, avoid title or premise repetition, and preserve reading direction, reading mode, maturity, established voices, style constraints, and any no-text rule.\n4. Fix incomplete context before generation; on a series with no drawn page yet, only the look comes before page 1 (see *First page first*). A series with no style profile is drawn in a default manga look nobody chose: ask the user which look they want (American comic, manga, webtoon, cartoon, European comic, or their own description) and write it with `set-series-style-profile-tool` first. Update weak character profiles and create missing location or prop sheets for recurring places/objects. Pass their IDs during generation and also use their names or aliases in scene text.\n5. Call `check-balance-tool`, `estimate-generation-cost-tool`, and `get-daily-limit-status-tool` before proposing a generation plan. Tell the user how many pages the balance draws (balance ÷ `cost_per_page`) and size the plan to it.\n\n## First page first\n\nWhen the series has no drawn page yet, usually a new creator's first chapter, do not open with a full beat sheet. The creator has not seen the look yet, and a new account's free credits cover a few pages, not a chapter.\n\n1. Write the premise and the beat for page 1 only. No character, location, or prop sheet is needed for it: describe the lead characters' looks in the scene text.\n2. Call `create-chapter-tool`.\n3. Offer to draw page 1 now for one image's worth of credits (`cost_per_page`); when they agree, draw it with `variant_count: 1`.\n4. Generate it and show it as soon as `get-art-status-tool` reports `review`. A page takes about 2 minutes. If your turn ends before it is ready, give the user the link from the generation reply and ask them to say \"show me\".\n5. Once they have seen page 1 and said whether the look is right, write the missing sheets from it (keep what it got right, fix what it got wrong) and plan the remaining pages as below. The first cover is drawn by itself, free, once page 1 exists: do not order it. Offer the banner now; an account's first is free.\n\nWhen a generation call is refused for credits, its reply says how many images the balance still draws and where credits come from. Pass that on plainly, offer to draw what the balance covers, and do not list packages or prices unless the user asks.\n\n## Plan before spending credits\n\nWrite a concise premise and page-by-page beat sheet. A normal chapter is 8–24 sequential pages, adjusted to the series and user request. It should establish one dramatic question early, escalate it through cause and effect, and pay it off or deliberately turn it on the final page.\n\nAn explicit user-requested panel count takes precedence: use exactly that count on the requested page, whether below or above the default range. Never silently reduce, increase or split it across pages. Apply the following defaults only when the user has not indicated a count. For ordinary paged manga, comics and manhwa, start from **3-6 panels** for a developing scene: establish, act, react, reveal and transition as needed. This is a starting range, not a quota. Use **1-2 panels deliberately** for a splash, a major reveal, a held emotional moment or the creator's requested sparse layout. An establishing shot can share a page with the action that follows. For vertical webtoons, compose for scroll rhythm, breathing space and screen-sized reveals rather than a print-page quota. Vary counts across the sequence.\n\nUse structured `panels` for multi-panel scenes. Free-text reliability warnings are a reason to use that structure, not to reduce panel count. Do not stretch a continuous exchange across sparse pages, collapse distinct actions into one image, or omit reactions and dialogue merely to save output tokens or avoid layout complexity. Respect the creator's pacing. If another constraint prevents the requested layout, explain it and ask how to resolve it rather than substitute a different count.\n\nAct as a comics art director. Plan layouts as well as panel counts, led by the series' look, varied by page: varying sizes, insets, borderless atmosphere, full-bleed reveals, diagonal borders where it uses them. Foreground characters or motion can deliberately cross panel borders while preserving readable order and keeping faces and lettering clear. For example, a lunging character can break a diagonal frame, a sword or hand can extend into a gutter, or a foreground prop can overlap a neighboring panel edge. Keep the intended overlap visible instead of clipping every element inside a box. State the intended layout in the page overview and panel descriptions; avoid repeating the same grid throughout the chapter.\n\nFor every page plan, identify:\n\n- the characters, location sheets, and prop sheets required;\n- the camera/framing and emotional beat;\n- continuity state carried from earlier pages;\n- speech bubbles or wordless (ask once if unsaid), and every exact line;\n- the alt text and transcript facts that must later match the final image.\n\n## Create and generate\n\n1. After plan/spend approval, call `create-chapter-tool` with the resolved `series_id`, next number, title, and a synopsis that includes the chapter's actual arc.\n2. Generate with `generate-pages-batch-tool` where practical. Use `variant_count: 1` unless the user knowingly approves the extra cost of alternatives. Keep batches manageable and preserve their job-ID-to-page order.\n3. Pass the `chapter_id` on every generation call. Pass the character, prop, and location IDs used by each beat.\n4. Prefer structured `panels`. For a text-free series, set `allow_text: false` and explicitly prohibit bubbles, signs, labels, packaging text, screens, and background writing. For text-enabled pages, include only essential dialogue and explicitly prohibit unplanned writing.\n5. Repeat critical continuity facts in each affected page, especially exact object counts, empty-state negative space, injuries, outfits, handedness, and the identity of recurring minor characters. Batch-level notes alone are not enough for premise-critical facts.\n\n## Inspect, correct, and approve\n\n1. Poll every job with `get-art-status-tool`. `processing` with no result URLs is normal; wait and poll again. Do not regenerate merely because one job finishes later than the others.\n2. When a job reaches `review`, inspect the returned image or call `get-page-image-tool`. Verify composition, character identity, continuity, object counts, panel order, anatomy, and every rendered word.\n3. If a page is wrong, refine only that beat and regenerate it. Repeated failure should lead to a simpler composition or a question to the user, not an unbounded retry loop.\n4. Never claim visual verification when the client could not display the image. Explain the limitation and ask whether to hold the chapter or approve unseen.\n5. Approve accepted jobs in ascending story order with `approve-pages-tool` or `batch-approve-pages-tool`. If approval order differs, call `reorder-pages-tool` with every current page ID exactly once.\n\n## Add the readable text layer\n\nAfter approval, call `set-page-text-tool` for every page, preferably in one bulk call:\n\n- `alt_text`: one or two plain sentences describing the visible setting, characters, action, and important composition;\n- `transcript`: the full reader-facing text version in the series' reading order, including scene description, visible characters, and exact dialogue.\n\nGround both fields in the inspected final image. Do not keyword-stuff, reuse one generic description, or describe elements the artwork does not show. This step is required even for silent chapters because it is the accessibility and discovery layer.\n\n## Verify and optionally submit\n\n1. Call `get-pages-tool` and check the complete sequence. Fix ordering if necessary.\n2. Call `confirm-page-order-tool` with `confirmed: true` only after actually verifying the narrative order. Any later insert, delete, reorder, or new approval requires reconfirmation.\n3. If the user asked to publish or submit, call exactly one of `publish-chapter-tool` or `submit-for-review-tool`; it goes live after a quick review. Otherwise offer it: readers see no page until the chapter is published, and creators rarely know. A creator who wants it private, say as a gift, can make a gift link on the series page in the studio instead.\n4. Report the chapter ID, page count, text-layer completeness, order confirmation, generation failures/retries, and moderation status. Do not wait indefinitely for moderation unless the user asked you to monitor it.\n\n## Revising a draft or rejected chapter\n\n- Start with `get-pages-tool`; IDs remain stable while page numbers may move.\n- Use `regenerate-page-tool` to replace one page in place when its beat remains valid.\n- For a structural rewrite, use `delete-page-tool`, generate replacement beats, then `reorder-pages-tool`.\n- Pages are locked while pending review or approved. If edits are unavailable, explain the state rather than attempting to bypass it.\n- Regeneration spends credits; obtain approval for additional spend that was not part of the accepted plan.\n\nThe detailed platform and tool reference is available at https://inkroost.com/llms-full.txt.\n"
}