Skip to content

FAQ

Both — but the standard comes first. PO9 defines the .po9-skin format; the app is one way to use it. Anything can implement the standard.

A single, portable JSON document describing an AI workspace skin: a manifest, a --dream-* color palette, and one embedded hero image. Not a zip, not a folder. See the Specification.

Yes — that’s a first-class path. Because a skin is plain JSON with a token-only palette, you can point an AI at the Specification and have it produce a complete .po9-skin. Always validate the result; the importer enforces every rule.

Is it safe to import a skin from someone else?

Section titled “Is it safe to import a skin from someone else?”

Yes. Skins carry no code and no network access, and the Validator re-checks every file on import. See Security.

Not in v1. There is no marketplace, no paid skins, and no commissioning built in — PO9 is the standard and the tooling. A Gallery for featuring community work is planned for Phase 2.

No. The spec is versioned with a compatibility promise. Breaking changes only happen on a new format version and always ship a migrator.

The PO9 app is the reference implementation and trust boundary. The format is open — any tool may produce a valid .po9-skin from the spec alone.