Local-first theme studio · Enhanced only

Build locally.Validate honestly.

Build and validate Enhanced themes locally for the independent Codex Dream Skin engine. Your selected files stay in this browser; Structural checks never become unsupported Runtime claims.

CODEXSKIN LOCAL STUDIO
CONCEPT PREVIEW · NOT RUNTIME EVIDENCE

Your image.
A reviewable package.

STRUCTUREPASS
RUNTIMENOT_VERIFIED

Browser concept preview — not an exact Codex rendering.

  • LOCALselected-file processing
  • EXACTstructural checks and hashes
  • 0published production themes
Delivery
Enhanced theme for the independent Codex Dream Skin local engine
Runtime pin
a1c48b3
Native delivery
Disabled
Production themes
0 published

Choose the task you need

Use the gallery when you want to review an approved theme record, Builder when you are creating a portable theme from your own image, and Validator when you already have files to inspect. Every path keeps structural results separate from platform runtime evidence. Start with the task, then read the status panels before you use an artifact with the independent local engine.

  • Browse approved theme records with source, rights, integrity, Structural status, and platform Runtime status.
  • Build supported fields from one local PNG, JPEG, or WebP image without sending the selected file to this website.
  • Validate a theme JSON, image pair, or supported package before following platform-specific local Engine steps.
LOCAL WORKFLOW · FOUR STOPS

From file to local use

Create or select files, run validation, review every warning and hash, then choose the macOS or Windows guide that matches your machine. Apply and Restore belong to the independent local Engine—not to this website.

01
Build
Prepare one theme JSON and its referenced image.
02
Validate
Validate the pair and resolve FAIL results before continuing.
03
Apply
Review source rights, redistribution status, and available SHA-256 values.
04
Restore
Use the platform guide and verify that stock Codex reopens without debug flags.
TWO INDEPENDENT SIGNALS

Read two statuses, not one

Structural status reports known format and file checks. Runtime status requires evidence for the exact platform, Codex build, Engine version, Runtime SHA, artifact hash, date, and recovery path.

Structural status
Known format and file checks.
PASS WARN FAIL CANNOT_VERIFY
Runtime status
Exact platform + build evidence.
VERIFIED_BY_US REFERENCE_ONLY NOT_VERIFIED REVERIFY_REQUIRED

PASS can coexist with NOT_VERIFIED. WARN requires review. FAIL blocks use. CANNOT_VERIFY means a required capability or input was unavailable.

Builder preview is an approximation

The browser preview helps check cropping, focus, contrast, and basic composition. It does not run Codex, the local Engine, or an exact Codex renderer. A good-looking preview cannot establish runtime behavior.

Open Builder
BUILDER PREVIEW
APPROXIMATION

Frame the image.
Inspect the fields.

Browser approximation — not exact Codex rendering

Validate before export

Validator surfaces PASS, WARN, FAIL, or CANNOT_VERIFY from structural checks. PASS means the known checks completed without a blocking structural result. WARN requires review. FAIL blocks a ready-to-use claim and identifies the field or file that needs correction. CANNOT_VERIFY means a required parser, browser capability, metadata value, hash operation, or counterpart file was unavailable.

Open Validator
Example structural report
JSON syntaxPASS
schemaVersionPASS
Image formatPASS
Runtime evidenceNOT_VERIFIED

Platform evidence is exact-build only

A SHA-256 value supports byte-for-byte integrity comparison; it is not a signature, certification, malware assessment, or runtime test. Theme records remain unpublished when source rights, redistribution permission, required artifacts, or formal evidence are incomplete. The site does not fill missing fields with assumptions.

macOS
NOT_VERIFIED
Formal exact-build evidence for the current Codex build and pinned Engine is pending.
macOS guide →
Windows
NOT_VERIFIED
Formal exact-build evidence for the current Codex build and pinned managed Engine is pending.
Windows guide →
PRODUCTION GALLERY

Evidence first. Publishing second.

No production theme is published until rights, artifacts, structural review, exact integrity values, QA, and release approval are complete. Internal candidates never appear as public inventory.

View the production gallery state →

Evidence before claims

A SHA-256 value supports byte-for-byte integrity comparison; it is not a signature, certification, malware assessment, or runtime test. Theme records remain unpublished when source rights, redistribution permission, required artifacts, or formal evidence are incomplete. The site does not fill missing fields with assumptions.

Read Safety boundaries →

Current product boundary

Enhanced themes require the independent Codex Dream Skin local engine. Native delivery, analytics, billing, accounts, cloud sync, and active Contact submission are outside the current True MVP. CodexSkin Tools is an independent project and is not affiliated with, endorsed by, or sponsored by OpenAI.

A practical review order

For a first visit, use the same review order on every artifact: identify the task, inspect the approved source and rights fields, run the structural checks, compare available integrity values, and then read the platform Runtime status. This sequence keeps creation, file inspection, permission to redistribute, and exact-build evidence from being mistaken for one another. Finish by opening the platform guide and reading Restore before any local Engine operation.

States

task_ready
Choose a task: browse, build, validate, or read installation steps.
runtime_default
Runtime status: NOT_VERIFIED until exact-build evidence is shown.
release_hold
Theme downloads remain unavailable until rights, artifact, evidence, QA, and release gates pass.

Errors

tool_unavailable
This browser task is unavailable. Keep your files local and try a supported browser; no result was produced.
evidence_missing
Required runtime or rights evidence is missing. Review the record without inferring compatibility or permission.

Frequently asked questions

Which CodexSkin tool should I start with?

Use Builder to create supported theme fields from your image, Validator to inspect existing files, the gallery to review approved records, and Install for the platform handoff after validation.

Does a PASS result mean a theme will run on my Codex build?

No. PASS covers known structural checks only. Runtime behavior needs evidence for the exact platform, build, Engine version, Runtime SHA, artifact hash, date, and recovery path.

Do selected Builder or Validator files leave my browser?

Under the current True MVP contract, selected images and theme JSON are processed in the browser and are not uploaded to CodexSkin Tools.

Start with the task you need

Browse approved records, build from a local image, or validate existing files. Every path keeps Structural and Runtime status separate.