Open source foundation

Open source Codex themes.
Inspect the pack.

The format, themes, validators, creator Skill, and local installation path are open for inspection and contribution. The hosted site is a free community Registry.

What is open

The compatibility layer belongs in daylight.

Advanced image themes depend on a local compatibility layer outside Codex's native color settings. Open implementation and restoration tools make that boundary visible.

01

Theme Pack Schema

A versioned manifest and documented tokens for palette, focal point, assets, compatibility, and licensing.

02

Validator and pack tools

Checks that themes are complete, safe to distribute, and clear about platform and delivery paths.

03

Local installers

macOS and Windows helpers designed around local state, explicit changes, and complete restoration.

04

Eight free themes

Original templates with redistributable assets, illustrative layout previews, compatibility notes, and attribution records.

05

Creator Skill

An optional Codex Skill for advanced creators who want to generate, inspect, and validate theme packs from source assets.

06

Compatibility tests

Regression checks for manifests, packages, installer safety, and the Codex versions the visual layer supports.

Repository map

Built for contribution.

Theme packs, the schema, CLI, creator Skill, and safety runtime stay public. The private website repository operates the reviewed community gallery, auth, likes, and upload queue.

get-codex-theme/
├── packages/       schema, CLI, preview, installer core
├── platforms/      macOS and Windows adapters
├── themes/free/    original redistributable themes
├── plugins/        Codex plugin and creator/manager Skills
├── docs/           spec, security, compatibility
└── tests/          validation and regression coverage

For theme creators

Use the Skill.

The optional create-codex-theme Skill helps turn artwork into a validated pack. It is not required to browse, download, or install a theme.

Explore the Skill →

For maintainers

Test the boundary.

Contributions should preserve signed application packages, bind visual services to loopback only, describe every local change, and include a complete restoration path.

Read contribution guidance →
PUBLISHER ACCESS

Sign in to
share your work.

Use an identity you already trust. We only use it to attribute submissions and review status.

No password or email registration. Your provider verifies your identity.