Create and update V4 themes

V4 is the current protocol. New works use independently optional app artwork, launch screens, palettes, reader themes and fonts. Legacy V1/V2/V3 packages remain readable. Import saves a copy; application is explicit. Current manifest · Historical V1.

Shared module catalogue

V1, V2, V3 and V4 share the same groups, names and order. A protocol version expands supported modules; it does not define another catalogue. Rows remain visible with provided, author omitted or protocol unsupported status. Only provided modules can be selected.

Group	Module	Key	Minimum protocol
App appearance	App colors	palette	V1
App appearance	Interface icons	icons	V1
App appearance	Page background	pageBackground	V1
App appearance	Navigation decoration	navigation	V1
App appearance	Launch screen	launchScreen	V4
Reading appearance	Reading paper	readerPaper	V2
Reading appearance	Paragraph review decoration	paragraphReview	V2
Reading appearance	Loading animation	openingIndicator	V2
Reading appearance	Information bar styling	informationBars	V2
Reading appearance	Comment cards	commentCard	V3
Fonts	Fonts	fonts	V2

Comment cards style both chapter discussions (本章说) and god comments (神评论). Card background, border, radius, padding and badges belong here. Reading paper and paragraph review button decoration are separate modules; subset downloads never implicitly include each other. This styles existing comments and does not enable comment content. Information bar styling can adjust font, size, weight, color, opacity and density, plus bounded content presets; device placement and margins remain local, and application leaves it off by default. Fonts are one selectable module with ui/body/header/footer roles. skin, palette, reader and fonts are storage containers, not another public grouping.

The machine protocol publishes the same catalogue under moduleCatalog. Current catalogVersion: 3 adds the V4 launch-screen module. New packages use schemaVersion: 4, while the author's version increases independently.

Choose the requested modules

New works use schemaVersion: 4 and format: "origo.theme-suite". Export an existing appearance from the App or start with the V4 artwork template. components.skin contains app icons, artwork and launch-screen imagery; palette contains light/dark colors; reader contains reader appearance; fonts contains licensed fonts and role assignments. Include at least one module. Omitted modules preserve the recipient's choice. Portrait launch screens use skin.artwork.launchScreen; optional landscape artwork uses launchScreenLandscape. Both accept optional darkAsset and static PNG/WebP only, at most 2 MiB per file and 2048 pixels on the longest edge. Without landscape artwork the App contains and centers the portrait image. It exits as soon as home is ready with no forced dwell time.

Keep artwork coherent

Use the 80 semantic icon slots. Keep stroke, perspective, optical size and transparent margins consistent. Use transparent icon backgrounds. Prefer 128 or 192 pixel icons for large sets. Normal, selected and light/dark variants are optional. App backgrounds and reader paper have different roles. The App owns button geometry, spring feedback and glass/solid behavior.

Each palette appearance uses one seed or the full primary/secondary/tertiary set. Custom fonts require redistribution rights and packaged license text; system choices do not copy device font files.

Manifest, preview and packaging

Read the current manifest. Promotional images are optional packaged media.images; media.cover selects an image ID. Do not use the V1 root preview field. Distinguish real app captures from artwork mockups.

Place manifest.json at ZIP root, referenced resources under assets/, and optional README.md/LICENSE.txt at root. Remove unreferenced drafts and OS junk; keep this Skill outside the theme directory. Authors upload one complete ZIP. Recipients select modules and receive one standalone subset ZIP.

Updates and migration

Preserve the original ZIP and work on a separate copy. Verify ownership and the highest submitted version, including pending/rejected records, in the workbench. Retain ID, author, license and unchanged resource bytes; increase the work's version for a new submission. Ordinary content updates do not change schemaVersion. Label private facts unverified if they cannot be checked.

For V1 migration, move icons/artwork/iconScale into components.skin, map palette into V4 light/dark appearances and declare the former preview under media.images. Preserve resource bytes and attribution, then validate. Changing only the protocol number is invalid. Historical reference.

Validate locally

Download the current creator Skill, then run:

uv run --with pillow --with 'pydantic>=2,<3' python scripts/check_theme.py ./my-theme --output ./my-theme.zip

Default validation accepts valid partial suites. Use --complete only to audit all four storage containers, not every optional resource. Deliver the complete ZIP, module summary, validation and actual testing limits. Continue to publishing.