Prompt-driven theme packages and private marketplace

A theme can be a portable design system

Storefront work often starts with a strong visual brief, then turns into a long series of one-off edits. Stoify theme packages give that brief a durable, reviewable format: a versioned stoify.theme JSON file that contains the storefront configuration without products, orders, customers, or credentials.

The package includes global tokens, responsive layout values, typography, navigation, footer settings, reusable builder presets, and editable section content. That makes a client direction such as MOTORVELLUM a real starting point for a site rather than a locked visual skin.

Generate with a clear prompt contract

Give Codex the brand brief, audience, visual references, color and type direction, responsive requirements, media rules, and content structure. Ask for one valid JSON package and specify the desired handle and version. The complete contract lives in the repository’s docs/themes/theme-package-format.md file for teams building repeatable generation workflows.

Stoify validates the envelope, metadata, size, URLs, and required sections, then normalizes every payload through the same builder defaults used by existing sites. Missing optional details receive safe defaults rather than becoming hardcoded theme behavior.

Import locally, then preview and apply deliberately

Owners and Admins can import a package from Dashboard → Themes. The package is saved as a local preset first, so it can be reviewed and applied deliberately. Exporting produces the same canonical JSON format, which makes it practical to keep a package in version control or move it between sites.

Applying a package updates only storefront configuration: theme tokens, builder presets, navigation, footer, and page-builder sections. Existing local package presets remain available. Merchant data is outside the package boundary and is never modified.

Use the builder as the editor

An import is a starting point, not a locked theme. Open the package in the storefront builder to adjust the theme tokens, responsive values, section content, navigation, footer, and reusable presets. The editor is still the place for day-to-day changes, while the package is the portable source you can export again when the design is ready to hand off.

That separation makes the workflow useful for teams: keep a clean source package for a client or brand family, apply it to a site, then make site-specific edits without changing products, orders, or customer data. Export the updated configuration when those improvements should become the next reusable version.

Reusable ideas for a theme library

Theme packages work well as more than full-site skins. Teams can keep a small library of focused starting points, such as a high-conversion product card system, an editorial landing-page layout, a seasonal campaign header, a newsletter call-to-action, or a client-specific typography and color system. Each package can be previewed before it is applied, saved locally for one site, or published privately when it has been approved for reuse across sites.

Public HTTPS media is copied into the target site when possible. If a provider blocks a file or the media is unavailable, Stoify keeps the safe original URL and shows a warning instead of failing the theme application.

Publish approved versions privately

Super admins can turn an imported package into a marketplace draft, preview it through the normal builder, and publish it after approval. Published versions appear to authorized site Owners and Admins in the private marketplace and use the existing install/update flow. Handle collisions create a new version, so an existing published version is not overwritten.

For the launch story, read Building a storefront theme from a prompt.