Skip to content

Quick Start

Your first .po9-skin in five minutes. You’ll need the Creator Kit.

Terminal window
npx po9-skin new my-first-skin
cd my-first-skin

This gives you a valid skin folder with two files to edit: manifest.json (name, colors, attribution) and theme.css (the palette tokens).

A skin is a color palette, nothing more. Set the baseTheme colors in manifest.json, then tune the --dream-* tokens in theme.css:

:root.codedrobe-codex-skin {
color-scheme: dark;
--dream-ink: #e7e9ee; /* primary text */
--dream-page-bg: #0a0a0c; /* page background */
--dream-panel-bg: #16181d; /* sidebar surface */
--dream-send-bg: #6366f1; /* accent */
}

Only colors, gradients, and glyphs go here — never Codex selectors, so your skin can’t break when Codex updates its DOM. Omit any token to inherit the base default.

Let AI do it. Point any AI at the Specification and describe the vibe — “a dark Vader-red theme,” “warm Game Boy green” — and it can fill in the tokens for you. Then run validate below to check the result is safe and well-formed.

Terminal window
npx po9-skin validate .

Fix anything the Validator flags — it checks security, compatibility, structure, and version.

Terminal window
npx po9-skin pack . # → outputs/<id>-<version>.po9-skin

Open the PO9 app, import the .po9-skin file, and apply it.

That’s the full lifecycle: Create → Validate → Package → Import → Use. Next, browse the Templates or read the Specification.