Skip to main content
Frontic gives you two places to build against your project: Frontic Studio and the Experience Designer. Both are agent-driven, both run against your live data, and both draw on the same Context Base — they differ in what they produce and who they’re for.

Frontic Studio

Build an entire frontend. A real Git repository, a sandboxed workspace, a live preview, and GitHub built in. Studio ships code.

Experience Designer

Build a single page. A campaign landing page, a seasonal moment, a promo section — designed against your real storefront and published into it. No repository, no code surface.

​
Which one to use

The split is about the unit of work, not about skill level. Reach for Studio when the answer to “where does this live?” is “in the codebase” — a new template, a component library, a checkout change, a data-fetching fix. Reach for the Designer when the answer is “on this one page” — a Black Friday landing page, a brand collaboration, a category takeover that shouldn’t wait on a sprint.

​
What they share

Neither tool starts from zero. Both read the same project-level knowledge, so a decision you record once shows up in both.

Context Base

Skills, rules, commands, and guides. A rule like “no rounded corners on the brand” applies in Studio, in the Designer, and in your editor.

Initialize

The one-time reading of your shop that writes the first draft of that knowledge — styleguide, tone of voice, assortment, brand tokens.

Design Library

Your brand as tokens — colors, typography, corners, logos. One published brand, referenced by everything Frontic builds.

The backend

Blocks, listings, pages, and Menu Trees. Both surfaces read live product and category data through the same typed API.
Each surface also keeps its own system prompt and its own always-on project rules, so the two can diverge where they should — Studio’s rules can talk about repository layout and commit conventions, the Designer’s about campaign voice and what a hero must never do. See Studio Settings and Designer settings.

​
Where each one runs

Both live in the admin app:
  • Studio → Board for jobs and workspaces
  • Designer for experiences
The Designer is also reachable from outside Frontic. With the Shopware connector installed, an editor can create and open an experience straight from a Shopping Experience layout in the Shopware admin — see Frontic Experiences in Shopware.

Frontic Studio

Jobs, workspaces, plan mode, and shipping through GitHub.

Experience Designer

Experiences, the canvas, versions, and publishing.

Build in Your IDE

The third surface — your own editor, with the CLI and MCP server.

Your first feature

Walk through a complete Studio job end-to-end.