By Good Omens

OmensUI

Codestar's old magic, rebuilt for React and WordPress.

OmensUI turns Codestar and Saltus-style configuration into a typed React form engine for modern WordPress admin screens. Keep the migration path. Lose the legacy UI debt.

Join the Waitlist See the Migration Path
Explore
I. The Migration

Codestar config, carried forward

Keep the shape of the WordPress admin screens your plugins already know. Render them through a modern React engine.

schema.001
Codestar Options Schema
v2.1.0
Parity Gate Progress 104 / 259
43
Fields
259
Cases
WP
Native

Not a redesign mandate.
A migration path.

OmensUI reads Codestar and Saltus-style configuration, normalizes it into a typed schema, and renders familiar WordPress admin forms through React.

Compatibility mode preserves Codestar semantics and density while the native Omens mode gives new projects room for cleaner component architecture.

43
Codestar Field Families
259
Parity Variations
5
Core Packages
WP
Storage Adapters
II. The Parity

The signs that
migration can hold

OmensUI is built around evidence, not vibes: real Codestar config, live reference captures, and scenario-checked React output.

Codestar Compat

Field-level compatibility mode preserves Codestar row layout, native controls, dependency behavior, and stored value shapes.

01 / Compatibility

Field Coverage

Primitive, composite, layout, media, editor, and selector fields are tracked against the 259 captured Codestar variations.

02 / Coverage

WordPress Native

Storage adapters target options, post/user/term/comment meta, theme mods, transients, and network settings.

03 / WordPress

Evidence Gated

Baseline, open, and interaction screenshots must pass readiness, state, mutation, and image checks before a variation is signed.

04 / Verification
III. The Architecture

The engine beneath the veil

A schema core, a renderer, field packages, and WordPress adapters working together behind the admin screen.

Schema Engine typed
Zod
Validation

"Normalize source config, resolve compatibility, validate values, and keep the form state legible."

Core
WordPress Adapter native
Options Storage
Settings screens can persist through WordPress options and network options.
Meta Storage
Post, user, term, and comment meta adapters keep admin data close to WP.
REST Selectors
Posts, pages, users, terms, menus, roles, and locations can load as field options.
Parity Progress ledger
Legacy Baseline History 26
Enforceable v2 Passes 12
Current Failures Under Review 19
40% Gate Target 104
Migration Script 
// Carry Codestar config into OmensUI
import { normalizeSaltusCodestarConfig } from '@omens-ui/saltus';
import { FormRenderer } from '@omens-ui/ui';

const schema = normalizeSaltusCodestarConfig(csfConfig, {
  compat: 'codestar'
});

const SettingsScreen = () => (
  <FormRenderer
    schema={schema}
    storage="wordpress-options"
  />
);

// Same admin intent. Modern render path.
IV. For Builders

Built for Codestar upgrades

The first audience is practical: plugin and theme developers carrying real WordPress admin surfaces forward.

"Codestar configs in. Typed OmensUI schemas out. Migration starts with the settings arrays you already maintain."

C
Config First
Codestar and Saltus Normalizers

"React fields out. Native text, switcher, checkbox, radio, Chosen-style select, and deeper field families as parity lands."

R
Renderer Layer
React 19 Form Engine

"WordPress storage wired. Options, meta, theme mods, transients, selectors, and REST-backed admin data stay in view."

A
WP Adapter
Admin Storage and REST Selectors
Early Access

Be first through
the migration gate.

Join the waitlist for progress updates, early migration notes, and preview access as Codestar parity lands.