From nothing to a live Shopify store.

Three steps that used to look like separate products. First the brand kit: name, palette, typography and voice, from a brief, uploaded assets or a Figma file read over OAuth. Then a real Shopify development store claimed from a pre-provisioned pool, with the custom app already installed, followed by 29 launch milestones, 13 of which run on their own via the launch-tick cron. Then generation and theme editing in the same conversation: pages, sections, product copy, Liquid files, inside the Custom App scope you granted.

Shopify has no public API that creates a merchant store for you. We claim a real Partner-side dev store from DevStorePool, run the playbook, and stop at ownership transfer: that invite is always human.

• Brand kitName, palette, typography and voice from a brief, uploaded assets or a Figma file. Tokens can export as W3C format.
• Turnkey Shopify storeAtomic claim from DevStorePool, with the Custom App already installed. Then launch-tick runs the automated milestones every fifteen minutes.
• GenerationPages, product copy and image variants from the brand inputs, inside the chat that already holds the kit.
• Theme editsLiquid and settings_data changes through the theme-editor skill, scoped to the Custom App, preview-first.

Figma is read-only via OAuth. We extract palette and type; we never write back into the Figma file.

1. 1

   Brand kit

   Seven-step wizard. Upload assets, describe the brand, or import paint and text styles from a Figma file you duplicated. Exports W3C design tokens as JSON.

   • Name
   • Palette
   • Typography
   • Voice
   • Figma styles, read only
   • Design tokens (JSON)
2. 2

   Turnkey store

   Creates the Store row, claims a DevStorePool entry atomically, and starts the launch playbook. The operator never pastes a token.

   • Development store from the pool
   • Custom App installed
   • Playbook started
   • No token to paste
3. 3

   Populate

   13 automated milestones: theme, products, collections, pages, menus, blog, accessibility, SEO meta, structured data, crawl surface, legal docs, pricing, webhooks. 16 human checkpoints stay human on purpose.

   • Theme
   • Products
   • Collections
   • Pages
   • Menus
   • Blog
   • Accessibility
   • SEO meta
   • Structured data
   • Crawl surface
   • Legal docs
   • Pricing
   • Webhooks
4. 4

   Generate and edit

   Ask @Atlas to generate pages, sections and product descriptions, or to read and write theme files. Every write is logged against the Custom App scope.

   • Pages
   • Sections
   • Product copy
   • Liquid theme files
   • Preview first

• A real Shopify development store, provisioned in advance and handed to you. Shopify has no API to create one on demand, so an empty pool puts you on the waitlist rather than failing halfway through.
• More than half the steps are yours to approve: payments, domain, legal, publishing. Those are the calls an owner signs, and the OS does not sign them for you.
• Ownership transfer ends with an invite you send from your Shopify Dev Dashboard. The platform detects the moment you accept it and carries on from there.
• Figma is read, not written. Styles come out into your brand kit; nothing is pushed back into your file.

• From nothing to a draft storeA founder with a brief and no Shopify login yet. Pool claim plus brand kit in one path.
• Agency kickoffBrand system first, then a disposable dev store the client can accept later.
• Refresh an existing brandRe-run generation and theme edits against a kit that already exists, without a second product.

When to use it

• Use it when. When you are starting a brand or a store from scratch and want the OS to carry the first weeks instead of a pile of apps and a freelance brief.
• Do not use it when. When the store already exists and you only need one page rewritten. Open the chat and ask. Launch is the on-ramp, not the daily editor.