CREATOR ACCOUNT

Name it once.
Let Codex build it.

This is the same Create workflow used on the public page. You lock the public name and generated Registry id; Codex derives the visual system, artwork, listing copy, previews, validation, reversible local install, and restore evidence.

Name→Create + test→Publish session

Start Create I already have a finished pack →

CREATOR ACCOUNTLoading account…

1Name2Create with Codex

Name your theme.

This name is locked into the manifest and public page. The website generates the Registry id; Codex handles the visual system, artwork, public copy, validation, and reversible local QA.

Theme name · 2–80 characters

Registry idEnter a theme nameGenerated automatically from the theme name and locked before Codex creates the pack.

I will attach one local reference image to the Codex message. Codex should use it as inspiration, not automatically redistribute it.

External assetsOnly needed when the published pack includes third-party material

The final pack must include a third-party image, logo, icon, font, or other external asset.

I authorize Codex to install and select the generated local pack, run automated checks in a clean demo workspace, test restore, and reselect the candidate. This does not authorize quitting or restarting Codex.