Inkroost: Comic & Manga Maker

View saved version →

---
name: get-started
description: Welcome a creator who has just connected Inkroost and get the first page of their comic drawn in this conversation. Use when the user chooses to set up Inkroost or asks how to start.
---

# Get started with Inkroost

A creator decides to keep going when they see a drawn page, so the goal of this conversation is one page of their own story, drawn, in front of them. Keep questions few and short.

1. Call `list-series-tool`. If the creator already has a series, open it with `open-studio-tool`, offer to continue the chapter they worked on last (`open-chapter-panel-tool`) and stop here unless they want something new. A creator with no series yet never sees an empty studio: go straight on.
2. If their message already holds a story idea, use it. Otherwise offer three one-line story ideas, numbered, in one short message, and say they can pick a number or type their own. Invent anything else they leave open and say what you chose in one line.
3. Call `show-looks-tool` right away so they choose the look from pictures. In the same message, ask whether the characters should talk in speech bubbles or the pages should stay wordless; never decide it for them. Their look arrives as a message naming the `style_preset`.
4. Create the series with `create-series-tool`, then `set-series-style-profile-tool` with that `style_preset` and the subject and background drawn from their premise, then chapter 1 with `create-chapter-tool`.
5. Offer to draw page 1: it uses one page of their free credits and takes about 2 minutes. When they agree, draw it with `generate-pages-tool`, `variant_count: 1`, and their answer as `allow_text`: true with each line in `panels[].dialogue`, or false for wordless. The reply shows the page as soon as it is drawn, with a button to keep it.
6. Once they have seen it, offer the next page or a change to this one. Their language and email settings are on this plugin's settings page.
7. If they ask for an anime, a cartoon or an animated video, show `show-animation-examples-tool` first. An episode is made from a chapter with drawn pages; price it with `estimate-episode-tool` before anything is spent.

Never list prices or packages and never link a page that sells credits. If a generation is refused for credits, pass on what its reply says.

View saved version →

---
name: inkroost-create-chapter
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.
---

# Create an Inkroost chapter

Author a complete chapter through Inkroost's MCP tools while preserving the series' established story, format, cast, visual continuity, accessibility text, and publication boundaries.

Discover and call the MCP tools named below.

## Ask only when the answer changes the work

Use the client's structured question tool when available; otherwise ask concise questions in chat. Ask no more than three related questions at once.

Resolve 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.

Understand 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.

Credit-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.

## Resolve the series and its rules

1. 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.
2. Call `get-story-state-tool`, `get-consistency-context-tool`, `get-chapters-tool`, `get-locations-tool`, and `get-props-tool` for the resolved series.
3. 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.
4. 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.
5. 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.

## First page first

When 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.

