Skip to content

lanseqingling/lantern / skills/create-with-lantern

create-with-lantern

Verified

Use Lantern's application MCP to create, draw, compose, revise, organize, inspect, or review a creator's comics through the domain capabilities Lantern currently exposes. Use for comic work in Lantern; do not use for developing the Lantern source repository.

references/pages.md

View on GitHub
# Page structure and page-manga operations

Load this reference when the creator wants to create, name, duplicate, order, delete, merge, or split pages.

## Read page identity correctly

`lantern_context_get` returns two complementary page views:

- `pageSequence` is the lightweight Chapter reading sequence. It lists every PresentationUnit by reading position, role, kind, optional name, and physical page numbers without exposing content handles for the whole Chapter.
- `pages` contains at most the requested two PresentationUnits with revision-bound page and PageSurface handles.

Use `physicalPageNumber` when the creator identifies a printed story page. Use `position` only for an explicit PresentationUnit position in the Chapter reading sequence, and use `name` for an accurate custom name or unambiguous role alias. A true spread has one reading position and two physical page numbers. A cover has one reading position and no physical story-page number.

## Distinguish the three page roles

- `story` is a normal story page and can contain comic Frames and dialogue.
- `cover` is unique within a Chapter, always remains first, has one surface, and does not consume a physical story-page number.
- `interlude` is a transition or special paper page. It participates in reading order and physical numbering like story pages, but only another adjacent interlude can merge with it.

Page roles are fixed at creation. Cover and interlude pages support paper-level images and narration but do not accept new comic Frames or dialogue. Lantern enforces cover uniqueness, fixed order, supported paper content, and valid page numbering; do not simulate those rules with extra moves or raw document edits.

## Distinguish display pairs from true spreads

Two ordinary pages shown together by a reader or workbench remain separate PresentationUnits. Do not merge them merely because they are visually paired.

A true spread is one `spread` PresentationUnit with exactly two PageSurfaces. `surfaceReadingOrder` follows the Chapter reading direction: left then right for LTR, right then left for RTL. Use the returned `page_surface` handles to identify a physical side in later surface-aware operations; do not reconstruct a surface ID.

Only adjacent ordinary pages with the same `story` or `interlude` role can become a true spread. Splitting is rejected when a frame or paper object crosses the gutter and cannot be preserved on one surface.

## Apply the narrow page action

- Create a story or interlude relative to one current page handle with `side: before | after`. A cover still uses one current page handle to bind ownership and revision, but Lantern fixes its position.
- Create a new true story spread relative to one current page handle with `side: before | after`. Use this direct operation when the creator wants a new cross-page composition; after it succeeds, refresh context and compose the returned true spread. Do not create two ordinary pages and merge them as a substitute.
- Rename one page without changing its role or order. An empty name restores the derived label.
- Duplicate one non-cover PresentationUnit. A true spread is duplicated as one complete unit.
- Move a page with two handles: the page to move first, the reference page second, plus `side`.
- Merge two existing adjacent pages using their two handles only when the creator wants to preserve those pages as one true spread; their input order does not replace the Chapter reading order.
- Split one true-spread handle.
- Delete only after the creator confirms the exact page. Pass the same handle in `targetHandles` and `confirmedTargetHandles`.

Every page mutation is revision-bound, idempotent, and atomic inside the AgentDraft. After the first success, continue from that draft and read fresh context before locating another page. Reuse the same idempotency key only for an exact retry of the same logical action. The finished task becomes one ChangeProposal for the creator to review.

Page-manga capabilities do not authorize rolling-segment creation, device viewport management, scroll grouping, or cross-segment composition.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall