PO9 Skin Specification

Specification v1 · Stable. This is the authoritative definition of the .po9-skin format. If a file conforms to this spec, it is a valid PO9 skin.

Design goals

• Portable — one file, no external dependencies.
• Secure — data only; no code, no network. See Security.
• Versioned — explicit versions and a compatibility promise. See Versioning.

Contents

1. Manifest — the required entry point.
2. Metadata — name, author, description, license.
3. Folder Structure — the layout inside a skin.
4. Theme Tokens — the styling values.
5. Asset Rules — allowed files, types, and limits.
6. Packaging — how a folder becomes a .po9-skin.
7. Versioning — how the spec evolves.

Conformance

A skin conforms to v1 when it passes the Validator at spec version 1. The words MUST, SHOULD, and MAY are used as defined in RFC 2119.