1. 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.
2. Call `create-chapter-tool`.
3. 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`.
4. 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".
5. 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.

When 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.

## Plan before spending credits

Write 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.

An 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.

Use 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.

Act 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.

For every page plan, identify:

- the characters, location sheets, and prop sheets required;
- the camera/framing and emotional beat;
- continuity state carried from earlier pages;
- speech bubbles or wordless (ask once if unsaid), and every exact line;
- the alt text and transcript facts that must later match the final image.

## Create and generate

1. 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.
2. 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.
3. Pass the `chapter_id` on every generation call. Pass the character, prop, and location IDs used by each beat.
4. 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.
5. 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.

## Inspect, correct, and approve

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

## Add the readable text layer

After approval, call `set-page-text-tool` for every page, preferably in one bulk call:

- `alt_text`: one or two plain sentences describing the visible setting, characters, action, and important composition;
- `transcript`: the full reader-facing text version in the series' reading order, including scene description, visible characters, and exact dialogue.

Ground 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.

## Verify and optionally submit

1. Call `get-pages-tool` and check the complete sequence. Fix ordering if necessary.
2. 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.
3. 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.
4. 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.

## Revising a draft or rejected chapter

- Start with `get-pages-tool`; IDs remain stable while page numbers may move.
- Use `regenerate-page-tool` to replace one page in place when its beat remains valid.
- For a structural rewrite, use `delete-page-tool`, generate replacement beats, then `reorder-pages-tool`.
- Pages are locked while pending review or approved. If edits are unavailable, explain the state rather than attempting to bypass it.
- Regeneration spends credits; obtain approval for additional spend that was not part of the accepted plan.

The detailed platform and tool reference is available at https://inkroost.com/llms-full.txt.

View saved version →

---
name: inkroost-create-series
description: Create and prepare a new comic, webtoon, or manga series through the Inkroost MCP. Use when a user asks to start, set up, design, or create a new Inkroost series; do not use for adding a chapter to an existing series.
---

# Create an Inkroost series

Set up a private series through Inkroost's MCP tools and get its first page drawn early. A creator decides whether to keep going when they see a drawn page, so the order is page first: series, look, chapter 1, page 1, then the sheets, written from what page 1 shows.

Discover and call the MCP tools named below.

## Clarify only material gaps

Use the client's structured question tool when one is available; otherwise ask concise questions in chat. Group related questions and ask no more than three at a time.

Before creating records, establish these decisions when the user has not already supplied or delegated them. Infer the rest and say in one line what you inferred; questions should not stand between the user and page 1.

- working title and one-paragraph premise;
- comic format: paged comic/manga or vertical webtoon, plus LTR or RTL panel order;
- intended audience and deliberate maturity rating (`all_ages`, `teen`, or `mature`);
- how the pages will be made (`content_origin`): `ai_assisted` (AI draws every image), `human` (no AI on any page) or `mixed` (some pages by the user, some by AI; prompting or editing AI images counts as AI-drawn);
- the look of the art (see "Choose the look with the user" below);
- tone, genre, colour treatment, and major constraints;
- the lead characters and what they look like, in a line each (their full sheets come after page 1).

Do not make the user choose details they explicitly asked you to invent. If several materially different directions remain plausible, offer two or three short options.

## Choose the look with the user

Never assume manga. Most first-time creators do not know what a generated page can look like, so before the style profile is written, ask which look they want, offering these families in one question with the invitation to describe their own:

- **American comic**: bold brush inking, flat colour, heavy blacks and big lettering. Presets: Superhero, Noir, Golden Age, Graphic novel, Kirbyism.
- **Manga**: black and white ink, screentone, expressive faces. Presets: Manga B&W, Shonen, Shojo, Seinen, Chibi.
- **Webtoon**: clean digital colour made for scrolling. Presets: Webtoon, Anime colour.
- **Cartoon**: simple shapes, thick outlines, big expressions. Presets: Cartoon, Storybook.
- **European comic**: uniform clean lines or painted colour, detailed backgrounds. Presets: Ligne claire, Belgian humour, Painted album.

A look the user names in their own words is just as valid as a preset: keep their wording where it is concrete and never replace it with a preset. When the user leaves the choice to you, pick the family that fits the premise and say which in one line; a Western premise usually wants an American comic or European look.

Ask in the same message whether characters talk in speech bubbles or pages stay wordless; never decide it for them.

## Workflow

1. Call `search-series-tool` with the proposed title to detect a likely duplicate. If a close match exists, show it and ask whether to continue with a distinct new series.
2. Read the live `create-series-tool` schema before calling it. Its `genre_ids` description contains the valid genre catalogue; never guess a genre ID.
3. Call `create-series-tool` with a strong synopsis, deliberate maturity rating, reading direction, and reading mode. Set `content_origin` as established above: it is the origin badge readers see and defaults to `ai_assisted`. Keep the returned `series_id`.
4. Immediately call `set-series-style-profile-tool`, built on the look chosen above:
   - `subject`: the series-wide human/creature rendering baseline;
   - `photography`: for a chosen preset, pass its id as `style_preset` and leave this group out (Inkroost writes it); otherwise the user's own words for medium, linework, shading, framing and composition;
   - `background`: recurring environment language, atmosphere, lighting, and time-of-day defaults;
   - `constraints`: with a preset the palette comes from it; otherwise palette, logo/text restrictions, and other hard rules.
5. Call `create-chapter-tool` for chapter 1 and keep its `chapter_id`.
6. Page 1. Offer to draw it now: one image's worth of credits (`cost_per_page`), well within a new account's free credits. When they agree, draw it with `variant_count: 1` and their `allow_text` (lines in `panels[].dialogue`). Describe the lead characters' looks in the scene text; no sheet is needed yet. Say in one line what page 1 will show ("Drawing: ..."), and ask nothing more about it. Generate it with `generate-pages-tool` and show it as soon as `get-art-status-tool` reports `review`. A page takes about 2 minutes; if your turn ends first, give the user the link from the generation reply and ask them to say "show me".
7. Once the user has seen page 1, write the sheets from it, keeping what it got right and fixing what it got wrong:
   - every named character: `create-character-tool`, then `set-character-style-profile-tool`, with reproducible traits rather than adjectives: build, age range, hair length/colour/parting, eye shape/colour, distinguishing marks, default outfit, posture, and expression range;
   - each recurring place whose geometry matters: `create-location-tool` with aliases used in story beats, concrete measurements/counts/relative positions, materials, and continuity rules;
   - each recurring object with a describable shape: `create-prop-tool` with aliases, concrete appearance notes, continuity rules, and either a supported `looks_like` key or a brand-free `real_world_model_anchor`. One-off objects do not need sheets.
   If the user declined page 1, write the same sheets from the premise.
8. Call `get-consistency-context-tool`. Fix incomplete profiles or sheets before planning the rest of the chapter.
9. After page 1 the account's first cover is drawn by itself, free, in page 1's look: do not call `generate-cover-tool` for it. Offer the banner after page 1; the first banner (`generate-banner-tool`) is free.
10. Return a concise summary: series, chapter, character, location and prop IDs, page 1 status, format, maturity rating, and any deferred work.

## Boundaries

- Creating the requested private series, its look, and chapter 1 is within a clear request to create a series. Credit-charged art needs the user's yes, page 1 included: offer one image first, never a whole chapter they have not seen.
- Do not accept the content policy or choose a maturity rating on the user's behalf when the user has not delegated that creative decision.
- Do not submit or publish the series as part of setup unless the user explicitly asks. Publication begins a moderation workflow and can make approved work public.
- When the user wants the rest of the first chapter, continue with the `inkroost-create-chapter` workflow rather than improvising a shorter path.

The detailed platform and tool reference is available at https://inkroost.com/llms-full.txt.